Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
Issue ID
1159300
Regression
No
[PostProcessing] [Ambient Occlusion] Ambient Occlusion result incorrect
How to reproduce:
1. Open the attached project
2. Go to the Hierarchy window/KFS_Framework_v2.0/VRRigMaltiplayer/Head
3. Go to the Inspector window-> Disable and Enable "Post Processing Behavior (script)" Component
4. Inspect the joint between a wall and ground
Actual: Ambient Occlusion result is incorrect (link for the video attached in the Edit section)
Reproducible with: 2018.3.14f1, 2018.4.2f1
Note: Could not strip the project because the issue disappears, could not test on 2018.3 earlier versions, 2019.1, 2019.2 and 2019.3 because of the thrown errors and broken lights
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
- [Mobile] Player Crash on scripting_invoke_profiler_begin when the built Player Scene has an empty UIDocument and is built on IL2CPP
- Unnecessary Warnings are logged when running Player with -batchmode -nographics
- [Android] [iOS] Application silently crashes when creating and setting up Textures2D in large amounts
- Some VFX Window Panels close on entering Play mode
- VFX Graph using Redo action for Move and Connect node results in an unknown input value
Resolution Note:
This project is using PostProcessing v1 which has been deprecated with 2018.1. The fact that the issue "disappeared" means that it's either a project setup issue or a weird rendering state the editor got stuck in (from the look of it, I'd say the generated normal buffer is wrong).