Search Issue Tracker
Active
Votes
1
Found in
2020.2.0b10
2020.3
2020.3.25f1
Issue ID
1395216
Regression
Yes
TerrainData.AwakeFromLoad takes around 13-19 ms after loading a Terrain from an asset bundle
How to reproduce:
1. Open the attached project ("TerrainBundleTest.zip")
2. Open Profiler if it's not open (Ctrl/command + 7)
3. Enter Play Mode, wait for the terrain to load, and exit Play Mode
4. In the Profiler hierarchy view search for the keyword "TerrainData.AwakeFromLoad" in the first few frames of the Profiler data
Expected result: TerrainData.AwakeFromLoad does not take 13-19 ms of time
Actual result: TerrainData.AwakeFromLoad takes 13-19 ms of time
Reproducible with: 2020.2.0b10, 2020.3.26f1
Not reproducible with: 2019.4.34f1, 2020.2.0b9, 2021.2.8f1, 2022.1.0b4, 2022.2.0a2
Note:
- If you select the Assets/Terrain and change the heightmap resolution of the terrain to 513 * 513, rebuild the asset bundle that contains the terrain asset (I.e. Go to the addressables group window and perform a rebuild there) and repeat steps 1 - 5, the delay for TerrainData.AwakeFromLoad reduces to less than 5 ms.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Unexpected exception System.DllNotFoundException" error thrown in the Console window when creating a project with 2D (URP) Template
- [Backport] [XR SDK] [HDRP] XRSettings.gameViewRenderMode does not change Game View Render Mode
- [Backport] [Android][Vulkan] Crash on Samsung Note8 while running gfx tests
- [Backport] Wrong sorting for "GC Alloc" column in Show Related Objects panel of Profiler Window
- [Backport] [iOS] Unfreed allocation errors thrown in Console when executing Build And Run with iOS platform
Add comment