Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0p4
Issue ID
954113
Regression
No
[OpenGL ES 3.0][Android] Visual artefacts due to rounding errors on Android GLES3 builds with YUV image encoding
When an image is encoded in YUV NV21 format, visual artefacts are visible on certain Android devices.
Steps to reproduce:
1) Open the attached project.
2) Set the Graphics API to OpenGL ES 3.0.
3) Build & Run on an Android device (Galaxy S7/S7Edge w/ Android 7).
The image is striped and discolored. This does not happen with OpenGL ES 2.0 and Vulkan. Not all devices reproduce this issue.
Reproduced on:
2018.1.0a1 (trunk as of 20/10/2017), 5.6.2f1
Devices:
Samsung Galaxy S7 (Global) 4x ARM Cortex-A53@1586 + 4x Samsung Exynos M1@2600 w/ Android 7.0 - reproduced
Samsung Galaxy S7 (Verizon) Qualcomm Kryo 2x@1593 + 2x@2150 w/ Android 7.0 - did not reproduce
LG G4 1.8GHz 2x ARM Cortex-A57 MPcore + 4x ARM Cortex-A53 MPcore w/ Android 6.0 - did not reproduce
The user was also able to reproduce this issue on a Samsung Galaxy S7 Edge Qualcomm Snapdragon 820 w/ Android 7.0
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