Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2019.1.0a2
Issue ID
1085573
Regression
No
[Android][LWRP] Shader compilation takes a very long time to start rendering the scene
1) Download attached project and open in Unity
2) Build and run project on a device
Observe the black screen (the app is not freeze, it just compiles the shaders very long)
Reproduced with:
2019.1.0a2 - 6 minutes took to launch the game scene (Nexus 7)
2018.3.0b4 - 7 minutes took to launch the game scene (Nexus 7)
Devices under testing:
Reproduced with:
VLNQA66653 Google Nexus 7, OS:5.1.1, CPU:armeabi-v7a, GPU:NVIDIA Tegra 3
VLNAQ00055 Samsung SC 06D (Galaxy S3), OS:4.1.2, CPU:armeabi-v7a, GPU:Adreno (TM) 225
Not reproduced with:
VLNQA00126 Samsung SM G800F (Galaxy S5 Mini), OS:6.0.1, CPU:armeabi-v7a, GPU:Mali-400 MP
VLNQA00202 Samsung Galaxy Note9, OS:8.1.0, CPU:arm64-v8a, GPU:Adreno (TM) 630
VLNQA00178 Xiaomi Redmi Note 4, OS:6.0, CPU:arm64-v8a, GPU:Mali-T880
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