• Advertisement
Sign in to follow this  

OpenGL Best practices when rendering scenes (particularly sorting objects)?

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

I'm using OpenGL ES 2.0 right now on an Android game, but I think the ideas here apply to D3D stuff as well. What are the typical best practices when rendering scenes (particularly with sorting objects)? And how are these ideas best implemented (i.e. who sorts them (and when/how often) and stores them, and how are they sorted)?

To give you an idea of what I'm talking about, consider rendering a scene that uses multiple vertex and fragment shaders. Is it best to:[list]
[*]Sort each object in the scene by the texture used first (so that those using the same texture are rendered sequentially so the texture can be reused)
[*]Then sort each object in the scene by the shader program (so that you don't have to call [font=courier new,courier,monospace]glUseProgram()[/font] (or the D3D equivalent) on every object in the scene)
[/list]
Or is it better to do it the other way around (sort by shader program, then by texture)? Or are neither of these the best way to sort objects, and is there a better way to do it? I don't want to overcomplicate this and do too much work on the CPU, as it has other things it needs to do other than sorting objects in a scene.

When sorting these things, would the sorting be done in some [font=courier new,courier,monospace]scene[/font] object that stores references to all the renderable objects in the scene, sorts them, and draws them?

And finally, how can these ideas best be translated into a 2D game (I'm also curious about these answers for a 3D game though too)? In 2D games, the depth buffer is usually disabled, which makes the sorting/drawing order significant. There are so many transparent parts to textures and alpha blending going on that the order in which things are drawn need to be carefully controlled. Would you do the sorting above first, and then sort by layer number to ensure the correct drawing order? And if two sprites have the same layer number, you just have to make no guarantees about which will be drawn on top of the other (though you'd use a stable sorting algorithm, so that they don't alternate every frame which one is on top of the other)?

Sorry for the eleventy billion questions, but a huge thanks in advance for any responses!

Share this post


Link to post
Share on other sites
Advertisement
[quote name='web383' timestamp='1338917329' post='4946520']
Sort opaque objects by shader, then by texture, then if you want by depth (front to back). Transparent objects need to be sorted by depth first (back to front) in order for things to look correct, then by shader, then by texture.

Most of this information has come from [url="http://lspiroengine.com/?p=96"]http://lspiroengine.com/?p=96[/url]
[/quote]
I was actually hoping L. Spiro would reply, so thank you for that link, as it covers a lot of the stuff I was trying to get at!

Share this post


Link to post
Share on other sites
Web383++

[quote name='Cornstalks' timestamp='1338912188' post='4946488']
When sorting these things, would the sorting be done in some scene object that stores references to all the renderable objects in the scene, sorts them, and draws them?
[/quote]
For different materials/shaders use [url="http://en.wikipedia.org/wiki/Bucket_sort"]bucket sort[/url].

[quote name='Cornstalks' timestamp='1338912188' post='4946488']
In 2D games, the depth buffer is usually disabled, which makes the sorting/drawing order significant.
[/quote]
Why disable it ? When you have an order, you have some kind of indicator. Just assign this indicator to an according z-value, render the 2d sprites as simple quads (orthogonal projection) and utilise the z-buffer to do the sorting. But this will only work if you don't use transparency (i.e. alpha blended sprite edges).

[quote name='Cornstalks' timestamp='1338912188' post='4946488']
There are so many transparent parts to textures and alpha blending going on that the order in which things are drawn need to be carefully controlled.
[/quote]
You can try to render each layer on a separate render target (is this supported by andriod hardware ?) and blend the whole layer on-top of each other (use stencil to minimise overdraw). I.e. a background layer (one shader, only opaque objects), a moving object layer, a fog layer (lot of alpha blended, unsorted sprites).

Share this post


Link to post
Share on other sites
A few extended notes on what I said in my blog post.

#1: For PowerVR or other tile-based deferred rendering hardware, you do not, and I repeat do [i]not[/i] want to sort front-to-back except where necessary for a proper effect (which is usually for alpha objects which instead requires back-to-front).
For these devices, you [i]will[/i] notice a drop in speed if you add distance testing; it is nothing but overhead.

#2: Your sorting routine can slow you down rather than help you if not done correctly.
If you using something like the C-style std::qsort() which works with function pointers you will likely lose performance.
Here are the rankings based on my own tests. The % is the percent of speed without performing any sort at all, meaning anything below 100% is slower than having no sort.
* Top-Down Merge Sort C-Style: ~87%
* Quick Sort C-Style: ~95%
* Quick Sort Template: ~111%
* Insertion Sort Template: ~120%

I haven’t tested a bucket sort so I can’t compare it to a raw insertion sort. As long as you can easily take advantage of temporal coherence it could end up being a bit faster.
And I want to additionally say explicitly that temporal coherence is one of the most important factors here—insertion sort is slower than quick sort without it.
Also I want to reiterate that I sorted the indices of the “render queue items” instead of moving the actual items all over. This reduces copy bandwidth heavily.
Also you must use a stable sort. With quick sort, things flicker when they are on top of each other etc., meaning it is really only for benchmarks/comparisons and not practical for actual use anyway.

#3: For PowerVR and similar hardware, avoid dependent texture reads. There are many ways to accidentally cause reads to become dependent:
* If the texture coordinates are not used as-is (as they were sent from the vertex shader) in the fragment shader (including adding any offsets to them even if it is just for the read).
* Using anything but the x and y of the texture-coordinate vector causes dependent texture reads, so you can’t avoid it by packing one texture read into xy and another into zw.
* Check the hardware documents for your device for the rest of the list.
For 2D, the most likely place where this would happen is if you have any post-processing taking place. One way to handle it there is by determining all of the texture-coordinates in the vertex shader and you will be bound by the number of texture units available to use (unless you are willing to take the dependent-texture-read hit a little bit).

#4: If you have a lot of sprites you should not be using a bunch of small vertex buffers. Keep 2 buffers and fill one each frame (with only objects that are on the screen), swapping between them each frame to avoid hardware stalls.


L. Spiro Edited by L. Spiro

Share this post


Link to post
Share on other sites
Sorry it's taken so long to reply... work has been hectic.

[quote name='L. Spiro' timestamp='1339061679' post='4946991']
#1: For PowerVR or other tile-based deferred rendering hardware, you do not, and I repeat do [i]not[/i] want to sort front-to-back except where necessary for a proper effect (which is usually for alpha objects which instead requires back-to-front).
For these devices, you [i]will[/i] notice a drop in speed if you add distance testing; it is nothing but overhead.
[/quote]
Good to know. My current game is 2D (but this is useful for future stuff), so I'll disable distance testing all together. I only need to sort draw calls to make sure the right "layers" are drawn in order.

[quote name='L. Spiro' timestamp='1339061679' post='4946991']
#2: Your sorting routine can slow you down rather than help you if not done correctly.
[/quote]
Yes, I figured; thanks for the stats though!


[quote name='L. Spiro' timestamp='1339061679' post='4946991']
#3: For PowerVR and similar hardware, avoid dependent texture reads. There are many ways to accidentally cause reads to become dependent:
* If the texture coordinates are not used as-is (as they were sent from the vertex shader) in the fragment shader (including adding any offsets to them even if it is just for the read).
* Using anything by the x and y of the texture-coordinate vector causes dependent texture reads, so you can’t avoid it by packing one texture read into xy and another into zw.
* Check the hardware documents for your device for the rest of the list.
For 2D, the most likely place where this would happen is if you have any post-processing taking place. One way to handle it there is by determining all of the texture-coordinates in the vertex shader and you will be bound by the number of texture units available to use (unless you are willing to take the dependent-texture-read hit a little bit).
[/quote]
Interesting. Good to know. I shouldn't be modifying texture coords in my current game, but this is good for future stuff.

[quote name='L. Spiro' timestamp='1339061679' post='4946991']
#4: If you have a lot of sprites you should not be using a bunch of small vertex buffers. Keep 2 buffers and fill one each frame (with only objects that are on the screen), swapping between them each frame to avoid hardware stalls.
[/quote]
Now [i]that's[/i] an interesting idea. I suppose it only works if you enable depth testing or break the buffer filling/draw calls up by layer.



[quote name='Ashaman73' timestamp='1338963407' post='4946667']
For different materials/shaders use [url="http://en.wikipedia.org/wiki/Bucket_sort"]bucket sort[/url].
[/quote]
Thanks for that! I've used radix sorting but haven't ever used bucket sorting, so I'll check it out.

[quote name='Ashaman73' timestamp='1338963407' post='4946667']
[quote name='Cornstalks' timestamp='1338912188' post='4946488']
In 2D games, the depth buffer is usually disabled, which makes the sorting/drawing order significant.
[/quote]
Why disable it ? When you have an order, you have some kind of indicator. Just assign this indicator to an according z-value, render the 2d sprites as simple quads (orthogonal projection) and utilise the z-buffer to do the sorting. But this will only work if you don't use transparency (i.e. alpha blended sprite edges).
[/quote]
That's an idea I had a while ago, and [url="http://en.sfml-dev.org/forums/index.php?topic=7535.0"]proposed it over at the SFML forums[/url], but most sprites these days make use of alpha blending (for antialiasing the edges). If only I was working on an 8-bit retro game...

[quote name='Ashaman73' timestamp='1338963407' post='4946667']
You can try to render each layer on a separate render target (is this supported by andriod hardware ?)
[/quote]
I have no idea... I'll find out, but even if I can't, it's an interesting idea for desktop games, so I'll have to remember that.

Share this post


Link to post
Share on other sites
All that L. Spiro said about PowerVR is correct.


About sorting, you may keep your radix sorter, depending how it's implemented (8bits/11bits radices, w/ or w/o histogram, stable (+mem) or unstable (in-place)) it can be quite fast and depending on your dataset size you can even multithread it.
(8 bits radices, histogram and stable did it for me. Check "A Cache-Aware Hybrid Sorter" from GPU Gems 2 AFAIR for a good implementation.) Edited by Ingenu

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Now

  • Advertisement
  • Similar Content

    • By Balma Alparisi
      i got error 1282 in my code.
      sf::ContextSettings settings; settings.majorVersion = 4; settings.minorVersion = 5; settings.attributeFlags = settings.Core; sf::Window window; window.create(sf::VideoMode(1600, 900), "Texture Unit Rectangle", sf::Style::Close, settings); window.setActive(true); window.setVerticalSyncEnabled(true); glewInit(); GLuint shaderProgram = createShaderProgram("FX/Rectangle.vss", "FX/Rectangle.fss"); float vertex[] = { -0.5f,0.5f,0.0f, 0.0f,0.0f, -0.5f,-0.5f,0.0f, 0.0f,1.0f, 0.5f,0.5f,0.0f, 1.0f,0.0f, 0.5,-0.5f,0.0f, 1.0f,1.0f, }; GLuint indices[] = { 0,1,2, 1,2,3, }; GLuint vao; glGenVertexArrays(1, &vao); glBindVertexArray(vao); GLuint vbo; glGenBuffers(1, &vbo); glBindBuffer(GL_ARRAY_BUFFER, vbo); glBufferData(GL_ARRAY_BUFFER, sizeof(vertex), vertex, GL_STATIC_DRAW); GLuint ebo; glGenBuffers(1, &ebo); glBindBuffer(GL_ELEMENT_ARRAY_BUFFER, ebo); glBufferData(GL_ELEMENT_ARRAY_BUFFER, sizeof(indices), indices,GL_STATIC_DRAW); glVertexAttribPointer(0, 3, GL_FLOAT, false, sizeof(float) * 5, (void*)0); glEnableVertexAttribArray(0); glVertexAttribPointer(1, 2, GL_FLOAT, false, sizeof(float) * 5, (void*)(sizeof(float) * 3)); glEnableVertexAttribArray(1); GLuint texture[2]; glGenTextures(2, texture); glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, texture[0]); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR); sf::Image* imageOne = new sf::Image; bool isImageOneLoaded = imageOne->loadFromFile("Texture/container.jpg"); if (isImageOneLoaded) { glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, imageOne->getSize().x, imageOne->getSize().y, 0, GL_RGBA, GL_UNSIGNED_BYTE, imageOne->getPixelsPtr()); glGenerateMipmap(GL_TEXTURE_2D); } delete imageOne; glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, texture[1]); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_S, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_WRAP_T, GL_CLAMP_TO_EDGE); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_LINEAR); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_LINEAR); sf::Image* imageTwo = new sf::Image; bool isImageTwoLoaded = imageTwo->loadFromFile("Texture/awesomeface.png"); if (isImageTwoLoaded) { glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, imageTwo->getSize().x, imageTwo->getSize().y, 0, GL_RGBA, GL_UNSIGNED_BYTE, imageTwo->getPixelsPtr()); glGenerateMipmap(GL_TEXTURE_2D); } delete imageTwo; glUniform1i(glGetUniformLocation(shaderProgram, "inTextureOne"), 0); glUniform1i(glGetUniformLocation(shaderProgram, "inTextureTwo"), 1); GLenum error = glGetError(); std::cout << error << std::endl; sf::Event event; bool isRunning = true; while (isRunning) { while (window.pollEvent(event)) { if (event.type == event.Closed) { isRunning = false; } } glClear(GL_COLOR_BUFFER_BIT); if (isImageOneLoaded && isImageTwoLoaded) { glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, texture[0]); glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, texture[1]); glUseProgram(shaderProgram); } glBindVertexArray(vao); glDrawElements(GL_TRIANGLES, 6, GL_UNSIGNED_INT, nullptr); glBindVertexArray(0); window.display(); } glDeleteVertexArrays(1, &vao); glDeleteBuffers(1, &vbo); glDeleteBuffers(1, &ebo); glDeleteProgram(shaderProgram); glDeleteTextures(2,texture); return 0; } and this is the vertex shader
      #version 450 core layout(location=0) in vec3 inPos; layout(location=1) in vec2 inTexCoord; out vec2 TexCoord; void main() { gl_Position=vec4(inPos,1.0); TexCoord=inTexCoord; } and the fragment shader
      #version 450 core in vec2 TexCoord; uniform sampler2D inTextureOne; uniform sampler2D inTextureTwo; out vec4 FragmentColor; void main() { FragmentColor=mix(texture(inTextureOne,TexCoord),texture(inTextureTwo,TexCoord),0.2); } I was expecting awesomeface.png on top of container.jpg

    • By khawk
      We've just released all of the source code for the NeHe OpenGL lessons on our Github page at https://github.com/gamedev-net/nehe-opengl. code - 43 total platforms, configurations, and languages are included.
      Now operated by GameDev.net, NeHe is located at http://nehe.gamedev.net where it has been a valuable resource for developers wanting to learn OpenGL and graphics programming.

      View full story
    • By TheChubu
      The Khronos™ Group, an open consortium of leading hardware and software companies, announces from the SIGGRAPH 2017 Conference the immediate public availability of the OpenGL® 4.6 specification. OpenGL 4.6 integrates the functionality of numerous ARB and EXT extensions created by Khronos members AMD, Intel, and NVIDIA into core, including the capability to ingest SPIR-V™ shaders.
      SPIR-V is a Khronos-defined standard intermediate language for parallel compute and graphics, which enables content creators to simplify their shader authoring and management pipelines while providing significant source shading language flexibility. OpenGL 4.6 adds support for ingesting SPIR-V shaders to the core specification, guaranteeing that SPIR-V shaders will be widely supported by OpenGL implementations.
      OpenGL 4.6 adds the functionality of these ARB extensions to OpenGL’s core specification:
      GL_ARB_gl_spirv and GL_ARB_spirv_extensions to standardize SPIR-V support for OpenGL GL_ARB_indirect_parameters and GL_ARB_shader_draw_parameters for reducing the CPU overhead associated with rendering batches of geometry GL_ARB_pipeline_statistics_query and GL_ARB_transform_feedback_overflow_querystandardize OpenGL support for features available in Direct3D GL_ARB_texture_filter_anisotropic (based on GL_EXT_texture_filter_anisotropic) brings previously IP encumbered functionality into OpenGL to improve the visual quality of textured scenes GL_ARB_polygon_offset_clamp (based on GL_EXT_polygon_offset_clamp) suppresses a common visual artifact known as a “light leak” associated with rendering shadows GL_ARB_shader_atomic_counter_ops and GL_ARB_shader_group_vote add shader intrinsics supported by all desktop vendors to improve functionality and performance GL_KHR_no_error reduces driver overhead by allowing the application to indicate that it expects error-free operation so errors need not be generated In addition to the above features being added to OpenGL 4.6, the following are being released as extensions:
      GL_KHR_parallel_shader_compile allows applications to launch multiple shader compile threads to improve shader compile throughput WGL_ARB_create_context_no_error and GXL_ARB_create_context_no_error allow no error contexts to be created with WGL or GLX that support the GL_KHR_no_error extension “I’m proud to announce OpenGL 4.6 as the most feature-rich version of OpenGL yet. We've brought together the most popular, widely-supported extensions into a new core specification to give OpenGL developers and end users an improved baseline feature set. This includes resolving previous intellectual property roadblocks to bringing anisotropic texture filtering and polygon offset clamping into the core specification to enable widespread implementation and usage,” said Piers Daniell, chair of the OpenGL Working Group at Khronos. “The OpenGL working group will continue to respond to market needs and work with GPU vendors to ensure OpenGL remains a viable and evolving graphics API for all its customers and users across many vital industries.“
      The OpenGL 4.6 specification can be found at https://khronos.org/registry/OpenGL/index_gl.php. The GLSL to SPIR-V compiler glslang has been updated with GLSL 4.60 support, and can be found at https://github.com/KhronosGroup/glslang.
      Sophisticated graphics applications will also benefit from a set of newly released extensions for both OpenGL and OpenGL ES to enable interoperability with Vulkan and Direct3D. These extensions are named:
      GL_EXT_memory_object GL_EXT_memory_object_fd GL_EXT_memory_object_win32 GL_EXT_semaphore GL_EXT_semaphore_fd GL_EXT_semaphore_win32 GL_EXT_win32_keyed_mutex They can be found at: https://khronos.org/registry/OpenGL/index_gl.php
      Industry Support for OpenGL 4.6
      “With OpenGL 4.6 our customers have an improved set of core features available on our full range of OpenGL 4.x capable GPUs. These features provide improved rendering quality, performance and functionality. As the graphics industry’s most popular API, we fully support OpenGL and will continue to work closely with the Khronos Group on the development of new OpenGL specifications and extensions for our customers. NVIDIA has released beta OpenGL 4.6 drivers today at https://developer.nvidia.com/opengl-driver so developers can use these new features right away,” said Bob Pette, vice president, Professional Graphics at NVIDIA.
      "OpenGL 4.6 will be the first OpenGL release where conformant open source implementations based on the Mesa project will be deliverable in a reasonable timeframe after release. The open sourcing of the OpenGL conformance test suite and ongoing work between Khronos and X.org will also allow for non-vendor led open source implementations to achieve conformance in the near future," said David Airlie, senior principal engineer at Red Hat, and developer on Mesa/X.org projects.

      View full story
    • By _OskaR
      Hi,
      I have an OpenGL application but without possibility to wite own shaders.
      I need to perform small VS modification - is possible to do it in an alternative way? Do we have apps or driver modifictions which will catch the shader sent to GPU and override it?
    • By xhcao
      Does sync be needed to read texture content after access texture image in compute shader?
      My simple code is as below,
      glUseProgram(program.get());
      glBindImageTexture(0, texture[0], 0, GL_FALSE, 3, GL_READ_ONLY, GL_R32UI);
      glBindImageTexture(1, texture[1], 0, GL_FALSE, 4, GL_WRITE_ONLY, GL_R32UI);
      glDispatchCompute(1, 1, 1);
      // Does sync be needed here?
      glUseProgram(0);
      glBindFramebuffer(GL_READ_FRAMEBUFFER, framebuffer);
      glFramebufferTexture2D(GL_READ_FRAMEBUFFER, GL_COLOR_ATTACHMENT0,
                                     GL_TEXTURE_CUBE_MAP_POSITIVE_X + face, texture[1], 0);
      glReadPixels(0, 0, kWidth, kHeight, GL_RED_INTEGER, GL_UNSIGNED_INT, outputValues);
       
      Compute shader is very simple, imageLoad content from texture[0], and imageStore content to texture[1]. Does need to sync after dispatchCompute?
  • Advertisement