Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.2f1
Issue ID
1118453
Regression
No
[Android] Visual artifacts in Android Player due to rounding errors on GLES3 builds with YUV image encoding
Steps to reproduce:
1. Open the attached project
2. Build and Run to android device
3. Compare the image on the device to the one in the editor. Notice that it's striped/glitched out (editor.png vs player.png)
Reproducible with: 2017.4.18f1, 2018.3.0b1, 2018.3.0f1, 2018.3.3f2, 2019.1.0b1, 2019.2.0a3
Notes:
- Tested on OpenGLES3. Vulkan works fine on all devices, OpenGLES2 results in a pink screen
DUT:
Reproducible with:
Samsung Galaxy S9+ (SM-G965F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
Samsung Galaxy S7 (SM-G930F), Android 7.0, CPU: Exynos 8 Octa 8890, GPU: Mali-T880
Samsung Galaxy S4 (GT-I9505), Android 5.0.1, CPU: Snapdragon S4 Plus MSM8960, GPU: Adreno (TM) 320
Not reproducible with:
Samsung Galaxy S8 (SM-G950U), Android 7.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
Google Pixel XL (Pixel XL), Android 9, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530
Samsung Galaxy S7 (SM-G930V), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
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 when reimporting fbx asset used as tree by specific Terrain component
- The position of the "X" in the search section is not consistent with other search boxes in the engine
- Unable to pan outside of the active state viewing window in the Animator when the Play Mode is paused
- Window Zoom stops working after Editor window is moved
- Some package directories are not found, and errors are thrown in the Console when the project path is quite long
Resolution Note (2019.2.X):
Shader is using "float" types for columns/rows/indexes that introduces precision errors. Changing appropriate variable types to integers fixes the issue.