Roblox character model becomes disorientated and jittery after big animation

Now, I’ve been trying to get my game to have a system where you can do a huge cinematic attack on another character. This of course would require some sort of cool animation. Went around and got to it, slapped it on a random NPC that counterattacks you when you hit them, works pretty well until when you recover from the animation.

The character’s movement becomes… Special, to say the least. Just by doing a simple WASD input will make you a beyblade spinning around. I thought it was just because of the torso and humanoidrootpart becoming offset with eachother, but that’s not the case. Digged into all the Motor6Ds of the rig and their C0/C1s, nothing’s standing out at all either. I tried googling or searching it up on the dev forum but I don’t really know what name would this sort of situation have… So I had to make my own post about it.

Can somebody tell me what may be causing this sort of problem? And maybe redirect me to a thread or a post that can help me out on this situation. I know this may happen due to the fact that your character’s torso moves too far away from the humanoidrootpart, which was in one place in a static sense.

1 Like

I have never seen this problem before. What happens when removing the HumanoidRootPart after you experience the problem?

After removing the part, the Humanoid started to use the Torso as its Root instead, but the issue became fixed. So I’m starting to believe something in this process messed with the HumanoidRootPart.

Possibly the HumanoidRootPart came offset. Try to make your code anchor the HumanoidRootPart for at least some of the animations.

It’s been anchored throughout the entire animation, and only unanchored when the animation supposedly ends.

Well, I’m not sure then. All I know is don’t anchor everything, only anchor the HumanoidRootPart. If that doesn’t work, try manually setting the C0/C1 properties of the Root Hip to their default values.

I see. I tried that as well, and even checked the values before hand too, but nothing seems to have been changed both before and after the problem.

That’s weird. Is the character welded to anything after the animation?

Nope, didn’t do anything with them before or after the animation aside from loading them, placing the victim’s rig into the attacker’s rig’s position before resuming them to their original position, which I don’t think would be affecting anything.

The main issue I think may come from the fact that the vicim’s torso was dragged away too much from the spot of their humanoidrootpart during the animation, so when it ends when they were away from the rootpart, it messes something up. Is there perhaps a way to find a solution for that?

I’d doubt that. How were you placing the rig?

Possibly, try a different animation ID and see if that fixes the issue.

I’d doubt that. How were you placing the rig?

The victim’s humanoidrootpart’s CFrames are put exactly the same as the attacker’s, so the animation’s interaction is properly synced in the way I animated them. And then the victim’s humanoidrootpart is anchored to prevent them from moving during animation as well.

Possibly, try a different animation ID and see if that fixes the issue.

Tried that earlier, and the character moves properly without an issue. So I’m very convinced that it has something to do with the fact that the Torso was moved away from the Rootpart.

Where is the RootPart after the animation ended? Still didn’t get a very clear answer on that.

Still in the character, exactly at the same correct spot of where it was before.

Okay, is anything different on the server vs the client?

No, unfortunately. I don’t see anything out of place or different from eachother on both places.

Does parenting the HumanoidRootPart to nil and then back again fix the issue, or at least do anything?

Just tried that, doesn’t seem like it works, either.

Very confusing. When you said deleting the HumanoidRootPart fixed the issue, I got an idea thinking maybe setting the RootPriority of the Torso to 1 will fix the issue.

But then again, that will make the Torso the rootpart instead, right?

It will. I want to see what the difference is when it’s the RootPart and when it’s not. Switching between both should have an effect.