Search Issue Tracker
Fixed in 5.0.1
Votes
3
Found in
5.0.0p2
Issue ID
683176
Regression
Yes
TerrainData.SetHeights doesn't update TerrainCollider properly
By changing terrain heights in small area TerrainData.SetHeights doesn't update terrain collider.
1. Open project "SetHeightsBug" (attached by Lukas).
2. Play scene "Test".
3. Click mouse left button to spawn box, that going to fall on the terrain.
4. While the box is falling, click mouse right button to increase terrain height at the same point where you spawned the box (click it few times to make big hill).
5. You should notice that box goes threw hill and only stops at y = 10 (Because box size is 20), so it means that terrain collider was not update.
There is few things that I noticed, that by changing terrain in other place sometimes updates terrain collider and some points always updates. So I believe maybe there is small mistake in terrain code that caused incorrect terrain change detection, because when you change all terrains height terrain collider is updated properly.
Regression: 5.0.0f3
Reproduced: 5.0.0p2, 5.0.0b1, 5.0.0f4, 5.0.0f3
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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
GXMark
Mar 28, 2015 06:27
Yes can confirm this behaviour. Terrain collider not updating when only small areas of the terrain height are updated at runtime procedurally.