Search Issue Tracker
Fixed in 2022.1.X
The time Required to load Gameobjects or Prefab instances does not scale linearly
Steps to reproduce:
1. Open User-supplied project
2. Open Scene ("Transform_10000) with 10000 objects
3. Run Test -> Measure Open/Close Current Scene and Inspect the time in Console Window
4. Open Scene ("Transform_50000) with 50000 objects
5. Run Test -> Measure Open/Close Current Scene and Inspect the time in Console Window
Expected: the time scales linearly
Actual: the time does not scale linearly
Reproduced in: 2017.4.33f1, 2018.4.12f1, 2019.2.10f1, 2019.3.0b8, 2020.1.0a9
Reproduces on Asset Pipeline V2 and V1
Reproduces on Mixed, Force Binary, and Force Text Asset Serialization
* Loading prefab instances is more expensive than loading game objects.
* Saving prefab instances is significantly faster than saving game objects.
* The time Unity requires to load Gameobjects or prefab instances does not scale linearly with the number of objects.
* The time Unity requires to save Gameobjects does not scale linearly with the number of objects.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Camera active Texture is not written if another camera has a Script using "OnRenderImage"
- The Camera's background color is white when the device Appearance is "Light Mode"
- Particle System isn't culled off-screen when the Culling Mode is set to Automatic and the Simulation Space is set to World
- Main Player window is moved to the primary display when it's launched on a 3rd monitor and the 2nd monitor is activated
- Crash on Mesh::RecalculateBounds when assigning not enough vertices for two submeshes