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
- “Frame Debugger On” text color not maintained across different Editor Themes in toolbar
- Rendering artefacts appear in the Game view window when maximizing/minimizing Inspector window and Frame Debugger is Enabled
- Threads dropdown in the Profiler is not scrollable even when not all options in the list are visible
- Memory leak when a lot of Particle Systems instantiated while Profiler is open
- "ArgumentOutOfRangeException" error is thrown when trying to delete letters from an RTL TextField when using the Advanced Text Generator
Add comment