On Nov 16, 2007 5:31 PM, Paul Martz <[EMAIL PROTECTED]> wrote: > In a dedicated flight sim, I tend to agree with you. Go ahead and let it > continuously redraw the scene, even if it is static -- the processor isn't > used for anything else anyway. But for any type of desktop/PC rendering > application, users expect the CPU to be free for other tasks when they pause > or stop the animation.
As long as vsync is on, as it should almost should be then the CPU load shouldn't be overwhelming with a standard frame loop. > In my experience, dedicated rendering loops have actually generated end-user > bug reports, claiming the CPU was occupied even when they had stopped the > animation. After I modified the app to only render when needed, never once > did I receive a single bug report along the lines of "this wrecked my > suspension of disbelief". Desktop users might not worry about an occassional dropped frame, proper sims though, if you don't hit a solid 60Hz (or whatever vsync is) then you will find users feeling nauseous or suffering from undue fatigue, but they won't neccessarily know why - one of the reasons for this is inconsistent/juttery framerate. The more immersive the simulator the more critical this issue is. Robert. _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
