Sign in to follow this  

OpenGL OpenGL3 and NeHe relevance

This topic is 3620 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi, To avoid making someone angry in the OpenGL forum, I'm posting this here :-) I'm still very much an OpenGL newbie (slowly working my way through the excellent NeHe tutorials, using SDL + OpenGL). I read that OpenGL3 really fundamentally changes the API. The question is, just how fundamental is this change? That is, is the majority of the NeHe tutorial work pretty much obsolete, or do the changes only kick in for the more advanced shader stuff? I've only gotten to maybe lesson 6-7 and took a break for other stuff, so starting over with a very different API isn't the end of the world hehe... Also, if my video card supports OpenGL2, will everything I do with the new 3.0 API be software-only, or does it have a good conversion layer to still use the OpenGL2-based hardware acceleration? cheers!

Share this post


Link to post
Share on other sites
I don't see why this would make anyone mad -- and it's offtopic for the beginners forum. So I'm moving it to the OpenGL forum.

A good chunk of the early NeHe stuff uses immediate mode, which will be going away in GL3. All of that will be obsolete, then. I haven't see too much of the GL3 API details, but I'd bet there will be fairly signifigant API break.

OTOH, GL3 has been on the horizon for a while now. I haven't seen anything to make me believe it will actually show up soon, so there's no reason to worry about learning the "wrong stuff" (the underlying concepts will transfer between GL and GL3 as they do between GL and D3D anyway).

OTOH (again), I don't think NeHe is a particular good learning resource anyway. The code's pretty bad, and the explanations of the fundamentals are not sufficient enough for me.

Share this post


Link to post
Share on other sites
The interface is changing. They haven't said what the new interface will be so that is a very hard question to answer at the moment. It should be fairly similar as it will provide the exact same abilities as the current release of opengl. Don't worry about it to much and focus on learning graphics programming, while using opengl as a tool. Don't learn opengl and not pay attention to the math going on in the background.

Share this post


Link to post
Share on other sites
Quote:
Original post by jpetrie
I don't see why this would make anyone mad


I figured, while my searches didn't turn up anything, it was probably asked before, because it seems like a fairly obvious question to ask :-)

Quote:
OTOH (again), I don't think NeHe is a particular good learning resource anyway. The code's pretty bad, and the explanations of the fundamentals are not sufficient enough for me.


You have a lot of hands! I agree, the code is fairly 'bleh', and I wouldn't exactly use it as an example of good architecture by any stretch. And I always go to the official API docs with every new API call he makes. It's just a decent way of getting shown around in a modular fashion. If you can recommend a better source from which to learn it in a way that doesn't feel like a reference manual, I'm all ears.

Share this post


Link to post
Share on other sites
Quote:
Original post by Replicon
You have a lot of hands! I agree, the code is fairly 'bleh', and I wouldn't exactly use it as an example of good architecture by any stretch. And I always go to the official API docs with every new API call he makes. It's just a decent way of getting shown around in a modular fashion. If you can recommend a better source from which to learn it in a way that doesn't feel like a reference manual, I'm all ears.


I would reccomend the red book (OpenGL Programming guide, mentioned in this forum FAQ) over NeHe anytime.

Share this post


Link to post
Share on other sites
Quote:
Original post by Replicon
I read that OpenGL3 really fundamentally changes the API. The question is, just how fundamental is this change? That is, is the majority of the NeHe tutorial work pretty much obsolete, or do the changes only kick in for the more advanced shader stuff? I've only gotten to maybe lesson 6-7 and took a break for other stuff, so starting over with a very different API isn't the end of the world hehe...


OpenGL3.0 is going to be a totally breaking API change, consider it a fresh start for OpenGL.
That said, there are a number of things to consider;
1) GL3 has been 'soon' for around 6 months now and the ARB has gone silent on us again so we aren't expecting it any time soon (the lack of OpenGL at GDC doesn't bode well either).
2) Even if GL3 was released tomorrow everyone pretty much expects a 6month lead time before drivers are stable.
3) GL2.x isn't going to vanish over night. You'll still be able to use GL2.1 in it's current form for some time to come (years), just dont' expect any updates or new extensions for it; what you've got is what you've got.

Now, as for learning, personally I swear by the Red Book aka OpenGL programmers guide. NeHe got me intrested but it was the Red Book and alot of poking about which got me the rest of the way.

Quote:

Also, if my video card supports OpenGL2, will everything I do with the new 3.0 API be software-only, or does it have a good conversion layer to still use the OpenGL2-based hardware acceleration?


GL3.0 is, effectively, the feature set of GL2.0 with a new, cleaner, API.

What this means in real terms is that as long as you've got at least a Nvidia GFFX or a ATI 9500 graphics card you should be able to support it (as to if either company will make it work on their hardware or not is another matter) as the 'lowest end' has been fixed to supporting DX9 level features. However it will be in hardware, like GL2.x is now.

Share this post


Link to post
Share on other sites
Since you already reference the API as you go through the NeHe tutorials and though the Red book is undoubtly a good resource, I would recommend "Advanced Graphics Programming using OpenGL, McReynolds/Blythe". This book is better at explaining the concepts behind a lot of more modern techniques rather than going through the API from A-Z like Red Book / OpenGL Superbible. Much of the contents of the Red book can be found online at http://www.opengl.org/sdk/docs. Another good book down the same alley is "Realtime Rendering, Moller/Haines" with the difference that this discusses the concepts without going into any API details. I feel that these two books have a better chance of being useful after OpenGL 3 is introduced and you can probably pick up an updated OpenGL Superbible / Red Book when the specifications have been revealed.

Share this post


Link to post
Share on other sites
I also started learning OpenGL using the NeHe-tutorials, but i bought the red book and later also the orange book. The red book is in my opinion (as others here have stated as well) the best way to learn OpenGL. Its just excellent, as well as the orange book.

EDIT: If you learn OpenGL and the techniques it uses, moving between OGL2 and OGL3 shouldn't be very difficult, just read some API specs.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Similar Content

    • By xhcao
      Does sync be needed to read texture content after access texture image in compute shader?
      My simple code is as below,
      glUseProgram(program.get());
      glBindImageTexture(0, texture[0], 0, GL_FALSE, 3, GL_READ_ONLY, GL_R32UI);
      glBindImageTexture(1, texture[1], 0, GL_FALSE, 4, GL_WRITE_ONLY, GL_R32UI);
      glDispatchCompute(1, 1, 1);
      // Does sync be needed here?
      glUseProgram(0);
      glBindFramebuffer(GL_READ_FRAMEBUFFER, framebuffer);
      glFramebufferTexture2D(GL_READ_FRAMEBUFFER, GL_COLOR_ATTACHMENT0,
                                     GL_TEXTURE_CUBE_MAP_POSITIVE_X + face, texture[1], 0);
      glReadPixels(0, 0, kWidth, kHeight, GL_RED_INTEGER, GL_UNSIGNED_INT, outputValues);
       
      Compute shader is very simple, imageLoad content from texture[0], and imageStore content to texture[1]. Does need to sync after dispatchCompute?
    • By Jonathan2006
      My question: is it possible to transform multiple angular velocities so that they can be reinserted as one? My research is below:
      // This works quat quaternion1 = GEQuaternionFromAngleRadians(angleRadiansVector1); quat quaternion2 = GEMultiplyQuaternions(quaternion1, GEQuaternionFromAngleRadians(angleRadiansVector2)); quat quaternion3 = GEMultiplyQuaternions(quaternion2, GEQuaternionFromAngleRadians(angleRadiansVector3)); glMultMatrixf(GEMat4FromQuaternion(quaternion3).array); // The first two work fine but not the third. Why? quat quaternion1 = GEQuaternionFromAngleRadians(angleRadiansVector1); vec3 vector1 = GETransformQuaternionAndVector(quaternion1, angularVelocity1); quat quaternion2 = GEQuaternionFromAngleRadians(angleRadiansVector2); vec3 vector2 = GETransformQuaternionAndVector(quaternion2, angularVelocity2); // This doesn't work //quat quaternion3 = GEQuaternionFromAngleRadians(angleRadiansVector3); //vec3 vector3 = GETransformQuaternionAndVector(quaternion3, angularVelocity3); vec3 angleVelocity = GEAddVectors(vector1, vector2); // Does not work: vec3 angleVelocity = GEAddVectors(vector1, GEAddVectors(vector2, vector3)); static vec3 angleRadiansVector; vec3 angularAcceleration = GESetVector(0.0, 0.0, 0.0); // Sending it through one angular velocity later in my motion engine angleVelocity = GEAddVectors(angleVelocity, GEMultiplyVectorAndScalar(angularAcceleration, timeStep)); angleRadiansVector = GEAddVectors(angleRadiansVector, GEMultiplyVectorAndScalar(angleVelocity, timeStep)); glMultMatrixf(GEMat4FromEulerAngle(angleRadiansVector).array); Also how do I combine multiple angularAcceleration variables? Is there an easier way to transform the angular values?
    • By dpadam450
      I have this code below in both my vertex and fragment shader, however when I request glGetUniformLocation("Lights[0].diffuse") or "Lights[0].attenuation", it returns -1. It will only give me a valid uniform location if I actually use the diffuse/attenuation variables in the VERTEX shader. Because I use position in the vertex shader, it always returns a valid uniform location. I've read that I can share uniforms across both vertex and fragment, but I'm confused what this is even compiling to if this is the case.
       
      #define NUM_LIGHTS 2
      struct Light
      {
          vec3 position;
          vec3 diffuse;
          float attenuation;
      };
      uniform Light Lights[NUM_LIGHTS];
       
       
    • By pr033r
      Hello,
      I have a Bachelor project on topic "Implenet 3D Boid's algorithm in OpenGL". All OpenGL issues works fine for me, all rendering etc. But when I started implement the boid's algorithm it was getting worse and worse. I read article (http://natureofcode.com/book/chapter-6-autonomous-agents/) inspirate from another code (here: https://github.com/jyanar/Boids/tree/master/src) but it still doesn't work like in tutorials and videos. For example the main problem: when I apply Cohesion (one of three main laws of boids) it makes some "cycling knot". Second, when some flock touch to another it scary change the coordination or respawn in origin (x: 0, y:0. z:0). Just some streng things. 
      I followed many tutorials, change a try everything but it isn't so smooth, without lags like in another videos. I really need your help. 
      My code (optimalizing branch): https://github.com/pr033r/BachelorProject/tree/Optimalizing
      Exe file (if you want to look) and models folder (for those who will download the sources):
      http://leteckaposta.cz/367190436
      Thanks for any help...

    • By Andrija
      I am currently trying to implement shadow mapping into my project , but although i can render my depth map to the screen and it looks okay , when i sample it with shadowCoords there is no shadow.
      Here is my light space matrix calculation
      mat4x4 lightViewMatrix; vec3 sun_pos = {SUN_OFFSET * the_sun->direction[0], SUN_OFFSET * the_sun->direction[1], SUN_OFFSET * the_sun->direction[2]}; mat4x4_look_at(lightViewMatrix,sun_pos,player->pos,up); mat4x4_mul(lightSpaceMatrix,lightProjMatrix,lightViewMatrix); I will tweak the values for the size and frustum of the shadow map, but for now i just want to draw shadows around the player position
      the_sun->direction is a normalized vector so i multiply it by a constant to get the position.
      player->pos is the camera position in world space
      the light projection matrix is calculated like this:
      mat4x4_ortho(lightProjMatrix,-SHADOW_FAR,SHADOW_FAR,-SHADOW_FAR,SHADOW_FAR,NEAR,SHADOW_FAR); Shadow vertex shader:
      uniform mat4 light_space_matrix; void main() { gl_Position = light_space_matrix * transfMatrix * vec4(position, 1.0f); } Shadow fragment shader:
      out float fragDepth; void main() { fragDepth = gl_FragCoord.z; } I am using deferred rendering so i have all my world positions in the g_positions buffer
      My shadow calculation in the deferred fragment shader:
      float get_shadow_fac(vec4 light_space_pos) { vec3 shadow_coords = light_space_pos.xyz / light_space_pos.w; shadow_coords = shadow_coords * 0.5 + 0.5; float closest_depth = texture(shadow_map, shadow_coords.xy).r; float current_depth = shadow_coords.z; float shadow_fac = 1.0; if(closest_depth < current_depth) shadow_fac = 0.5; return shadow_fac; } I call the function like this:
      get_shadow_fac(light_space_matrix * vec4(position,1.0)); Where position is the value i got from sampling the g_position buffer
      Here is my depth texture (i know it will produce low quality shadows but i just want to get it working for now):
      sorry because of the compression , the black smudges are trees ... https://i.stack.imgur.com/T43aK.jpg
      EDIT: Depth texture attachment:
      glTexImage2D(GL_TEXTURE_2D, 0,GL_DEPTH_COMPONENT24,fbo->width,fbo->height,0,GL_DEPTH_COMPONENT,GL_FLOAT,NULL); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_EDGE); glFramebufferTexture2D(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, GL_TEXTURE_2D, fbo->depthTexture, 0);
  • Popular Now