Ian Romanick wrote: > Nathan Gray wrote: >> Ian Romanick wrote: >>> >>>So, the example is drawing a wire-frame cube and clearing the screen as >>>fast as it can on a single-buffered display? What do you think the odds >>>are on a fast video card that the video refresh logic will just happen >>>to be displaying something when it's not cleared? Pretty close to 0 I'd >>>say. The driver isn't broken. You only see it with indirect rendering >>>because the drawing / clearing is slower, so the cube is on the screen >>>for a larger amount of time. >> >> In that case shouldn't LIBGL_SYNC_REFRESH fix the problem? It doesn't. > > LIBGL_SYNC_REFRESH causes the GL to wait until the vertical retrace to > perform a glXSwapBuffers. That code segment has no glXSwapBuffers > (because it's single buffered). Put a 'glFinish(); sleep(1);' at the > end of the rendering function.
Ah, I see. Thanks for your patience. Cheers, -n8 -- >>>-- Nathaniel Gray -- Caltech Computer Science ------> >>>-- Mojave Project -- http://mojave.cs.caltech.edu --> ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
