Every 0:05 is not every 0:05

[Jarzka]

Check this:
www.voimalaitos.org/temp/every05.mfa

The counter value does not increase as fast as it should be. I used many different FPS values and noticed that the speed depends on that. Why? I think "Every 0:05" should work like that no matter what the FPS is.

[MechatheSlag]

Because you're not using timer based which was introduced in the newest versions. You need to know your definitions on FPS, which actually means frames pro second. Now if there's more or less frames pro second, the program has no knowledge on whenever it is running too fast or too slow compared to the actual time. So if you had 1 fps then YES every 0:05 wouldn't be 0:05 but more like a second. The obvious solution to this is to use the timer based option which calculates everything independant on framerate but rather on some kind of magical time feature I have yet to discover.

[Jarzka]

Timer based movements is turned on?

[Jaffob]

In case you haven't noticed, MechaBowser, it's called timer-based movements, not timer-based timers.

[Jarzka]

Well, any idea how to fix this? Timer should not depend on FPS...

[MechatheSlag]

In case you haven't noticed, MechaBowser, it's called timer-based movements, not timer-based timers.

My bad, I haven't actually looked into the timer based features as of yet, because it haven't had any signifient meaning to me.

[Jarzka]

I think my game won't work very well if "every 0:05" is not the same if I play the game on the computer which runs the game with 20fps or something...

EDIT: I updated the example file and noticed that if I use

every 0:10 -> + 10
instead of
every 0:05 -> + 5

it works perfectly if fps is more than 10. And if it is lower than 10 then you don't really want to play the game anyway

[James]

Just speculating here, but I guess if the timer is faster than an Always event with the selected FPS, there's no way MMF2 can keep up with it accurately, as MMF2 only processes data as fast as the selected FPS.