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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
This is a duplicate of issue #757905