Search Issue Tracker
Third Party Issue
Votes
1
Found in [Package]
4.0.0
Issue ID
OXPB-135
Regression
No
[Quest][OculusXR] CPU/GPU reported by OVRMetrics is 2x higher with OculusXR than when compared to OpenXR
Steps to reproduce:
1. Open the attached user's project "URP VR 2023.zip"
2. Make sure OVR Metrics tools are installed via Meta Developer Hub and GPU/CPU Levels are enabled
3. In the Unity Editor, make sure OculusXR is selected as the XR Plugin
4. Build for Quest 2/3
5. In the Application, the overlay reports CPU and GPU levels as 4
6. Switch to OpenXR in the Editor and Build for Quest 2/3
7. Observe in the Application that the overlay reports CPU and GPU levels as 2 within the same Scene
Expected Result: CPU/GPU level reported by OVRMetrics is the same when compared to using OpenXR
Actual Result: CPU/GPU level reported by OVRMetrics is 2x higher than when compared to using OpenXR
Reproducible with: OculusXR 4.1.2 (2023.3.0b1)
Could not test on 2021.3.33f1, 2022.3.16f1, 2023.2.5f1 due to URP package errors after downgrading
Testing Environment: Windows 11
Not reproducible on: No other environment tested
Notes:
-Issue does not reproduce on a new project
-Issue reproduces with Vulkan and OpenGLES3
-Issue does not reproduce with OpenXR, GPU and CPU levels stay the same (reported by OVR Metrics at 2)
-Forum post: https://forum.unity.com/threads/2020-3-2023-3-urp-standalone-vr-performance.1487736/
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory Leak warnings are thrown when creating a new material
- The type selector in the UI Builder does not display primitive types when trying to select one in the "Select Type…" window
- Inspector's custom tooltip is displayed incorrectly when the name is truncated in UI toolkit
- Crash on ScriptableRenderLoopDraw when rendering a specific VFX in Play Mode
- The script is not renamed in the Project window when renaming and a compilation Error is present
Resolution Note:
We've determined that this is a Meta issue and have communicated that to Meta.