Hey Guys,
So I know that the NeHe website is very popular for learning openGL. Ive done some reading and it seems like there were major changes regarding a fixed function pipeline vs shaders, etc. Im not exactly sure of the details. My question is, is the info on NeHe up to date for the version of openGL I should be focusing on, or is there a better resource? I am eventually accessing openGL thorugh LWJGL, but I am probably going to learn through C++ since its easier to find examples in it. I can always use Java and LWJGL later, its basically the same. I am basically looking for beginner tutorials, which are easy to find, but I dont know enough about what version of openGL I should find tutorials on. I wouldnt even know if I was using the right one or not since I really dont know the difference.
2
Best openGL resource
Started by Joe P, Jul 12 2011 03:03 PM
18 replies to this topic
Ad:
#2 Members - Reputation: 102
Posted 12 July 2011 - 03:14 PM
NeHe is deprecated, in newer OpenGL you have no fixed function pipeline and have to write shaders yourself. A lot of the old API calls are removed in OpenGL 3/4, which means that you have to do more of the work yourself, like creating your own matrices etc...
There is a large tutorial on it here (haven't checked it out myself, though. ) You should also check out the OpenGL documentation, which I use a lot myself since it tells you what the different API calls do.
There is a large tutorial on it here (haven't checked it out myself, though. ) You should also check out the OpenGL documentation, which I use a lot myself since it tells you what the different API calls do.
#3 Members - Reputation: 152
Posted 12 July 2011 - 03:36 PM
fluffybeast, on 12 July 2011 - 03:14 PM, said:
NeHe is deprecated, in newer OpenGL you have no fixed function pipeline and have to write shaders yourself. A lot of the old API calls are removed in OpenGL 3/4, which means that you have to do more of the work yourself, like creating your own matrices etc...
There is a large tutorial on it here (haven't checked it out myself, though. ) You should also check out the OpenGL documentation, which I use a lot myself since it tells you what the different API calls do.
There is a large tutorial on it here (haven't checked it out myself, though. ) You should also check out the OpenGL documentation, which I use a lot myself since it tells you what the different API calls do.
Ahh I figured that much, the dates on the articles are really old. I cant get that link to work, are theyre any books/tutorials that cover the new stuff? I dont want to learn information that isnt up to date. What about those big openGl bibles on Amazon?
I must say Im going to need more than just the API documentation. Im really new to graphics programming so I would prefer some explanations. I dont need my hand held, but a nice organized tutorial with examples and explanations would really help.
I can probably find this stuff myself, so what exactly is the difference between the old and new openGL? If I know the difference, I will have an easier time knowing if a particular tutorial I find is outdated. Im sure there are a ton out there, I just dont want to use an old one.
EDIT: That link is fine, just blocked at my job.. its categorized under PORN lol... strange.
Never, ever stop learning.
- Me
- Me
#4 Members - Reputation: 694
Posted 12 July 2011 - 04:11 PM
A general rule of thumb is that if a tutorial contains calls to glBegin, glEnd and/or any of the glTexEnv functions then it's old and you should avoid it. There's a slight grey area where OpenGL made a transition from old to new (1.5 with extensions, 2.0, 2.1) which can muddy things a little. A danger is that you may find a few such tutorials or resources and end up using a somewhat outdated API that looks on the surface as if it could be new-style, but in reality has since been superseded. Have a read of the arcsynthesis link posted above; it is really quite good and gives some background info which is written a lot better than I could do. Specific details on differences in how old vs new operate probably won't make sense to you right now as you'll need some grounding in 3D graphics terminology to understand such an explanation.
#5 Members - Reputation: 127
Posted 13 July 2011 - 06:16 AM
Wiki it
http://www.opengl.org/wiki/Main_Page
Here's the reference pages
http://www.opengl.org/sdk/docs/
Cheers
http://www.opengl.org/wiki/Main_Page
Here's the reference pages
http://www.opengl.org/sdk/docs/
Cheers
#6 Members - Reputation: 694
Posted 13 July 2011 - 08:47 AM
mhagain, on 12 July 2011 - 04:11 PM, said:
A general rule of thumb is that if a tutorial contains calls to glBegin, glEnd and/or any of the glTexEnv functions then it's old and you should avoid it. There's a slight grey area where OpenGL made a transition from old to new (1.5 with extensions, 2.0, 2.1) which can muddy things a little. A danger is that you may find a few such tutorials or resources and end up using a somewhat outdated API that looks on the surface as if it could be new-style, but in reality has since been superseded. Have a read of the arcsynthesis link posted above; it is really quite good and gives some background info which is written a lot better than I could do. Specific details on differences in how old vs new operate probably won't make sense to you right now as you'll need some grounding in 3D graphics terminology to understand such an explanation.
Yes, but even when you reach shader land (GL2.0 and above), there are some big differences.
With GL 2, you can use built-in attributes, built-in varyings, built-in variables and with fixed function parallels like glLoadMatrix and other matrix calls and glTexGen, glLight, glTexEnv, glMaterial, glColor.
With GL 3.0, 3.1, 3.2, 3.3, further changes came along. You have "core context" and "forward compatible context".
GL is a rather complex beast. Try to find some GL 3.3 tutorials which cover "forward compatible context".GL 3.2 would be fine as well as long as you use VAO everywhere. GL is pretty much stabilized now.
Let's hope they get rid of the bind to modify issue in GL 4.2
Sig: http://glhlib.sourceforge.net
an open source GLU replacement library. Much more modern than GLU.
float matrix[16], inverse_matrix[16];
glhLoadIdentityf2(matrix);
glhTranslatef2(matrix, 0.0, 0.0, 5.0);
glhRotateAboutXf2(matrix, angleInRadians);
glhScalef2(matrix, 1.0, 1.0, -1.0);
glhQuickInvertMatrixf2(matrix, inverse_matrix);
glUniformMatrix4fv(uniformLocation1, 1, FALSE, matrix);
glUniformMatrix4fv(uniformLocation2, 1, FALSE, inverse_matrix);
an open source GLU replacement library. Much more modern than GLU.
float matrix[16], inverse_matrix[16];
glhLoadIdentityf2(matrix);
glhTranslatef2(matrix, 0.0, 0.0, 5.0);
glhRotateAboutXf2(matrix, angleInRadians);
glhScalef2(matrix, 1.0, 1.0, -1.0);
glhQuickInvertMatrixf2(matrix, inverse_matrix);
glUniformMatrix4fv(uniformLocation1, 1, FALSE, matrix);
glUniformMatrix4fv(uniformLocation2, 1, FALSE, inverse_matrix);
#9 Members - Reputation: 126
Posted 13 July 2011 - 02:09 PM
Friendly advice: Take a look at proposed tutorial, or even better - grab some good book!
- OpenGL ES 2 Programming Guide is an excellent one.
- OpenGL Superbible 5th Edition is also great (but with too many basic stuff for my taste).
- OpenGL Shading Language 3rd Edition - great book but not for beginners.
- OpenGL ES 2 Programming Guide is an excellent one.
- OpenGL Superbible 5th Edition is also great (but with too many basic stuff for my taste).
- OpenGL Shading Language 3rd Edition - great book but not for beginners.
#10 Members - Reputation: 152
Posted 13 July 2011 - 02:26 PM
Aks9, on 13 July 2011 - 02:09 PM, said:
Friendly advice: Take a look at proposed tutorial, or even better - grab some good book!
- OpenGL ES 2 Programming Guide is an excellent one.
- OpenGL Superbible 5th Edition is also great (but with too many basic stuff for my taste).
- OpenGL Shading Language 3rd Edition - great book but not for beginners.
- OpenGL ES 2 Programming Guide is an excellent one.
- OpenGL Superbible 5th Edition is also great (but with too many basic stuff for my taste).
- OpenGL Shading Language 3rd Edition - great book but not for beginners.
The superbible was the book I was considering. It says it covers up until version 3.3, is that up to date enough?
Never, ever stop learning.
- Me
- Me
#11 Members - Reputation: 100
Posted 13 July 2011 - 02:31 PM
Avoid deprecated functionality.
One thing that will make everything easier is if you try and create a framework as you move along,
i.e.
I created an object with hard code,
Then I created code to make the object for me,
Now I can have hundreds of objects on screen.
I created a shader\program object with hard code,
Then I created code to do all the compiling, linking, for me.
Now it's much easier for me to make shaders.
Just START SLOW, Don't move on until you understand something.
One thing that will make everything easier is if you try and create a framework as you move along,
i.e.
I created an object with hard code,
Then I created code to make the object for me,
Now I can have hundreds of objects on screen.
I created a shader\program object with hard code,
Then I created code to do all the compiling, linking, for me.
Now it's much easier for me to make shaders.
Just START SLOW, Don't move on until you understand something.
#12 Members - Reputation: 126
Posted 13 July 2011 - 02:37 PM
joeparrilla, on 13 July 2011 - 02:26 PM, said:
The superbible was the book I was considering. It says it covers up until version 3.3, is that up to date enough?
Yes!
The only "fancy" thing that is missing is - the tessellation shaders (OpenGL 4.0).
There is also some other stuff in GL 4.0/4.1 but they are not crucial for understanding main concepts.
#13 Members - Reputation: 152
Posted 13 July 2011 - 02:39 PM
Aks9, on 13 July 2011 - 02:37 PM, said:
joeparrilla, on 13 July 2011 - 02:26 PM, said:
The superbible was the book I was considering. It says it covers up until version 3.3, is that up to date enough?
Yes!
The only "fancy" thing that is missing is - the tessellation shaders (OpenGL 4.0).
There is also some other stuff in GL 4.0/4.1 but they are not crucial for understanding main concepts.
Gotcha, I think thats gonna be the one then. It got pretty good Amazon reviews.
Never, ever stop learning.
- Me
- Me
#14 Members - Reputation: 104
Posted 13 July 2011 - 02:44 PM
I like this one:
http://duriansoftwar...f-Contents.html
It was quite easy to follow, though I had already used some fixed functionality before.
I'm not sure if it's easy to catch for a starter, but at least it states no previous OpenGL experience is required...
http://duriansoftwar...f-Contents.html
It was quite easy to follow, though I had already used some fixed functionality before.
I'm not sure if it's easy to catch for a starter, but at least it states no previous OpenGL experience is required...
#15 Members - Reputation: 212
Posted 15 July 2011 - 08:31 AM
If I can just add a two bits of info that could help you greatly while trying to understand what is wrong with the programs you are going to make:
1) OpenGL is a state machine. Always keep this in mind, remember to bind objects before you attempt modify them, and don't bother trying to use OpenGL across multiple threads (single thread for all OpenGL operations).
2) Use gDEbugger to quickly identify errors in your OpenGL calls, and to easily view the current OpenGL state (textures, shaders, variables, bound objects etc.)
1) OpenGL is a state machine. Always keep this in mind, remember to bind objects before you attempt modify them, and don't bother trying to use OpenGL across multiple threads (single thread for all OpenGL operations).
2) Use gDEbugger to quickly identify errors in your OpenGL calls, and to easily view the current OpenGL state (textures, shaders, variables, bound objects etc.)
#16 Members - Reputation: 102
Posted 15 July 2011 - 11:39 AM
I've read often that the SuperBible 5 is really biased toward the author's GLToolKit or whatever its called. I understand what they were going for in order to introduce graphics programming, but its an OpenGL book, I don't really see the logic in wrapping OpenGL. Unless of course the ToolKit is built and explained during the book's progression.
I think, if what I've read of the SB5 is true, that, maybe a better route (besides the two ebooks posted earlier which are very good,) is something like the Orange Book(OpenGL Shading Language) and OpenGL ES 2.0 Programming Guide.
I think, if what I've read of the SB5 is true, that, maybe a better route (besides the two ebooks posted earlier which are very good,) is something like the Orange Book(OpenGL Shading Language) and OpenGL ES 2.0 Programming Guide.
#17 Members - Reputation: 152
Posted 15 July 2011 - 11:40 AM
The_Doc, on 15 July 2011 - 11:39 AM, said:
I've read often that the SuperBible 5 is really biased toward the author's GLToolKit or whatever its called. I understand what they were going for in order to introduce graphics programming, but its an OpenGL book, I don't really see the logic in wrapping OpenGL. Unless of course the ToolKit is built and explained during the book's progression.
I think, if what I've read of the SB5 is true, that, maybe a better route (besides the two ebooks posted earlier which are very good,) is something like the Orange Book(OpenGL Shading Language) and OpenGL ES 2.0 Programming Guide.
I think, if what I've read of the SB5 is true, that, maybe a better route (besides the two ebooks posted earlier which are very good,) is something like the Orange Book(OpenGL Shading Language) and OpenGL ES 2.0 Programming Guide.
yes most of the negative reviews say this.... which totally confuses me. If its an openGL intro book, why in the world would they wrap openGL and teach that? It doesnt make sense to me.
Never, ever stop learning.
- Me
- Me
#18 Members - Reputation: 102
Posted 15 July 2011 - 12:30 PM
Exactly.
I guess it may be a misunderstanding. That is, perhaps the reviewers mean that the authors spend 7 chapters DEVELOPING the GLToolKit (the ins and outs) instead of going straight to GLSL. But that would mean the tool kit has shaders in it, which leads me to think they are indeed just black boxing the whole thing. I was hoping someone here had read it and could shed some light on it.
The two ebooks linked, I think, would do a good job of filling in the holes the SB5 would inevitably leave. So, I think it would still be a safe investment, I'm just boggled as to how a thousand page book would feel the need to approach the material that way.
I guess it may be a misunderstanding. That is, perhaps the reviewers mean that the authors spend 7 chapters DEVELOPING the GLToolKit (the ins and outs) instead of going straight to GLSL. But that would mean the tool kit has shaders in it, which leads me to think they are indeed just black boxing the whole thing. I was hoping someone here had read it and could shed some light on it.
The two ebooks linked, I think, would do a good job of filling in the holes the SB5 would inevitably leave. So, I think it would still be a safe investment, I'm just boggled as to how a thousand page book would feel the need to approach the material that way.
#19 Members - Reputation: 102
Posted 16 July 2011 - 11:34 AM
Nothing like suggesting something you yourself aren't willing to do, but I'll go ahead and do it anyway...
It'd be great if someone went and rewrote the NeHe tutorials using only the OpenGL 3+ core profile only. I'm sure it'd immediately become a very popular site.
(By the way, I completely agree with the last couple posts. It understand why it happens, but it's frustrating when tutorials, books, lessions, etc. develop a framework or toolkit when they claim to be about learning the core API. Sure, to get to some advanced features you'll need to reuse some code, but limit it to functions, not frameworks - and write out the API calls full in when possible!)
It'd be great if someone went and rewrote the NeHe tutorials using only the OpenGL 3+ core profile only. I'm sure it'd immediately become a very popular site.
(By the way, I completely agree with the last couple posts. It understand why it happens, but it's frustrating when tutorials, books, lessions, etc. develop a framework or toolkit when they claim to be about learning the core API. Sure, to get to some advanced features you'll need to reuse some code, but limit it to functions, not frameworks - and write out the API calls full in when possible!)
