hybr wrote: > Hi, Gianni Ambrosio > It can be the case that in old drivers vsync were disabled, and in new ones > its enabled by default. >
OK, it seems I got the point but I have some questions. Basically the monitor refresh rate is 60Hz but the timer to update the widget was 10 milliseconds (just like in the OSG example!). That means I was forcing a refresh of 100HZ, useless since my monitor is set to 60Hz. So I set the update timer to 17 milliseconds (~60Hz) and it works fine. Looking around the forum I realized, as suggested, that the problem is related to vsync. But if I understand correctly when vsync is enabled it should work without extra CPU usage even if the timer is set to 100Hz on a monitor with 60HZ. Is that correct? Moreover getSyncToVBlank() returns true so I guess the vsync is enabled. If that's correct I don't understand why sometimes the app gets a full cpu (without moving anything). Now a question about setSyncToVBlank(). If I call it I get a "not implemented" message. That's because GraphicsWindowQt inherits from GraphicsWindow. But why GraphicsWindowQt derives from GraphicsWindow? Both GraphicsWindowWin32 and GraphicsWindowX11 implements setSyncToVBlank(). Is there a way to have a GraphicsWindowQt and setSyncToVBlank() implemented? One more question about get/setSyncToVBlank(). If I get 'true' from the getter, does that mean the vsync is enabled in the gfx card driver or just an option of OSG? Thanks Gianni ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=39536#39536 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
