Sign in to follow this  

OpenGL Current OpenGL

Recommended Posts

Hi everyone, i'm a little bit confused at the moment as i've just started to get into OpenGL again after a while and things seemed to have changed. I had started going through the NeHe tutorials until I saw a forum post on here about their approach being "ancient" and "deprecated" so I did a little bit of research and found that there seems to have been a shift away from glBegin/glEnd to the use of vertex buffers and shaders. So i'm wondering if there are any good resources for learning this new approach out there at the moment. What books are recommended now? Seeing as the red book I guess has been somewhat made obsolete. Also are there any good tutorial sites for starting off? I thought this might need to go in the "beginners" section but seeing as people who know more about OpenGL specifically will visit this section I thought i'd give it a go here. Thanks in advance.

Share this post

Link to post
Share on other sites
The NeHe lessons are in the process of beeing updated to use more up-to-date approaches. While only the very basic ones are done, they should still be of some use since they deal with vertex buffers:

For shaders (GLSL), I highly recommend Lighthouse3d:

Share this post

Link to post
Share on other sites
Cheers, i've been wading through GLSL tutorial and information for a few hours now and feeling a little bogged down. I'm confused as to what are current functions which are considered to be "best". For example the difference between "VBO" and "vertex arrays". The new NeHe tutorial use simple vertex arrays but according to another website "oZone3D.Net" you can get huge performance boosts through the use of VBO's.

Share this post

Link to post
Share on other sites
Read the OpenGL Specifications. Section 2.9 explains the difference between vertex data arrays and buffer objects:
The vertex data arrays described in section 2.8 are stored in client memory. It is sometimes desirable to store frequently used client data, such as vertex array and pixel data, in high-performance server memory. GL buffer objects provide a mechanism that clients can use to allocate, initialize, and render from such memory.

Thus, VBOs are faster specially for static objects.

ps. The specification also includes a list of deprecated features.

Share this post

Link to post
Share on other sites
Original post by havok4567
The new NeHe tutorial use simple vertex arrays but according to another website "oZone3D.Net" you can get huge performance boosts through the use of VBO's.

Oh, sorry, I thought VOBs were demonstrated too in the new NeHe lessons.

Typically, vertex arrays in one form or another is used in combination with VBOs. In fact, the only difference from using just vertex arrays and vertex arrays + VBOs is simply that instead of sending the geometry to the GPU you tell the GPU where in memory it allready is (inside the vbo). Like a display list, a VBO simply moves the data to the video RAM.

Using vertex arrays over imidiate mode (glBegin()/glEnd()) is *a lot* faster. Adding VBO's speeds things up even further (in my own engine, using VBOs speeds things up by 300%+ when using VBOs + vertex arrays, as opposed to just using vertex arrays).

It's relatively straight-forward to implement VBOs, even more so if you're allready using vertex arrays. Detailed explainations can be found here:

Share this post

Link to post
Share on other sites
Awesome, thanks guys, the songho link is really useful. So I think i've caught up somewhat in terms of what i *need* to learn. Just need to start implementing this stuff.

Any chance someone has some really basic code kicking around for drawing some simple shape with a simple shader? I'm going to start trying to implement this myself now.

Share this post

Link to post
Share on other sites
Because all the things for using VBO, shaders and so on are ARB extensions, I would recommend you use something like GLee or GLEW if you haven't already so you have all of the extensions included in your project, it can become messy otherwise.

Like someone said earlier for getting going with GLSL lighthouse 3d is about the best there aren't first tutorials are great to see what it takes to compile a shader and link the program.

As for VBO tutorials I found A LOT of the ones you find of google are just confusing I think the one on ozone3d is pretty good though. if you have done any direct3d its very similar to how you do vertex buffers in that.

for what you need to learn it depends what you want to do, if you want to use VBO just work on that and forget about shaders for now, just draw an object first in fixed function then you can think about adding shaders when the VBO is working. Don't work on both of them at once if you are new to it because then you have 2 new things which could potentially cause problems.

Share this post

Link to post
Share on other sites
I'd recommend that you start off with vertex arrays + shaders, and move on to using VBO's afterwards. It's easier to get one thing working at a time. ;)

Also keep in mind what BlackSeeds said about Glee/glew, it makes your life a whole lot easier since you dont have to deal with setting up opengl extensions yourself (vanilla opengl headers are OpenGL 1.1, so newer features such as VBOs and shaders aren't in there).

You can find glee here:
Latest version also supports OpenGL 3.0.

As for shaders, the first lighthouse tutorial is indeed a good starting point. You can find it here:

Share this post

Link to post
Share on other sites
Thanks again, this has been really helpful. Okay I think i'll start on just getting one thing done at a time otherwise i'm just gonna hit a brick wall.

Extensions are kind of new to me but i'm slowly kind of figuring out how they work so i'll check GLEE out. So are there no official releases of the OpenGL header and library files up to version 2.1 or 3.0? Are these extensions necessary to get these recent features?

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  

  • Announcements

  • Forum Statistics

    • Total Topics
    • Total Posts
  • Similar Content

    • By test opty
      Hi all,
      I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?
    • By DejayHextrix
      Hi, New here. 
      I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc.... 
      I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn? 
      How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want? 
      Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn. 
      So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started. 
      Dejay Hextrix 
    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
  • Popular Now