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. Qt3D VR rendering
Forum Update on Monday, May 27th 2025

Qt3D VR rendering

Scheduled Pinned Locked Moved Solved General and Desktop
2 Posts 1 Posters 424 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.
  • Brad Austin DavisB Offline
    Brad Austin DavisB Offline
    Brad Austin Davis
    wrote on last edited by
    #1

    I need to integrate a Qt3D project with OpenXR. However, the asynchronous model of of Qt3D doesn't really mesh very well with OpenXR APIs. Specifically, when I start an OpenXR frame, I get the eye poses I need to use for the rendering... I need to synchronously execute the render with those poses, and then submit the frame to OpenXR.

    Strictly speaking, I can submit poses to OpenXR that are different than the ones it gave me, but that just moves the problem to finding a reliable way to find out what the current camera poses are.

    So I need to be able to do one of two things...

    • Ensure that my most recent changes to the cameras via eyeCamera->lens()->setProjectionMatrix and eyeCamera->transform()->setMatrix are properly applied when I next call m_renderAspectPrivate->renderSynchronous(false)

    OR

    • Immediately after calling m_renderAspectPrivate->renderSynchronous(false), be able to determine the exact projection matrix and transform used by the eye camera

    Right now I'm working in 5.13.1 but I know there have been some changes in this area in 5.14 and I'm happy to switch if it will make solving this problem easier.

    1 Reply Last reply
    0
    • Brad Austin DavisB Offline
      Brad Austin DavisB Offline
      Brad Austin Davis
      wrote on last edited by
      #2

      I eventually discovered that the frame latency was not inside the Qt code, but on my side, in the order I was calling OpenXR functions and Qt functions.

      1 Reply Last reply
      3

      • Login

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