Search Issue Tracker
Fixed in 5.3.0
Votes
4
Found in
5.2.0b6
Issue ID
720398
Regression
Yes
HingeJoint.motor no longer accepts a negative JointMotor.targetVelocity
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)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Label” name in Sprite Library Editor window lacks character limit causing long names go under the Object Field
- Preview image (screenshot) is not available after capturing snapshot in Memory Profiler
- Crash on UNITY_FT_Stream_ReadAt when changing TMPro properties after unloading an AssetBundle
- Particles spawn at the same position when using raw byte address buffer in VFX Graph
- Decal Shader Graph - Custom vertex interpolators are always 0
Adam_is_learning_all_the_time
Jul 20, 2018 03:23
This issue is present in 2017.3.1f1 in case it helps.
Angel-Devs
May 22, 2018 17:58
I'm using Unity 2017.3 and it still isn't fixed.
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)?