# OpenGL Advice needed for basic model / entity system

## Recommended Posts

Aliii    1456

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,
Texture,
data for the draw function(draw type, start index, etc)

};

class/struct Model Instance{

modelMatrix

};

Thanks!

##### Share on other sites
3TATUK2    714

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 on other sites
L. Spiro    25622

-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 on other sites
Aliii    1456

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.

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

##### Share on other sites
L. Spiro    25622

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

## Create an account

Register a new account

• ### Similar Content

• By tyhender
Hello, my name is Mark. I'm hobby programmer.
So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine).
And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
Sorry for late replies.
I mostly give more information when people PM me,but this post is REALLY short,even for me =D
So here's few more points:
Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me.

• By Zaphyk
I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?

• I'm trying to get some legacy OpenGL code to run with a shader pipeline,
The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
I've got a version 330 vertex shader to somewhat work:
#version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
Question:
What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?

Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.

• Hi i am new to this forum  i wanted to ask for help from all of you i want to generate real time terrain using a 32 bit heightmap i am good at c++ and have started learning Opengl as i am very interested in making landscapes in opengl i have looked around the internet for help about this topic but i am not getting the hang of the concepts and what they are doing can some here suggests me some good resources for making terrain engine please for example like tutorials,books etc so that i can understand the whole concept of terrain generation.

• By KarimIO
Hey guys. I'm trying to get my application to work on my Nvidia GTX 970 desktop. It currently works on my Intel HD 3000 laptop, but on the desktop, every bind textures specifically from framebuffers, I get half a second of lag. This is done 4 times as I have three RGBA textures and one depth 32F buffer. I tried to use debugging software for the first time - RenderDoc only shows SwapBuffers() and no OGL calls, while Nvidia Nsight crashes upon execution, so neither are helpful. Without binding it runs regularly. This does not happen with non-framebuffer binds.
GLFramebuffer::GLFramebuffer(FramebufferCreateInfo createInfo) { glGenFramebuffers(1, &fbo); glBindFramebuffer(GL_FRAMEBUFFER, fbo); textures = new GLuint[createInfo.numColorTargets]; glGenTextures(createInfo.numColorTargets, textures); GLenum *DrawBuffers = new GLenum[createInfo.numColorTargets]; for (uint32_t i = 0; i < createInfo.numColorTargets; i++) { glBindTexture(GL_TEXTURE_2D, textures[i]); GLint internalFormat; GLenum format; TranslateFormats(createInfo.colorFormats[i], format, internalFormat); // returns GL_RGBA and GL_RGBA glTexImage2D(GL_TEXTURE_2D, 0, internalFormat, createInfo.width, createInfo.height, 0, format, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); DrawBuffers[i] = GL_COLOR_ATTACHMENT0 + i; glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0 + i, textures[i], 0); } if (createInfo.depthFormat != FORMAT_DEPTH_NONE) { GLenum depthFormat; switch (createInfo.depthFormat) { case FORMAT_DEPTH_16: depthFormat = GL_DEPTH_COMPONENT16; break; case FORMAT_DEPTH_24: depthFormat = GL_DEPTH_COMPONENT24; break; case FORMAT_DEPTH_32: depthFormat = GL_DEPTH_COMPONENT32; break; case FORMAT_DEPTH_24_STENCIL_8: depthFormat = GL_DEPTH24_STENCIL8; break; case FORMAT_DEPTH_32_STENCIL_8: depthFormat = GL_DEPTH32F_STENCIL8; break; } glGenTextures(1, &depthrenderbuffer); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); glTexImage2D(GL_TEXTURE_2D, 0, depthFormat, createInfo.width, createInfo.height, 0, GL_DEPTH_COMPONENT, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, depthrenderbuffer, 0); } if (createInfo.numColorTargets > 0) glDrawBuffers(createInfo.numColorTargets, DrawBuffers); else glDrawBuffer(GL_NONE); if (glCheckFramebufferStatus(GL_FRAMEBUFFER) != GL_FRAMEBUFFER_COMPLETE) std::cout << "Framebuffer Incomplete\n"; glBindFramebuffer(GL_FRAMEBUFFER, 0); width = createInfo.width; height = createInfo.height; } // ... // FBO Creation FramebufferCreateInfo gbufferCI; gbufferCI.colorFormats = gbufferCFs.data(); gbufferCI.depthFormat = FORMAT_DEPTH_32; gbufferCI.numColorTargets = gbufferCFs.size(); gbufferCI.width = engine.settings.resolutionX; gbufferCI.height = engine.settings.resolutionY; gbufferCI.renderPass = nullptr; gbuffer = graphicsWrapper->CreateFramebuffer(gbufferCI); // Bind glBindFramebuffer(GL_DRAW_FRAMEBUFFER, fbo); // Draw here... // Bind to textures glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, textures[0]); glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, textures[1]); glActiveTexture(GL_TEXTURE2); glBindTexture(GL_TEXTURE_2D, textures[2]); glActiveTexture(GL_TEXTURE3); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); Here is an extract of my code. I can't think of anything else to include. I've really been butting my head into a wall trying to think of a reason but I can think of none and all my research yields nothing. Thanks in advance!

• 16
• 15
• 16
• 10
• 18