I cant understand this timescale and pixel dislocation problem.

So, theres this cube moving linearly across the screen using a timeline, and it dislocates about 10 pixels in the X axis, and about 3.5 pixels in the Y axis.

Consider these values represent timescale = 1.

So, to my surprise, when I set timescale to 0.5, it actually makes the dislocation in both axes to be a quarter, and not half.

I know my brain is probably not mathing right, but can someone explain to me why? Im very confused.

For anyone interested in seeing the example running:

drive.google.com/file/d/1kKKSs1NWihDnfvbXudm2XPHklDcwFRBG/view

Thank you in advance

I think this is actually a bug in timeline playback. The timeline has keyframes every 1 second. If you add another action like "Every 1 second, rotate sprite", then it rotates on the keyframes at normal speed, but at a timescale of 0.5 it rotates twice for every keyframe. So the timeline really is playing at one-quarter speed at a timescale of 0.5 which is incorrect. DiegoM

Just took a look and the system timescale is applied to the main delta time of the runtime to calculate the playback speed of a timeline.

The problem with that is the the runtime delta time already has the time scale applied to it by the time it is used by a timeline, so it's using a value that is multiplied twice by the current timescale.

Will the next beta drop with this fix? My current project is essentially a bowl full of timelines and timescales.

Since this was a very simple fix, it will go out in the next beta.