Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
0
Found in
2019.4.13f1
2020.2.0b6
Issue ID
1284748
Regression
No
Validation - Unity on launch can take a while to compile shaders but it tells the user it's Initializing Package Manager
When reopening a project, Unity seems to hang at the "Find Available Build Targets" or "Initializing Package Manager". Unity at this point seems to be recompiling shaders.
The logging is incorrect.
Steps to reproduce
- Clone project git@github.cds.internal.unity3d.com:unity/benchmark-office.git -b 2020.2.
- Open it, with 2020.2.0b8
- Once finished. Close the project and reopen.
Notice issue - project hangs on "Find Available Build Targets" or "Initializing Package Manager". It's not actually hanging but taking a while to compile without logging. Some customer reports have this up to 10 minutes.
Tested broken: Windows 10, 2020.2.0b6, 2020.2.0b1, 2020.2.0a1 (crashes on reopening), 2020.2.0a15 (crashes on reopening), 2019.4.13f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on mono_class_inflate_generic_method_full_checked when accessing static properties or methods of a Generic Interface in a Generic Class
- Crash on RendererScene::NotifyInvisible when switching QualitySettings of the HDRP pipeline asset in a specific project
- Compute and graphics queues are not run asynchronously when asynchronous compute shaders are enabled in DX12
- Unity Version Control window during "Create workspace" updates only when the mouse is moved
- Crash on AudioMixer::GetFloat when entering Play Mode in a specific project
Add comment