Search Issue Tracker
Duplicate
Votes
0
Found in
5.4.0f3
Issue ID
832120
Regression
No
Collision between CharacterController and a Kinematic Rigidbody is always resolved by moving CharacterController vertically
To reproduce:
1. Open the attached project
2. Open "TestScene" scene
3. Enter play mode
Observe that CharacterController that was inside the object with Kinematic Rigidbody is popped out at the top of the object instead of the side which was the shorter path.
Notes:
Collision between CharacterController and a Kinematic Rigidbody is resolved by moving CharacterController vertically no matter the height of the object with Kinematic Rigidbody.
Expected: Collision between CharacterController and a Kinematic Rigidbody is resolved by CharacterController taking the shortest path to pop out
Actual: Collision between CharacterController and a Kinematic Rigidbody is always resolved by CharacterController moving vertically
Reproduced on: 5.5.0b4, 5.4.1p1, 5.3.6p5, 5.2.5f1
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
This is a duplicate of issue #757905