Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Fixed in 2018.1.X
Votes
0
Found in
2018.1.0b7
Issue ID
1003263
Regression
Yes
Time it takes to create a new project is increasing to unreasonable levels compared to older versions
Steps to reproduce:
1. Create a new project on an older Unity version (e.g. 5.4)
2. Measure the time taken
3. Create a new project with a new Unity version (e.g 2018.2.0b7)
4. Measure the time taken
Expected result: similair or not too different times
Actual result: new version is taking an extreme amount of time
Notes:
Average of 3 runs for each version on SATA 6.0Gb/s 5400 RPM Hard Drive, i5-6400 2.7 GHz
18.1 51s
17.3 35s
17.2 25s
17.1 20s
5.6 22s
5.5 18s
5.4 11s
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build fails when building with ILCPP Scripting Backend and ARMv7 as the Target Architecture
- Textures turn black in Player when they are referenced by a script instance
- [Android] Virtual device crashes with "Scudo ERROR: invalid chunk state when deallocating address" error in Firebase Test Lab when Optimized Frame Pacing is enabled
- Particle System does not resume when its Culling Mode is set to "Pause" or "Pause and Catch-up," and particle position simulate in world space
- "Custom Render Queue" field cannot be set above "2000" when changing it in the Inspector window using Debug mode
Add comment