Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0b7
Issue ID
639982
Regression
No
Calling Move() on the GameObject which has Rigidbody and CharacterController causes wildly incorrect results
Summary of discussion: This behavior is the same as 4.x, but in 4.x it would miss small colliders which 5.0 got better at due to new elevator handling code in PhysX 3.3. This is by design, and won't be changed for 5.0 now.
However, it does seem like a desirable change to not collide with any child colliders. This could be implemented in ControllerContactFilter::preFiter. Consider this for future releases.
To reproduce this bug:
1. Open the attached project
2. Open 'CompanionCube' scene
3. It has a cube with rigidbody, character controller attached
4. Press play
5. Move() is called on character controller
6. The cube should move down slowly, but instead flies up
Works as expected on 4.5.x
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment