Timing goes weird when VFPS is not divisible by FPS

[OpenMindNL]

• Create a 15 frame animation at a speed of 15 FPS and set VFPS to 60.
  Result: The animation repeats nicely every second.

• Now set VFPS to 55.
  Result: The animation is running much faster than once per second while FPS says that it should still run one cycle per second.

This is a know bug in Homey's operating system (current and earlier) that will be worked on but has no priority... which is understandable.
https://github.com/athombv/homey/issues/1623

This might be a problem when you need timing-critical visual information... like when showing a pulse or cycle per second.

Until the bug has been fixed by the Athom wizards, you can overcome this problem by being sure that the number for VFPS is divisible by FPS.

Examples:
The 15 FPS animation from the start of this post runs relative accurate at 15, 30, 45 and 60 VFPS.
If your animation only has 14 frames, the timing would be correct at 14, 28, 42 and 56 VFPS
More FPS gives less choices for an accurate VFPS.
A 30 FPS animation would only be timed correct at 30 and 60 VFPS.