As of today, I’ve observed that when an object connected to another via a rope constraint comes into close proximity with its attachment point, it behaves as if it is axis-locked in terms of orientation—essentially becoming stiff, similar to the behaviour of a prismatic constraint. Previously, the object would freely rotate (or rather swing during motion) regardless of how close the attachment points were. This change in behaviour is new and was not present before.
This is causing issues as we need our object to be able to have a degree of orientational movement or rather “swing” even when its in its up-ward position and the rope hasn’t lowered yet.
In my example photo, even that distance is enough to cause the hanging object to become axis-locked and immune to any proper rotation. As I said, you can imagine the behaviour in this bug the rope-constraint behaving similar to what a Prismatic-Constraint would
More examples can be seen in these videos.
In the first video, the two attachments are at a fairly fair distance from one another, and it behaves as expected.
In the second, slightly close, but still not touching, and we can see the axis-locking issue. NOTE: That this has not behaved like this in years!
Lastly, you can clearly observe in this third video of the axis-locking happening in real-time, as the two attachments approach each other. It’s almost as if it just turned into a prismatic-constraint.
This is a much clearer example from our game which shows the issue on more complex-parts. You can see that as it goes upwards it completely loses its ropeconstraint properties and tries to behave like a prismatic-constraint, trying to fixate on a particular set axis, instead of naturally swinging as it always has prior. The left/right bouncing as it opens along with the static fixed movement is unnatural.
We’re desperate to have this issue fixed ASAP, as our game heavily relies on the ropeconstraint.
Yes, it started yesterday. Joined several of my games server instances and noticed that our mechanism using rope-constraints were behaving incorrectly on all platforms. Then tested in isolation on studio and the issue still persisted.
Can you share your repro file? I believe we have identified the code change responsible for the new behavior but I would like to confirm locally. Thanks.
Thanks. It was the code change that I suspected and I’ve disabled the change. Can you try your experience and see if the problem is still occurring? Thanks.
