Hi Robert,
We could possible provide an env var to provide a hint to
DisplaySettings for what the defaults should be.
Yes, that would be nice.
As a related point, in Vortex we have a frame lock which will sleep a
given number of milliseconds at the end of the post-update phase before
starting the next frame. The amount of time it sleeps is dictated by a
given frame rate, i.e. if the time taken by the pre-update, update,
post-update phases was less than say 1/60th of a second then it sleeps
for the remaining time. This can be disabled at any time, and the
physics work whether it's on or not, it's just to give a consistent user
experience whether vsync is on or off. From what you've said you want to
do something similar.
So then, we'd have three frame-rate control mechanisms: vsync, OSG's
mechanism and Vortex's mechanism. So you see why I'd want a way to
disable the one in OSG easily (since we have more control over the one
in Vortex to make sure it does exactly what we want).
Also, I've always been suspicious of this kind of scheme when related to
vsync. What if both vsync and the frame-rate control scheme in OSG are
turned on, but the frames finish rendering in between vsync cycles.
Won't that introduce tearing? We'd have to synchronize the end of OSG
frame rendering with the vsync so that the swap occurs at the right
time, wouldn't we? (this is a question I have about our own scheme too,
I haven't had the chance to look into how it's done that much)
Anyways, just curious.
J-S
--
______________________________________________________
Jean-Sebastien Guay [email protected]
http://www.cm-labs.com/
http://whitestar02.webhop.org/
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
