"C.Reinke" wrote:
[...] according to my reading of the OpenGL spec, it seems part of the update to 1.2 (it's hidden in some table as GL_TEXTURE_BINDING_xD, where x should presumably include 3 now).
Hmmm, the OpenGL spec is a bit strange here: GL_TEXTURE_BINDING_xD is not mentioned in the index, but is used in the tables describing the state queries. But it's quite clear that GL_TEXTURE_BINDING_3D should be there if texture objects and 3D textures are supported (both OpenGL 1.2 features). SUN's header claims to implement 1.2, but fails to #define the above token. Simple solution: Either comment it out if you don't need it or have a look at your favourite correct header and substitute the numeric value, perhaps the query is implemented nevertheless. BTW, SGI's OpenGL sample implementation (which is 1.2x) #defines it, and the token is mentioned in the official enumerant spec, so it's SUN's fault, not HOpenGL's... >:-) This is just another example why the next release of HOpenGL won't depend on those #defines, but will use numeric values directly...
[...] and as Sun is a member of the OpenGL ARB, I'd expect them to have a spec-conforming implementation!-)
There have been rumors that there are incorrect OpenGL implementations which "pass" the official conformance tests, and correct implementations which don't get official approval. Politics & $$$... Cheers, S. -- Sven Panne Fon: +49/89/99567000 Fax: +49/89/99567461 BetaResearch GmbH, Betastr. 1, D-85774 Unterfoehring mailto:Sven_Panne@BetaResearch.de http://www.betaresearch.de