Stereo sync (swapinterval)
Thant Tessman
thant at horus.esd.sgi.com
Fri Dec 7 06:46:03 AEST 1990
In article <mg.660259402 at godzilla>, mg@ (Mike Gigante) writes:
>
[...]
> On gsync, I don't understand Thant Tessman's comment -- surely a swapbuffer
> doesn't happen until a vertical retrace anyhow -- so the gsync is redundant
> right?
The act of swapbuffering itself only happens on the vertical retraces. The
old swapbuffer used to freeze the program thread until that happened. The
new swapbuffer actually allows the program to continue as long as it doesn't
draw into the same context. This allows swapbuffers to be ganged up. A
program that had three windows used to be limited to 3/60 of a second per
update cycle assuming a swapbuffers was called for all three windows. Now
the whole thing is only limited to 1/60 of a second if I understand it
correctly.
A call to 'gsync' would force the program to wait. It isn't clear that
this was the source of the original problem. But I thought I'd mention
it.
> Mike
> mg at godzilla.cgl.rmit.oz.au
thant
More information about the Comp.sys.sgi
mailing list