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
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Add comment