HingeJoint: ETA for backporting fixes from 5.3 to 5.2?

Unity Engine
1

I reported a couple of HingeJoint bugs which appeared after upgrading from 5.1 to 5.2:

(Case 720398) Physics: HingeJoint.motor no longer accepts a negative JointMotor.targetVelocity
(Case 720408) Physics: HingeJoint.angle is always a positive/abs value

I was notified on Aug 26 that these issues were fixed in 5.3 and would be backported to 5.2. As of 5.2.0p1 and 5.2.1f1, the fixes have not yet been backported. Is there any ETA for 5.2 receiving these fixes?

1 Like
2

Hi,
I can also confirm that hinge joints no longer takes negative target velocity values, which is a major issue for most of our projects here.

Is there any info on when this will be solved ?

3

I am also anxious to see this update back ported.

4

Howdy…I had the same issue but managed to create workaround by changing the axis to a negative value instead:

hinge.axis = new Vector3 (0.0f, moveHorizontal, 0.0f);

Hope this helps

5

Having the same issue

6

I tried your workaround, but it didn’t work.

locomo_hinge.axis = - locomo_hinge.axis;

In the inspector the axis did inverted, but the angle moves the same direction regardless of the axis.

7

The 5.2.2p2 patch that was released a few days ago addresses these bugs. I haven’t fully tested it to check if everything is actually fixed, I’m just looking at the release notes. You may want to try the patch release and find out for sure: Download Archive

8

LeonH,

It should be the bugs that you described in your OP that got fixed in 5.2.2p2.
Let me know if you guys are blocked by something else that’s fixed in the 5.3 betas.

1 Like
9

OH THANK YOU!!! PATCHES!!

1 Like
10

Thanks, Morten!

Ironically, these bugs getting fixed in 5.2 at this point is actually worse for us. :wink: Since I was unable to get any info from Unity about an ETA and we were nearing the end of the project, I already spent a couple days implementing a project-wide workaround. The workaround is not compatible with properly functioning hinge joints, so our hinges are again not working in 5.2.2p2+. I’ll need to spend about a day removing the workaround from the project and hope the fixes are perfect. All in all, about three days that should have been spent on other areas that will now go unfixed/unfinished in the game.

If we had received even the slightest bit of info, even something like, “we hope to back port the fixes into 5.2 some time between patch xxx and yyy” that would have been a huge help. I guess that is my primary feedback-- for projects that are anywhere near the end of their dev cycle, information (or lack thereof) about upcoming bug fixes can be quite critical in influencing outcomes.

Anyway, this is great news for everyone who is on 5.2. We appreciate the fixes, Morten! I would just love to see more communication sometimes.

11

BTW if anyone hasn’t seen Morten’s presentation from Unite 2015 on some of Unity’s physics systems, you should definitely watch it, it’s great:

12

Great to hear about the patch release :slight_smile:

13

@LeonH there are several good reason why we chose to put the fixes in 5.2, sorry if it created critical issues for you. I can list the reasoning if you want.

But what I think is more interesting is how we (Unity) become better at this in the future. Because we will definitely port other fixes back, which will require tune-ups in the game using the specific features.

Should we have like a yellow warning section in the patch notes with “breaking changes”? We basically have that for the non-patch releases.
What do you have in mind that can lessen the surprise?

Regards,
Morten