Torque3D/Engine
Hein-Pieter van Braam 08622e9601 Use different extension detection mechanism
I got this from looking at the code from the glew utility 'glewinfo' on my system it reported the following for GL_ARB_geometry_shader4:  OK [MISSING]. This lead me to believe that there are two different ways of determining extensions. The first 'OK' seems to refer to the entrypoint existing while the second one seems to refer to the extension being available.

The difference is this:
The first OK comes from : GLEW_ARB_geometry_shader4 the global whereas the second 'MISSING' comes from glewGetExtension("GL_ARB_geometry_shader4"). By replacing the gglHasExtension I got the desired result.

We may want to implement some caching if we want to keep using GLEW perhaps?

Anyway I suggest this merely as a test, I'm not sure if this is a viable long-term solution.
2015-07-30 22:18:00 +02:00
..
bin style.css changes for Project Manager modules 2013-05-01 17:08:43 -04:00
lib Fixed some minor compiler warnings on Linux 2015-06-28 22:29:23 +02:00
source Use different extension detection mechanism 2015-07-30 22:18:00 +02:00