It worked fine …
Now I use Win2000 with the latest G400 drivers, and something strange happens…
The doublebuffering is broken, that is one frame is the FIRST frame ever rendered and the other frame is the actual frame… Very psychedelic!
Here is what I discovered; when running on a Matrox card, you can get rid of the psychedlic spazziness by calling wglMakeCurrent() with your current render & device contexts prior to your call to SwapBuffers(). In my game I wrapped the call to SwapBuffers(), and so on Matrox hardware I use a special swapping function that calls wglMakeCurrent() before the call to SwapBuffers() - since calling wglMakeCurrent() prior to SwapBuffers() broke on other cards. ::sigh::
Originally posted by DJ Tricky S: I use a special swapping function that calls wglMakeCurrent() before the call to SwapBuffers() - since calling wglMakeCurrent() prior to SwapBuffers() broke on other cards. ::sigh::
It works… Can you explain how you fixed the problem with the other cards? What does your “special swapping function”?