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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
GCCooper
May 09, 2022 20:48
Duplicate of...?