detecting if player is runing

[Nahuel]

is there a way to know if the player is pressing the "+speed" button? i know is possible to know if the player is pressing button1 for example

Code: Select all

if (self.button1)

thanks in advance

[mankrip]

Without some extension like CSQC, probably not.

Maybe you can check the value from self.movement (which only works in some engines), and see if it matches the velocity for the running. This won't work if the running speed cvars have been modified.

[Nahuel]

i am using

Code: Select all

vlen (self.velocity)  > ...

but i need to know if the player is pressing the button , do you know what about csqc and button pressed?

[Spike]

I'm not really trying to troll... but who out there actually uses +speed (as opposed to always-run)?
does it actually make sense to try to detect it?
ssqc has no way to distinguish between +speed and merely setting cl_forwardspeed to 400 (aka: always-run) or so.

The evil way:
alias +speed +button5
alias -speed -button5

[Baker]

Check onground flag and check velocity > 200 (or so depending on what you expect) ?

Sure this doesn't check the button, but if the player is pressing the run button and forward while standing in a corner facing the corner, is he actually running?

[Does QuakeC get to know "wish velocity" [desired speed client sends to server?]

[frag.machine]

Check onground flag and check velocity > 200 (or so depending on what you expect) ?

This actually can work pretty well. I already used this. In Darkplaces the relation between running/walking speed is controlled by a cvar (cl_movespeedkey, default = 2.0). In other engines this relation is fixed in 2.
Basically, check your effective speed (doing some nasty math with self.velocity or directly with .movement if available) against sv_maxspeed / factor; if lower or equals, it's walking.

As a side note cl_movespeedkey with values below 1.0 actually slow down the player. This can be handy for stalking mods (like in the shadows).

[Spike]

"Does QuakeC get to know "wish velocity" [desired speed client sends to server?]"
.movement is exactly that.
not fantastically different from velocity, but doesn't get clipped by sv_maxspeed, has lower latency, and works even if they're stupid enough to be running into a wall.

[r00k]

player.qc uses this

Code: Select all

   if (self.velocity_x || self.velocity_y)
   {
      self.walkframe=0;
      player_run();
      return;
   }


you can just before the self.walkframe=0; test for how fast. Like Baker suggested >200 is running/+speed is on...

Spike I cant find .movement in vanilla qc...

[frag.machine]

Spike I cant find .movement in vanilla qc...

IIRC not all engines support it, or it's like the .gravity field that is supported by Quake 1.08 and above, because it was added in hipnotic. Memory is failing a lot today (I need sleep)...
EDIT: also, vanilla QC just tests if the player is in movement, it doesn't check if running or just walking (since the animations are the same).

[Spike]

.movement is a dp extension.

[r00k]

ack note toself add .movement extention

[drm_wayne]

afaik p0x qcv1.06 addons have this feature in the footsteps, if you run the play faster...

[leileilol]

I believe the p0x method is dropping entities and comparing their vector lengths with the current player origin.