OpenGL EXTension not detected by GLEW?

Asked Dec 02 '14 at 20:16

Active Dec 02 '14 at 20:51

Viewed 70 times

I'm writing some modules using "DirectStateAccess" capabilities. If it's not supported, I made the necessary stuff.

On a customer laptop, I was able to create an OpenGL 3.3 Core Profile context. In a first call to glGetString(GL_EXTENSIONS), GL_EXT_direct_state_access was available.

However, GLEW_EXT_direct_state_access variable definitely equals false. Subsequent call to wglGetProcAddress("glTextureParameteriEXT") returns a non null value though. And the functions glTextureParameterxx() seem available as well...

At this point, I wonder if I can rely on GLEW variables to check if an extension is indeed supported or not.

Oh, by the way, I made my tests with a "valid OpenGL context activated"...

edited Dec 02 '14 at 20:51

genpfault

47,669
9
68
119

asked Dec 02 '14 at 20:16

Zyend

1

Are you also setting `glewExperimental` to `GL_TRUE` before calling `glewInit()`? – genpfault Dec 02 '14 at 20:52
Yes I did it though. – Zyend Dec 03 '14 at 06:22
1

Seems this is already filed as a bug [here](http://sourceforge.net/p/glew/bugs/167/). – Thomas Dec 03 '14 at 20:39

OpenGL EXTension not detected by GLEW?

0 Answers0