Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. GlCopyTexImage2D() results in black image on iOS but works on Desktop
Qt 6.11 is out! See what's new in the release blog

GlCopyTexImage2D() results in black image on iOS but works on Desktop

Scheduled Pinned Locked Moved Mobile and Embedded
1 Posts 1 Posters 1.4k Views 1 Watching
  • 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.
  • K Offline
    K Offline
    k.gaitanis
    wrote on last edited by
    #1

    Hi,

    my application has the same configuration as the "OpenGL Under QML" example (http://qt-project.org/doc/qt-5.0/qtquick/scenegraph-openglunderqml.html).

    So i'm drawing raw openGL under QML components. After calling all my openGL commands on the default framebuffer (I do not use framebuffers at all, I rely on the QuickWindow for that and simply draw directly on the currently bound framebuffer) I want to use glCopyTexImage2D() to grab the contents of the default framebuffer and store them in a texture. All of this is done on the QSGRenderingThread ofcourse.

    This works great on desktop but on iOS it results in a black image. Are the openGL contents stored in a different framebuffer on iOS? How can I retrieve only my OpenGL content from the frameBuffer on iOS?

    Since blit operations are not available on OpenGL/ES, is there a way to capture the default framebuffer contents and store them in a texture or do I have to render on a separate framebuffer instead? I'd like to avoid rendering on a separate framebuffer for performance reasons.

    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