Search Issue Tracker

Fixed

Fixed in 1.9.0

Votes

13

Found in [Package]

1.9.0

Issue ID

OXRB-164

Regression

Yes

[OpenXR] Editor performance drops extremely after HMD becomes inactive using OpenXR due to GFX.WaitForRenderThread while in Play Mode

Package: OpenXR Plugin

-

Steps to reproduce:
1. Open the attached user's project "XRPerformance.zip"
2. Connect the Oculus link to Quest 2
3. Make sure OpenXR is selected as the XR Plugin
4. Open the Profiler
5. Enter Play Mode
6. Observe the Profiler while the headset is active (press a finger over the sensor)
7. Dismount the headset for it to become inactive
8. Observe the GFX.WaitForRenderThread in the Profiler climbing rapidly when the headset is inactive

Expected results: Editor performance does not drop extremely after HDM becomes inactive using OpenXR due to GFX.WaitForRenderThread
Actual Results: Editor performance drops extremely after HDM becomes inactive using OpenXR due to GFX.WaitForRenderThread

Reproducible in: OpenXR 1.5.0, 1.7.0 (2020.3.47f1, 2021.3.24f1, 2022.2.18f1, 2023.1.0b15, 2023.2.0a13)
Not reproducible OpenXR 1.4.2 (2020.3.47f1)

Notes:
-Issue only reproduces with OpenXR as the XR Plugin provider
-As per user comments it's also reproducible in Build

  1. Resolution Note (fix version 1.9.0):

    This issue has been resolved and will be included in an upcoming release.

Log in to vote on this issue

Comments (2)

  1. FabioGavinelli

    Oct 04, 2023 08:39

    I am still facing the problem too

  2. saif-studio-b12

    Sep 19, 2023 12:12

    I am still facing this issue in Unity version 2022.2.21.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues