• Advertisement
Sign in to follow this  

OpenGL Current OpenGL

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

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
Advertisement
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:

http://nehe.gamedev.net/wiki/NewLessons.ashx

For shaders (GLSL), I highly recommend Lighthouse3d:

http://www.lighthouse3d.com/opengl/

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:
Quote:
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
Quote:
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:
http://www.songho.ca/opengl/gl_vbo.html
http://www.opengl.org/wiki/index.php/VBO

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:
http://elf-stone.com/glee.php
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:
http://www.lighthouse3d.com/opengl/glsl/index.php?ogloverview

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
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?
      Regards,
      LifeArtist
    • 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