Search Issue Tracker
By Design
Votes
0
Found in
5.4.0f3
Issue ID
823586
Regression
No
"Detail Resolution Per Patch" property value does not change amount of draw calls per frame
Steps to reproduce:
1. Open "GuffTerrain" project
2. Open "GuffScene" scene
3. Enable Frame Debugger
4. Select TerrainContaienr>Terrain game object
-- Remember the number of draw calls which you can see in frame debugger
5. Expand terrain settings
6. Change "Detail Resolution Per Patch" value in Terrain Settings>Resolution part
Results: "Detail Resolution Per Patch" property value doesn't change amount of draw calls
Note: each terrain draw call draws ~290 vertices and ~1510 indices.
Reproduced with: 5.5.0a5, 5.4.0p2, 5.3.6f1, 5.3.4f1
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
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
- Mouse and Pointer Events are called incorrectly in ScrollView with XRUIInputModule
- Scene view freezes when "NullReferenceException" is thrown in a .delayCall
- Memory leak occurs when repeatedly minimizing and maximizing the UI Builder window
Resolution Note (2017.2.0f3):
Detail patches control the number of draw calls for detail placements -- grass, rocks, etc.
It has no effect on the actual terrain geometry, which is the large number of draw calls you are seeing here.
The Terrain geometry draw call count is only indirectly controllable through the 'Pixel Error' control.
We are working on an update for 2018.3 that will vastly reduce the number of draw calls for the terrain geometry.