Search Issue Tracker
Fixed in 2.0.13-preview
Votes
2
Found in [Package]
2.0.8-preview
Issue ID
1059893
Regression
Yes
[iOS] [Post Processing] Ambient Occlusion does not work
To reproduce:
1. Open project
2. Build and run on iOS device
Expected vs Actual: Game view should look identical in editor and iOS build(see images attached)
Reproduced: 2018.2.0a7, 2018.2.0f2, 2018.3.0a3
Not reproducible: 2017.3.2f1, 2017.4.6f1, 2018.1.8f1
Could not reproduce on 2018.2.0a1-2018.2.0a7 because of compiler errors
Comments (3)
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
- Huge memory allocations when TMP dynamically adds glyphs from AssetBundle fonts
- “Redefinition of 'LOD_FADE_CROSSFADE'" shader errors thrown when opening SpeedTree9_URP.shadergraph in Universal 3D Template
- NullReferenceException is thrown and the window is broken when opening the "Active Scenario" window in Multiplayer Center
- Invalid Blue value in MotionBlurMergeTilePass when objects move at certain speeds
- Physics Debugger displays mouse cursor ray casts when Game view is not open if Input System package is used
AurimasA
Oct 11, 2018 11:43
Hi GHUBERT_TWIN,
I just retested the issue with Unity 2018.2.7f1 using Post-processing Version 2.0.14 - preview and it is working for me just fine.
Please make sure you are using the latest Post-processing package version in your project.
Navigate to Window > Package Manager and select Post-processing package.
Bellow package name you can see the current package version that you are using.
If you press the version number in the top right corner, a pop-up list will open with the latest version in the top and current version below. Select latest version and press Update to button.
Now it should be the latest version and as I am currently writing this, the latest version available in Package manager window is 2.0.14 - preview.
Hope this helps.
Unity QA Team
ghubert_twin
Oct 11, 2018 06:44
Aint just resolved at all guys wtf ^^ using 2018.2.7f1
jbergs
Sep 07, 2018 14:14
What version was this fixed in? There's been several releases since this. Does anyone know?