Henri Beauchamp wrote: I don't intend to implement frame limiting in the Cool VL Viewer !
And yes, I'm proud that it can do 300+ FPS (it means that I optimized the main loop very well), and yes this is actually useful (because a frame is not just about displaying an updated 3D view: it's also about dealing with sim to viewer and viewer to sim messages, taking into account the user's interaction (mouse, keyboard), updating the UI, rezzing objects, decoding textures, computing various things, etc, etc... At lower frame rates, the viewer simply becomes overall more sluggish. And yes, I don't really care about power consumption (my own systems are overclocked and locked in "turbo"/"performance" modes always); if I wanted low power systems, I won't buy high performance ones in the first place...
If you really want to slow down the viewer, you still can enable the "sync to VBlank" feature of your driver, meaning the viewer will get artificially slowed down to 60 FPS (or whatever rate corresponding to the vertical refresh frequency of your monitor) for its peak rates. I still don't recommend doing it.
In an ideal world, the 3D rendering loop of the viewer would be done in a separate thread, that could then be limited to produce lower frame rates while not slowing down the rest of the operations of the viewer (that would still be executed by the main thread). Achieving this result would however involve a huge overhaul of the code, and it's unlikely that it will ever happen. |