Sign in to follow this  

OpenGL Qt+OpenGL texture issue

This topic is 3051 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 all! I'm having a weird (at least to me) problem with textures using OpenGL through Qt. I made a user interface in Qt and I'm using OpenGL to show the images captured from two different cameras. For this purpose, I created a GLCamWidget, which inherits from QGLWidget, and a GLStereoWidget, which also inherits from QGLWidget. In the preview window, I instantiate two objects of GLCamWidget. Each object shows a different camera image through a 2D texture. As I have two instances of the class, I suppose (I'm not sure about it) that I have two different OpenGL contexts. The reason for this line of thought is that I use glGenTextures() in the constructor of the class, and the function returns the same ID (ID = 1) for each texture. And it all works fine. When I choose "Stereo Mode" in my program, I create an instance of GLStereoWidget and it shows the images of both cameras side by side, using 2 textures, one for each image. Again, I suppose it's a different context, because the ID's returned are 1 and 2. If it was the same context, it could not return 1, right? Ok, that works fine too. The problem occurs when I close the stereo window. I delete the GLStereoWidget object, and, in his destructor, I use glDeleteTextures() to delete these 2 textures (I suppose from THIS CONTEXT). Although, this function is misteriously affecting one of my GLCamWidget objects, because one of them stops exhibiting the image from the camera, while the other one remains normal. I can see no reason for that happening. If anyone can help me get through this, I would really appreciate. I didn't post any code here because it's split in several modules, but if you think it's really necessary, I'll do it. Screenshots: 1) Before stereo (GLCamWidget objects) 2) During stereo (GLStereoWidget object) 3) After stereo (GLCamWidget objects, the one on the right not working anymore) Thank you!!

Share this post


Link to post
Share on other sites
You should either make sure that the corresponding context is the current one (there is some QGLWidget::getContext ()->makeCurrent function) or you can just share a context between all GL widgets. I think the QGLWidget constructor can accept a context to share. The latter option seems to be better suited because it enables you to avoid context switches as well as it allows you to possibly use all textures in all of your GL widgets no matter in which one you have created the texture.

Share this post


Link to post
Share on other sites
Waterwalker, thanks for replying. I'll try your suggestion, it seems better than what I'm doing. Still, I'm curious about why deleting those 2 textures are interfering with the GLCamWidget one. Do you have any clue?

Share this post


Link to post
Share on other sites
I think Waterwalker hit the nail on the head. My guess is the widget that loses a texture is always simply going to be the last one you drew to before deleting the texture, because that's the one with the active context. Remember, the gl___ commands are totally naive about context; they just assume it's set up and ready to go. Also keep in mind that GL's object naming is very simple for most drivers; every context starts with object 1 as the first object allocated, and just increments it for further objects, meaning that GL has no way to tell which context the texture you're referring to is supposed to belong to. That means that when you ask it to delete texture 1, it's just deleting texture 1 in whatever happens to be the current context.

I would strongly recommend following Waterwalker's advice and sharing a context among all your widgets, for a number of reasons. First, you'll consume less memory only having a single copy of each texture loaded at once. Second, context switching can be a VERY expensive operation, so you should always avoid multiple contexts whenever possible. Third, you won't have to concern yourself with the active context.

Share this post


Link to post
Share on other sites
Quote:
Original post by antimouse
Waterwalker, thanks for replying. I'll try your suggestion, it seems better than what I'm doing. Still, I'm curious about why deleting those 2 textures are interfering with the GLCamWidget one. Do you have any clue?

Just as Shinkage said I would assume that the GLCamWidget's context is active when you call delete on the textures of the other widget. Hence the texture id's 1 and 2 in the GLCamWidget get deleted, not the ones of the other widget you are closing.

Share this post


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

  • Similar Content

    • 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?
    • By Jonathan2006
      My question: is it possible to transform multiple angular velocities so that they can be reinserted as one? My research is below:
      // This works quat quaternion1 = GEQuaternionFromAngleRadians(angleRadiansVector1); quat quaternion2 = GEMultiplyQuaternions(quaternion1, GEQuaternionFromAngleRadians(angleRadiansVector2)); quat quaternion3 = GEMultiplyQuaternions(quaternion2, GEQuaternionFromAngleRadians(angleRadiansVector3)); glMultMatrixf(GEMat4FromQuaternion(quaternion3).array); // The first two work fine but not the third. Why? quat quaternion1 = GEQuaternionFromAngleRadians(angleRadiansVector1); vec3 vector1 = GETransformQuaternionAndVector(quaternion1, angularVelocity1); quat quaternion2 = GEQuaternionFromAngleRadians(angleRadiansVector2); vec3 vector2 = GETransformQuaternionAndVector(quaternion2, angularVelocity2); // This doesn't work //quat quaternion3 = GEQuaternionFromAngleRadians(angleRadiansVector3); //vec3 vector3 = GETransformQuaternionAndVector(quaternion3, angularVelocity3); vec3 angleVelocity = GEAddVectors(vector1, vector2); // Does not work: vec3 angleVelocity = GEAddVectors(vector1, GEAddVectors(vector2, vector3)); static vec3 angleRadiansVector; vec3 angularAcceleration = GESetVector(0.0, 0.0, 0.0); // Sending it through one angular velocity later in my motion engine angleVelocity = GEAddVectors(angleVelocity, GEMultiplyVectorAndScalar(angularAcceleration, timeStep)); angleRadiansVector = GEAddVectors(angleRadiansVector, GEMultiplyVectorAndScalar(angleVelocity, timeStep)); glMultMatrixf(GEMat4FromEulerAngle(angleRadiansVector).array); Also how do I combine multiple angularAcceleration variables? Is there an easier way to transform the angular values?
  • Popular Now