Hexen 2: side speed is wrong
Brought to you by:
acceptthis,
timeserv
Menu
▾
▴
#135 Hexen 2: side speed is wrong
Version: 6202
In regular Hexen II and Hexen II specific source ports, cl_sidespeed is entirely ignored. Instead, the value of cl_forwardspeed is used (400) for side step.
FTEQW though does not ignore the value of cl_sidespeed (225), thus it is way too slow, which is immediately apparent when strafing.
This can be trivially worked-around by users by setting cl_sidespeed to 400. But it would be better if it worked correctly out of the box. For this, if FTEQW detects it is running Hexen II, it should automatically internally use the value of cl_forwardspeed for both cl_sidespeed and cl_backspeed: Hexen II uses a single speed for all directions (400 by default).
Actually that's not quite right.
The h2mp code uses cl_forwardspeed>200 ONLY as an always-run flag - set cl_movespeedkey to 1 and you should see that it stops having any effect at all.
Instead its actual forwardspeed is hardcoded to 200, and its sidespeed is hardcoded to 225.
FTE's default cl_sidespeed is already 400 (should actually be 450 to match hexen2), probably you're only noticing because of existing configs (probably including default.cfg...)
I can make FTE's options menu force them appropriately when running hexen2 (but setting cl_run instead of cl_forwardsped>200), but that won't help existing configs until they fiddle with the menus.
The speed-boots artifact is also an issue however. FTE is lazy and basically just scales maxspeed without scaling intents, while hexen2 has a higher maxspeed and scales intents instead.
Merged into https://github.com/fte-team/fteqw/issues/15