Sign in to follow this  
Blips

OpenGL Possibly corrupt VBO/IBO?

Recommended Posts

Blips    129
I'm currently attempting to get vertex buffer objects to work with interleaved data for indexed triangles.

I've manually confirmed that both the index data and the actual vertex data is correct [i]prior[/i] to being loaded into their appropriate buffer objects. The array holding the index data is simply an array of unsigned shorts. The vertex array is an array of floats with the following format (with each bracket symbolizing a float):

[vect x][vect y][vect z] [texture u][texture v] [norm x][norm y][norm z] [r g b a]

In total, each vertex in array is a series of 9 floats. I have the following offsets and strides as:

[code]
newMesh.vertexOffset = 0;
newMesh.vertexStride = sizeof(GLfloat) * 6;
newMesh.uvOffset = sizeof(GLfloat) * 3;
newMesh.uvStride = sizeof(GLfloat) * 7;
newMesh.normalOffset = sizeof(GLfloat) * 5;
newMesh.normalStride = sizeof(GLfloat) * 6;
newMesh.colorOffset = sizeof(GLfloat) * 8;
newMesh.colorStride = sizeof(GLfloat) * 8;
[/code]

Here is where and how I create the buffer objects. I was originally using glMapBufferOES() but replaced it with a simpler solution in an attempt to find what is wrong. The arrays being passed into the objects are allocated dynamically, but I'm unsure if I should free them after having passed them to the buffer objects.

[code]
glGenBuffers(1, &vertexBufferID);
glBindBuffer(GL_ARRAY_BUFFER, vertexBufferID);
glBufferData(GL_ARRAY_BUFFER, vertexBufferSize, vertexBufferList, GL_DYNAMIC_DRAW);
glBindBuffer(GL_ARRAY_BUFFER, 0);

//creating index buffer object
glGenBuffers(1, &indexBufferID);
glBindBuffer(GL_ELEMENT_ARRAY_BUFFER, indexBufferID);
glBufferData(GL_ELEMENT_ARRAY_BUFFER, indexBufferSize, indexBufferList, GL_STATIC_DRAW);
glBindBuffer(GL_ELEMENT_ARRAY_BUFFER, 0);
[/code]

The buffer sizes have been checked and rechecked and are correct. And here is how I actually go about attempting to render the content. It's probably safe to ignore the texture code block but I included it just in case:

[code]
glPushMatrix();

glTranslatef(tempMeshInstance.x ,tempMeshInstance.y, tempMeshInstance.z);
glRotatef(tempMeshInstance.rotX, 1.0f, 0.0f, 0.0f);
glRotatef(tempMeshInstance.rotY, 0.0f, 1.0f, 0.0f);
glRotatef(tempMeshInstance.rotZ, 0.0f, 0.0f, 1.0f);
glScalef(tempMeshInstance.scaleX, tempMeshInstance.scaleY, tempMeshInstance.scaleZ);

//binding vertices
glBindBuffer(GL_ELEMENT_ARRAY_BUFFER, tempMeshInstance.meshPtr.indexBufferID);
//binding vertex buffer objects
glBindBuffer(GL_ARRAY_BUFFER, tempMeshInstance.meshPtr.vertexBufferID);
//passing the mesh instance data to OpenGL
glMaterialfv(GL_BACK, GL_AMBIENT_AND_DIFFUSE, tempMeshInstance.material);
glVertexPointer(3, GL_FLOAT, tempMeshInstance.meshPtr.vertexStride, ((char *)NULL + (tempMeshInstance.meshPtr.vertexOffset)));
glTexCoordPointer(2, GL_FLOAT, tempMeshInstance.meshPtr.uvStride, ((char *)NULL + (tempMeshInstance.meshPtr.uvOffset)));
glNormalPointer(GL_FLOAT, tempMeshInstance.meshPtr.normalStride, ((char *)NULL + (tempMeshInstance.meshPtr.normalOffset)));
glColorPointer(4, GL_UNSIGNED_BYTE, tempMeshInstance.meshPtr.colorStride, ((char *)NULL + (tempMeshInstance.meshPtr.colorOffset)));

//working with textures
if (tempMeshInstance.meshPtr.textureID != prevTextureID && tempMeshInstance.meshPtr.textureID != 0) {
glBindTexture(GL_TEXTURE_2D, tempMeshInstance.meshPtr.textureID);
//if 2d texturing is disabled, renable it
if (!glIsEnabled(GL_TEXTURE_2D))
glEnable(GL_TEXTURE_2D);
} else if (tempMeshInstance.meshPtr.textureID == 0 && glIsEnabled(GL_TEXTURE_2D))
glDisable(GL_TEXTURE_2D);
prevTextureID = tempMeshInstance.meshPtr.textureID;

//rendering the mesh instance
glDrawElements(tempMeshInstance.meshPtr.renderFormat, tempMeshInstance.meshPtr.indices, GL_UNSIGNED_SHORT, ((char *)NULL + (0)));
//popping the matrix off the stack
glPopMatrix();

//continuing through list
gameObjs = gameObjs.nextNode;
glBindBuffer(GL_ELEMENT_ARRAY_BUFFER, 0);
glBindBuffer(GL_ARRAY_BUFFER, 0);
[/code]

And this is the lovely rendering I'm rewarded with:

[img]http://img204.imageshack.us/img204/7107/img0019o.png[/img]

Which looks nothing like what the actual object used to look like. So in summary, I don't know if the buffer objects are somehow becoming corrupted, or if I'm incorrectly using the buffer objects (strides and offsets?), or if I'm incorrectly creating the buffer objects, but something is clearly wrong.

And clues or hints as to what may be causing this would be more than welcome!

Share this post


Link to post
Share on other sites
Blips    129
[quote name='johnchapman' timestamp='1312954903' post='4847047']
"Stride' should be the same.for each attribite; the size of a whole vertex (sizeof(float) *9 in your case.

Also, how are you counting RGBA as one float?
[/quote]

Oh I thought stride was spacing in bytes between two like components (so the bytes between two repetitions of normal data for example). I tried treating the one float for the RGBA data as 4 separate bytes, and hoped that OpenGL would be able to work with it given I've specified color to be unsigned bytes. There's a good chance I'll have to change it I'm guessing though.

I'll try making your suggested changes.

Share this post


Link to post
Share on other sites
mhagain    13430
[quote name='Blips' timestamp='1312958072' post='4847054']Oh I thought stride was spacing in bytes between two like components (so the bytes between two repetitions of normal data for example).[/quote]

It is, but your understanding of the effect that has on your params seem to be incorrect. If you think about it, the normal data will be at the same offset for each vertex (in fact every component of the vertex will be at the same offset for each vertex - position at 0, texcoords at 12, etc) so the difference between two vertexes will always be the size of your vertex struct.

[quote name='Blips' timestamp='1312958072' post='4847054']I tried treating the one float for the RGBA data as 4 separate bytes, and hoped that OpenGL would be able to work with it given I've specified color to be unsigned bytes. There's a good chance I'll have to change it I'm guessing though.

I'll try making your suggested changes.[/quote]

I'd suggest not trying anything fancy when you're getting something new working for the first time. Do it the slow/more storage/predictable way instead. There's too much going on in this code and you need to be able to isolate errors to specific causes.

Share this post


Link to post
Share on other sites
Brother Bob    10344
[quote name='mhagain' timestamp='1312968409' post='4847089']
[quote name='Blips' timestamp='1312958072' post='4847054']Oh I thought stride was spacing in bytes between two like components (so the bytes between two repetitions of normal data for example).[/quote]

It is, but your understanding of the effect that has on your params seem to be incorrect. If you think about it, the normal data will be at the same offset for each vertex (in fact every component of the vertex will be at the same offset for each vertex - position at 0, texcoords at 12, etc) so the difference between two vertexes will always be the size of your vertex struct.
[/quote]
Just clarifying here, because the word "between" is often the source of the confusion when misunderstanding the stride. The stride is [i]the distance from the start of one attribute to the start of the next consecutive entry[/i], not the "empty" space between two consecutive attributes (which would be from the end of one to the beginning of the next). If you have a tightly packed array of an interleaved vertex structure, the stride for all attributes is, as mhagain said, simply the size of the vertex itself; no need for fancy calculations with the individual attributes.

Share this post


Link to post
Share on other sites
mhagain    13430
[quote name='Brother Bob' timestamp='1312969390' post='4847094']Just clarifying here, because the word "between" is often the source of the confusion when misunderstanding the stride. The stride is [i]the distance from the start of one attribute to the start of the next consecutive entry[/i], not the "empty" space between two consecutive attributes (which would be from the end of one to the beginning of the next). If you have a tightly packed array of an interleaved vertex structure, the stride for all attributes is, as mhagain said, simply the size of the vertex itself; no need for fancy calculations with the individual attributes.[/quote]

Said it better than I did.

It's actually easier if you use a struct for your vertexes rather than a float array - you'll see the layout in your code clearer, reduces potential for error, offsets are just a small bit of pointer arithmetic, and you can use sizeof (mystruct) for your stride param.

Share this post


Link to post
Share on other sites
Blips    129
[quote name='mhagain' timestamp='1312991821' post='4847194']
[quote name='Brother Bob' timestamp='1312969390' post='4847094']Just clarifying here, because the word "between" is often the source of the confusion when misunderstanding the stride. The stride is [i]the distance from the start of one attribute to the start of the next consecutive entry[/i], not the "empty" space between two consecutive attributes (which would be from the end of one to the beginning of the next). If you have a tightly packed array of an interleaved vertex structure, the stride for all attributes is, as mhagain said, simply the size of the vertex itself; no need for fancy calculations with the individual attributes.[/quote]

Said it better than I did.

It's actually easier if you use a struct for your vertexes rather than a float array - you'll see the layout in your code clearer, reduces potential for error, offsets are just a small bit of pointer arithmetic, and you can use sizeof (mystruct) for your stride param.
[/quote]

Yeah I'm already working on changing the small program I wrote converting Wavefront files to binary files to use structs rather than an array of floats. Then I'll do the same changes to the actual game!

Thanks guys for help and clarification. It's really appreciated.

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++.
      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.
  • Popular Now