If you are using shaders then you already moved away the legacy fixed function pipeline. You can disable the legacy functionality by requesting a core context. If you are developing for OpenGL 3 capable hardware you should most definitely not be using it. Which OpenGL 3.1 with a compatibility context supports, but that doesn't mean it should be used. Legacy OpenGL would be: glMatrixMode(GL_MODELVIEW) Just to clear this up OpenGL 3.1 is not legacy OpenGL. Updating your graphics card will probably bump you up to OpenGL 3.3. Whether the driver always support of it is another matter. This is really confusing, give me concrete examples.įurthermore, I want my app to be able to run on most OpenGL implementations, then could you tell me where the border is between legacy GLSL and modern GLSL? Is GLSL 300 the modern GLSL, and is there a compatibilty with OpenGL 3.+ with older GLSL versions?Īny hardware that supports OpenGL 3.1 is capable of supporting OpenGL 3.3.

Then how am I supposed to use them when I am using core functions in my client app (OpenGL 3+)?

The problem is : version 130 is fully based on the legacy opengl pipeline, because it contains things like viewmatrix, modelmatrix, etc. My GLSL version is 1.30 via NVIDIA Cg compiler (full definition), and GLSL 1.30 -> version 130. I however do not have a graphics card supporting these newer GLSL implementations, either I have to update my driver but still I'm not sure if my card is intrinsically able to support it.Ĭurrently my openGL version is 3.1, and I created on windows with C++ a modern context with backwards compatibility. So, I googled a lot of opengl 3.+ tutorials, all incorporating shaders (GLSL 330 core).

Graphics card that supports opengl 3.3