Sign in to follow this  
wforl

OpenGL The big red Book

Recommended Posts

Hi guys, I currently have the book, beginning OpenGl game programming, and am kind of struggling, as in theres some stuff that just dont understand, and i thought that maybe a more explanational book would help. And i came across this book http://www.amazon.co.uk/OpenGL-Programming-Guide-Official-Learning/dp/0321335732/ref=pd_bbs_sr_1/202-7256194-6888620?ie=UTF8&s=books&qid=1184233886&sr=8-1 does anybody have both of these books, and could they tell me, if they found the later easyier to read. I think that the first book is great, but maybe its for somone with a better understanding of programming than me, as they go through stuff quickly. Thanks

Share this post


Link to post
Share on other sites

I don't have both books but, as any serious OpenGL programmer should, I do have the red book.

When I started OpenGL programming (some 15 years or so back), I bought two books:
- The OpenGL Super Bible (http://www.starstonesoftware.com/OpenGL/)
- The OpenGL Programming Guide (http://www.opengl.org/documentation/red_book/)

I still think it's the perfect start for the beginning Graphics/OpenGL programmer.
The Red book can be used as a reference guide and adds very accessible explanations. The Super bible covers all basic topics in a clear step by step tutorial style. It also features full source code including project files for Visual studio of all examples in the book.

There is plenty of info on those book on the web, if you're not convinced.

I hope this helps,

Serge van Keulen

Share this post


Link to post
Share on other sites
Thanks for your comments Treestory, both the books look great, and will probaly purchase them soon,

is there any that you would recommend over the other?

i also noticed that they've both been revised for 2007, ...cool

Share this post


Link to post
Share on other sites
If you really have to pick one, and if you are beginning to learn OpenGL/Graphics programming I guess you should pick the Super bible. But the red book is something that ever OpenGL programmer should have within reach. Especially when you start using more advanced techniques.

Share this post


Link to post
Share on other sites
I also started with Beginning OpenGL Game Programming. I, on the other hand, really liked it and learned a lot from it. I think that you could too.

As for a book going "through stuff rather quickly", you have to remember that it's a book. It is entirely self-paced. If you need more time on something, you can take that time on it. There's no set "must read 50 pages a week" schedule on a book. So take it slowly - don't move onto the next section before you truly understand the previous section. This stuff isn't easy; it takes time to learn it. But time you have when it's a book. If you need more information on a topic, search for it online. There's tons of stuff out there, including a free copy of the Red Book, which really is the definitive guide to OpenGL.

I guess what I'm saying is take you time and make sure to do the exercises and if you don't understand something, use your resources. There's lots online, so google. You can ask about more than just errors here; you can ask about topics you don't understand and I'm sure that someone will be able to either point you to a good site, or answer you themselves. But most importantly, don't give up.

Good luck. [smile]

Share this post


Link to post
Share on other sites
The second edition of the red book is free and can be found here. It's outdated but it still contains a lot of useful information and it will give you a feel for the book's writing style. I strongly recommend that you look at it before buying a new version. As many people will tell you, it can be quite daunting for someone new to 3D math of graphics.

I think an old version of the reference manual can also be found somewhere online.

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  

  • Forum Statistics

    • Total Topics
      627718
    • Total Posts
      2978792
  • Similar Content

    • By DelicateTreeFrog
      Hello! As an exercise for delving into modern OpenGL, I'm creating a simple .obj renderer. I want to support things like varying degrees of specularity, geometry opacity, things like that, on a per-material basis. Different materials can also have different textures. Basic .obj necessities. I've done this in old school OpenGL, but modern OpenGL has its own thing going on, and I'd like to conform as closely to the standards as possible so as to keep the program running correctly, and I'm hoping to avoid picking up bad habits this early on.
      Reading around on the OpenGL Wiki, one tip in particular really stands out to me on this page:
      For something like a renderer for .obj files, this sort of thing seems almost ideal, but according to the wiki, it's a bad idea. Interesting to note!
      So, here's what the plan is so far as far as loading goes:
      Set up a type for materials so that materials can be created and destroyed. They will contain things like diffuse color, diffuse texture, geometry opacity, and so on, for each material in the .mtl file. Since .obj files are conveniently split up by material, I can load different groups of vertices/normals/UVs and triangles into different blocks of data for different models. When it comes to the rendering, I get a bit lost. I can either:
      Between drawing triangle groups, call glUseProgram to use a different shader for that particular geometry (so a unique shader just for the material that is shared by this triangle group). or
      Between drawing triangle groups, call glUniform a few times to adjust different parameters within the "master shader", such as specularity, diffuse color, and geometry opacity. In both cases, I still have to call glBindTexture between drawing triangle groups in order to bind the diffuse texture used by the material, so there doesn't seem to be a way around having the CPU do *something* during the rendering process instead of letting the GPU do everything all at once.
      The second option here seems less cluttered, however. There are less shaders to keep up with while one "master shader" handles it all. I don't have to duplicate any code or compile multiple shaders. Arguably, I could always have the shader program for each material be embedded in the material itself, and be auto-generated upon loading the material from the .mtl file. But this still leads to constantly calling glUseProgram, much more than is probably necessary in order to properly render the .obj. There seem to be a number of differing opinions on if it's okay to use hundreds of shaders or if it's best to just use tens of shaders.
      So, ultimately, what is the "right" way to do this? Does using a "master shader" (or a few variants of one) bog down the system compared to using hundreds of shader programs each dedicated to their own corresponding materials? Keeping in mind that the "master shaders" would have to track these additional uniforms and potentially have numerous branches of ifs, it may be possible that the ifs will lead to additional and unnecessary processing. But would that more expensive than constantly calling glUseProgram to switch shaders, or storing the shaders to begin with?
      With all these angles to consider, it's difficult to come to a conclusion. Both possible methods work, and both seem rather convenient for their own reasons, but which is the most performant? Please help this beginner/dummy understand. Thank you!
    • By JJCDeveloper
      I want to make professional java 3d game with server program and database,packet handling for multiplayer and client-server communicating,maps rendering,models,and stuffs Which aspect of java can I learn and where can I learn java Lwjgl OpenGL rendering Like minecraft and world of tanks
    • By AyeRonTarpas
      A friend of mine and I are making a 2D game engine as a learning experience and to hopefully build upon the experience in the long run.

      -What I'm using:
          C++;. Since im learning this language while in college and its one of the popular language to make games with why not.     Visual Studios; Im using a windows so yea.     SDL or GLFW; was thinking about SDL since i do some research on it where it is catching my interest but i hear SDL is a huge package compared to GLFW, so i may do GLFW to start with as learning since i may get overwhelmed with SDL.  
      -Questions
      Knowing what we want in the engine what should our main focus be in terms of learning. File managements, with headers, functions ect. How can i properly manage files with out confusing myself and my friend when sharing code. Alternative to Visual studios: My friend has a mac and cant properly use Vis studios, is there another alternative to it?  
    • By ferreiradaselva
      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. 
  • Popular Now