• Advertisement
Sign in to follow this  

OpenGL Crash when attempting to wrap a VBO with a Display List

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

Ok, before I start:
1. Yes, I know that display lists are deprecated, and will only be supported through manufacturer specific extensions in the future.

2. Yes, I know that some of you think this is completely unnecessary, and I agree to some extent, but this is school stuff, and I lost a small fraction of my grade because I couldn't do this, *YET OTHERS COULD*.

3. I use an object called "sdata", which contains:
- a VBO id "vertices" (already populated and working when I try to draw/construct the display list)
- an IBO id "indices" (already populated and working)
- a Display List id "vlist", which is where I want to put the result in.

As with the title, I'm trying to shove a VBO (with corresponding IBO) into a Display List. The following code works properly in my render step (AND does compile in my construction step):

//I need the following arrays:
//indices for the VBO, supplied as CORRECTION: an array of integer.

int curr_indice_count = sdata.indice_count;
//I keep a count of my indices when I construct the geometry.
int curr_xtessel = sdata.tesselx;
//I'm drawing based on the number of stacks. I do keep slices around but my
//current implementation doesn't use that value to draw.
int index_offset = 0; //a buffer object starts from position 0, once bound.
int index_eachrow = (curr_xtessel +1) *2; //each row has this amount of vertices.

//bind my VBO and IBO.
glBindBuffer(GL_ARRAY_BUFFER, sdata.vertices);

unsigned vertsize = sizeof(Vertex); //precalculated size of a Vertex struct.
unsigned elemsize = 3* sizeof(float); //precalculated size of each element of a vertex.

//set pointers. I should NOT need to set a pointer for my IBO, that's what
//Element_Array_Buffer does.
glVertexPointer(3, GL_FLOAT,
vertsize, 0);
(GLvoid*) elemsize);
glTexCoordPointer(2, GL_FLOAT,
(GLvoid*)(4 * elemsize));

unsigned usize = sizeof(unsigned); //precalculated size of unsigned.

//This is where I actually draw the geometry.
while (index_offset < curr_indice_count)
((char*)0 + index_offset * usize));
index_offset += index_eachrow;

//unbind from VBO

//disable client states.

However, the minute I try something like this in my construction step:

sdata.vlist = glGenLists(1);
glNewList(sdata.vlist, GL_COMPILE);



The application crashes with an access violation, on the VERY FIRST CALL to

This occurs no matter where I position my glGenList, glNewList and glEndList statements, or where I read the indices as a GL_UNSIGNED_INT or a GL_UNSIGNED_SHORT.

I have another Display List implementation in the program that uses non-VBO Vertex Arrays, and it works fine. So much so that currently I'm under the impression the Display List code is IGNORING my calls to glBindBuffer() and thinks I'm trying to use a Vertex Array.

I've already updated to the latest builds of GLEW, to no avail. My card is an Nvidia 9500GT, and the drivers are straight from the manufacturer (XFX) so there should be no issues with display list or basic openGL support.

I've tried looking at the implementations of my fellows and I can see nothing that I've missed (as far as I can tell). Is there anyone who has successfully pulled this stunt, who can point me in the right direction? I've been scratching my head over this for a few weeks now.

Thanks in advance.

Edit: Just a note that glGetError() at any point in this code returns 0 (absolutely nothing wrong).

[Edited by - Ultimate Chicken on July 18, 2010 3:04:27 AM]

Share this post

Link to post
Share on other sites
Can you draw the vertex arrays successfully without putting them in a display list?

It should be ignored in RGB color mode, but you enable the index color array but don't set it's pointer. The index color array is not for indexing vertices (that's what element buffer arrays are used for), but the glColorPointer equivalent for indexed color mode, as opposed to the RGB color mode. Even if it shoulnd't affect anything in this case, don't enable the index color array.

Share this post

Link to post
Share on other sites

It should be ignored in RGB color mode, but you enable the index color array but don't set it's pointer. The index color array is not for indexing vertices (that's what element buffer arrays are used for), but the glColorPointer equivalent for indexed color mode, as opposed to the RGB color mode. Even if it shoulnd't affect anything in this case, don't enable the index color array.

Ok, that's one hell of a head slapping two weeks. I was under the impression that I needed GL_INDEX_ARRAY for the IBO - turns out that the call to glEnableClientState(GL_INDEX_ARRAY) was the problem all this time, because I misinterpreted its purpose. Silly noob mistake >.<

I don't have color attached to my Vertex struct (they're stored as separate Materials), so I didn't see the need to set a glColorPointer).

Yes, I am able to draw in Vertex Array mode with the same code I used for the Vertex Array part. Looks like I don't need it anymore, but I'll keep it for legacy systems support.

Thanks! :)

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?
    • 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