Releasing Character Physics Controllers

[700000002 (Tenny)]

Nice resource, but the clip in your post destroyed my eardrums

[BlueDeveloper24]

This seems more complicated and less performant than the original humanoid. Can we get events like when it enters swim/run/landed/inAir states?

[Fraiixen (Zoroark)]

It is meant to be more complicated, it is specifically for that, just use humanoids if you want those.

[xKiiyoko (Kiiyoko)]

Hi there, I noticed that having AirController.MaintainLinearMomentum off does not seem to respect ControllerManager.UpDirection. Whenever it is disabled, it stops all momentum in the y-axis–not the set up direction.

I should land in the same spot every time, but when MaintainLinearMomentum is off it offsets me each time I jump.

[Fraiixen (Zoroark)]

This feature released like 2 years ago and it is still ultra Jank, just tried it today, and at first, I thought since controllers are supposed to float above the ground to be able to climb over stairs and slopes, they didn’t apply force to the objects they were standing on (This turned out to be false).

Trying to figure out whether they applied or not force led me to find that the reason why my seesaw was not going down, is because the part goes to sleep and since our character controller cannot touch it, we can’t wake it up.

Roblox provides no way to wake up sleeping parts so we can’t even wake it up despite our ground sensor telling us we are standing on it.

Roblox has no shape casting either, making detecting ground ultra Jank, a single ray cast or a ground sensor just doesn’t cut it.

[MikesDSL (Miks)]

Introducing Shapecasts

Today we’re officially releasing two new APIs for the Roblox Engine: WorldRoot:Blockcast WorldRoot:Spherecast You may know these as swept volume queries, thick raycasts, continuous collision detection, or various other names across the industry. We call them Shapecasts. [image] Shapecasts are closely related to raycasts – Raycasts push a point along a line, while shapecasts push a 3D shape and find the first hit point. Use cases Some examples of when you might find these useful: Chara…

<3

[Fraiixen (Zoroark)]

Shapecasts are useless since they do not have margins, that’s why you can’t use them yet, this makes them unreliable as hell when the origin shape has already clipped through a wall, and it is exactly the same reason why I can’t build a kinematic character controller and I am using this one instead.

[wodgedev (wodge)]

is there any way to get the ground controller to change height faster? when i go from standing to crouching it does this very slow transition

[Fraiixen (Zoroark)]

If you are using a raycast to update the ground sensor perhaps you could calculate the position of the player according to the distance of the player from the ground to instantly snap it to the crouched position.

[wodgedev (wodge)]

used to do this actually and it just made more issues to fix than it solved, had to cap slope steepness and step up max values and in the end people could still just clip on walls and stick to them. not to mention its also framerate based, so if you’re running it at 60 fps its gunna be harder/different than someone at 240 fps. The groundcontroller does have two values called “StandForce” and “StandSpeed” which seem like exactly what i want right now by the name, but they do nothing different when changed. I think this is a feature they had planned but never got to

[bear2126]

I cant really explain it all to well, but is there any reason as for why the character rotates like this when setting the UpDirection?, I would assume this is how you are supposed to use it since movedirection works fine with same values
I am setting the UpDirection to be the raycast normal from under the root part, and I’m setting both MoveDirection and Facing Direction to be the movement input direction relative to the camera

The UpDirection feature is greatly needed for my project, if anyone can help me with this, I will appreciate it!

[bear2126]

Welp, i dont mean to sound impatient but its been a couple days now, is anyone there?

[Redridge (Red)]

@kleptonaut are there any updates on the official Roblox implementation to replace the Humanoid? I am very interested in that and judging by this thread it seems a lot of people see the value in this.

EDIT: At the very least, could we get the default values used by the Humanoid for things like:

• TurnSpeedFactor
• AccelerationTime
• MoveMaxForce
• etc

Seems like the default values do not create the same exact feeling in the character’s movement.

EDIT2: Setting UpVector seems to work for simple values like (1, 0, 0) and (0, -1, 0) but set it to (1, 0, 1) and it automatically gets set to (0.7, 0, 0.7) why?

EDIT3: That’s because of normalization my bad. Just use .Unit to normalize the UpDirection.

[Nuskusame (Nuska)]

Hi everyone,

I’m currently working on a character controller system and I’ve run into an issue with my GroundController. Specifically, the Active attribute of the GroundController (which inherits from ControllerBase) is not being set to true under certain conditions, and I can’t figure out why.
AirController seems to activate with no problem.

However if I publish the place and play test it in an actual Roblox game instance it works completely fine.

I’m suspecting that a recent Roblox Studio update might have changed an interaction that I didn’t account for.

Here are my questions:

1. What could cause the GroundController.Active attribute to remain false even when it is set as the ActiveController?
2. Are there any recommended ways to debug this issue further? For example, is there a way to trace what might be preventing the Active attribute from being set to true?

[Nuskusame (Nuska)]

To fix this issue make sure your PartSensors are Children of the RootPart of your Character.
Otherwise the physics to apply the offset or rotation of your GroundController will stay inactive.

controllerManager.GroundSensor = groundSensor
groundSensor.Parent = HumanoidRootPart --Insert your rootpart here

[xKiiyoko (Kiiyoko)]

Hi there, somewhat major bug that was introduced in a recent roblox update, that is plaguing my game.

I noticed that if a part was destroyed below the character, the game has lag spikes and then all the balancing physics will stop, making the game unplayable until a player resets.

Here is a repro place with the original scripts provided in this thread.
CharacterControllerDestroy_Repro.rbxl (63.7 KB)

[inHeadspace (vee)]

Yeah, that’s an issue I’ve been having. With the provided Character State localscript, the AirController gets stuck as the active controller when a part below the player suddenly gets deleted. A hacky workaround is to add a RenderStepped:Wait() on the line before cm.ActiveController = cm.GroundController

edit: this does not work consistently, nevermind.

This is a major thing that needs to be addressed soon.

[bear2126]

thats because updirection can only face one way, your example of 1,0,1 is facing 2 different directions

[Redridge (Red)]

I edited my original comment. It’s because the vector needs to be normalized. It has nothing to do with picking one direction.