Sign in to follow this  
superwave

OpenGL Traditional OpenGL vs GLSL vs CG

Recommended Posts

superwave    200

Hi,

 

I was just wondering which of the three is best right now?

 

I used traditional OpenGL like glBegin...glEnd. 

 

Last semester, I tried GLSL, which I think is more flexible, however, not so intuitive and very time consuming (Maybe I am not proficient)

 

One student recommend CG programming.

 

How do you think? 

 

Cheers

Share this post


Link to post
Share on other sites
mhagain    13430

What you're calling "traditional OpenGL" is actually deprecated functionality that is no longer likely to be supported in hardware.

 

It's important to remember that glBegin/glEnd pairs (also known as immediate mode) was always the slowest path, even in the pre-GLSL days, when use of vertex arrays would be what you would want if performance mattered to you.  Vertex arrays, by the way, are a feature going all the way back to GL1.1 in 1997 (they were even available under GL1.0 - even earlier - as an extension) so they should not be considered any kind of "new way of doing things" either.

 

It's also important to realize that you're actually talking about two different things here.  GLSL is not a replacement for glBegin/glEnd pairs and it's perfectly possible to use GLSL with glBegin/glEnd.  GLSL is a replacement for glTexEnv calls (as well as a few other things unrelated to glBegin/glEnd), and when you start trying to express any kind of moderately complex texturing setup using glTexEnv/etc you'll quickly see how much simpler a shader-based approach is (and that's not even saying anything about those things that glTexEnv/etc just flat-out cannot do).

 

Cg is just another shading language so that's a matter of personal preference (so long as you're sticking with OpenGL) more than anything else.

Share this post


Link to post
Share on other sites
BornToCode    1185

GLSL works only on OpenGL, like HLSL only works for DirectX. CG is made and managed by NVIDIA and it works in Both OpenGL and DirectX. The best way to look at this is if you are making an engine where you will have both DirectX and OpenGL for your rendering and one to have a single shader code based then by all mean use CG. But if your engine is going to be specific then use either HLSL if you are going to use DirectX or use GLSL if you are going to use OpenGL.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Similar Content

    • By povilaslt2
      Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).
    • By ZeldaFan555
      Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
      Skype: Mangodoor408
    • By tyhender
      Hello, my name is Mark. I'm hobby programmer. 
      So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine). 
      And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
      Sorry for late replies.
      I mostly give more information when people PM me,but this post is REALLY short,even for me =D
      So here's few more points:
      Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
      I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me. 
       
    • By Zaphyk
      I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?
    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      Question:
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
       
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
  • Popular Now