I have a constraint between two rigid bodies in my VR hands (neither RB is connected to the controller directly). I migrated from 4.27.2 oculus fork to 5.3.2 oculus fork and suddenly the BP GetConstraintForces node will only return 0,0,0 for both torque and linear force. Through trial and error I found that disabling Enable Projection brought the forces back (though they’re much weaker now vs 4.27.2).
Is this an intended behavior?
Is there more information on what was changed in the constraint code between these engine versions?
In my ragdoll physics asset, I can get the torque on the neck joint, yet its projection is enabled. It has limited angular limits, whereas the VR hands constraint has locked for all 6 degrees. I attempted changed the limit values but they didn’t seem to fix the zero-forces I was getting from GetConstraintForces. So I am confused. The constraint behavior change between the two engines has been a source of much frustration, though I can understand that changing physics engines is not a 1:1 sort of thing.
Here’s the joint’s settings:
