Sign in to follow this  

OpenGL OpenGL 4 and Index Buffer

Recommended Posts

Atemu    263



I'm following a tutorial about OpenGL 4 and the author always use glDrawArrays (with simple shape) but I'm wondering how he could draw complex shape without using any Index Buffer ?

Share this post

Link to post
Share on other sites
haegarr    7372

glDrawArrays can be used for meshes of any complexity. Indexing is just a vehicle that helps in certain situations to improve performance. A code snippet w/o indexing looks less cluttered, so it may be meant to be better suited for demonstration purposes as occurs in such a tutorial (assuming that the attention is on something else, of course).

Share this post

Link to post
Share on other sites
richardurich    1352

The only thing you wind up doing if you don't have an index buffer is repeating vertex data. Unless that is causing your program to bottleneck, it really doesn't matter that you're repeating the vertex data. Index buffers just add a layer of indirection like pointers do for normal code.


Whether you use index buffers or duplicate data a bit, it probably won't matter. Odds are pretty good you won't meaningfully impact your end result either way since you're probably not trying to make a AAA title. If you ever do need to optimize, you might just do it in different places for each approach.


Most people don't even have noticeable performance issues when using TRIANGLE_LIST or such until they are well into development, and in that situation you're talking almost 2/3 of the data being duplicated for no benefit.

Share this post

Link to post
Share on other sites
Kaptein    2224

if you are using complex models, and they are indexable - use it

if you have a flat-ish world that uses normals that are weighted - use it

otherwise, just stay away from indexing

if your meshes aren't indexable to a larger degree, you will likely just incur a performance loss


the thing that matters the most is reusing indices to the maximum degree, and that is something you really want a mesh generator for

you can also google the subject as there are various methods to generating heightmapped terrain with varying degrees of effectiveness vs generation speed


in the end it doesn't really matter much.. maybe its 15 fps at some extreme


also, use a profiler if you can :) you'd be surprised at what REALLY chopped your fps in half :D

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 povilaslt2
      Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).
    • By ZeldaFan555
      Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
      Skype: Mangodoor408
    • 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?
    • 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++.
      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.
  • Popular Now