Quote:
fps_max works fine at 1200
I just have to point out, from the scripting side, that having such a high frame rate can cause nasty bugs in C-Script if you use time_step. If the frame rate goes too high, time_step will reduce down to zero. You can probably guess what happens next...
my.x += force_x * time_step; // nothing moves when time_step = 0
foo = bar/time_step; // divide by zero error!
| 
