Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.2.0p4
2017.2.0a1
Issue ID
1029389
Regression
Yes
[Android] Textures become black in the build
To reproduce:
1. Open the project, attached by the user (knight_j3_render_bug.zip)
2. Build and run the project for Android
3. On the device, touch the screen a few times to forward the intro
4. Finally, observe that when the actual game play scene opens, the textures are black
Expected: the textures are not black
Reproduced in 2017.2.0a1, 2017.2.0p4, 2017.2.2p4, 2017.3.2f1, 2017.4.0f1
Did not reproduce in 2017.1.4f1, 2017.4.2f2, 2018.1.0f2, 2018.2.0b4, 2018.3.0a1
Regression introduced in 2017.2.0a1
Reproduced only on
Samsung SM G903F*, OS:6.0.1, CPU:armeabi-v7a, GPU:Mali-T720, Build:samsung/s5neoltexx/s5neolte:6.0.1/MMB29K/G903FXXU1BQC1:user/release-keys
Fixed in 2017.4.1f1
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