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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment