Search Issue Tracker
Active
Under Consideration for 1.12.X
Votes
0
Found in [Package]
1.8.2
Issue ID
OXRB-233
Regression
Yes
[OpenXR] Average Fill Percent Per Eye is exceedingly high when using Vulkan along Oculus Integration and OpenXR MetaXR Feature which causes significant performance impact
Steps to reproduce:
1. Open the attached user project "OpenXR Passthrough Test.zip"
2. Install OVR Metrics tool into the Quest 2 headset
3. Switch to Android in the Editor
4. In CMD prompt or Terminal type in "adb shell ovrgpuprofiling -e/--enable-detailed"
5. Navigate in the OVR Metrics tool to enable the "Average Fill Percent Per Eye" under the Stats Tab
6. Build the project to Quest 2
7. Observe the "Fill" stat
Expected results: No performance impact when using Vulkan along with Oculus Integration and OpenXR MetaXR Feature
Actual results: Average Fill Percent Per Eye is exceedingly high when using Vulkan along Oculus Integration and OpenXR MetaXR Feature which causes significant performance impact
Reproducible in: OpenXR 1.5.0 - 1.8.2 (2021.3.29f1, 2022.3.7f1, 2023.1.7f1, 2023.2.0b4)
Not Reproducible in: OpenXR 1.4.2 (2021.3.11f1)
Reproducible on: Windows 10 2H22
Not reproducible on: No other environment tested
Notes:
-Issue reproduces with Multi-pass and Single Pass Instanced
-Issue only reproduces on Vulkan
-Issue only reproduces with OpenXR
-Issue only reproduces when MetaXR Feature is enabled
-Issue only reproduces when Oculus Integration asset is present
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Add comment