Search Issue Tracker
Fixed
Fixed in 2020.2.X
Votes
2
Found in
2020.2
Issue ID
1276114
Regression
Yes
[Android] Loading the Viking Village scene takes a couple of minutes
Steps to reproduce:
1. Get the URP project from https://github.com/Unity-Technologies/VikingVillage/tree/master (use the master branch)
2. Change target platform to Android
3. Build and Run to an Android device
Expected results: The scene starts a few seconds after the splash screen is displayed
Actual results: Black screen lasting over 1-2 minutes before the scene starts rendering
Reproducible with: 2020.2.0b7
Reproducible on:
Samsung Galaxy S10 (SM-G973F), Android 10, CPU: Octa-core, GPU: Mali-G76
Samsung SM-G960U1, Android 10, GPU: Adreno 630
Samsung SM-N960F, Android 10, GPU: Mali-G72
HUAWEI CLT-L29, Android 8.1, GPU: Mali-G72
Notes:
-Not reproducible with any 2019.4 or 2020.1 build
-It is also possible to reproduce using the built-in renderer version of Viking Village
Comments (3)
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
theyorgis
Nov 24, 2020 19:32
2020.2 has a massive loading time problem and it can never be production worthy without fixing these in a timely manner. This is especially upsetting since for those who depend on URP combined with XR, the situation is a total assault on developers: URP with XR is an unfinished pile of junk unless you're using a beta version of Unity (URP 8 is a disaster with XR), but then you end up stuck between a rock and a hard place because the 2020.2 branch has this major glaring issue dragging back since June... no hurry, guys, right? smooth sailing. Take your time.
ROBYER1
Nov 20, 2020 16:12
This one took a while, been going on about this since June, hoping for a fix soon.