Search Issue Tracker
In Progress
Fix In Review for 6000.0.X, 6000.1.X
Fixed in 6000.2.0b1
Votes
15
Found in
6000.0.23f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-84612
Regression
Yes
The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
How to reproduce:
1. Open the user's attached project
2. Build And Run the project on Meta Quest 2
3. Put on the headset
Expected results: The Scene is shown on the screen
Actual results: The screen is black
Reproducible with: 6000.0.22f1, 6000.0.23f1
Not reproducible with: 6000.0.21f1
Could not test with: 2021.3.45f1, 2022.3.50f1 (compilation errors in the Console window)
Reproducible on these devices:
Oculus (Quest 2), Android 12.1, CPU: Snapdragon XR2, GPU: Adreno (TM) 650
Reproducible on: Windows 10 22H2
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- “UnityException: GetInvalidFilenameChars” errors are thrown, and the Overlay Save Preset button becomes unusable when entering Play Mode with a shortcut while Overlay Save Preset window is opened
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
Add comment