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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment