Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.4f1
Issue ID
1159632
Regression
No
[Android] Black artifacts on a Reflection Probe with Post Processing on certain device after rotating it to a portrait position
To reproduce:
1. Download "Shader Calibration Scene" from the Asset Store;
2. Open "CalibrationScene";
3. Build and run the scene on Android devices;
4. Rotate device to the Portrait position.
Expected results: the scene is rendered correctly.
Actual results: black artifacts are rendered on game object that uses Reflection Probe when Temporal Anti-Aliasing is enabled in Post Processing Profile
only on Samsung Galaxy S9 with Mali-G72 GPU. This happens with all Graphics APIs: Vulkan, OpenGLES3, OpenGLES2.
Reproduced with: 2019.2.0b5, 2019.3.0a6
Devices under testing:
Reproduced with:
VLNQA00122, SAMSUNG SM-G960F, Exynos 9 Series 9810, Mali G72, 8.0.0
VLNQA00149, SAMSUNG SM-G960F, Exynos 9 Series 9810, Mali-G72, 9.0.0
Not reproduced with:
VLNQA00138, HUAWEI P20 Pro, HiSilicon Kirin 970, Mali-G72, 8.1.0
VLNQA00267, Samsung Galaxy S10+, Exynos 9 Series 9820, Mali-G76, 9.0.0
VLNQA00006, SAMSUNG SM-G930F, Exynos 8 Octa (8890), Mali-T880, 8.0.0
VLNQA00004, MEIZU, MX5, Snapdragon 200 MSM8225Q, PowerVR Rogue G6200, 5.0.1
VLNQA00219, SAMSUNG SM-N960U, Snapdragon 845 SDM845, Adreno (TM) 630, 8.1.0
VLNQA00150, SAMSUNG SM-G960U, Snapdragon 845 SDM845, Adreno (TM) 630, 8.0.0
VLNQA00263, GOOGLE Pixel 3, Snapdragon 845, Adreno (TM) 630, 9.0.0
VLNQA00027, XIAOMI, MI MAX, Snapdragon 650 MSM8956, Adreno (TM) 510, 7.0.0
VLNQA00034, LGE, Nexus 4, Snapdragon S4 Pro APQ8064, Adreno (TM) 320, 5.1.1
VLNQA00111, SAMSUNG, SM-J510FN, Snapdragon 410 MSM8916, Adreno (TM) 306, 7.1.1
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note (2019.3.X):
Won't fix: affects only specific device, caused by depth of field post processing, post processing v1 is not supported anymore.