• Advertisement
Sign in to follow this  

OpenGL Stack Overflows And Disappearing DisplayLists

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

Hello, I'm working on an editor to place nature on landscapes. The Idea is kinda like billboarding, select an texture of some small plant/grass, and draw quad across the landsscape. This means many quads. Apart from framerate related problem; I got an stackoverflow when I projected about 20000 quads. So I thought up the following; - At each click start drawing a display list - the displaylist contains the 'new billboards' - start drawing a new display list - draw the old display list - draw the new display list toghether they contain all the nature which is added at each click. Still stackoverflow. (also got rid of pushMatrix() and popMatrix(), the overflow shifted in the code) So the problem is not in drawing, this goes well at each click, but in adding the nature elements in a linear list. Now I have a class with a base-list-element. from there I keep adding new items through new nextpointers in the list-elements. The stack overflow seems to come from very long recursive Next(list-item) calls, but definitily not inifinite. I know this is a 'general problem', but what is the main approach to making this work, calling things more than 30000+ times ?? But my openGl problem is yet another. The drawing part goes fine, but when about 70000 quads are drawn within the mainlist, it just disappears,nothing is projected anymore. a bit of code to specify; void StartCache ( ) { Cache_List = glGenLists(1); glNewList ( Cache_List, GL_COMPILE ); } void StopCache ( ) { glEndList(); } void JoinLists ( ) { int JoinedList = glGenLists(1); glNewList ( JoinedList, GL_COMPILE ); glCallList ( BoardList ); // boardlist is the displaylist, uptill now glCallList ( Cache_List ); glEndList ( ); BoardList = JoinedList; } void AddStuff () { StartCache( ); DrawStuff ( ); StopCache ( ); JoinLists ( ); glCallList( BoardList ); } So is there a limit to what a Display List can contain, which seems logical enough, and what is it, 70000+\-??? And is the problem here also created through stacking errors ?? Well, the basic question is, how the fudge do I project and add a hell of a lot of stuff to my scene ?

Share this post

Link to post
Share on other sites
70000 quads is best done with an array kept either on the card or in memory, depending on how you update it, or maybe using instancing or any of several other techniques.

Read up on vertex arrays and also VBOs, at least.

If the list runs out of memory, the error state will be set to GL_OUT_OF_MEMORY. Check for errors at glEndList();

I don't see any queries that will give how big those can be. I assume that this is because different operations take different amounts of memory.

Share this post

Link to post
Share on other sites
I know all aout vertex arrays. VBO's not yet, but I'll take a crack at them.
But still, it doesn't help with the stack overflow, because the vertex array data or VBO still has to be set. It's then when the problem presents otself. how to process that many numbers into an array??
and besides, my stuff is static, so lists serve my purposes best.
Arrays are reserved for dynamic data.
How do modern games project so many vertices? - apart from te real question, how to do it so fast as possible?

Share this post

Link to post
Share on other sites
You should brush up on your GL basics - stack overflows here refer to the projection/modelview/texture matrix stacks within OpenGL's state machine (most probably the modelview), the vertex count is irrelevant. The minimum value for these is two for projection and texture, and 32 for modelview.

Check all occurances of pushMatrix and make sure they've all got a corresponding popMatrix. Also check that you're not exceeding the matrix depth at any given point (eg. more than 32 nested transformations, although thats unlikely). At the very least post what your DrawStuff function contains, as your problem likely lies within it.

(Also, it looks like you're creating lots of new display lists and discarding old ones without deleting them. This is sloppy and will likely cause problems later).

Share this post

Link to post
Share on other sites
know my basics, as said, no matrix pushes or pops within the code anymore.
checked it, the problem shifted.
I am referring to the more general 'stack overflow'.
as to opengl, I asked another question.
Also, Im only creating 2 display lists at the time, and then join them.
deleting them seems only redundant to mention.
the drawstuff is, logically;
Just drawing a quad.

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