Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0a5
2018.3.13f1
Issue ID
1148175
Regression
Yes
Terrain thickness do not cause objects beneath the terrain to move above the terrain
How to reproduce:
1. Open attached project "Terrain Thickness Test.zip" and scene "SampleScene"
2. In the Hierarchy window, select "Terrain" object
3. In the Inspector window, Terrain -> Terrain Settings(gear icon) -> Physics (On Terrain Data) -> make sure that thickness is 1000 (or any high value)
4. Enter Play mode
5. Observe Scene or Game view
Expected result: the Sphere is teleported on the terrain
Actual result: the Sphere is not teleported on the terrain and falls down
Reproducible with: 2018.3.14f1, 2019.1.0f2, 2019.2.0a13
Not reproducible with: 2017.4.26f1
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Terrain thickness is available only with the legacy heightmap collision detection. The new unified heightmaps approach doesn't support it anymore, and is default in 2018.3.