Search Issue Tracker
Active
Under Consideration for 2022.3.X, 6000.1.X
Votes
0
Found in
2022.3.45f1
2022.3.50f1
6000.1.0a1
Issue ID
UUM-84755
Regression
No
[Quest] Foveation Level is 0 when SRP Foveation is enabled
Reproduction steps:
1. Open the attached project "ReproProj"
2. Connect Quest with Oculus Link
3. Build and Run the “Scenes/Foveate“
4. Use the OVR Metrics Tool to check the Foveation level
Expected result: The Foveation level is above 0 and the foveation is present
Actual result: The Foveation level is 0
Reproducible with: 2022.3.45f1, 2022.3.50f1, 6000.1.0a1
Reproducible on:
Android Player (VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650)
Windows Standalone Player (VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650)
Play Mode (VLNQA00379, Oculus (Quest 2), Android 10, CPU: Snapdragon XR2, GPU: Adreno (TM) 650)
Oculus Quest 3 (user reported)
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- Does not reproduce with Legacy Foveated Rendering Api (by changing the OpenXR plugin settings and changing the script to make calls to OVRManager instead of the new SRP API)
- Reproducible with Vulkan
- Reproducible with Oculus XR and OpenXR
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/HDRP/DownsampleDepth'" warnings are thrown after building a project
- Scene is not rendered and appears black when the Custom Renderer Feature is utilized
- The Context Menu is not updated in the Shortcuts menu when resolving a Binding Conflict
- [Quest] Foveation Level is 0 when SRP Foveation is enabled
- Freeze when displaying text with "-T" in Play mode
Add comment