Stereo sync (swapinterval)

Brian McClendon bam at sgi.com
Fri Dec 7 07:45:58 AEST 1990


In article <1990Dec6.194603.7016 at odin.corp.sgi.com> thant at horus.esd.sgi.com (Thant Tessman) writes:
>
>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.
>
>
>thant


On the VGX, 'gsync' acts just like swapbuffers(), only hanging the program
when it tries to access gfx in the same window.  This seems to do everything
we could imagine gsync used for, but is slightly different from what
might be expected.   Any comments on how you _want_ it to work?

--
----------------------------------------------------------------------------
 Brian McClendon bam at rudedog.SGI.COM ...!uunet!sgi!rudedog!bam 415-335-1110
** Legalize drugs! **                                            ** RU486 **
----------------------------------------------------------------------------



More information about the Comp.sys.sgi mailing list