Matt is correct. If you have a Max FPS higher then the monitors refresh rate, then you are just wasting processing power. The engine would be drawing frames that are never drawn by the monitor.

hmmm what if you were to try:
fps_max = 60;
fps_min = 30;
fps_lock = on;

ok with this set i get a framerate of ~32 fps...hmm i will try other combinations and see which i can get to work better
although i am not in a blank box and there is more that one piece of code, this is helpful though, as you can test how well the game will play with all this working together

Well , since for my game I just finished I needed to use DX8 , I installed gamestudio on another folder , and only updated it to 6.22 , and remembered this topic , so I checked the fps while running the game and it stays solid at 59 on fps_max 60 , using fps_max 61 it stays at like 61 i think , this is how I remember gamestudio acting before the weird fps problems , so its definately something from 6.31 and up , as if i run the game on my 6.31 installation I have the messed up fps , where i have to set it to 64 so itll stay at aroudn 60 , but even then theres always that 3 to 4 frame drop every now and then I constantly get , and when I run it on the 6.22 installation it stays solid at 59 , no fluctuation at all , and this is the exact same game with the exact same code running , so definately something with the 6.31 update and above.

I confirm this too myself. In 6.22, it was very constant. In 6.31 and 6.4, this is happening a lot. In my 2D game, I watch the F11 debug panel slowly dropping toward 63 then suddenly changing to 66 within one frame then dropping back down to 63. From using a panel to display the value of this:

game_fps = pow(time, -1)*16;

then displaying the game fps value, I can see this value change from around the 64 area then, for one frame, changes to 128, then returns to normal and this change occurs 2 to 4 times a second and would explain the behavior I see in the F11 debug panel. Do you get this in the 6.22 update and does it start occurring since the 6.31 update?