Search Issue Tracker
Duplicate
Votes
0
Found in
2020.3
2020.3.7f1
2021.1
2021.2
2022.1
Issue ID
1371729
Regression
Yes
[Performance][Oculus] GPU utilization is higher by ~20% and frame time is higher by 2.5ms on Quest 2 when using OpenGLES 3/2
Reproduction steps:
1. Open the attached user's project "CactusShaderOptimizations_2020.zip"
2. Make sure that Graphics API is set to OpenGLES 3 or 2
3. Switch to Android platform and Build to Quest 2
4. Install the OVR metrics through the Oculus Developer Hub
5. Enable the OVR metrics hud in the Oculus Developer Hub under Performance
6. Inspect GPU utilization and frame time in the headset
Expected result: GPU utilization and frame time is the same when using OpenGLES 3 or OpenGLES 2
Actual result: GPU utilization is higher by ~20% and frame time is higher by 2.5ms when using OpenGLES 3 or OpenGLES 2 (See attached Results.png)
Reproduces on: 2020.3.20f1, 2021.1.24f1, 2021.2.0b15, 2022.1.0a11
Does not reproduce on: 2019.4.31f1
Notes:
-GPU utilization is higher by ~30% in 2022.1.0a1 and up
-Issue does not reproduce when using Vulkan
-Issue reproduces with both OpenXR and Oculus plugins
Comments (1)
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
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
GCCooper
May 09, 2022 20:48
Duplicate of...?