Search Issue Tracker
Fixed
Fixed in 6000.0.50f1, 6000.1.4f1, 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
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 6000.1.4f1):
XR: Fix a specific instance where the player would render a black screen when using XR and the copydepth pass
Resolution Note (fix version 6000.0.50f1):
XR: Fix a specific instance where the player would render a black screen when using XR and the copydepth pass