Search Issue Tracker

Fixed in 2022.2.X

Fixed in 2019.4.X, 2020.3.X, 2021.2.X, 2022.1.X

Votes

0

Found in

2019.4

2019.4.35f1

2020.3

2021.2

2022.1

2022.2

Issue ID

1399880

Regression

Yes

Culling Dynamic Objects takes significantly longer in 2019.4 and above compared to 2018.4

Culling

-

Reproduction steps:
1. Open project "BattleState-CullingTest2018.zip"
2. Open Build Settings window from File > Build Settings
3. Enable Development Build, Auto Connect Profiler, Deep Profiling
4. Build and Run the Scene "SampleScene"
5. Stop recording frames at around 100
6. In the Editor, open the Profile Analyzer window from Windows > Analysis > Profile Analyzer
7. Pull the data from the Profiler and save it
8. Repeat the process for 2018.4, then compare the data in the Profile Analyzer with the previous saved Data

Expected result: Newer versions of Unity take around the same time for Culling Dynamic Objects
Actual result: Newer versions of Unity take more time for Culling Dynamic Objects

Reproducible with: 2019.4.36f1, 2020.3.28f1, 2021.2.11f1, 2022.1.0b7, 2022.2.0a5
Not reproducible with: 2018.4.36f1

  1. Resolution Note (fix version 2022.2):

    Fixed in: 2022.2.0a8

  2. Resolution Note (fix version 2022.1):

    Fixed in: 2022.1.0b15

  3. Resolution Note (fix version 2021.2):

    Fixed in: 2021.2.19f1

  4. Resolution Note (fix version 2020.3):

    Fixed in: 2020.3.33f1

  5. Resolution Note (fix version 2019.4):

    Fixed in: 2019.4.38f1

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.