Search Issue Tracker
Fixed in 2020.1
Fixed in 2019.3
Votes
1
Found in
2019.3.0a5
2019.3.0b12
2020.1.0a1
Issue ID
1200526
Regression
Yes
GameObjects with colliders have inaccurate collision with Terrain
Steps to reproduce:
1. Open attached Unity project
2. Open "SampleScene" scene
3. Press Play
Expected outcome: Cube lands on the very top of terrain surface
Actual outcome: Cube ignores collision, landing partly inside of terrain surface
Reproducible with: 2019.3.0a5, 2019.3.0f1, 2020.1.0a15
Not reproducible with: 2019.3.0a4
Could not test with: 2017.4.35f1, 2018.4.13f1, 2019.1.14f1, 2019.2.14f1 (Project errors when downgrading)
Note: Tested with various types of colliders (Box, Sphere, Cylinder, etc.)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- LineRenderer points lists suffers from performance issues when list is large
- Shaders take a lot of memory at runtime even when only one variant is used
- Lego Microgame crashes the Linux Editor at "ScanFilter::Merge" when selecting a WebGL build location
- GameObject reference is null when creating it inside Reset() function and assigning Script as component
- GameObject/Prefab inspector preview is slow for complex hierarchies
Add comment