Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2018.4
2019.4.0f1
2020.2
Issue ID
1256373
Regression
No
[Terrain] High CPU usage from Terrain.UpdateMaterials method when Editor is rendering terrain
How to reproduce:
1. Open attached project "case1256373.zip" and scene Assets -> Scenes -> Bugs -> "TerrainBugReproScene"
2. Enter Play Mode
3. Observe CPU Usage in the Profiler window
Expected result: Rendering terrains should not take 1/3 to 1/2th of the frame's CPU budget
Actual result: Rendering terrains take 1/3 to 1/2th of the frame's CPU budget
Reproducible with: 2018.4.26f1, 2019.4.9f1, 2020.1.2f1, 2020.2.0a21
Note: This issue is also being discussed in this forum thread: https://forum.unity.com/threads/terrain-updatematerials-very-expensive.622768/
-
Tomcat9
Jun 20, 2021 11:04
Still no fix for 2020. So now I have the choice of using a 2020 version with this huge performance hit bug, or 2021 which is entirely a buggy mess itself. Terrible.
-
i2eilly
Dec 16, 2020 23:58
Is there any chance this can be back ported to 2019.4 LTS, I am currently near the end of my project and this issue is still present in the LTS versions of Unity.
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
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a1