There is a bug posted about this but wanted to know if anyone else is suffering from this setback.
Worked fine in v 5.0.2f1 but fails in later versions.
a. Cannot set negative velocity for a joint motor - results in a velocity of zero.
Issue ID 720398. Fixed in a future release - but when is that?
a. Rotations in either direction under motor control show only positive angles. Need negative angle for rotations in the reverse direction. This is not marked as a bug, but seems related to a.
If anyone has information of when we’ll see a release for this problem, please do tell.
I’m afraid you may be wasting your time. I posted this three weeks ago and no one responded:
We have a project that is supposed to go into cert on multiple platforms next month and it depends heavily on hinge joints behaving properly. I couldn’t get an answer from anyone, but I wish you luck.
PS: what I ended up doing was switching from using the joint motor to the joint spring instead, which still works properly. Not sure if that’s feasible for you-- obviously, I had to spend a lot of time retuning an entire game’s worth of content for that, but at least it does work for our setup. As for the hinge angle being reported incorrectly, I spent time writing a workaround for that where I calculate the hinge angle myself, based on the local rotation of the object the hinge is attached to, relative to the starting rotation, accounting for the anchor offset, hinge axis, etc. Those workarounds took me almost a week to perfect for our entire project-- time that should have been spent on other things that now will just go unfixed/unfinished. But with no one even acknowledging my questions, it was getting too close to cert to have uncertainties like that floating around.
@LeonH : Thanks for you reply. I am really surprised that they managed to break something so fundamental as hinge joint feedback. It’s a sign that they do not have sufficient regression / automated testing in place. We have also used a work around using spring instead of the motor, but are waiting for a fix as this would require a significant change to an app already in the apple store and google play. The fix in 5.3 apparently will be released Dec. 8th. We cannot migrate from 4.6 to 5.x until this happens.
I seem to be experiencing something similar to this in 5.5f3. I’m using Limits of -40 and 40, but HingeJoint.angle is always positive. So in the center position the angle is zero and at either limit the angle is reports as 40. Was this bug ever fixes? Maybe it has returned?
Edit: I’m new to HingeJoints and it looks like this happens because I hadn’t set the Hinge joint axis to anything. It’s working for me fine now. I’ll leave this comment here just in case someone else makes the same mistake.