Search Issue Tracker
By Design
Votes
2
Found in
4.3.0f4
Issue ID
576619
Regression
No
Character Controller improperly factors Step Offset into the ControllerColliderHit function
To reproduce:
1. Open attached project
2. Open scene repro - it has a character controller and a sphere on a plane. The character controller's Step Offset is set to 0.55, which is lower than the height of the sphere
3. Enter play mode and walk into the sphere
4. A console message prints out the hit.moveDirection values. These are wrong, as they output {0,-1,0} (meaning that the sphere is below the controller) while the player is clearly in front of the sphere
If you set the Step Offset to 0, the correct values are printed.
This is by design, as this is how the Character Controller works. If you just want the direction the controller is moving in, just use the vector you passed to the move function.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
Add comment