Search Issue Tracker
Not Reproducible
Votes
7
Found in
2019.3.0a9
2019.3.0f6
2020.1
Issue ID
1217274
Regression
Yes
Culling performance regression when spawning a large amount of primitive models
How to reproduce:
1. Open the "SampleScene" Scene in the attached "1217274.zip" project
2. Open the Profiler window
3. Ensure that Module details panel is set to Timeline
4. Enter Play Mode
5. Exit Play Mode after getting a "Finished Benchmarking" message in the Console window
6. Observe the Culling performance in the Timeline Module
Expected result: The time that it takes for culling stays relatively the same or lower throughout versions
Actual result: The time that it takes for culling has increased by an average of 3 ms
Reproducible with: 2019.3.0a9, 2020.1.0a20
Not reproducible with: 2017.4.37f1, 2018.4.17f1, 2019.3.0a8
Could not test with: 2019.3.2f1, 2020.1.0a21, 2020.1.0a24 (Editor freezes when entering Play Mode)
Comments (2)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Per-Morten
May 06, 2020 06:44
If you create a standalone build with the supplied project you can easily see the performance drop, even if you go as far down as 50000 cubes (then there's a performance regression of around ~0.6-0.7ms). It's not easy to see the difference with anything lower than that.
Also, if the editor freezes now, but didn't freeze before, perhaps that is something else that should be looked into?