Search Issue Tracker
By Design
Votes
1
Found in [Package]
4.2.0
4.3.0-pre.1
Issue ID
OXPB-159
Regression
No
CPU is level 5 when a project with an empty Scene is deployed on Meta Quest 2
How to reproduce:
1. Open the attached project "HighCPUTest.zip"
2. Make sure that Basic OVR Metrics HUD is enabled on Meta Quest 2
3. Build And Run the project on Meta Quest 2
Expected results: "CPU L" is lower than 5
Actual results: "CPU L" is 5
Reproducible with: 4.2.0, 4.3.0-pre.1 2022.3.47f1, 6000.0.21f1)
Could not test with: 2021.3.44f1 (compilation errors in Console window)
Reproducible on: Oculus (Quest 2), Android 12.1, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Not reproducible on: No other environment tested
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
- IndexOutOfRangeException occurs when entering "<a></a>" tags in a TextMeshPro UI field
- Numeric property drag cursor gets enabled in the Inspector Preview window when the window is above numeric properties
- UI elements become unusable due to Object and Text Fields being set to empty/"0" when clicking "Reset" on their Components
- Scene Asset is not attached to a Lighting Data Asset for a URP Package Sample Scene
- Gizmos are not rendered for the Base Camera when using Camera Stacking
Resolution Note:
Unity does not set any CPU and GPU levels by default for Meta platforms. Please follow the Meta documentation, they allow the app creator to request what levels they would like the device to run at: https://developers.meta.com/horizon/documentation/unity/os-cpu-gpu-levels/#setting-cpu-and-gpu-levels.