OpenGL Learning materials for OGL 3.0-3.1

Recommended Posts

Hey, I've been reading "OpenGL Programming Guide Seventh Edition" book. What I really didn't like here is that the author is using a bunch of deprecated functions. I don't want to learn them, because it wouldn't be effective to use them. I heard about "SuperBible" book, but lots of people complain that the author is using something called GLTools, which hides a lot of low level stuff. So when you try to write something without GLTools, it's really hard. If not that GLTools thing, I'd surely read that book. Besides these 2 books, I couldn't find any good material to learn OGL 3.0 (my GPU supports OGL version only up to 3.1). Do you, guys, know any good materials, tutorials, books or anything, which doesn't use deprecated functions and are good to learn OGL?

Edited by arnsa

Share on other sites

I'd look at two things here.  The Open GL Shading language book, which by nature pretty much has to describe things in regards to the updated API's.  But this won't cover GL itself particularly well, just the bits required for communicating with the shader and such.  The other option is to look at Open GL ES 2.0 books.  Basically ES 2.0 is a subset of the full GL but only the bits related to latest and greatest functionality survived when trimmed down for the little devices.  Again, it's not a perfect example but it is a pretty good start.

Otherwise, I really don't know of any books which are likely to be "pure" to the new GL standards.

Share on other sites

I've found this page to be a great resource for OpenGL 3+, other than that, I usually just look at the official references on khronos.org for specific info on any particular function.

Share on other sites

This website is pretty awesome goes through a lot of the basics and some advanced topics

http://ogldev.atspace.co.uk/

Create an account

Register a new account

• Partner Spotlight

• Forum Statistics

• Total Topics
627665
• Total Posts
2978531
• Similar Content

• Both functions are available since 3.0, and I'm currently using glMapBuffer(), which works fine.
But, I was wondering if anyone has experienced advantage in using glMapBufferRange(), which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
• By xhcao
Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness.
• By cebugdev
hi guys,
are there any books, link online or any other resources that discusses on how to build special effects such as magic, lightning, etc. in OpenGL? i mean, yeah most of them are using particles but im looking for resources specifically on how to manipulate the particles to look like an effect that can be use for games,. i did fire particle before, and I want to learn how to do the other 'magic' as well.
Like are there one book or link(cant find in google) that atleast featured how to make different particle effects in OpenGL (or DirectX)? If there is no one stop shop for it, maybe ill just look for some tips on how to make a particle engine that is flexible enough to enable me to design different effects/magic
let me know if you guys have recommendations.
• By dud3
How do we rotate the camera around x axis 360 degrees, without having the strange effect as in my video below?
Mine behaves exactly the same way spherical coordinates would, I'm using euler angles.
Tried googling, but couldn't find a proper answer, guessing I don't know what exactly to google for, googled 'rotate 360 around x axis', got no proper answers.

References:
Code: https://pastebin.com/Hcshj3FQ
The video shows the difference between blender and my rotation:

• By Defend
I've had a Google around for this but haven't yet found some solid advice. There is a lot of "it depends", but I'm not sure on what.
My question is what's a good rule of thumb to follow when it comes to creating/using VBOs & VAOs? As in, when should I use multiple or when should I not? My understanding so far is that if I need a new VBO, then I need a new VAO. So when it comes to rendering multiple objects I can either:
* make lots of VAO/VBO pairs and flip through them to render different objects, or
* make one big VBO and jump around its memory to render different objects.
I also understand that if I need to render objects with different vertex attributes, then a new VAO is necessary in this case.
If that "it depends" really is quite variable, what's best for a beginner with OpenGL, assuming that better approaches can be learnt later with better understanding?

• 10
• 10
• 12
• 22
• 13