Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I'm using this setting, good set with my setup.
And when I ask 'what do they do?' the answer is mostly 'google it', but even if I google them, there's hardly any info I could find that's easy to understand.
https://steamcommunity.com/sharedfiles/filedetails/?id=2082815521
Of course this image was taken on a local server, it change a bit depends of your ping and the enemy pings and also the servers, but basically this is what it does. In a big big picture.
Usually, the game uses the higher lerp to make the movement smooth by "estimating" where the common infected will be by the next time it checks, before it gets the next input of it's actual location. Due to the lowered lerp however, it doesn't have the time to calculate it as your client is asking for more inputs than the server can provide, and therefore displays it in a choppy manner. If you use the same lerp, but on a 100 tick server (which updates the location much more often) it isn't choppy. Generally a lerp of 0.60 is the threshold of the choppiness.
Do note that this explanation is really, really simplified, and far from super accurate, but I hope it helps understand it a bit better.
Also, the best lerp rates are ones you can toggle between easily:
bind u "rate 30000; cl_cmdrate 30; cl_updaterate 30; cl_interp_ratio 1; cl_interp 0.06"
bind j "rate 100000; cl_cmdrate 101; cl_updaterate 101; cl_interp_ratio -1; cl_interp 0.00"
bind "W" "+mfwd"
bind "A" "+mleft"
bind "S" "+mback"
bind "D" "+mright"
alias +mfwd "dsp_volume 0;-back;+forward;alias checkfwd +forward"
alias +mback "dsp_volume 0;-forward;+back;alias checkback +back"
alias +mleft "dsp_volume 0;-moveright;+moveleft;alias checkleft +moveleft"
alias +mright "dsp_volume 0;-moveleft;+moveright;alias checkright +moveright"
alias -mfwd "-forward;checkback;alias checkfwd none"
alias -mback "-back;checkfwd;alias checkback none"
alias -mleft "-moveleft;checkright;alias checkleft none"
alias -mright "-moveright;checkleft;alias checkright none"
alias checkfwd "none"
alias checkback "none"
alias checkleft "none"
alias checkright "none"
alias none ""
dsp_enhance_stereo "0"
dsp_slow_cpu "0"
bind "i" "snd_mixahead 0.056"
It needs to do this since audio is weird in this game. When you go into a different area (say you went from outdoors to indoors) you'd expect the sound to change. The settings you have here need to be constantly updated as you're going into multiple areas or it's useless, it just so happens that one of the basic functions we use is movement, so it's binded to that.
There was a source on this somewhere, I wouldn't go out of my way to post a malicious script.