Suspect the behaviour comes when you update reference frame from an object later in objects to an object earlier in objects. Suggested solution is to copy current reference frame object when doing initial update objects to ensure new reference frame object doesn't get set everything to 0 before it applies its changes to previous reference frame object.
Suspect the behaviour comes when you update reference frame from an object later in objects to an object earlier in objects. Suggested solution is to copy current reference frame object when doing initial update objects to ensure new reference frame object doesn't get set everything to 0 before it applies its changes to previous reference frame object.