Search Issue Tracker
Fixed in 2018.2.X
Won't Fix in 5.6.X, 2017.1.X, 2017.2.X, 2017.4.X, 2018.1.X
Votes
0
Found in
2017.2.0p1
Issue ID
963224
Regression
Yes
Graphical glitches on certain materials when creating a build for Android devices with Vulkan API using Standard shader
Graphical glitches on certain materials when creating a build for Android devices with Vulkan API using Standard shader
To reproduce:
1. Open the attached project and create a build for Android making sure that Vulkan is selected as graphics API.
2. Observe on device that some of the objects don't appear correctly and they are several glithces as they bounce.
Actual: They are glithces in how the scene is presented on Android devices. It seems tha glitches differ between devices. On Samsung S7 they are certain artifacts while on Pixel XL the objects disappear completely. Videos attached
Expected: The objects should appear without glitches.
Reproducible: 5.6.4p1, 2017.1.2p2, 2017.2.0p1, 2018.1.0a1, 2018.1.0a3
Not reproducible: 2017.2.0f3
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