Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
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
- OnPostprocessAllAssets() is not called for a modified Prefab when another Asset is set Dirty in the same callback
- [Android] UIToolkit ClickEvent is fired when the device is rotated
- Compilation errors occur when "uintBitsToFloat(int)" gets used in OpenGLES
- User Reporting does not send reports when Managed Stripping Level is set to Low or higher
- Editor crashes and a window with "GetManagerFromContext: pointer to object of manager 'MonoManager' is NULL (table index 5)" error is thrown when launching a project with a corrupted library
Add comment