Search Issue Tracker
Fixed
Fixed in 2020.3.39f1
Votes
0
Found in
2020.3.35f1
Issue ID
UUM-4946
Regression
Yes
[Performance Regression] GameObject.ActivateAwakeRecursively noticeably slower when rendering trees on terrain
Reproduction steps:
1. Open the attached project ("1225501.zip")
2. Open "Scene"
3. Enter Play mode
Expected result: Terrain GameObjects are redisplayed at the same speed as before
Actual result: Terrain GameObjects are redisplayed noticeably slower than before
Reproducible with: 2019.3.0a9, 2019.3.6f1, 2020.1.0b2, 2020.2.0a4
Not reproducible with: 2017.4.38f1, 2018.4.19f1, 2019.3.0a8
Notes:
- In this scenario, there are 7 terrains which are all being setActive(true) in an IEnumerator that is used as a coroutine
- The trees used on the terrain are the Broadleaf_Mobile from Standard Assets
- In the versions deemed not reproducible the same action would take 15-30ms, while in the versions deemed reproducible it would take 500-1000ms
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
- In Play Mode, an extra Sync Call is made every frame when a GameObject has a Rigidbody 2D component
- Crash on block_remove when a scene is opened in a specific project
- The GameObject with a Hinge Joint Component does not return to the initial position when the Use Motor property is toggled off
- The construction of a specific class breaks the binding Bool references and does not allow them to be toggled on back by hand when working in the Custom Editor window
- AssetReferenceAtlasedSprite creates a copy of the Sprite during Addressables.LoadAssetAsync<TObject> which does not release when Addressables.Release is used
Resolution Note (fix version 2020.3.39f1):
Fixed in 2020.3.40. (The dropdown was missing the value for 2020.3.40f1)