Search Issue Tracker
Fixed in 2018.3.X
Votes
1
Found in
2017.1.3f1
Issue ID
984290
Regression
No
[Android] Visual artefacts using Postprocessing Stack and GLES2
Steps to reproduce:
1) Download attached project and open in Unity
2) Make sure Graphics API is set to GLES2 in the Player Settings
3) Build and Run "OfflineTrainingScene" on a device
Expected result: No visual artefacts on the screen (check attached image "expected.png")
Actual result: Visual artefacts on the screen (check attached image "actual.png")
Reproduced with:
5.6.5f1, 2017.1.3f1, 2017.2.1p1, 2017.3.0p1, 2018.1.0b1
Devices under test:
Reproduced with:
0154 || Samsung Galaxy Note 8, OS: 7.1.1, CPU: Samsung Exynos 9 Octa, GPU: Mali-G71
0131 || Huawei P9, OS: 7.0, CPU: HiSilicon Kirin 955, GPU: Mali-T880
Not reproduced with:
5007 || Nvidia Shield Tablet, OS: 6.0, CPU: nVidia Tegra, GPU: GeForce ULP MP192
000037 || iPad Mini 2
Note: Works fine using GLES3 or Vulkan Graphics API
---------------------------------------------
Fixed in:
2018.3.0a6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment