Character "sliding" after engaging AppSpeed( )

[PapaGwan]

Hey all,

 

I was happily developing away when I found that enabling lights in my app cause a major speed reduction. So I changed it all up to incorporate AppSpeed in all my time-sensitive variables and whatnot. However, there was an unexpected side effect.

 

While before, my Character Controller moved happily when pressing the movement buttons, and stopped when you stopped pressing movement buttons, now he accelerates and decelerated very slowly. I've played with the maxacceleration argument with updating, trying ranges from 1-100 and it does not help.

 

Anyone got a magic solution? I don't want my Character Controller to be playing on ice!

 

Thanks!

[macklebee]

an acceleration of 1-100 is very low... try between 300-500.

[PapaGwan]

Nice thanks that did it! Increased it to 500 but had to drop speed down to .000005 =P

 

Thanks again!

[TylerH]

The units are in meters aren't they? An acceleration of 500 m/s ^ 2 would be ridiculously fast.

[Mumbles]

But we humans don't accelerate the same way vehicles do. Within about 1/2 a second, we're at our target speed (unless you're out of energy, or have a lard belly). So we just use 500 as a value to make it feel virtually instant. If the maximum speed is constrained to about 1 or 2 metres per second anyway, then we just reach that 1 or 2 m/s very, very quickly...

[TylerH]

That makes sense. I just think that logically, if the player controller represents human motion, the parameters should be altered so that it is input in such a way.

 

Most games simply have a speed value, where 700 is walking, 400 is out of breath, 900 is sprinting, etc. (using Source as an example)