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
- Editor crashes when debugging a for loop
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
Add comment