Search Issue Tracker
Duplicate
Votes
0
Found in
2017.2.0b4
Issue ID
934976
Regression
Yes
Editor start up times are through the roof in 2017.2
Editor start up times are getting slower and slower with every release. For starting an empty project (on my machine):
Unity 4.2.2 - 3 seconds
Unity 2017.1 - 11 seconds
Unity 2017.2 - 18 seconds
These times are just nuts. We're slower than even Visual Studio!!!
To repro, just launch Unity with "Unity.exe -createProject <someEmptyProject>", and see how long it takes for the editor to launch.
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 ProfilerSymbolsDelayedDeletion::AddCloneObject when deserializing an object-instantiate marker with a dangling/corrupt name string
- Characters overlap preceding text when monospace tags are used on a TMP_Text component set to RTL
- Wrong range is displayed in a 'resolutionPerPatch is clamped to the range of' warning
- Debug mode fails to build in Visual Studio when .csproj file is generated for Built-in packages
- "Too many sprite tiles on Image" error is spammed in the Console when editing Pixels Per Unit Multiplier on a Tiled Image Type for Scroll View
Add comment