ID:2713798
 
Not a bug
BYOND Version:514
Operating System:Windows 10 Enterprise 64-bit
Web Browser:Chrome 92.0.4515.159
Applies to:Dream Seeker
Status: Not a bug

This is not a bug. It may be an incorrect use of syntax or a limitation in the software. For further discussion on the matter, please consult the BYOND forums.
Descriptive Problem Summary:
Some animations do not work properly in builds after 514.1561. In the given test case the animation is slow in 514.1562, and in builds 514.1563-514.1566 does not work at all

Numbered Steps to Reproduce Problem:
Use the verb in the test case and observe the player mob

Code Snippet (if applicable) to Reproduce Problem:
FULL TEST CASE DOWNLOAD: https://www.dropbox.com/s/2uknbjkfplj63ye/ testcase_20210904.zip?dl=0
mob
player
icon = 'icons/player.dmi'

verb
do_animate()
var/matrix/M1 = matrix()
var/matrix/M2 = matrix()
M2.Scale(1.2,0.8)

animate(src, transform = M2, time = 10)
animate(src, transform = M1, time = 5)


Expected Results:
The provided test case is meant to do a squish animation and works properly in 514.1561

Actual Results:
In 514.1562 the animation is slow, in builds 514.1563-514.1566 the animation does not work at all

514.1561 example (normal): https://streamable.com/jkgisz
514.1562 example (broken - slow): https://streamable.com/fskzjq
514.1566 example (broken - does nothing): https://streamable.com/k21j5s

Does the problem occur:
Every time? Or how often?Every time
In other games?Yes
In other user accounts?Yes
On other computers?Yes

When does the problem NOT occur?
In build 514.1561

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
This issue does not occur in build 514.1561 or below. The bug was introduce in 514.1562

Workarounds:
Downgrade to 514.1561 (In my experience this is not an option if the server is running 514.1566 due to a separate crash issue)
Lummox JR resolved issue (Not a bug)
The behavior in 514.1561 through 1565 is incorrect. Doing nothing is the correct behavior, so 514.1566 is doing the right thing.

If you want the animation to actually play out as two steps, you need to remove the src argument from the second animate() call. Otherwise, this is interpreted as starting a new animation sequence. The old sequence doesn't even have a chance to get started before the new one takes over.