• Advertisement
Sign in to follow this  

OpenGL Ideas for rendering stacked UI elements

Recommended Posts

Hello Everyone,

I've developed a basic theme able user interface system with opengl by drawing different shapes and text. I want the UI to be used on both mobile and desktop so I only want the UI to redraw when absolutely necessary in order to conserve battery life. So there is no rendering call in the main application loop. The time to paint can be at anytime a UI control believes it requires a redraw.

The issue that I'm having is that I can't figure out how to only draw the Control that needs redrawing. If the control that needs redrawing is semi transparent, the control behind it will need to be redrawn as well due to the fact that the redraw causes an opengl clear in the control's scissor rect, but if the control behind the control that needs redrawing is redrawn, all controls behind that and inside of that will need to be redrawn as well. To the point where I'm redrawing the entire screen every time something changes in one control. This has come to a head where I'm attempting to draw a textbox control and every time the caret blinks I'm redrawing all the controls on the screen, which doesn't seem very efficient.

Does anybody have any ideas or suggestions for ways in which I could draw semi transparent controls sitting on top of each other without redrawing the entire screen?


Share this post

Link to post
Share on other sites

1. How sure are you that you're ACTUALLY being a power drain? Reason -- this is how all the rendering code on phones works and so the OS and GPU designers are really, really good at making them use very little power. Implement your basic version and use GPU debugging tools to see what workload you're actually generating..

2. Clip to the smallest changed area. Draw everything as you otherwise would. The clipping will cull out the areas that don't need rendering. Most mobile devices use tile-based renderings; the screen is rendered in squares, each of which accumulates its own processing list of primitive operations and they're rasterised/fragment processed independently. Draws which don't touch a lot of the tiles because they're clipped out incur no cost; the clipping ensures you're touching as few as possible. This is really all you should need to do. This only works for polygon clipping though, not stencil buffers. (You're after being able to discard geometry portions, not fragments).

3. There's a BUNCH of other "tricks" which *could* be used depending on exactly the drawing architecture you've got -- however, the last time I actually used any of them was on 8-bit micros where brute-force solutions like "redraw the whole screen" just weren't happening[1]. TBH, given that mid-range phones have **six to seven orders of magnitude** more processing power... you shouldn't need to be going there.

Seriously -- trust the machine developers, measure your impact and only optimise later.

Heck; if it comes to that --

4. Does your caret really need to blink? The cheapest geometry is geometry you don't draw at all...


[1] As an example, you grab a copy of the area under your caret. Now you can erase it to make it blink without needing a full redraw... Once you have a copy of the area without it and the screen buffer containing a version with the caret, you can just swap the memory areas over and save doing any drawing at all... See how strained that's all going to get?

Share this post

Link to post
Share on other sites

No I'm not positive that I am actually being a power drain. what I'm doing is I'm checking the CPU usage through the task manager while I let the application run. In my mind, if all the app is doing is blinking a cursor, CPU usage should be 0%. (I checked visual studio, and with all its UI complexity, when it just sits and blinks a cursor, its CPU usage is 0%).

Granted, checking the task manager probably isn't the most scientific and rigorous way to test performance.

Your answer did get me thinking though, and I made the Text box request a repaint every time the cursor blinked. Even though the UI was being re rendered every time the cursor blinked, its was still only using 0% CPU as well. So yeah, maybe I am too concerned about performance and power usage.

The problem with clipping to the smallest change areas is if the controls are semi transparent. If a small textbox control sitting in the center of a Form is semi transparent, I need to render it and the background Form control as well in order to get the final blend colour between the 2 controls. If that Form is filling the entire screen, I have to re render the entire screen (along with all the other controls in the Form as well).

The only thing I can think of is to perhaps run though all the controls and their children, test if they intersect the rect being redrawn, and only redraw the controls (and their parent controls as well) if they intersect, but I wasn't sure if that was the most efficient way to do things or if I was actually wasting my time and should just rather do a brute force redraw every time instead.


Share this post

Link to post
Share on other sites

The problem with clipping to the smallest change areas is if the controls are semi transparent. If a small textbox control sitting in the center of a Form is semi transparent, I need to render it and the background Form control as well in order to get the final blend colour between the 2 controls. If that Form is filling the entire screen, I have to re render the entire screen (along with all the other controls in the Form as well).

Why do you think that? If you just draw that background inside the changed rectangle you do not overdraw anything outside it and therefore you do not need to redraw anything else outside it. (You either just change the draws to be only inside or use scissor.)

Share this post

Link to post
Share on other sites

"only redraw the controls (and their parent controls as well) if they intersect"

The GL renderer is *already* doing that work (because it can't know you pre-clipped everything). Possibly it can even do it in hardware..

Just throw your geometry at it, let it sort it all out. Don't worry about it unless it's actually a problem.

Share this post

Link to post
Share on other sites

Okay cool, so what I've begun to realize now is that I don't actually have to worry about sending opengl geometry outside the clip region, since it will deal with that itself (right?). What that has now done is shifted the problem from an being opengl one to something less specific and more general to graphics programming, something akin maybe to software culling perhaps?

The problem now is ensuring that controls that don't actually need to be rendered, don't send vertices through the pipeline in the first place, since opengl is going to discard them any way, and its costing CPU resources to build all those vertices. To that end, I'm no longer sure if this still the right place for the question. 

But, given a control hierarchy, where each Paint() call runs through the hierarchy generating vertices for all controls and their children, is there a high performance solution that allows me to discard controls if they don't intersect the rect that needs redrawing? Right now, my only idea is to pass around the rect that will be redrawn and any control that doesn't intersect that rect doesn't get its vertices generated and sent to the GPU. My only concern is in situations where a tiny little square in the corner is being animated, but I now have to run through 300 other controls checking all of their rects every frame, seems a bit intensive, but at the same time, I'm guessing still cheaper than generating the vertices for those controls.

I hope I'm getting my concerns across properly?


Edited by LittleJimmy

Share this post

Link to post
Share on other sites

The controls form a tree. A dialogue contains a couple of panes, the panes contain controls, the controls contain some static text and an entry box and so on on.

If the outer control completely contains the inner controls, it can check if the redraw is within its bounds and if not... doesn't propagate it to the contained controls.


This is how most real-world UI rendering systems operate -- boxes within boxes within boxes. It's common to Windows, MacOS, X11. It's happening inside web browsers and it's also the case for most mobile phone UIs. It's not the only solution, but it's a well worked one.

Most UIs with non-transparent elements can optimise further (because it's only the top-most opaque object which needs to paint). You'll have to exhaustively run through ALL the nodes and paint them in reverse stacking order.


The other solution is to use several drawing layers. You draw each UI elements to one as if opaque and composite the outputs together afterwards. This needs more memory and more GPU power but less CPU work.

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  

  • 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
      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,
      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?
      glBindFramebuffer(GL_READ_FRAMEBUFFER, framebuffer);
                                     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