relaxtakenotes
commented
9 months ago syncing footsteps with the playermodel using numbers is pretty stupid and is just a waste of time. i am planning on adding some sort of a feature that emits footsteps when the actual leg hits something, but god knows when i'll get it right. there's an implementation of it here: https://github.com/PAC3-Server/notagain/blob/master/lua/notagain/essential/autorun/realistic_footsteps.lua, but due to the license and the fact that i just plain out don't like it, i'm pretty hesitant on using it.
Lombaxtard
I thing I've mentioned this a long time ago, but is it possible that you'd implement a different formula for stepsoundtime? There would be slowwalk, walk, and run definable variables (in ticks or ms, whatever it is now) that would determine stepsound delay (just like Simple Player Speed Changer has it now), then that value would be contracted by current movement speed percentage inverted (movtype - movspeedinv = stepsoundtime) or something like that. Apologies for a hasty explanation..
So if every move type has it's own stepsoundtime value, then let's say, walk move type has it at 400 at 100% walk speed (not transitioning), which would then transition into run move type's value of 200, gradually, being at 300 ticks when movement speed is 50% into transition in between walk and run movement speed. I said it once, and I'll say it again - being able to sync stepsoundtime exactly to the way your character moves it's legs is another level of feast for your eyes and ears. I think the implementation is something like duplicating movement speed acceleration and deceleration to instead feature stepsoundtime.
Perhaps even add an offset for every third step (L4D Reanimation has assymetrical animation loop just like in the game, which approximately means: step > 151ticks > step > 160 ticks > step > 151 ticks > and so on)
Anyway, separate stepsoundtime values would be enough of a bliss, I'm just daydreaming here in regards to third step offset, if you're up for this of course