Since the new NVIDIA driver release (29.42) I have got problems with the render to texture extensions. wglGetPtocAddress(…) returns NULL for wglBindTexImageARB(…), wglReleaseTexImageARB(…) and wglSetPbufferAttribARB(…). Has anyone else the same problem or has anybody an idea from where this comes? Here a code snoppet of the initialization function:
No, but these extensions ARE available on my card, because the corresponding NVIDIA demos work. And in my point of view glh_init() does nothing else than my init function.
The nVidia demos might have fall-back-to code that works even if the extensions are there. The do-all solution is to look at the result of glGetString(GL_EXTENSIONS); (you have it there in your code, but you’re ignoring the return value; make a char pointer and assign the return value of glGetString(GL_EXTENSIONS) to it and print it out,) maybe even write a routine that will parse it looking for the extensions.
No no no. Before this driver release hardware shadow mapping was working. Since this new driver hw shadow mapping doesn’t work anymore. I know the result of glGetString() and wglGetExtensionsStringARB() because I check it at another place in the code. The reason why wglGetExtensionsStringARB() is there is that it seems to do some initialization which must be done before creating the pbuffer.
before intializing the render to texture function pointers wglGetExtensionsStringARB(HDC hdc) has to be called. The problem was that I passed the return value of wglGetCurrentDC() to wglGetExtensionsStringARB(HDC hdc). This didn’t work. Now I use the device context MFC returns to me via CView->GetDC()->m_hDC. This works!
The problem where wglGetExtensionsStringARB had to be called before getting wgl extension function pointers has been fixed and should be in the next driver release.
The problem where wglGetExtensionsStringARB had to be called before getting wgl extension function pointers has been fixed and should be in the next driver release.[/b]
Jra101, as you are active also on the Linux side, do you plane to make render-to-texture GLX extensions too?
Yes, good to hear that it will be fixed in the next driver release. But currently nobody really says that you have to call wglGetExtensionsStringARB(…) before initializing render to texture functions.
[This message has been edited by gerogerber (edited 06-21-2002).]