• Advertisement
Sign in to follow this  

OpenGL Advice needed for basic model / entity system

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

Im new to the modern(3.3+) OpenGL, I understand the basics: shaders, VBOs, VAOs, texture objects, units, samplers. I can compile the shaders, fill the VBOs, and draw the object I want. However I dont know how to actually put these together into a "system" where there are lots of different objects(static and moving) ....using different textures, needing different shaders, etc.

 

I understand that this is a huge topic so I dont expect detailed answers(although they are welcome:)), .....I just want a few pointers/basic rules how to go about it.

The scope is a simple 3D app, a few different models, a few instances from each. No streaming, everything is in the RAM. Its a small project but I want to do it in the proper way and I want it to be scaleable. ....so Im not really looking for a "U just have a few models so put everything into one big global...." kind of answer.

 

So here are the questions:

-Do I need different VBOs for each different model? Or do I store them in one VBO and store the start indices.

-How do I draw different instances from the same model? I guess I use instanced rendering, but how do I store/update their model matrices? Lets say some of these objects are moving and some are static. Do I use uniform buffers or VBOs for their model matrices? Do I handle/draw static and moving objects separately?

-I want per-primitive lighting. For moving objects I guess I have to calculate the lighting level in the shader using the surface normals and the light direction. What about static objects? Should I store the precalculated lighting values in a VBO for each object? 

-Basically what data do I store per model / model instance?

class/struct Model{

    VAO,
    ShaderProgram,
    Texture,
    data for the draw function(draw type, start index, etc)

};

class/struct Model Instance{

    modelMatrix

};

Thanks!

 

Share this post


Link to post
Share on other sites
Advertisement

1. Yes, generally you use an individual VBO per model, or even multiple VBO's if you do some kind of spatial partitioning

2. You can use instanced rendering but from my experience, they're not worth it unless you're rendering LOTS (10,000's+) of LOW-POLYCOUNT objects (maybe billboard particle effects?) You don't really even need to store the matrices... Just translate/scale before you render your model, then load identity after

3. I don't think there's "per-primitive" lighting. There is per-vertex or per-pixel. I guess unless you do somehow calculate it yourself, *shrug*

 

Your example Model looks basically correct. Note obviously you will need to support multiple textures if your object has them.

Share this post


Link to post
Share on other sites

-Do I need different VBOs for each different model? Or do I store them in one VBO and store the start indices.

Neither.
1 model = 1 or more meshes = 1 or more VBO’s (or 1 VBO per mesh with start/end indices, but you should save that for when you get more experienced).
I have explained this with a graphic here:
http://lspiroengine.com/?p=96
 

-How do I draw different instances from the same model?

By making a class called a “shared model” with the source vertex data and then make classes called “model instance” that have a pointer to the source data and use the source model’s vertex buffers for rendering themselves at their own transforms etc.


L. Spiro Edited by L. Spiro

Share this post


Link to post
Share on other sites

Thanks! So both of you are saying that it doesnt matter that I have lots of VBOs and VAOs and I make a lot of glDraw... calls(even thousands), more important is not to do state/texture/shader changes. Im I right?

 

"By making a class called a “shared model” with the source vertex data and then make classes called “model instance” that have a pointer to the source data and use the source model’s vertex buffers for rendering themselves at their own transforms etc."

 

Sure. I did something like this in "glBegin-glEnd" openGL.

for( every model)
    for( every model instance)
        if( is in the view)
            draw(....)

My question was, that now with the new stuff, whats a more ideal way to do this. I have no idea how much overhead it means to bind VAOs, do a glDrawElements/drawArrays call, and have 1000+ VBOs.

(Ive read your article BTW, it has lots of useful info, ...going to read more of them.)

 

So still every model needs a separate VBO(or more) and every model-instance needs a separate draw call. Plus I should sort the objects before rendering.

 

"You don't really even need to store the matrices... Just translate/scale before you render your model, then load identity after"

 

So whether the object is static or not, I should calculate the matrix just before rendering and send it with glUniformMatrix? It doesnt sound good.

 

"...then load identity after"

 

I dont get this. It rather sounds like glTranslate,glRotate, draw, glPopMatrix:)

 

 

Share this post


Link to post
Share on other sites


"...then load identity after"
 
I dont get this. It rather sounds like glTranslate,glRotate, draw, glPopMatrix:)

It is.  Don’t do it.

 

I’m not ready right at this moment to explain the details, but if someone else is feel free to chime in.  With your own matrix library you can just send matrices as-is without all the pushing and popping that limited fixed-function OpenGL so much.

 

 

L. Spiro

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