BallSocketConstraint explodes when twist limits are 0

Bug Reports Engine Bugs
#1

When I set both TwistLowerLimit and TwistUpperLimit to 0, I expect the constraint to allow no twisting. Instead the parts attached to the constraint disappear.

The following reproduction demonstrates the issue.

exploding-socket.rbxl (18.8 KB)

  • Constraint 1 has limits of -1 and 1.
  • Constraint 2 has limits of 0 and 1.
  • Constraint 3 has limits of -1 and 0
  • Constraint 4 has limits of 0 and 0.
1 Like
#2

Thanks for reporting this. I will take a look. For now use:

  • UpperAngle > 0
  • LowerAngle < 0
#3

Ok found the bug. Unfortunately the fix will not ship before new year due to Holiday release restrictions.

1 Like
#4

Fix for this has been enabled today.

#5

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.