Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0a5
2018.3.2f1
2019.1.0a1
2019.2.0a1
Issue ID
1118715
Regression
Yes
GameObjects with Colliders go through terrain collider when the velocity of a GameObject is high and the Scale.Y is around 0.1
Steps to reproduce:
1. Open "case_1118715"
2. Press Play
3. Press the button in the top left corner of the Game Window
Expected results: GameObject with continues to collide with colliders until there are none
Actual results: Small scale GameObjects with high velocity fails to collide with terrain colliders
Reproducible with: 2018.3.0a5, 2018.3.3f1, 2019.1.0b1, 2019.2.0a2
Not reproducible with: 2017.4.19f1, 2018.2.18f1, 2018.3.0a4
Note: Changing collision detection mode doesn't make any difference
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
- Crash on mono_dump_native_crash_info when changing a Particle System Renderer’s Material Shader to Standard Unlit
- VFX Prefab doesn’t have Preview icon in Project window and Preview window is empty in Inspector window
- Visual Effect Graph error message does not disappear and lasts forever until the Visual Effect Graph is reopened even when the error causing connection/node is deleted and Visual Effect Graph is saved
- “RenderSettings customReflection texture has invalid type” error keeps getting thrown even when Environment Reflections was set back to Skybox from Custom with an invalid texture
- Particle System with the custom Material breaks the Scene view when the material is using a Shader Graph with the Texture with the power of negative value
Resolution Note:
Setting transform.position is an effective way to teleport stuff, overriding any physics. The only physical response happening here is after the fact pull out of obstacles stuff right after the object has been put into overlap by user code. Now, this pull out worked OK with the old TerrainCollider code pre-2018.3, because terrain had thickness that allowed to pull out in this particular case, however with the new code that doesn't feature thickness it's not possible to. I suggest either to use forces and velocities (the physical parameters suited for solver and proper collision detection), or to switch off the Unified Heightmaps flag in the physics settings.