[Hedgehog Fog]

Hey there,
I found out that decreasing think delay affects movement speed.

For example, in this case, the entity will move for 250 units in the second:

PHP Code:

    static Float:vDirection[3];
    // get direction somehow

    static Float:vVelocity[3];
    xs_vec_mul_scalar(vDirection, fSpeed, vVelocity);
    set_pev(ent, pev_velocity, vVelocity);

    set_pev(ent, pev_nextthink, get_gametime() + 0.04); // 25 fps 


but for 0.1 seconds delay (10 fps) the entity will move for about 224 units:

PHP Code:

    set_pev(ent, pev_nextthink, get_gametime() + 0.1); 


I've tried to set FL_BASEVELOCITY flag in every think, but it didn't really affect the behavior.

So for 0.1 delay velocity should be about 280 ups to cover the 250 units in 1 second.

I can't find any mention of the effect of time on velocity for entities with MOVETYPE_STEP move type in HLSDK and Xash3D engine code.
Is there any way to fix this effect?

Thanks!

[AnimalMonster]

Originally Posted by Hedgehog95 Hey there, I found out that decreasing think delay affects movement speed. For example, in this case, the entity will move for 250 units in the second: PHP Code:     static Float:vDirection[3];     // get direction somehow     static Float:vVelocity[3];     xs_vec_mul_scalar(vDirection, fSpeed, vVelocity);     set_pev(ent, pev_velocity, vVelocity);     set_pev(ent, pev_nextthink, get_gametime() + 0.01);  but for 0.1 seconds delay (10 fps) the entity will move for about 224 units: PHP Code:     set_pev(ent, pev_nextthink, get_gametime() + 0.1);  I've tried to set FL_BASEVELOCITY flag in every think, but it didn't really affect the behavior. So for 0.1 delay velocity should be about 280 ups to cover the 250 units in 1 second. There is no visible effect on velocity for 0.04 seconds delay. I can't find any mention of the effect of time on velocity for entities with MOVETYPE_STEP move type in HLSDK and Xash3D engine code. Is there any way to fix this effect? Thanks!

I guess this script you make you need on android cs 1.6??
Maybe you can use MOVETYPE_FOLLOW

[Natsheh]

Originally Posted by AnimalMonster I guess this script you make you need on android cs 1.6?? Maybe you can use MOVETYPE_FOLLOW

what are you talking about !@>!>!#>!$>!#@>$%@#>%>>??

and for the OP show the full code that weird for me too i don't remember hearing the entity think length effects the entity velocity.

[Hedgehog Fog]

Not resolved, but closed.
I'm going to change the approach and update velocity every think, but I'll move the main logic to another task which will be called less often than think handle.

[Natsheh]

i know this is an old topic the reason why this is happening because entities with MOVETYPE_STEP has a friction, so during the process they might slow down!