• Advertisement
Sign in to follow this  

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

This topic is 2897 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

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
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
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
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 opengl.org, 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
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
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By LifeArtist
      Good Evening,
      I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
      First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
      I am really stucked right now because of the fundamental question:
      Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
      If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on. 
      In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
      Should I treat those debug objects as entities/components?
      For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
      Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
    • By QQemka
      Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
      Let's go:
      Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
      Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
      Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
      What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
      There were several more but i forgot/solved them at time of writing
      Thanks in advance
    • By RenanRR
      Hi All,
      I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
      I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
      Vertex Shader:
      #version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
      ..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);  
      So, some doubts:
      - Why use it like that?
      - Is it okay to manipulate the camera that way?
      -in this way, are not the vertex's positions that changes instead of the camera?
      - I need to pass MVP to all shaders of object in my scenes ?
      What it seems, is that the camera stands still and the scenery that changes...
      it's right?
      Thank you
    • By dpadam450
      Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

      int rgbValue = int(textureSample.w);//4 bytes of data packed as color
      // algorithm might not be correct and endianness might need switching.
      vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
      extractedData /= 255.0f;
    • By Devashish Khandelwal
      While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
      Anyone has any idea .. what should I do?
  • Advertisement