Can someone explain to me how to lower the lerp value?

[Samwise]

Firstly, dont worry i don't intent to cheat in versus, i don't even play that mode. I just want to things to happen ingame closer to real time. Afaic, there is standard "lag" of 100ms in the game, regardless of your ping. I get around 30 or lower, but i still notice there's annoying delay when i shoot something. this is especially noticeable when i use snipers.

What values i need to lower and how to reset them? i don't want to mess anything up and i changed the default survivor fov and it never resetted back to default value.

[Sharpie The Dragon]

Well changing your lerp is pretty advantageous. It's not a cheat IMO, since everybody in the game can modify their lerp settings.

1. Go into console
2. type cl_interp 0.[NUMBER HERE] you can have your lerp from 500ms to 0.10ms in official versus if I recall. If you want it as close to real time as possible, it would be: cl_interp 0.010, anything lower and it will auto adjust to that value unless you're in a server that allows a lower lerp setting.

Just keep in mind that you may see some juttering of infected, in which case you may want to up your lerp setting.

Default lerp is cl_interp 0.100, to see your current lerp, use net_graph 1/2/3/4 command.

cl_viewmodelfovsurvivor <NUMBER HERE> never changes, but lerp does. Not sure why, but you can create an autoexec to have said lerp numbers you desire if you're into that sort of thing.

[$pirit]

// RATE SETTINGS & NET USAGE GRAPH SETTINGS
rate "100000" //(Default 10000)
cl_cmdrate "101" //(Default 30)
cl_updaterate "101" //(Default 20)
cl_interp "0.0167" //(Default 0.1) THIS IS THE LERP YOUR GAME WILL LOAD IN AT.
cl_interp_ratio "-1" //(Default 2)
net_graph 1 //(Default 0)
net_graphproportionalfont "0" //(Default 1)
net_graphpos 1 //(Default 1)

Cram all that into your autoexec.cfg file.

Or type them manually.

https://steamcommunity.com/sharedfiles/filedetails/?id=159267328

[Samwise]

Originally posted by Feathers:

Well changing your lerp is pretty advantageous. It's not a cheat IMO, since everybody in the game can modify their lerp settings.

1. Go into console
2. type cl_interp 0.[NUMBER HERE] you can have your lerp from 500ms to 0.10ms in official versus if I recall. If you want it as close to real time as possible, it would be: cl_interp 0.010, anything lower and it will auto adjust to that value unless you're in a server that allows a lower lerp setting.

Just keep in mind that you may see some juttering of infected, in which case you may want to up your lerp setting.

Default lerp is cl_interp 0.100, to see your current lerp, use net_graph 1/2/3/4 command.

cl_viewmodelfovsurvivor <NUMBER HERE> never changes, but lerp does. Not sure why, but you can create an autoexec to have said lerp numbers you desire if you're into that sort of thing.

I actually already see slight juddering, but i always thought its because my laptops is so bad. Sure i get 60fps without drops and ping of 30, but i still notice the juddering occasionally.

If i lower the lerp do i need to tweak other values as well? I'd imagine something like half of the current lerp could help a ton without causing any noticeable issue.

[Samwise]

Originally posted by SPIRIT:

// RATE SETTINGS & NET USAGE GRAPH SETTINGS
rate "100000" //(Default 10000)
cl_cmdrate "101" //(Default 30)
cl_updaterate "101" //(Default 20)
cl_interp "0.0167" //(Default 0.1) THIS IS THE LERP YOUR GAME WILL LOAD IN AT.
cl_interp_ratio "-1" //(Default 2)
net_graph 1 //(Default 0)
net_graphproportionalfont "0" //(Default 1)
net_graphpos 1 //(Default 1)

Cram all that into your autoexec.cfg file.

Or type them manually.

https://steamcommunity.com/sharedfiles/filedetails/?id=159267328

What those settings do? I have to admit that i have no idea about any of that, i only read about lerp and how you get massive 100ms added to your ping and it makes me miss and get downed. Do i even need to change those values?

Oh and i have 50mb connection and i play with wifi, but its very stable connection, but not the best. So, i imagine i shouldnt aim for an actual real time but lessen the delay of default lerp.

[$pirit]

Rate, cl_cmdrate and cl_updaterate are to do with how your client talks to the server, basically stops network bottlenecks.

The interp ones are to do with lerp.

And the others just put a little network graph in the corner of your screen.

[Samwise]

One more question. Is this negative 1 or just number 1???

cl_interp_ratio "-1" //(Default 2)

I read about this and apparently, 1 is for connection that is fast and stable, and 2 is for one which has margin for error. Idk, if i even need to change this value. Does it even affect anything if i change rates and lower the interp value?

[Nodoka]

Originally posted by Samwise:

Firstly, dont worry i don't intent to cheat in versus, i don't even play that mode. I just want to things to happen ingame closer to real time. Afaic, there is standard "lag" of 100ms in the game, regardless of your ping. I get around 30 or lower, but i still notice there's annoying delay when i shoot something. this is especially noticeable when i use snipers.

What values i need to lower and how to reset them? i don't want to mess anything up and i changed the default survivor fov and it never resetted back to default value.

https://developer.valvesoftware.com/wiki/Interpolation
https://developer.valvesoftware.com/wiki/Source_Multiplayer_Networking

Interpolation smooths movement animation but adds artificial latency. Physical interactions, like dead-stopping and pouncing, are not lag compensated. Among other things, this higher interp will mean you have less time to dead stop a hunter, and it will be harder to hit pounces/charges.

[Blaquicat]

Originally posted by Samwise:

One more question. Is this negative 1 or just number 1???

cl_interp_ratio "-1" //(Default 2)

I read about this and apparently, 1 is for connection that is fast and stable, and 2 is for one which has margin for error. Idk, if i even need to change this value. Does it even affect anything if i change rates and lower the interp value?

Use negative value to "disable" the "ratio".

Valve developer states this:

cl_interp_ratio : 2.0 : , "user", "cl" : Sets the interpolation amount (final amount is cl_interp_ratio / cl_updaterate).

With cl_interp_ratio the game wil always "auto-set" the lerp based on the server sv_minupdaterate. (and maxupdaterate) and obviously on your own updaterate.

Lower lerp means better game response, but more teleporting, as it has less interpolation to work with.
Lerp exists to make the game play more smooth, if you don't care much (like i) you can always set to minimum..

The best value in my opinion is the same as your ping, 30 ping = 30 lerp, it is more smooth as possible, but with a good response from the game server.

note:

Unfortunately Valve's games still default to a minimum interpolation delay ("lerp") of 100ms, a value tuned for the era of dial-up modems!

[Manhattan Cafe]

Originally posted by $pirit:

// RATE SETTINGS & NET USAGE GRAPH SETTINGS
rate "100000" //(Default 10000)
cl_cmdrate "101" //(Default 30)
cl_updaterate "101" //(Default 20)
cl_interp "0.0167" //(Default 0.1) THIS IS THE LERP YOUR GAME WILL LOAD IN AT.
cl_interp_ratio "-1" //(Default 2)
net_graph 1 //(Default 0)
net_graphproportionalfont "0" //(Default 1)
net_graphpos 1 //(Default 1)

Cram all that into your autoexec.cfg file.

Or type them manually.

https://steamcommunity.com/sharedfiles/filedetails/?id=159267328

Thank you so ♥♥♥♥♥♥♥ very mucho you are my ♥♥♥♥♥♥♥ hero.

[Muneer John]

Originally posted by $pirit:

// RATE SETTINGS & NET USAGE GRAPH SETTINGS
rate "100000" //(Default 10000)
cl_cmdrate "101" //(Default 30)
cl_updaterate "101" //(Default 20)
cl_interp "0.0167" //(Default 0.1) THIS IS THE LERP YOUR GAME WILL LOAD IN AT.
cl_interp_ratio "-1" //(Default 2)
net_graph 1 //(Default 0)
net_graphproportionalfont "0" //(Default 1)
net_graphpos 1 //(Default 1)

Cram all that into your autoexec.cfg file.

Or type them manually.

https://steamcommunity.com/sharedfiles/filedetails/?id=159267328

ty

[76561199570567320]

.

[Dieter]

This thread was quite old before the recent post, so we're locking it to prevent confusion.