Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.5.1f1
Issue ID
883558
Regression
No
ControllerColliderHit.moveLength() returns CharacterController.Move() parameter value instead of distance traveled by collider
Reproduction steps:
1.Open project attached (ReproduceBug.zip).
2.Open scene "Scene01".
3.Press play.
4.Press "Arrow up" to move.
Expected result: after collision with box, ControllerColliderHit.moveLength() returns 0.
Actual result: ControllerColliderHit.moveLength() returns CharacterController.Move() parameter value.
Note: expected result refers to https://docs.unity3d.com/ScriptReference/ControllerColliderHit-moveLength.html
Check console to see current ControllerColliderHit.moveLength() return value.
Reproduced on: 5.3.7p3, 5.4.4p4, 5.5.2f1, 5.6.0b10.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on GfxDeviceD3D12::AllocBottomLevelAccelerationStructure when using Raytracing
- The search icon in the "Searches" sections is blurry and inconsistent
- "RenderingCommandBuffer" error is thrown when switching to the tvOS platform
- Left side cog menu button is obstructed by the maximum Y value of the graph when editing a curve in the Particle System Curves
- "Property exceeds previous array size (64 vs 32)." warnings are thrown when switching from tvOS platform to a Standalone platform after restarting the Editor
Add comment