A lot of maps have this problem even maps like 63 to 66 and 164 vanilla But why? Is it game sync, or other issues?

---

LAIBA DO NOT TALK HEREEEE

This bug has been around forever. As far as I can tell from some experimenting in the map editor, it might be related to the total amount of rotation applied to the object - when it rotates faster, it stops earlier.

Here is an example map code:

<C><P /><Z><S><S T="0" X="402" H="33" Y="387" P="0,0,0.3,0.2,0,0,0,0" L="800" /></S><D><T Y="370" X="26" /><F Y="365" X="776" /><DS Y="355" X="32" /></D><O><O Y="214" C="4" X="412" P="0" /><O Y="214" C="13" X="413" P="0" Mv="200" Mp="Infinity" /></O></Z></C>

The "Mv" attribute in the last object tag is the motor's rotation speed. When setting it to 200, the visible rotation stops after about 3 seconds; with a value of 20, it runs for ~28 seconds. (Spawning an object in the plank's path shows that it's actually still rotating afterwards. Also, when the plank and motor are not exactly centered on top of each other - in the sample code, the x value is 1 pixel off - you can see the plank still moving/bouncing around after it stops rotating properly.)

Maybe someone who is familiar with the game's code can explain why this happens, and why only the visuals are wrong, while the object's actual position seems to get updated correctly?

Thanks for the explanation. But it isn't known.
And I know the Mv="" XML.

This behaviour happens due to the rotation not using a modulo to be clipped to a range of 0° to 359°. Instead the value keeps increasing with each revolution until it reaches a limiting value, 32767 I believe, at which point it overflows, causing the dynamic object/nail to no longer visually update.

Syrius a dit :

This behaviour happens due to the rotation not using a modulo to be clipped to a range of 0° to 359°. Instead the value keeps increasing with each revolution until it reaches a limiting value, 32767 I believe, at which point it overflows, causing the dynamic object/nail to no longer visually update.

Oh..

Syrius a dit :

This behaviour happens due to the rotation not using a modulo to be clipped to a range of 0° to 359°. Instead the value keeps increasing with each revolution until it reaches a limiting value, 32767 I believe, at which point it overflows, causing the dynamic object/nail to no longer visually update.

Thank you!