Skip to main content
gamedev.net
🔒 Locked

glTexImage3D ?

Started by ophir Nov 16, 2004 at 9:13 PM 7 replies 2.2k views
Original Post
ophir
ophir
I have a big problem with glTexImage3D. I use wglGetProcAddress as follow: 

#include <glext.h>
glTexImage3D = wglGetProcAddress("glTexImage3D");
glTexImage3DEXT = wglGetProcAddress("glTexImage3DEXT");
but it just return NULL; What can I do? help me
_the_phantom_
_the_phantom_
which card?
which driver version?
which windows version?
ophir
ophir
GeForce2 MX/MX 400
Microsoft Windows XP Professional Version 2002 Service Pack 2
Enigma
Enigma
Do you have a valid hardware accelerated OpenGL context when you make those calls?

Enigma
Lutz
Lutz
GeForce2 MX doesn't support 3D textures.

If you want to know which extensions are supported by your card, have a look at the NeHe bump mapping tutorial. If I remember correctly, they have implemented a function there which prints out all supported extensions.
Enigma
Enigma
Quote:
Original post by Lutz
GeForce2 MX doesn't support 3D textures.


GeForce2 MX doesn't support 3D textures in hardware. It still supports 3D textures through the drivers, it'll just be a lot slower. Even my old GeForce 256 supports 3D textures through the drivers!

Enigma
Lutz
Lutz
Then maybe I had an old driver version. The 3D texture extension was not listed in the extensions list.
Enigma
Enigma
It probably wouldn't be. glTexture3D has been core since OpenGL 1.2.

Enigma
zedzeek
zedzeek
enigma is correct, from what one of the guys at nvidia said they only expose stuff (usually) in the extension sting that the hardware can do natively, thus even though u can use 3dtextures with a gf2, itll be the graphics card doing it

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.

Sign in to reply to this topic.