Search Issue Tracker
Fixed in 2.2.3
Found in [Package]
[XR][Post Processing] Ambient Occlusion effect moves when moving HMD and using Multi Scale Volumetric Obscurance
How to reproduce:
1. Open the 1150006-ReproProject Project
2. Open the Scenes/SampleScene Scene
3. Enter the Play Mode
Expected Result: Ambient Occlusion effect stays in the same place
Actual Result: Ambient Occlusion effect moves when moving the HMD
Reproducible with 2019.1.0a11, 2019.1.2f1, 2019.2.0b2, 2019.3.0a2
Not Reproducible with 2018.3.14f1, 2018.4.0f1
Note1: This issue appears to be related to the Unity Editor version and not the Post Processing package version
Note2: Could not test on earlier 2019.1 than 2019.1.0a11 versions because of compile errors
Note3: Scalable Ambient Obscurance is not affected
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- The Editor does not recognize button release when first releasing the "LShift" button and then "Numpad2"
- Reflection Probe doesn't load until it's selected in the Hierarchy window when the project has been opened
- "ArgumentNullException" error in the Console when selecting certain ScriptableObjects and entering Play Mode
- Configurable joints become bouncier when setting "Bounciness" below 1
- Prefabs get corrupted when editing Particle System curves
Dec 25, 2019 13:16
waiting and hoping, no other good solution found yet >.<
Nov 25, 2019 12:09
I have this issue too with TAA in 2019.2.13 with UWP VR (w/ Mixed Reality Headset)
Sep 24, 2019 03:52
Changing the AO mode on the Post Process Volume component from the default "Multi Scale Volumetric Obscurance" to "Scalable Ambient Obscurance" is a workaround in the meantime. Tested on both 2019.1.11f1 and 2019.2.6f1.
Aug 21, 2019 16:50
I have reproduced this issue on Unity 2019.2.1f1 on the relatively new Postprocessing 2.1.7.
Outside of VR, the effect works as expected:
in VR, there are some obvious issues:
Any progress or timeline on the fix? Thank you!
May 10, 2019 04:55
This bug seems to affect TAA in VR as well, as was reported on the official GitHub repo: