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
- 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
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment