Player input velocity overrides | Character Physics Controller

Help and Feedback Game Design Support
,
#1

I’ve been working with the “new” Character Physics Controllers and ran into somewhat of a limitation. In games such as Counter Strike and other source games, you can redirect movement with the A/D keys to strafe left and right while the w key is released. To the contrary, with the physics controller, pressing any movement key overrides the velocity vector and ends up slowing you down to send you in that direction, overriding any previous forward momentum. This even happens when holding ‘W’ while moving faster than the base movement speed, slowing you down instead of, in a perfect world, having no effect.

How it behaves right now:
Holding W example
Strafing example (a bit harder to see)

Here is an example of how I would want it to behave, but without the b-hop acceleration.

Is there some way to manage this behavior? I might make a feature request otherwise.
These new controllers are nice and I’ve enjoyed working with them. It would be a shame to have to end up creating my own controller.
I’m not sure how well I explained this, so tell me if I need to clarify anything.

Summary: Moving overrides already existing momentum instead of adding on to it.

#2

they may only have checked friction or somthing when moving
could be somthing else

1 Like
#3

Friction is checked regardless if you are moving or not. In that example, there was negligible friction. The issue here is that BaseMoveSpeed basically just sets your speed instead of either adding to it or having no effect, based on the direction of the vector. If I were to be moving at the speed in my example and were to, lets say, hold D, It would redirect the vector from {-200, 0, 0} to {0, 0, -20} (20 being my BaseMoveSpeed) instead of maintaining the speed and just adding to the vector3 {-200, 0, -20}. BaseMoveSpeed is basically just a flat value that the characters assemblyLinearVelocity is set to

(which I would like to be able to manage in some way)

#4

I’ll probably just make a feature request for this tomorrow