On Saturday 21 February 2009 2:00:26 pm Jérôme Gardou wrote:
according to http://msdn.microsoft.com/en-us/library/dd374387(VS.85).aspx, wglMakeCurrent proceeds a flush before switching.
glXMakeCurrent also forces a flush: http://www.opengl.org/documentation/specs/man_pages/hardcopy/GL/html/glx/xma...
If it needs a wglFlush, it should call X11DRV_wglFlush (and only if there's a current context; you can't call gl* functions without one set). It can be an exceptionally costly call though, especially if it's going to be flushed again immediately after, so unless it's needed to fix some bug, I'd recommend not flushing explicitly.
Chris Robinson a écrit :
On Saturday 21 February 2009 2:00:26 pm Jérôme Gardou wrote:
according to http://msdn.microsoft.com/en-us/library/dd374387(VS.85).aspx, wglMakeCurrent proceeds a flush before switching.
glXMakeCurrent also forces a flush: http://www.opengl.org/documentation/specs/man_pages/hardcopy/GL/html/glx/xma...
If it needs a wglFlush, it should call X11DRV_wglFlush (and only if there's a current context; you can't call gl* functions without one set). It can be an exceptionally costly call though, especially if it's going to be flushed again immediately after, so unless it's needed to fix some bug, I'd recommend not flushing explicitly.
Good catch. I read this page before sending, searching for this piece of information, but for some reason I did not see it... It seems that I needed some sleep yesterday. Thanks.
-
Chris Robinson -
Jérôme Gardou