Search Issue Tracker
Fixed in 2020.3.41f1
Fixed in 2020.3.X, 2021.3.X, 2021.3.11f1
Votes
6
Found in
2020.3.35f1
2021.3.4f1
Issue ID
UUM-7568
Regression
No
Loading a scene with a large amount of light probes causes a performance spike
Steps to reproduce:
- Download and open user attached project (lightmaptest.zip)
- Open the "startingscene" scene & the profiler
- Start play mode
- Press "T" key to load using Additive
- Observe spike in profiler
- Stop play mode
- Repeat above, but press "Y" key to load using Single
Notes:
- We thought that is reproduces in 2021.3.5f1, 2022.1.7f1, 2022.2.0a13, 2023.1.0a1, but that was only a "few milliseconds spike", not the "few seconds spike" the user is seeing.
- Both LoadSceneMode.Single and LoadSceneMode.Additive causes a performance spike
- PostLoadSceneStaticLightmapSettings seems to be the culprit (see attached screenshots)
Comments (1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
TimHeijden2
Jul 08, 2022 07:21
Discussion about this issue is ongoing:
https://forum.unity.com/threads/additively-loading-scene-with-large-amount-of-lightprobes-causes-massive-performance-spike.1295442/#post-8254749