This is an interesting thread because I have some problem with those fps_ functions. The problem is not about the movement, it is about the shooting rate of projectile.

I found I use a wrong approach to control the shooting rate, after reading the AUM56 again, I realize that I should use total_frames to control the shooting rate.

Quote:

---

Acknex stores the total number of frames that have passed since the game was started in a variable named "total_frames". If we limit the frame rate to 80 fps, just like I did with this demo, and the PC is fast enough, total_frames will be set to 80 after 1 second, to 160 after 2 seconds, and so on - get it?



Our "if ((total_frames % 80) == 1)" line of code can be translated to "if total_frames reaches 1, 81, 161, 241...". This means that the two lines of code that are placed inside the curly brackets are executed each and every second, provided that the computer is able to deliver at least 80 fps in our level.

---

So my problem is, if I don't set fps_max, the default fps_max is 240, assume my game run really fast at 240 fps in window mode, if ((total_frames % 60) == 1) then I will fire 4 times a second. But if I switch to full screen and my screen refresh rate is 60Hz, it will fire 1 bullet a second!

And in the manual, the total_frames also use to control animation.
In that case, if the (total_frames %60) not change, the shooting rate and model animation in 75Hz monitor is faster than 60Hz monitor.

Right now I just set the fps_max and fps_min to 60. Any good idea?