Descriptive Problem Summary:
As the title suggests, in the latest byond build there is an issue with the flick() function repeating the icon state animation until the atom that the flick is applied to has changed location (either through a Move() call or not).
This behaves identically to just setting the icon_state of an atom to whatever you're trying to flick.
ID:1856412
![]() May 21 2015, 10:41 pm
|
|||||||||||||
Resolved
| |||||||||||||
![]() May 22 2015, 9:43 am (Edited on May 22 2015, 12:46 pm)
|
|
Is this 507.1284? I fixed some bugs specifically with animation and flicks in that version.
|
I was wondering if this existed since I use flick() a bit (but never noticed an issue), so I tested it myself. I didn't experience a problem in either 507.1284 or 507.1285.
player |
I tested this on 507.1285 and I am experiencing the issue exclusively on the webclient.
|
Lummox JR resolved issue with message:
flick() did not end properly until the atom moved. |
Experiencing this in 508.1288 in the webclient still. I'm also experiencing abnormal world CPU when virtually nothing is going on. Confirmed both in a basic test project and can send if necessary.
Edit: DS has no problems. |
508.1288 isn't current. Multiple fixes to the webclient were done in subsequent versions. But that's probably moot with DSificaiton. The CPU usage you're seeing is definitely a result of the old webclient and the DSified version will be much better on that as well.
|