Adding new parts to a rig no longer working correctly (again)

[fearfant]

This issue happened back in August and was resolved after about a week but it has appeared again with all the same issues so I’ll just copy paste my old bug report

I’m experiencing an issue where parts that are cloned into a character model and rigged onto it with motors are not working the way they were. Rather than being rigged onto the character and playing the animation like normal, the character is teleporting to the new part and starts flinging all over the place. SetNetworkOwner and RootPriority don’t seem to change anything.

Expected behavior

How it used to look:

What is now happening:

[DrCherenkov]

Are you using any LinearVelocity, AlignPosition, AlignOrientation or AngularVelocity constraints? This kind of issue may relate to this rollout:

Improved Mover Constraints: Enhancing Stability and Network Ownership

[Update] September 24, 2024 Hi all, A few weeks ago, we identified some bugs with these improvements so we rolled back this transition to Phase 1 (experiences are opted-out by default with the ability to opt-in). We have since addressed those bugs and are ready to provide updated dates for phasing in these changes: Rollout Phases: Phase 2 (November 4th, 2024 - February 2nd, 2025): Default and Enabled = opted-into improvements, Disabled = opted-out of improvements. Final Phase (from Febr…

You can check by disabling the workspace property MoverConstraintRootBehavior.

[fearfant]

No, this works entirely by inserting new models into the player character and attaching their primary parts with new Motor6ds. The inserted models have no anchored parts.

[pseudosc1ence (1989TIANAMENSQUARE)]

Can you turn on the Massless property on the added parts? I know that sometimes fixes things for welded items like tools but I’m not sure if it’ll do the same for Motor6Ds.

[fearfant]

This does seem to fix it, but this should probably still be looked into as the teleporting was fixed without me making any changes previously (and before my last bug report for it was responded to)