Sign in to follow this  
CombatWombat

OpenGL Buffers, Drawing many of the same object

Recommended Posts

CombatWombat    673
Hello,

I am a convert from opengl...

I am having some trouble developing an overall strategy for how to implement Index and Vertex Buffers for a particular application. All the tutorials I find focus on one or two objects in a scene.

Say, for the sake of argument, that my scene consists or 1000 cubes, all of identical size, but which will all be at different locations and orientations. These locations and orientations change every frame. Texture and lighting will also likely vary between cubes. I gather that many calls to drawPrimitive is a bad thing. Therefor it sounds like all the triangles that make up these many cubes should be batched together into a buffer. Additionally, cubes may be "joined together" such that drawing their adjoining faces is unnecessary.

So option 1, looks like:
Make a Vertex/Index Buffer to store the dimensions of a single cube. Write this to the GPU, since this will not change.

for (loop through cubes)
Call Translate/Orient Matrix Transforms
Draw A cube

Option 1 sounds terrible since it makes a ton of draw calls, but how else can I handle the transformations since they occur every frame?

Option 2
Transform all model-space verticies into worldspace.
Cull faces that are touching each other, as these are not necessary to draw.
Batch verticies based on texture.
Write them to vertex buffers.
Draw cubes, only stopping to switch texture groups.

This seems better, except now the CPU is doing a lot of work for the transforms ahead of time.

I'm not really sure how to proceed, as the architecture of the problem seems like it could become very convoluted if I do not have a clear plan ahead of time.

Thank you for any assistance!

Share this post


Link to post
Share on other sites
turch    590
Look into instancing. [url="http://msdn.microsoft.com/en-us/library/ee418269%28v=vs.85%29.aspx"]This[/url] has an overview of both hardware and software instancing and the benefits and limitations of both.

Share this post


Link to post
Share on other sites
NewtonsBit    102
Both options you've listed will probably CPU issues. With 1000 draw calls, your FPS will drop significantly. And if you're doing CPU transforms on 1000 you're also going to be running slow. If you're only moving a small number of the cubes each frame then your best bet is to use one vertex buffer that contains pre-transformed vertices. You can then set just the vertices that change each frame.

Share this post


Link to post
Share on other sites
CombatWombat    673
[quote name='NewtonsBit' timestamp='1306714327' post='4817289']
Both options you've listed will probably CPU issues. With 1000 draw calls, your FPS will drop significantly. And if you're doing CPU transforms on 1000 you're also going to be running slow. If you're only moving a small number of the cubes each frame then your best bet is to use one vertex buffer that contains pre-transformed vertices. You can then set just the vertices that change each frame.
[/quote]

Thank you both for your replies.

I am looking into Instancing, as the SDK sample is actually exactly what I need. Now I just need to understand it. I still do not really understand how I encode the data that is changing (translate and rotate transforms), into a FVF structure. I think that is what is required for this approach to work, correct? I will research this more.

It is entirely possible for [i]all[/i] of my cubes to be moving at any given frame, so I think keeping a separate buffer of static objects may not really help me.

Share this post


Link to post
Share on other sites
pekarn    173
[quote name='CombatWombat' timestamp='1306726462' post='4817349']
[quote name='NewtonsBit' timestamp='1306714327' post='4817289']
Both options you've listed will probably CPU issues. With 1000 draw calls, your FPS will drop significantly. And if you're doing CPU transforms on 1000 you're also going to be running slow. If you're only moving a small number of the cubes each frame then your best bet is to use one vertex buffer that contains pre-transformed vertices. You can then set just the vertices that change each frame.
[/quote]

Thank you both for your replies.

I am looking into Instancing, as the SDK sample is actually exactly what I need. Now I just need to understand it. I still do not really understand how I encode the data that is changing (translate and rotate transforms), into a FVF structure. I think that is what is required for this approach to work, correct? I will research this more.

It is entirely possible for [i]all[/i] of my cubes to be moving at any given frame, so I think keeping a separate buffer of static objects may not really help me.
[/quote]


Yes, you have to encode the instance data into your vertex buffer. Usually you would store the position and the forward and up vectors for each instance. As far as the FVF goes just put them as texcoords. Also I would look into using vertex declarations instead of FVF since it gives you much more control over how you store your data.

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  

  • Similar Content

    • 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?
    • By Kjell Andersson
      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.
    • By markshaw001
      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!
    • By Adrianensis
      Hi everyone, I've shared my 2D Game Engine source code. It's the result of 4 years working on it (and I still continue improving features ) and I want to share with the community. You can see some videos on youtube and some demo gifs on my twitter account.
      This Engine has been developed as End-of-Degree Project and it is coded in Javascript, WebGL and GLSL. The engine is written from scratch.
      This is not a professional engine but it's for learning purposes, so anyone can review the code an learn basis about graphics, physics or game engine architecture. Source code on this GitHub repository.
      I'm available for a good conversation about Game Engine / Graphics Programming
  • Popular Now