Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
3.1.0
Issue ID
1325664
Regression
No
[XR SDK][Post-Processing] Ambient Oclussion breaks in Play mode when XR is enabled
Reproduction steps:
1. Open the user's attached "XR Plugin Postprocessing Bug.zip" project
2. Load the SampleScene
3. Enter Play mode
Expected result: Ambient Occlusion is properly applied (see "AO_expected.png")
Actual result: Ambient Occlusion is broken (see "AO_actual.png")
Reproducible with: 2019.4.24f1, 2020.3.4f1, 2021.1.2f1, 2021.2.0a9
Not reproducible with: 2021.2.0a10, 2021.2.0a12
Could not test with: 2018.4.31f1 (XR SDK not available)
Notes:
- reproducible both with Single Pass Instanced and Multi-Pass Rendering mode
- the issue does not occur when "Initialize XR on Startup" in Project Settings is disabled
Tested with:
- Oculus Rift
- MockHMD
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 2D light leaks through ShadowCaster2D when ShadowCaster2D components are disabled then re enabled at runtime in Player builds
- Unity Hub redirects to The Unity Roadmap when navigating to “Send Feedback” option
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
- "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
Add comment