Releasing Character Physics Controllers

[shadow4765]

Increase Friction to 2 and put FrictionWeight 20-100 depending on if you want it to slow down while walking on ramps or keep the same speed

[shadow4765]

Hi walking down a set of stairs is quite janky (while walking up is fine), also an option to disable directional changes mid-air would be nice, as well as keeping momentum when jumping and jumping while running would also be nice.

[0Tenth (Lychee)]

@ResumavoidDev

Walking on an unanchored part makes you “walk in place” while the part below you moves in the opposite direction you’re moving in

What’s the mass of the part that you’re walking on?

[ToldFable (fable)]

Here’s some feedback:

• An easy way to detect default jump would be nice.
  Seems like the UserInputService.JumpRequest event requires a Humanoid, so the following code currently doesn’t work:
  UserInputService | Documentation - Roblox Creator Hub

local RayParams = RaycastParams.new()
RayParams.FilterType = Enum.RaycastFilterType.Exclude
RayParams.FilterDescendantsInstances = {Char}

function jump()
	local Raycast = workspace:Raycast(HumanoidRootPart.Position,Vector3.new(0,-5,0),RayParams)
	if Raycast and Raycast.Instance and Raycast.Instance.CanCollide then
		HumanoidRootPart.AssemblyLinearVelocity += Vector3.new(0,50,0)
	end
end
UserInputService.JumpRequest:Connect(jump)

• Not sure if I’m doing something wrong but this gets spammed in the console:

Player:Move called, but player currently has no humanoid. (x122)

unless I do

game.Players.LocalPlayer.Character = nil

• It’d be nice to disable rotational velocity inheritance in the Y axis

• Some sort of togglable built in “coyote time” mechanic, so players can change direction mid jump, might make things feel more fluid

Cool stuff overall, really excited about the realistic velocity inheritance!

[ResumavoidDev (Resumavoid)]

Not sure, I only noticed it when I had accidental unanchored parts in the game.

[nothing_1649 (gom_a)]

here’s the bug report:

Strange ControllerPartSensor behaviour when ModelStreamingBehavior is set to Improved

When Workspace.ModelStreamingBehavior is set to Improved, ControllerPartSensors occasionally behave “stuck”, not updating as if its UpdateType was set to Manual. Normally this seems to occur roughly 30% of the time, but is pretty much guaranteed when IncomingReplicationLag is increased. This does not occur with legacy model streaming behaviour, occurs regardless of the character’s ModelStreamingMode, and only seems to happen when a player’s character has been added for the first time. It allows…

[Scopetag (Scope)]

Threw together a whole character physics controller demo place to show some of the features I implemented.

[CartoonBlur (Dunold_Turmp)]

Changing the Base move speed of the ControllerManager doesnt not affect the character speed when a Humanoid is present… Any fix to this? if I dont use a Humanoid, game health script throws a bunch of errors.

[MatkeFTW]

@kleptonaut

What’s Next

Later, we will have an official implementation in Lua using these instances that is intended to match exactly how the Humanoid handles states and movement today, as well as even more customization options. These example scripts will become obsolete once that’s released.

Are there any updates on this official implementation? Maybe an ETA or a newer version of these scripts?

[nothing_1649 (gom_a)]

they seem to be getting close to releasing it, an enum relating to it was recently removed from the engine in either 607 or 608

[blowup999]

Is this not working for anyone else? I tried the InitializeCharacters script given as well as just making it based on the setup guide.

It seems to have a lag period of at least 30 seconds before characters start using the GroundSensor / GroundController appropriately. And until then, they’re stuck in the ground, and if I walk into them to see if it’ll refresh their position, it knocks them over but does nothing until it all of a sudden starts working, and once it starts working it doesn’t seem to have any issues.

ControllerManagerFailure.rbxl (105.2 KB)
^ Placefile

[nothing_1649 (gom_a)]

i’m having this issue too but for only a few seconds when playtesting in studio for the first time, when i tried your place file the controllermanagers only seem to work when the client has network ownership of them and they just don’t respond when the server owns them

however, it started working on the server while i was writing this after like 2 minutes, except that it went back to breaking unlike what you’re experiencing and it never worked in run mode, i genuinely can’t figure out why

also, when each controllermanager “loaded” in on the server i could also audibly hear my pc’s fans firing up for a bit which is a bit concerning, i don’t really know how to use the micro profiler so i can’t really provide data or anything but it still worries me a bit

[apenzijncoolenleuk1 (Apenz1)]

Hi
Any update on fixes or the lua release?
Would like to use this, but in it’s current state it’s not really usable…

[Mikos_Drafle (mikoblixel)]

yup this is pretty much unusable in most of my cases

i’m trying to make an obby but having yourself get flung for absolutely no reason when going up trusses is annoying

[kleptonaut]

NOTICE

This week we will be releasing fixes and stability improvements to the ControllerManager.

One in particular is a fix for GroundController turning. This prevents it from overshooting the FacingDirection at high speeds. In fact, the actual angular velocity was often higher than was defined by ControllerManager.BaseTurnSpeed * GroundController.TurnSpeedFactor defaults. This lead to turning faster with a GroundController as opposed to the AirController despite the same settings. Now, turn speeds should be consistent for both.

As a result, the GroundController turn speeds may appear slower than before. You can compensate for this by increasing the TurnSpeedFactor on the Controller or BaseTurnSpeed.

[bigtheangry]

very cool roblox

(character limit)

[focasds]

Is there a way to keep the RootPart from rotating indefinity without needing to use AlignOrientation? Currently when the offset is high and the object is floating, the part basically rotates left and right many times, and doesn’t get to face the right direction. Why is this? It should automatically just face the direction properly. (Not sure if this fix getting released fixes this)

I am using ControllerManager, GroundSensor, and GroundPartController with their default properties, except that the RootPart is just by itself, is big 200 each axis, and has an offset that creates this levitating effect that I need, and the SearchDistance is high as well to account for the GroundOffset.

If is to be expected that it will never get to face the direction fast enough and properly without going forward and then back again, should I just use the AlignOrientation?

[TEARAPARTJAMES (FROGMIRE)]

So, I’ve been messing around with this for a long time. I like my current result but am sort of at a stopping point as I prefer Gravity being lower for more real-world-like physics. However, it seems that messing with gravity messes with the friction or something so my character slides around and rotation overshoots even more than before. In a way, it makes sense but it’s annoying.

Is this intentional? If so, how can I avoid this sliding?

[kleptonaut]

Increase the Friction and FrictionWeight properties on the GroundController

[TEARAPARTJAMES (FROGMIRE)]

Thanks!
It seems to work, but it comes with the quirk of moving unanchored parts under the character. I guess that’s because it’s all physics-based, but I think I can come up with a solution for that.