Search Issue Tracker

Fixed in Unity 5.3.0

Votes

4

Found in

5.2.0b6

Issue ID

720398

Regression

Yes

HingeJoint.motor no longer accepts a negative JointMotor.targetVelocity

Physics

-

-

Priority: 7Not yet prioritized for a release

-

Severity: 2Core functionality majorly impacted

To reproduce:
1.Open attached project.
2.Open and play "repro" scene located in Assets.
3.Notice console output of JointMotor.targetVelocity.
4.Check Cube > HingeJoint > Motor > Target Velocity, notice that its value is set to 0, where it should be -45.

Regression from 5.2.0b1

Comments (3)

  1. 8156a3eb78611c61fa3f005f58c1a094?d=mm

    Adam_is_learning_all_the_time

    Jul 20, 2018 03:23

    This issue is present in 2017.3.1f1 in case it helps.

  2. Fe3f0ea6e8351b15d29bf59b2fc08a66?d=mm

    Angel-Devs

    May 22, 2018 17:58

    I'm using Unity 2017.3 and it still isn't fixed.

  3. 2561b5e501a377d4305387eb0c09cde2?d=mm

    NGC6543

    Nov 04, 2015 07:14

    I'm using Unity 5.2.2f1 but it still has the same issue.
    The "Status: Fixed in future release" message above, does that mean it will be solved on 'its' next release(like 5.2.1f1), or 'later' release(like 5.2.3)?

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.