Search Issue Tracker
By Design
Votes
1
Found in
2020.1.0a21
2020.2
2020.3
2020.3.14f1
2021.1
2021.2
2022.1
Issue ID
1370706
Regression
Yes
Game Object after Collisions goes through another Game object with a collider
Reproduction steps:
1. Open the user's attached project
2. Enter Play Mode
3. Drive with tank into some obstacle
Expected results: After a collision Game Object with a collider can't go through another Game object with a collider
Actual results: After a collision Game Object with a collider goes through another Game object with a collider
Reproduced in: 2020.1.0a21, 2020.2.7f1, 2020.3.20f1, 2021.1.25f1, 2021.2.0b16, 2022.1.0a13
Not Reproduced in: 2019.4.31f1, 2020.1.0a20
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
- 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
Resolution Note:
Users now need to change Physics.defaultMaxDepenetrationVelocity themselves to replicate earlier behaviour.