Sign in to follow this  

OpenGL Red book, blue book, orange book, etc?

Recommended Posts

Dark_Oppressor    163
I hope I've selected an OK forum to post this in. I saw a book discussion area, but it seemed devoid of threads. I've learned enough OpenGL to make some 2D games, but now I'd like to start seriously learning it, so I can make 3D stuff. I know that there is a red book, which seems to detail how OpenGL works and teaches one how to program with it. There is a blue book that is for more tutorials and reference material (I think?), and there is an orange book specifically for shaders. As of now, it seems that I want these three books. I am guessing they would keep me busy for a long while. I've noticed something on Amazon called the "OpenGL Library" which seems to be the red and orange books together. Is there any kind of larger collection of books? I'd like to pick up these three in one collection, as it would probably be cheaper (these are rather costly books!) Also, have I correctly identified the basic books?

Share this post

Link to post
Share on other sites
JohnnyDread    138
Looking on amazon it looks like the latest version of the blue book is 1.4, which is awful. You don't want to be reading that, just get the Latest versions of the Red and Orange (3.0 3.1 Orange). Also, OpenGL 4.0 and GLSL 4.0 just got released. So a new Orange and Red book may be only a few months away if your up to waiting. If not, the 3.1 Orange and 1.5 Red versions should be fine because they are very current in what they can do.

By the way, on the note of version numbers. The latest GLSL has been changed to version match OpenGL (ie, OpenGL 4.0 matches GLSL 4.0) but before this update it wasn't the same numbers, so OpenGL 3.2 matched GLSL 1.5
But under no circumstances do you want to be learning OpenGL 1.5, its outdated tech.

Share this post

Link to post
Share on other sites
TheBuzzSaw    143
I found the Red Book to be pretty bad at teaching concepts. I much prefer the blue SuperBible. The latest edition teaches version 2.1, which is a great start into 3D graphics. I would only recommend the Red/Orange books if you knew 3D well already and were looking for a transition over (from DirectX or whatever).

Share this post

Link to post
Share on other sites
karwosts    840
I own the most recent version of the OpenGL library (5th edition).

This contains Red book (7th Ed) and Orange Book (3rd Ed).

Personally I love the orange book, have found it very helpful and relevant. Unfortunately the latest red book leaves something to be desired, which you might notice from its reviews.

I believe the red book with cover everything you will need to know for the OpenGL 3.1+, but the problem is that 80% of the book's content is devoted to depreciated functions. You may find yourself skipping 80 pages of immediate mode content and find 5 pages on buffer objects in the back of the chapter. There's still a 40 page chapter on display lists. It's just not really very current.

I see that there's a "Bluebook" (OpenGL Reference Manual) on, but I've never used it. The Red and Orange book are reference enough, I can't imagine what else they would have put in there.

Go ahead and read the reviews for the books before purchasing, ultimately it's your call. There's really not much in these that you can't find with some google searching, but I know there can be something pleasant about having the texts to flip through.

I would be tempted to wait for a newer version of the texts (remove all the pre-3.1 junk and focus on the new rendering pipeline), although they had a chance to do this with 7th ed, and they just stuck in a few new pages and marked everything else depreciated without rewriting anything, which is pretty lazy. Of course there's no guarantee they'll do any better next time, and no timeline for when a new book might be out. You might be waiting a while for something that isn't much better.

The OpenGL Library also comes with a large poster of the entire opengl rendering pipeline (one side is 2.0 and the other is 3.1). Probably not worth more than $5 but its a nice bonus. Looks like this but is updated for the latest version.

Share this post

Link to post
Share on other sites
Dark_Oppressor    163
Thanks for the replies everyone. I don't have enough money to buy them all together, so I might wait until I do, to give them time to get new editions out. If they still don't have them out by then, I'll probably just go for the current editions.

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++.
      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