• Advertisement
Sign in to follow this  

OpenGL VBO problem

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

For the past few days I've been trying to get a a square to render using VBOs but, unfortunately, have not been able to. So, any help I could get would be much appreciated. Sorry in advance for this post being so long: I wanted to give enough information on the problem. Here's the problem: The square isn't rendering. I'm trying to render it using the primitive type GL_TRIANGLES. Of course, it has four vertices for the corners and 2 indicies to specify the top left triangle and bottom right triangle. Here's what I've done so far to try to solve the problem myself: I've compared the code I'm writing now to the code I've written before where I actually used VBOs and was successful. I've checked out several threads on VBOs on this forum and others. I've checked out several sites that had tutorials on VBO's and read the vertex array, display lists and VBOs chapter in the "OpenGL SuperBible" book. I've also been comparing my code to the VBO code samples in that book and on the sites with the tutorials. I've also run my program through the program gDEBugger and used the OpenGL function glGetError(). You guys are my last resort and I figure there must be something small that I'm missing that some fresh eyes would see. First, here's the output of gDEBugger's OpenGL calls history HTML log file. I've split it up into the setup and rendering to make it easier to read. I've also removed some of the calls that I thought were not related or useless; the comments are mine: // SETUP ... ... glGenBuffers(1, 0xE7648C) // generate buffer for vertices glGenBuffers(1, 0xE764EC) // generate buffer for indices glGenBuffers(1, 0xE7655C) // generate buffer for tex. coords: not used right now glBindBuffer(GL_ARRAY_BUFFER, 1) glBufferData(GL_ARRAY_BUFFER, 48, 0xE765B8, GL_STATIC_DRAW) glBindBuffer(GL_ELEMENT_ARRAY_BUFFER, 2) glBufferData(GL_ELEMENT_ARRAY_BUFFER, 24, 0xE76728, GL_STATIC_DRAW) ... ... // RENDERING glClear(0x4100) glPushMatrix() glMultMatrixf((1.00, 0.00, -0.00, 0.00) (-0.00, 1.00, -0.00, 0.00) (0.00, 0.00, 1.00, 0.00) (0.00, 0.00, 0.00, 1.00)) glTranslatef(-0.00, -0.00, -0.00) glTranslatef(0.00, 0.00, -2.00) // here's the VBO specific rendering: glEnableClientState(GL_VERTEX_ARRAY) glBindBuffer(GL_ARRAY_BUFFER, 1) glVertexPointer(3, GL_FLOAT, 0, 0x0) glBindBuffer(GL_ELEMENT_ARRAY_BUFFER, 2) glDrawElements(GL_TRIANGLES, 6, GL_UNSIGNED_INT, 0x0) glDisableClientState(GL_VERTEX_ARRAY) glBegin(GL_LINES) // drawing a line for testing purposes glVertex3f(0.50, 0.00, 0.00) glVertex3f(-0.50, 0.00, 0.00) glEnd() glBegin(GL_TRIANGLES) // used this to check winding order: it was fine glEnd() glPopMatrix() glGetError() wglSwapBuffers(0x1601202D) Here's my init code where I create the vertex and index buffers and add in the data:
void InitContextGL(void)
{
	glClearColor(0.0f, 0.0f, 1.0f, 1.0f);
	
        // the buffers are being generated in the constructor of CModel (see below).
	testModel = new CModel;

	// adding vertices to the vertex list
	const float fHalfWidth = 1.0f;
	const float fHalfHeight = 1.0f;
	const float fDepth = 2.0f;
	testModel->GetVertexData()->GetVertexList().reserve(4);
	testModel->GetVertexData()->GetVertexList().push_back(new tVertex3f(-fHalfWidth, fHalfHeight, -fDepth)); // top left 
	testModel->GetVertexData()->GetVertexList().push_back(new tVertex3f(-fHalfWidth, -fHalfHeight, -fDepth)); // bottom left
	testModel->GetVertexData()->GetVertexList().push_back(new tVertex3f(fHalfWidth, -fHalfHeight, -fDepth)); // bottom right
	testModel->GetVertexData()->GetVertexList().push_back(new tVertex3f(fHalfWidth, fHalfHeight, -fDepth)); // top right
	testModel->GetVertexData()->SetData(GL_STATIC_DRAW);

	// creating a square using indicies
	testModel->GetIndexData()->GetIndexList().reserve(2);
	testModel->GetIndexData()->GetIndexList().push_back(new tIndex3n(3,0,1)); // top left triangle
	testModel->GetIndexData()->GetIndexList().push_back(new tIndex3n(3,1,2)); // bottom right triangle
	testModel->GetIndexData()->SetData(GL_STATIC_DRAW);
}


Here's the rendering specific code:

void RenderFrame(void)
{
	Input(); // getting input

	glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);

	glPushMatrix();
	{
		camera.ApplyCameraTransform();

		glTranslatef(0.0f, 0.0f, -2.0f);
		testModel->Render(); // this is where the VBO data is supposed
                                     // to be rendering (see below for
                                     // definition).
		
		// drawing a line for test purposes (removed)
		...
		
		// rendering a white square to test winding order: it worked
                // fine. (removed)
		...
	}
	glPopMatrix();

	// this function checks if there was an OpenGL error using glGetError and displays
	// that error as a windows message box
	CheckForOpenGLError(__FILE__, __LINE__);
}

void CModel::Render()
{
	glEnableClientState(GL_VERTEX_ARRAY);

	m_VertexData->PrepareForRender();
	
	m_IndexData->Render();

	glDisableClientState(GL_VERTEX_ARRAY);
}


You may be wondering where I'm calling glGenBuffers and what testModel->SetData(), m_VertexData->PrepareForRender(), and m_IndexData->Render() do. Here they are:
CModelData::CModelData()
{
        // CVertexData and CIndexData (below) are derived off of CModelData, so 
        // they automatically get a buffer.
	...
	glGenBuffers(1, &m_uVertexBufferHandle);
}

void CModelData::BindBuffer()
{
	glBindBuffer(GetTarget(), GetVertexBufferHandle());
}

...

void CVertexData::SetData(GLenum usage)
{
	BindBuffer();
        // tVertex3f is a struct that contains an array of 3 floats
	glBufferData(GetTarget(), sizeof(tVertex3f) * m_VertexList.size(), &m_VertexList.front(), usage);
}

void CVertexData::SetVertexPointer()
{
	glVertexPointer(3, GL_FLOAT, 0, 0);
}

void CVertexData::PrepareForRender()
{
	BindBuffer();
	SetVertexPointer();
}

...

void CIndexData::Render()
{
	BindBuffer();
	glDrawElements(GetPrimitiveType(), GetNumElementsToRender(), GetTypeOfValue(), GetBufferDrawOffset());
}

void CIndexData::SetData(GLenum usage)
{
	BindBuffer();
        // tIndex3n is a struct that contains an array of 3 integers
	glBufferData(GetTarget(), sizeof(tIndex3n) * m_IndexList.size(), &m_IndexList.front(), usage);
	SetNumElementsToRender(static_cast<GLsizei>(m_IndexList.size()) * GetNumIndexComponents());
}


Sorry if the code isn't very helpful with all of the function calls and it being split up so much (I'm going to be fixing it up). I'm hoping the gDEBugger log file will help if you want to know what values are getting passed to the OpenGL functions. Edit: removed glEnableClientState(GL_INDEX_ARRAY) and glDisableClientState(GL_INDEX_ARRAY) to reflect a change that V-man suggested [Edited by - Switch0025 on November 24, 2007 7:46:02 PM]

Share this post


Link to post
Share on other sites
Advertisement
Remove
glEnableClientState(GL_INDEX_ARRAY)
glDisableClientState(GL_INDEX_ARRAY)
since you aren't using color index arrays.

Share this post


Link to post
Share on other sites
Quote:
Original post by V-man
Remove
glEnableClientState(GL_INDEX_ARRAY)
glDisableClientState(GL_INDEX_ARRAY)
since you aren't using color index arrays.


GL_INDEX_ARRAY is used for index arrays (for vertices) not "color index arrays" (I believe your talking about GL_COLOR_ARRAY) as specified by the OpenGL documentation:
Quote:

GL_INDEX_ARRAY If enabled, the index array is
enabled for writing and used during
rendering when glDrawArrays or
glDrawElements is called. See
glIndexPointer.

Share this post


Link to post
Share on other sites
No you are wrong. V-man is 100% correct. glIndexPointer is for color indexes.

Check the official documentation and see for yourself.

Share this post


Link to post
Share on other sites
Then I stand corrected. Thanks for the correction; I misunderstood the documentation. I have edited my code and my original post to reflect the change. However, my original problem still persists.

Share this post


Link to post
Share on other sites
hey

Firstly, I don't know if it's such a good idea to have removed things from the log file, hehe. What if something you removed was a key to identifying the problem? But i dunno, hehe.

Anyhows I think you should try unbinding your VBO's after you create them, and also after you render. Well I remember having probs with my VBO's, and I found things to work when I unbinded them :). I forget the exact details now though :\. I'm not sure what lead me to try this, I forget if I read about doing this from somewhere, or if it was just something I thought to try myself.

Incase you don't know, to unbind you just call glBindBuffer(), with the buffer ID as zero.

I also recommend you checkout http://www.spec.org/gwpg/gpc.static/vbo_whitepaper.html

edit
Other things to think about... are they being drawn inside the screen? have you tried drawing as points? is lighting enabled? (I think you should disable GL_LIGHTING for testing, and make sure to set your vertices color different to background) are textures enabled (again I think you should disable GL_TEXTURE_2D for testing). Hmm, maybe you should also try drawing with glBegin()/glEnd() in your render function???

cya

[Edited by - yosh64 on November 24, 2007 10:02:22 PM]

Share this post


Link to post
Share on other sites
Quote:
Original post by yosh64
Firstly, I don't know if it's such a good idea to have removed things from the log file, hehe. What if something you removed was a key to identifying the problem? But i dunno, hehe.


I agree, but I didn't want to make my post any longer then it was and most of it was wglGetProcAddress() calls and repeats of the rendering section.

I tried all of your suggestions but unfortunately I was unable to get it rendering. Putting the rendering code in between glBegin() and glEnd() causes an opengl error (that I "caught" using glGetError). The website you gave was one of the websites I checked out before I posted here but I'll have to go over it a little bit more. Thanks for your help, yosh64.

Edit: spelling mistakes

Share this post


Link to post
Share on other sites
Hey, I figured out the problem so if anyone else has this problem here's what happened and how to solve it:

The vertex list I had was holding pointers to the vertex/index structures and not the vertex/index structures themselves.

So I had this:

std::vector<tVertex3f*> m_VertexList; // bad

when it should have been:

std::vector<tVertex3f> m_VertexList; // good

BTW, tVertex3f is a structure that holds the X,Y,Z coordinate for a vertex.

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