Search Issue Tracker
Fixed in 2.2.3
Votes
32
Found in [Package]
2018.3.14f1
2019.1.0a11
2019.2.0a1
2019.3.0a1
Issue ID
1150006
Regression
Yes
[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
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Hexagonon
Dec 25, 2019 13:16
waiting and hoping, no other good solution found yet >.<
francescocagnetta
Nov 25, 2019 12:09
I have this issue too with TAA in 2019.2.13 with UWP VR (w/ Mixed Reality Headset)
snobalpaul
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.
AndyKorth
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:
https://i.imgur.com/KbRg0V7.png
in VR, there are some obvious issues:
https://i.imgur.com/pTYfpwa.jpg
Any progress or timeline on the fix? Thank you!
ManvydasVextur
May 10, 2019 04:55
This bug seems to affect TAA in VR as well, as was reported on the official GitHub repo:
https://github.com/Unity-Technologies/PostProcessing/issues/792