Throttling is to increase/decrease the activeness of parts of the system.

If for instance the user keeps the JME aplication open and then checks their email, then the JME ap should be throttled to give up some of its CPU space so the comp is still functional.

Likewise in full games there is a fair amount of game state going on as well as the jme graphics, if that game state is in a seperate thread and the JME ap is over say 70 fps ( matched to the screen hz reresh ), then the JME ap could be throttled to 70 fps.

Another use could be the GameState

Has anyone looked into this yet???, maybe something to think about with the multi threading

One thing that might be feasable for single-player games is when they are diactivated they simply stop updating (now of course when you reactivate you would not want to give the actual FPS between that last update and this one, but that can all be handled).

Would that handle what you're talking about?


Not sure if its possible, but could maybe slow down the swing/jme desktop updates if required

If the application is minimized the JMEDesktop would only update if you'd change it programmatically. So my suggestion would be to stop doing that, if that's the case.

However, the first two-part questions should be, how do you detect a minized application? Both how can jME do this, and how jME should tell it's users…

As for the first part I think it can be polled through org.lwjgl.openGL.Display.isActive().