Archived

This topic is now archived and is closed to further replies.

Ranger_One

OpenGL Best OpenGL Optimize method?

Recommended Posts

Ranger_One    300
Ok now that I''m getting into OpenGL bigtime- I have a slew of questions, this one is about optimization. Assuming I have a model that is static, what method is best for optimization of drawing that model for speed? Should I use vertex arrays? DrawElement? or Display lists? I have heard display lists offer no speed increase (another post), so what is their point then? reduce code overhead? Ranger

Share this post


Link to post
Share on other sites
Palidine    1315
display lists are to reduce code overhead, yes. if you have multiple instances of the same object you can just call the same display list to draw them all.

vertex arrays with glDrawElements are faster than glBegin/glVertex*/glEnd i think mostly b/c of function overhead.

what i''m trying to learn currently is how to cache an objects displaylist/geometry on the vid card. but my sense is that that is an implementation decision left to the card itself. i''m not sure.

-me

Share this post


Link to post
Share on other sites
Myopic Rhino    2317
quote:
Original post by Palidine
what i''m trying to learn currently is how to cache an objects displaylist/geometry on the vid card. but my sense is that that is an implementation decision left to the card itself. i''m not sure.

That''s what NVIDIA''s vertex array range extension does.

Share this post


Link to post
Share on other sites
Palidine    1315
interesting.

that''s not the same as glDrawRangeElements() is it?

my understanding currently is that the above function is just a restriced version of glDrawElements()?

note to self: STFW

-me

Share this post


Link to post
Share on other sites
Ready4Dis    180
Newer cards have vertex arrays, and if it''s a static object, you can use LOCKED vertex arrays.. these are ussually the fastest. I don''t know who told you that Display Lists offer no speed increase, but they do/can. OpenGL (depending on the implementation) does attempt to optomize your display list (minimize state changes, re-order the drawing functions, and it can store your vertices internally as static vertex arrays, etc, etc).

Anyways, to answer your question, I''d have to go with vertex arrays/locked vertex arrays (per card implementation would be best, or support certain cards, and fall back to normal if unkown card)... although, the smaller your vertex arrays are (low poly models), the less of a performance gain you''ll get.

Billy - BillyB@mrsnj.com
(Hey, I''''m no longer anonymous!)

Share this post


Link to post
Share on other sites
Palidine    1315
when you are talking about card vertex arrays you mean just standard openGL vertex arrays, right?

as in the card just recognizes when you are using them and caches the vertex info?

-me

Share this post


Link to post
Share on other sites
Myopic Rhino    2317
Wow, Billy, you registered.

In regards to locked vertex arrays, generally, you don't see much of an improvement in speed unless you're using some form of multipass rendering. At least, that's been the case in my own code, and I've heard the same from others.

Palidine: the vertex array range extension isn't the same thing as glDrawRangeElements. The former allows you to allocate the memory you use for vertex arrays in video memory; this is the fastest method available on NVIDIA hardware. The latter isn't exactly a restricted version of glDrawElements; rather, it allows you to specify the minimum and maximum indicies used in your vertex array, which allows the video driver to more efficiently cache vertex data.

Share this post


Link to post
Share on other sites
Yann L    1802
I would stay away from vertex array locking (CVAs). The extension is very ''experimental'', in the sense that it was never finalized. It''s not even a real standard extension, it was more or less a quick''n''dirty function they developed to make Carmack happy. In fact, early nVidia driver versions did only support one single array format in this mode: the one Quake used...

The only thing that CVAs brought me were problems. Their implementation is so extremely driver/manufacturer dependend, you can''t rely on their behaviour in any way.

If you want to be compatible: use standard vertex arrays. They offer good speed, and most modern drivers do a really good job accelerating data transfer through AGP streaming etc. If you want to go for maximum performance, and multi-manufacturer compatibility isn''t really an issue, then go with VAR/VAO. It will allow the highest possible transfer rates that your hardware can handle.

About Draw(Range)Elements: AFAIK, nVidia drivers do not make a difference between both, DrawRangeElements directly calls DrawElements. The speed difference is reportedly 0, and I can confirm that, at least in VAR mode. But there might be a difference with other manufacturers, so it''s probably safer to always use DrawRangeElements.

/ Yann

Share this post


Link to post
Share on other sites
zedzeek    529
i agree with Yann here, ive never liked cva''s + personally can find no difference speedwise with drawrangeelements vs normal drawelements

http://uk.geocities.com/sloppyturds/gotterdammerung.html

Share this post


Link to post
Share on other sites

  • Similar Content

    • By Arulbabu Donbosco
      There are studios selling applications which is just copying any 3Dgraphic content and regenerating into another new window. especially for CAVE Virtual reality experience. so that the user opens REvite or CAD or any other 3D applications and opens a model. then when the user selects the rendered window the VR application copies the 3D model information from the OpenGL window. 
      I got the clue that the VR application replaces the windows opengl32.dll file. how this is possible ... how can we copy the 3d content from the current OpenGL window.
      anyone, please help me .. how to go further... to create an application like VR CAVE. 
       
      Thanks
    • By cebugdev
      hi all,

      i am trying to build an OpenGL 2D GUI system, (yeah yeah, i know i should not be re inventing the wheel, but this is for educational and some other purpose only),
      i have built GUI system before using 2D systems such as that of HTML/JS canvas, but in 2D system, i can directly match a mouse coordinates to the actual graphic coordinates with additional computation for screen size/ratio/scale ofcourse.
      now i want to port it to OpenGL, i know that to render a 2D object in OpenGL we specify coordiantes in Clip space or use the orthographic projection, now heres what i need help about.
      1. what is the right way of rendering the GUI? is it thru drawing in clip space or switching to ortho projection?
      2. from screen coordinates (top left is 0,0 nd bottom right is width height), how can i map the mouse coordinates to OpenGL 2D so that mouse events such as button click works? In consideration ofcourse to the current screen/size dimension.
      3. when let say if the screen size/dimension is different, how to handle this? in my previous javascript 2D engine using canvas, i just have my working coordinates and then just perform the bitblk or copying my working canvas to screen canvas and scale the mouse coordinates from there, in OpenGL how to work on a multiple screen sizes (more like an OpenGL ES question).
      lastly, if you guys know any books, resources, links or tutorials that handle or discuss this, i found one with marekknows opengl game engine website but its not free,
      Just let me know. Did not have any luck finding resource in google for writing our own OpenGL GUI framework.
      IF there are no any available online, just let me know, what things do i need to look into for OpenGL and i will study them one by one to make it work.
      thank you, and looking forward to positive replies.
    • By fllwr0491
      I have a few beginner questions about tesselation that I really have no clue.
      The opengl wiki doesn't seem to talk anything about the details.
       
      What is the relationship between TCS layout out and TES layout in?
      How does the tesselator know how control points are organized?
          e.g. If TES input requests triangles, but TCS can output N vertices.
             What happens in this case?
      In this article,
      http://www.informit.com/articles/article.aspx?p=2120983
      the isoline example TCS out=4, but TES in=isoline.
      And gl_TessCoord is only a single one.
      So which ones are the control points?
      How are tesselator building primitives?
    • By Orella
      I've been developing a 2D Engine using SFML + ImGui.
      Here you can see an image
      The editor is rendered using ImGui and the scene window is a sf::RenderTexture where I draw the GameObjects and then is converted to ImGui::Image to render it in the editor.
      Now I need to create a 3D Engine during this year in my Bachelor Degree but using SDL2 + ImGui and I want to recreate what I did with the 2D Engine. 
      I've managed to render the editor like I did in the 2D Engine using this example that comes with ImGui. 
      3D Editor preview
      But I don't know how to create an equivalent of sf::RenderTexture in SDL2, so I can draw the 3D scene there and convert it to ImGui::Image to show it in the editor.
      If you can provide code will be better. And if you want me to provide any specific code tell me.
      Thanks!
    • By Picpenguin
      Hi
      I'm new to learning OpenGL and still learning C. I'm using SDL2, glew, OpenGL 3.3, linmath and stb_image.
      I started following through learnopengl.com and got through it until I had to load models. The problem is, it uses Assimp for loading models. Assimp is C++ and uses things I don't want in my program (boost for example) and C support doesn't seem that good.
      Things like glVertexAttribPointer and shaders are still confusing to me, but I have to start somewhere right?
      I can't seem to find any good loading/rendering tutorials or source code that is simple to use and easy to understand.
      I have tried this for over a week by myself, searching for solutions but so far no luck. With tinyobjloader-c and project that uses it, FantasyGolfSimulator, I was able to actually load the model with plain color (always the same color no matter what I do) on screen and move it around, but cannot figure out how to use textures or use its multiple textures with it.
      I don't ask much: I just want to load models with textures in them, maybe have lights affect them (directional spotlight etc). Also, some models have multiple parts and multiple textures in them, how can I handle those?
      Are there solutions anywhere?
      Thank you for your time. Sorry if this is a bit confusing, English isn't my native language
  • Popular Now