R15 / Rthro Ragdolls

I have the solution for the “Phase through object” bug.

You need to disable/enable the collision on the humanoidRootPart when the ragdoll is active/deactive. It’s set to always disabled when the ragdoll is created, but this is not correct.

function setRagdollEnabled(humanoid, isEnabled)
	
  ...

	local rootPart = humanoid.Parent:FindFirstChild("HumanoidRootPart")
	if rootPart then
		rootPart.CanCollide = not isEnabled
	end 

end
3 Likes

Also it’s possible to simply send a manual event from the client to the server, when the clients humanoid state changes, and apply the state manually to the players humanoid on the server. This fixes the bug in 99.9% of cases.

My code for doing this is not super pretty, but it works well enough.

3 Likes

(Pretty sure the humanoid state change bug has been fixed with the recent updates to humanoids btw!)

1 Like

Where do I put the script? New to ragdolls.

Hi, I was wondering if I should just ignore this error (wich btw, I get the second error on the screenshot 5 times on the output when I hit play) or not, since it works anyways and it also errors on the demo place. https://i.gyazo.com/89ff0a39ada6c9ba3fa15c3c49ca7139.png .

1 Like

@EchoReaper Does the module works with this?
Dogu15 Rig [Layered]

2 Likes

I personally think it should. It uses attachments as reference.

1 Like

Yes, it does:

6 Likes

How weird, i installed the dogu15 module and the reagdoll module in a test place, then i pressed R, and nothing happened.

Maybe you just run a code that makes thoose characters ragdoll?

1 Like

Are you using the script in the testing place that automatically morphs your character, or are you using the Dogu15 model as a StarterCharacter?

1 Like

Yes, im using it as starter character, do i need to make a ragdoll button?

gtg

2 Likes

In that case, you need to remove line 40 from the RagdollTestScript script.

player.CharacterAppearanceLoaded:wait()

CharacterAppearanceLoaded will never happen since you are using a custom character model, so the ragdoll will never be built. I ran into this issue as well and removing this line fixed it for me.

2 Likes

So, if i do it i press R for enable ragdoll mode?

2 Likes

Yes, that should work now, as without that line the ragdoll will be built and can be used.

1 Like

So, anybody have a solution for the sliding problem that @Kabozhi explained ? Because its so annoying and i can’t find a solution

1 Like

Did this not work? I haven’t been able to replicate the bug yet so I can’t tell.

3 Likes

I have an issue where the character being ragdolled flies up after being ragdolled and i think it could be because the player’s joints are colliding with the platform part. I tried fixing this by setting the player’s rootpart velocity to vector3.new(0,0,0) in a loop if they are in a ragdoll but this just makes my knockbacks look wierd. any solutions?

1 Like

If anyone is having this issue, the solution i used is setting the Y axis of the player velocity to 0 whenever the player humanoid state is not FallingDown , FreeFalling or jumping

1 Like

Ok, so I’m having a problem where my custom character freezes up instead of falling


Does anyone know how to fix this?

2 Likes

Yes hi, are you using a StarterCharacter? If you are then go into “RagdollTestScript” and remove this code from line 40:

player.CharacterAppearanceLoaded:wait()

Brief Explanation: CharacterAppearanceLoaded will never happen since you are using a custom character model

However if you are not using a Starter Character then go into “RagdollTestScript” and remove line 39 through 45 and replace it with this code

function characterAdded(player, character)
	player.Character:WaitForChild('Humanoid', 60)
	player.Character:WaitForChild('HumanoidRootPart', 60)
	wait(0.1)
	
	local humanoid = character:FindFirstChildOfClass("Humanoid")
	buildRagdoll(humanoid)
end

both have worked for me so far and I hope it can help you too.

6 Likes