Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. OpenGL QWidget Issues
Forum Updated to NodeBB v4.3 + New Features

OpenGL QWidget Issues

Scheduled Pinned Locked Moved Unsolved General and Desktop
3 Posts 2 Posters 535 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • webzoidW Offline
    webzoidW Offline
    webzoid
    wrote on last edited by
    #1

    I've posted previously about having OpenGL issues when using QWidgets and more of the same is happening.

    We have a OpenGL application which uses a QOpenGLWidget and running here on my machine which supports OpenGL 4.4, the application works perfectly well in both debug and release mode.

    Once the application is installed onto two machines owned by a client (one running Win10 and OpenGL 4.0, the other running Win7 and OpenGL 3.3), the software runs but there is either a transparent OpenGL window created or the QOpenGLWidget fails to be created. Either way, the application appears "broken" to the client, which isn't a great situation to be in.

    I've used something called OpenGL Extension Viewer to determine the features supported on both my development machine and the clients computers, however, is there any way by which I could narrow down which of these features is causing the issue on the clients machines? My guess is that there is some un-supported feature being used by the QOpenGLWidget but how can I ever find out what?

    On my previous post, there was suggestion of using the setVersion function of the QSurfaceFormat but this made no difference at all - even trying to specify version 1, 0.

    Not being of OpenGL ilk, I'm a little baffled as to what I'm actually looking for so any additional help would be greatly received.

    This is the previous post for reference:

    https://forum.qt.io/topic/85449/opengl-and-specific-version-support

    m.sueM 1 Reply Last reply
    0
    • webzoidW webzoid

      I've posted previously about having OpenGL issues when using QWidgets and more of the same is happening.

      We have a OpenGL application which uses a QOpenGLWidget and running here on my machine which supports OpenGL 4.4, the application works perfectly well in both debug and release mode.

      Once the application is installed onto two machines owned by a client (one running Win10 and OpenGL 4.0, the other running Win7 and OpenGL 3.3), the software runs but there is either a transparent OpenGL window created or the QOpenGLWidget fails to be created. Either way, the application appears "broken" to the client, which isn't a great situation to be in.

      I've used something called OpenGL Extension Viewer to determine the features supported on both my development machine and the clients computers, however, is there any way by which I could narrow down which of these features is causing the issue on the clients machines? My guess is that there is some un-supported feature being used by the QOpenGLWidget but how can I ever find out what?

      On my previous post, there was suggestion of using the setVersion function of the QSurfaceFormat but this made no difference at all - even trying to specify version 1, 0.

      Not being of OpenGL ilk, I'm a little baffled as to what I'm actually looking for so any additional help would be greatly received.

      This is the previous post for reference:

      https://forum.qt.io/topic/85449/opengl-and-specific-version-support

      m.sueM Offline
      m.sueM Offline
      m.sue
      wrote on last edited by
      #2

      Hi @webzoid

      Please give a screenshot of the transparency issue and a description of the error you get when you want to create the OpenGLWindow.

      -Michael.

      1 Reply Last reply
      0
      • webzoidW Offline
        webzoidW Offline
        webzoid
        wrote on last edited by
        #3

        @m-sue Thanks for your response.

        It's not a "transparency" issue as such, more the previous contents of the OpenGL framebuffer which is making it look transparent. I'm not able to log into the clients computer at the moment but as soon as I can, I will post some screenshots.

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved