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 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X
Votes
2
Found in
2019.4.29f1
2019.4.31f1
2020.3
2021.1
2021.2
2022.1
Issue ID
1375646
Regression
No
Poor performance when loading or unloading a large Scene
Reproduction steps:
1. Open the attached project "PerformanceTest.zip"
2. Open "Loader.unity" Scene
3. Enter Play Mode
4. Click "Load Heavy Scene" in the bottom left corner to load
5. Observe "time" to load in the bottom right corner.
6. Click "Load Heavy Scene" again to unload
7. Observe "time" to unload in the bottom right.
Expected result: The Scene loading and unloading time is similar to previous Editor versions
Actual result: The Scene loading and unloading time is slower than previous Editor versions
Reproducible with: 2019.4.29f1, 2020.3.17f1, 2021.1.17f1, 2021.2.0b9, 2022.1.0a6
Not reproducible with: 2019.4.28f1
-
Wawruch2
May 18, 2022 17:09
Same, it can take like 20-30minutes to load this amount of transforms, meanwhile older versions are doing it in like 10-20seconds. Going into playmode also takes 20-30minutes, sometimes it just freezes without going into playmode
-
tkslan
May 18, 2022 15:20
Hi, we have similar issue.
Heavy scene, loads of props (~60k) . Loads fast on 2021.3, on 2022.1 it take a few minutes.
Removing 10k props speeds up loading times, but still no compare to previous Unity versions.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2022.1.X):
This issue will be investigated further as part of our Domain Reload performance improvement as we are aware about the parts that could be further causing it. Will be closing this as the original source of the regression was fixed.