Search Issue Tracker
Not Reproducible
Votes
1
Found in
2022.3.58f1
6000.0.39f1
6000.1.0b7
6000.2.0a4
6000.3.0a1
Issue ID
UUM-97886
Regression
No
High "Total" value of the "TerrainManager.CullAllTerrains" when generating terrain
Reproduction steps:
1. Open the attached “repro_IN-95227“ project
2. Open the “Assets/OutdoorsScene.unity“ Scene
3. Open the “Profiler” (“Window → Analysis → Profiler“)
4. Enable “Deep Profile”
5. Set “Target selection“ to “Play Mode“
6. Enable recording
7. In the “CPU Usage” row, enable only the “Rendering“ graph
8. Enter the Play Mode
9. While the Game view is focused, press the “Spacebar“ button on your keyboard and wait for the terrain to be generated
10. Once it’s generated, pause the Play Mode
11. In the “Profiler”, in the “CPU Usage“ row, select the first green spike
12. In the Hierarchy of the Profiler, search for “TerrainManager.CutAllTerrains“
13. Notice the “Total” value
Expected result: Value of “Total” is low
Actual result: Value of “Total“ is high
Reproducible with: 2022.3.58f1, 6000.0.39f1, 6000.1.0b7, 6000.2.0a4
Reproducible on: Windows 10 (22H2),
Not reproducible on: No other environments tested
Notes:
- In the test project, the value of “Total“ can reach around 50%
- In the real user project (which is very complex), the value of “Total“ is around 17%
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Resolution Note:
We cannot sufficiently reproduce the issue with the provided repro project in player builds. The portion of the report showing excessive timings for MaterialPropertyDrawer on Terrain instantiation is an Editor-only issue and, unfortunately, not something we can change as it is part of the Material system keyword setup in Editor, among other things.