Sign in to follow this  
coden4fun

OpenGL I want to start OpenGL but I want to have everything I need.

Recommended Posts

Hi, I was going to start OpenGL tonight, but tonight has been time spent on much research in OpenGL what is supported now, what isn't being supported, and the fact that I am working in the Visual C++ "Orcas" Beta 2 Release I knew I would have to do my homework before moving toward OpenGL. First I read the nehe tutorials but was lost when using glaux.h then I read this forum posted here on Gamedev http://www.gamedev.net/community/forums/topic.asp?topic_id=357528 that it is no longer in use, so I thought that the NeHe tutorials are almost out dated, so I decided to go with a book that is of this year using OpenGL OpenGL SuperBible 4, but now I can't find gtools.h It's not in the OpenGL package from either SGI, or MS, and it's definitely not in the source code they give you to look through, and work on. So where is gtools.h or where is a good place to start programming OpenGL using the latest, or Visual C++ 2005 Express Edition? I'm gonna sleep and hope to find help by morning. [edited]I can tell you that I have edited my own include folder inside my Visual Studio VC folder where I do have a gl folder that has gl.h glut.h GLU.h and the respected libraries are in my lib folder, and the respected .DLL are where they should be. Thanks,

Share this post


Link to post
Share on other sites
I use and recommend these libraries for OpenGL development:

GLFW for window initialization and input management. This is newer than GLUT and under active development. I also think it's more sensible and lightweight.
GLEW for OpenGL extensions if you want to use any modern GPU features.
SOIL for easy texture loading.

All of these come with precompiled .lib files for Visual C++.

Just start from the most basic GLFW examples, and introduce new things from the NEHE tutorials without copy/pasting the entire code. Specifically use something like SOIL instead of glaux.h for texture loading, and GLEW functionality instead of GLUT for input management and such. It's all well documented on the homepages of these libraries.

Share this post


Link to post
Share on other sites
The NeHe tutorials are certainly still of use.
I learned a lot about OpenGL from reading them a couple a years ago.
You just need to replace glaux with some up to date, and preferably non memory leaking, library such as DevIL.

Share this post


Link to post
Share on other sites
Quote:
Original post by nife87
The NeHe tutorials are certainly still of use.
I learned a lot about OpenGL from reading them a couple a years ago.
You just need to replace glaux with some up to date, and preferably non memory leaking, library such as DevIL.


I'm sure that most of the things you will learn will be required for the OGL 3.0 also, but just to avoid wasting your time on older things, keep in mind that the new version is going to come out and that you may want to focus on those parts that will be present in the upcoming OGL 3: IIRC most of the extensions will be integrated in the api, the windows version will be updated and fixed functions removed.

Share this post


Link to post
Share on other sites
when will OpenGL 3.0 be released. When, and where can I grab it when it does come out, and what do I have to focus on now to make it to where I won't have to learn a new library, or a couple of header files to work with when it does come out?

Share this post


Link to post
Share on other sites
If you take a look at my website you will see that you can do quite a bit with OpenGL and a C++ compiler. You don't need any extra libraries. Just the ones that come with Platform SDK.

Share this post


Link to post
Share on other sites
Don't worry about OpenGL 3 or newer extensions, you want to learn the basics first anyway. You can do a great deal in immediate mode, without textures, etc. The Red Book is a great place to start and should introduce you to all the fundamentals.

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
      627738
    • Total Posts
      2978881
  • 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