Sign in to follow this  
nrgyzer

OpenGL Display lists very slow

Recommended Posts

Hey guys,

I've already worked with display lists and I always saw that they are boosts my SDL-OpenGL applications. But... now, I've started a new project. When I draw my scene without any display list, I get an FPS of around 1300 or 1400, but with display lists it slows down to 300 or 400 fps. In principle it's enough, but I think that's can't be normal.

My code to initialize SDL and OpeGL is the following:

SDL_Init(SDL_INIT_VIDEO);

SDL_Init(SDL_INIT_VIDEO);
screen = SDL_SetVideoMode(r.w, r.h, r.bpp, SDL_OPENGL|SDL_HWSURFACE|SDL_GL_DOUBLEBUFFER|SDL_INIT_NOPARACHUTE|SDL_INIT_EVENTTHREAD);

displayList = glGenLists(1);

glEnable(GL_BLEND);
glEnable(GL_ALPHA_TEST);
glEnable(GL_TEXTURE_2D);
glEnable(GL_DEPTH_TEST);

glDisable(GL_CULL_FACE);

glDepthMask(GL_TRUE);
glDepthFunc(GL_LEQUAL);

glBlendFunc(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA);
glAlphaFunc(GL_GREATER, 0.1);
glTexEnvf(GL_TEXTURE_ENV, GL_TEXTURE_ENV_MODE, GL_MODULATE);

glClearColor(0, 0, 0, 0);
glClearDepth(1);

glViewport(0, 0, r.w, r.h);

glMatrixMode(GL_PROJECTION);
glLoadIdentity();

glOrtho(0, r.w, r.h, 0, 0, -100);




My render loop looks like this:


glNewList(displayList, GL_COMPILE);

displayFunction();

glEndList();

glCallList(displayList);




... where displayFunction() calls all textures which should be drawn. The source for drawing textures is this:


glBindTexture(GL_TEXTURE_2D, textureId);

glBegin(GL_QUADS);

glTexCoord2i(0, 0);
glVertex3i(position.x, position.y, zPos);

glTexCoord2i(1, 0);
glVertex3i(position.x + textureSize.w, position.y, zPos);

glTexCoord2i(1, 1);
glVertex3i(position.x + textureSize.w, position.y + textureSize.h, zPos);

glTexCoord2i(0, 1);
glVertex3i(position.x, position.y + textureSize.h, zPos);

glEnd();




I think I've forgotten anything to initialize or similar mistake. I hope anyone can help me to solve the problem.

Share this post


Link to post
Share on other sites

glNewList(displayList, GL_COMPILE);

displayFunction();

glEndList();

glCallList(displayList);



If possible, only compile the display list once,
and later on, in your render function, call upon glCallList with
your compiled display list.

Share this post


Link to post
Share on other sites
Quote:
If possible, only compile the display list once, and later on, in your render function, call upon glCallList with your compiled display list.
Absolutely. The point of a display list is to cache draw operations on the GPU. The code bracketed by the glNewList()/glEndList() calls will be stored on the GPU for later use. Each frame, you're telling the GPU to remember the draw code, and then telling it to recall it--so of course it's going to run slower than if you just told it to draw it in the first place.
-G

Share this post


Link to post
Share on other sites
I've changed my source so that I compile my display list only once. But it doesn't grow up the FPS as much as I wish. Without any re-compiling during one second, I get the same rate as without display list. When I re-compile the display list, let's say all 10 ms, the FPS drops down to around 500 or 600.

Without drawing anything, the frame rate grows up to 2800 which is also a bit slow. When I comment out SDL_GL_SwapBuffers, the FPS grows up to some 100 thousand FPS. With SDL_GL_SwapBuffers, the FPS slows down to 2800. Does anyone have an idea what's the problem can be?

Share this post


Link to post
Share on other sites
At framerates that high, the numbers become less and less relevant to what kind of performance you're actually getting.

600fps is 1.6667ms
2800fps is 0.3571ms

The difference is 1.3095ms, or smaller than the difference between 55fps and 60.

Share this post


Link to post
Share on other sites
Why would you use a display list when you recompile it so many times?
I suggest you to move to vertex arrays and buffers.

Another suggestion is that you simply stop looking at the FPS because if it's 50000, 2000, 1000, or even 60, you wont see the difference...at all.
Optimize things when you actually need to.

Share this post


Link to post
Share on other sites
I'm trying to use VBOs to render my scenes, but I've got an black screen by using the following code:



Vertex[] vertices = [Vertex(0, 0, 0, 0, 50), Vertex(1, 0, 100, 0, 50), Vertex(1, 1, 100, 100, 50), Vertex(0, 1, 100, 100, 50)];

glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);

glGenBuffers(1, &vbo);

glBindBuffer(GL_ARRAY_BUFFER, vbo);
glEnableClientState(GL_VERTEX_ARRAY);

glBufferData(GL_ARRAY_BUFFER, vertices.sizeof, &vertices, GL_STATIC_DRAW);

glColor3f(1, 1, 1);

glInterleavedArrays(GL_T2F_V3F, Vertex.sizeof, null);
glDrawArrays(GL_QUADS, 0, vertices.length);

SDL_GL_SwapBuffers();



In this case it should draw at least one white rectangle. Do anyone know what I'm doing wrong? - Please note, that I'm using the D instead of C/C++.

Share this post


Link to post
Share on other sites
To be honest I've never seen glInterleavedArrays used before, so I'm not sure why it wouldn't work with that.

What I do know how to use is glVertexPointer, which you can try instead (not saying that it's better, but it's what I've typically always seen used).


Vertex[] vertices = [Vertex(0, 0, 0, 0, 50), Vertex(1, 0, 100, 0, 50), Vertex(1, 1, 100, 100, 50), Vertex(0, 1, 100, 100, 50)];

glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);

glGenBuffers(1, &vbo);

glBindBuffer(GL_ARRAY_BUFFER, vbo);
glEnableClientState(GL_VERTEX_ARRAY);
glBufferData(GL_ARRAY_BUFFER, vertices.sizeof, &vertices, GL_STATIC_DRAW);

glColor3f(1, 1, 1);

glVertexPointer(3, GL_FLOAT, sizeof(Vertex), (void*)(2*sizeof(float)) );
glDrawArrays(GL_QUADS, 0, vertices.length);

SDL_GL_SwapBuffers();



If you want to add your texture info, you throw in an enable client state for the texture coordinates, and specify another pointer.

Also the last two vertices in your quad are the same, not that this is why you're getting a black screen, but I think your quad is really only a triangle :)

Share this post


Link to post
Share on other sites
Quote:
Original post by karwosts
To be honest I've never seen glInterleavedArrays used before, so I'm not sure why it wouldn't work with that.
And for good reason - glInterleavedArrays has been deprecated for a very long time. All it does is call glVertexPointer/etc. under the hood, anyway.

Share this post


Link to post
Share on other sites
Hmm not sure, the vbo code with the modification I posted seems correct to me.

Have you tried glGetError()? Usually the first thing to check when debugging. Are you still setting your projection matrix and initialization, etc?

Share this post


Link to post
Share on other sites
I know that glInterleavedArays is deprecated, but I already had a running version (with glInterleavedArrays) on an other pc with onBoard graphic. Now... I'm in front of a computer with ATI HD3870 OC which should also support VBOs (or not?).

glGetError simply returns 0, thus no error.

I inited the environment with the following:



SDL_Init(SDL_INIT_VIDEO);

SDL_GL_SetAttribute(SDL_GL_RED_SIZE, 8);
SDL_GL_SetAttribute(SDL_GL_GREEN_SIZE, 8);
SDL_GL_SetAttribute(SDL_GL_BLUE_SIZE, 8);
SDL_GL_SetAttribute(SDL_GL_ALPHA_SIZE, 8);

SDL_GL_SetAttribute(SDL_GL_DEPTH_SIZE, 24);

SDL_GL_SetAttribute(SDL_GL_BUFFER_SIZE, r.bpp);
SDL_GL_SetAttribute(SDL_GL_DOUBLEBUFFER, 1);

SDL_Surface* screen = SDL_SetVideoMode(r.w, r.h, r.bpp, SDL_OPENGL|SDL_HWSURFACE|SDL_GL_DOUBLEBUFFER|/* SDL_INIT_NOPARACHUTE| */SDL_INIT_EVENTTHREAD);

glEnable(GL_BLEND);
glEnable(GL_ALPHA_TEST);
glEnable(GL_TEXTURE_2D);
glEnable(GL_DEPTH_TEST);

glDisable(GL_CULL_FACE);

glDepthMask(GL_TRUE);
glDepthFunc(GL_LEQUAL);

glBlendFunc(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA);
glAlphaFunc(GL_GREATER, 0.1);
glTexEnvf(GL_TEXTURE_ENV, GL_TEXTURE_ENV_MODE, GL_MODULATE);

glClearColor(0, 0, 0, 0);
glClearDepth(1);

glViewport(0, 0, r.w, r.h);

glMatrixMode(GL_PROJECTION);
glLoadIdentity();

glOrtho(0, r.w, r.h, 0, 0, -100);






Where r is a resolution-struct with w = width, h = height and bpp = bits per pixel.

Edit:\\ VAOs seems to work correctly.

[Edited by - nrgyzer on December 28, 2010 5:44:20 AM]

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  

  • Announcements

  • Forum Statistics

    • Total Topics
      628383
    • Total Posts
      2982384
  • Similar Content

    • By test opty
      Hi all,
       
      I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?
       
       
    • By DejayHextrix
      Hi, New here. 
      I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc.... 
      I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn? 
      How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want? 
      Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn. 
      So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started. 
      Thanks, 
      Dejay Hextrix 
    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
       
       
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
      Thanks!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
      Thanks.
  • Popular Now