Somehow I would prefer having FlipScreen() not changed how it currently works, because it should just flip the screen buffer like it name suggests. So a FlipScreenDelay( ms ) seems much more appropriate. Also you can write that function as a system script instead of hardcode it in the engine.
If that is the case I would agree on that solution. But -I think- the SetFrameRate was only affecting the MapEngine. I can't check it out currently...
So I'm curious, is TurboSphere's ultimate goal to be a drop-in replacement for the current 1.x engine? That's the vibe I'm getting, but I want to make sure.
It is mostly a drop in replacement for the 1.x engines, yes. At the same time, I've made a few minor changes that there had been talk of adding to the 1.x engine for ages (like using proper constructors for Sphere objects, for one).
Well, someone has seen Wreck-it Ralph.