Hello, I cant change my classes interp to .033 and .0152 unless my interp_ratio is 0.
Is there a reason why it won't work on ratio 1 or 2? I normally only see 1 and 2 being used on connection configs so I was wondering if using interp_ratio 0 is a bad thing?
Thanks.
interp won't change
posted in
Customization
Hello, I cant change my classes interp to .033 and .0152 unless my interp_ratio is 0.
Is there a reason why it won't work on ratio 1 or 2? I normally only see 1 and 2 being used on connection configs so I was wondering if using interp_ratio 0 is a bad thing?
Thanks.
Is there a reason why it won't work on ratio 1 or 2? I normally only see 1 and 2 being used on connection configs so I was wondering if using interp_ratio 0 is a bad thing?
Thanks.
There are basically two interpolation values. One is cl_interp and the other is cl_interp_ratio/cl_updaterate. The game always uses whichever is bigger.
There are basically two interpolation values. One is cl_interp and the other is cl_interp_ratio/cl_updaterate. The game always uses whichever is bigger.
Turns out it doesn't work on 0 either.
It's stuck on 50ms :/
Turns out it doesn't work on 0 either.
It's stuck on 50ms :/
It's stuck on 50ms :/
There are more net settings than just interp you have to change. If your cmdrate and updrate are low then you also limit how low your interp can go.
From chris/comanglia's configs:
// Good connection
cl_cmdrate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
cl_interp .033 // change to whatever you like for certain classes projectiles/popping uber/flames = .0152 hitscan = .031 on bad connections = .062
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
rate 62000 // anything above 62,000 is completely useless, anything above 48,000ish is useless in HL
// Bad connection
//cl_cmdrate 40
//cl_interp 0
//cl_interp_ratio 2
//cl_lagcompensation 1
//cl_pred_optimize 2
//cl_smooth 0
//cl_smoothtime 0.01
//cl_updaterate 40
//rate 35000
There are more net settings than just interp you have to change. If your cmdrate and updrate are low then you also limit how low your interp can go.
From chris/comanglia's configs:
// Good connection
cl_cmdrate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
cl_interp .033 // change to whatever you like for certain classes projectiles/popping uber/flames = .0152 hitscan = .031 on bad connections = .062
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
rate 62000 // anything above 62,000 is completely useless, anything above 48,000ish is useless in HL
// Bad connection
//cl_cmdrate 40
//cl_interp 0
//cl_interp_ratio 2
//cl_lagcompensation 1
//cl_pred_optimize 2
//cl_smooth 0
//cl_smoothtime 0.01
//cl_updaterate 40
//rate 35000
From chris/comanglia's configs:
// Good connection
cl_cmdrate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
cl_interp .033 // change to whatever you like for certain classes projectiles/popping uber/flames = .0152 hitscan = .031 on bad connections = .062
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
rate 62000 // anything above 62,000 is completely useless, anything above 48,000ish is useless in HL
// Bad connection
//cl_cmdrate 40
//cl_interp 0
//cl_interp_ratio 2
//cl_lagcompensation 1
//cl_pred_optimize 2
//cl_smooth 0
//cl_smoothtime 0.01
//cl_updaterate 40
//rate 35000
KairuThere are more net settings than just interp you have to change. If your cmdrate and updrate are low then you also limit how low your interp can go.
From chris/comanglia's configs:
// Good connection
cl_cmdrate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
cl_interp .033 // change to whatever you like for certain classes projectiles/popping uber/flames = .0152 hitscan = .031 on bad connections = .062
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
rate 62000 // anything above 62,000 is completely useless, anything above 48,000ish is useless in HL
// Bad connection
//cl_cmdrate 40
//cl_interp 0
//cl_interp_ratio 2
//cl_lagcompensation 1
//cl_pred_optimize 2
//cl_smooth 0
//cl_smoothtime 0.01
//cl_updaterate 40
//rate 35000
still there is a lot of wrong info here,
// Good connection
cl_cmdrate 66 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
cl_interp .0303 // change to whatever you like for certain classes projectiles/popping uber/flames = .0152 hitscan = .0303 on bad connections = .045
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 66 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
rate 60000
you should use cl_interp_ratio to control your interp, the values are in natural numbers, 1 in ratio equals 0.0152 in regular interp, and every value is multiplying the interp value, so the next one is not 0.033, but 0.0303 and then 0.0455.
[quote=Kairu]There are more net settings than just interp you have to change. If your cmdrate and updrate are low then you also limit how low your interp can go.
From chris/comanglia's configs:
// Good connection
cl_cmdrate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
cl_interp .033 // change to whatever you like for certain classes projectiles/popping uber/flames = .0152 hitscan = .031 on bad connections = .062
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
rate 62000 // anything above 62,000 is completely useless, anything above 48,000ish is useless in HL
// Bad connection
//cl_cmdrate 40
//cl_interp 0
//cl_interp_ratio 2
//cl_lagcompensation 1
//cl_pred_optimize 2
//cl_smooth 0
//cl_smoothtime 0.01
//cl_updaterate 40
//rate 35000[/quote]
still there is a lot of wrong info here,
// Good connection
cl_cmdrate 66 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
cl_interp .0303 // change to whatever you like for certain classes projectiles/popping uber/flames = .0152 hitscan = .0303 on bad connections = .045
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 66 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
rate 60000
you should use cl_interp_ratio to control your interp, the values are in natural numbers, 1 in ratio equals 0.0152 in regular interp, and every value is multiplying the interp value, so the next one is not 0.033, but 0.0303 and then 0.0455.
From chris/comanglia's configs:
// Good connection
cl_cmdrate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
cl_interp .033 // change to whatever you like for certain classes projectiles/popping uber/flames = .0152 hitscan = .031 on bad connections = .062
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
rate 62000 // anything above 62,000 is completely useless, anything above 48,000ish is useless in HL
// Bad connection
//cl_cmdrate 40
//cl_interp 0
//cl_interp_ratio 2
//cl_lagcompensation 1
//cl_pred_optimize 2
//cl_smooth 0
//cl_smoothtime 0.01
//cl_updaterate 40
//rate 35000[/quote]
still there is a lot of wrong info here,
// Good connection
cl_cmdrate 66 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
cl_interp .0303 // change to whatever you like for certain classes projectiles/popping uber/flames = .0152 hitscan = .0303 on bad connections = .045
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 66 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
rate 60000
you should use cl_interp_ratio to control your interp, the values are in natural numbers, 1 in ratio equals 0.0152 in regular interp, and every value is multiplying the interp value, so the next one is not 0.033, but 0.0303 and then 0.0455.
Phoenix21[
you should use cl_interp_ratio to control your interp, the values are in natural numbers, 1 in ratio equals 0.0152 in regular interp, and every value is multiplying the interp value, so the next one is not 0.033, but 0.0303 and then 0.0455.
The reason I have mine set to 0.033 is due to a comment by wareya somewhere on these forums I remember reading (perhaps I was mistaken or misread) saying that you shouldn't use the exact interval value, but slightly above it..
I also use cmdrate and updaterate on 67 because 66 is lower than the game's tickrate of 66.6. Whether it helps or not I don't know, but figured it can't really hurt.
Edit: http://www.teamfortress.tv/33270/question-about-interp-and-interp-ratio#6
http://www.teamfortress.tv/33804/can-i-get-some-help-with-my-cl-settings#4
http://www.teamfortress.tv/33804/can-i-get-some-help-with-my-cl-settings#7
[quote=Phoenix21][
you should use cl_interp_ratio to control your interp, the values are in natural numbers, 1 in ratio equals 0.0152 in regular interp, and every value is multiplying the interp value, so the next one is not 0.033, but 0.0303 and then 0.0455.[/quote]
The reason I have mine set to 0.033 is due to a comment by wareya somewhere on these forums I remember reading (perhaps I was mistaken or misread) saying that you shouldn't use the exact interval value, but slightly above it..
I also use cmdrate and updaterate on 67 because 66 is lower than the game's tickrate of 66.6. Whether it helps or not I don't know, but figured it can't really hurt.
Edit: http://www.teamfortress.tv/33270/question-about-interp-and-interp-ratio#6
http://www.teamfortress.tv/33804/can-i-get-some-help-with-my-cl-settings#4
http://www.teamfortress.tv/33804/can-i-get-some-help-with-my-cl-settings#7
you should use cl_interp_ratio to control your interp, the values are in natural numbers, 1 in ratio equals 0.0152 in regular interp, and every value is multiplying the interp value, so the next one is not 0.033, but 0.0303 and then 0.0455.[/quote]
The reason I have mine set to 0.033 is due to a comment by wareya somewhere on these forums I remember reading (perhaps I was mistaken or misread) saying that you shouldn't use the exact interval value, but slightly above it..
I also use cmdrate and updaterate on 67 because 66 is lower than the game's tickrate of 66.6. Whether it helps or not I don't know, but figured it can't really hurt.
Edit: http://www.teamfortress.tv/33270/question-about-interp-and-interp-ratio#6
http://www.teamfortress.tv/33804/can-i-get-some-help-with-my-cl-settings#4
http://www.teamfortress.tv/33804/can-i-get-some-help-with-my-cl-settings#7
Phoenix21KairuThere are more net settings than just interp you have to change. If your cmdrate and updrate are low then you also limit how low your interp can go.
From chris/comanglia's configs:
// Good connection
cl_cmdrate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
cl_interp .033 // change to whatever you like for certain classes projectiles/popping uber/flames = .0152 hitscan = .031 on bad connections = .062
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
rate 62000 // anything above 62,000 is completely useless, anything above 48,000ish is useless in HL
// Bad connection
//cl_cmdrate 40
//cl_interp 0
//cl_interp_ratio 2
//cl_lagcompensation 1
//cl_pred_optimize 2
//cl_smooth 0
//cl_smoothtime 0.01
//cl_updaterate 40
//rate 35000
still there is a lot of wrong info here,
// Good connection
cl_cmdrate 66 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
cl_interp .0303 // change to whatever you like for certain classes projectiles/popping uber/flames = .0152 hitscan = .0303 on bad connections = .045
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 66 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
rate 60000
you should use cl_interp_ratio to control your interp, the values are in natural numbers, 1 in ratio equals 0.0152 in regular interp, and every value is multiplying the interp value, so the next one is not 0.033, but 0.0303 and then 0.0455.
to bad cl_interp_ratio is/(was?) locked to 1/0 on esea.
sv_client_max_interp_ratio "1"
sv_client_min_interp_ratio "0"I won't go any further into the mostly trivial nuances of interp.
UngirthedTurns out it doesn't work on 0 either.
It's stuck on 50ms :/
The only reason I can think of for you being stuck on 50ms is either the servers you're playing on are only 20tick are you have your client set to 20tick.
[quote=Phoenix21][quote=Kairu]There are more net settings than just interp you have to change. If your cmdrate and updrate are low then you also limit how low your interp can go.
From chris/comanglia's configs:
// Good connection
cl_cmdrate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
cl_interp .033 // change to whatever you like for certain classes projectiles/popping uber/flames = .0152 hitscan = .031 on bad connections = .062
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
rate 62000 // anything above 62,000 is completely useless, anything above 48,000ish is useless in HL
// Bad connection
//cl_cmdrate 40
//cl_interp 0
//cl_interp_ratio 2
//cl_lagcompensation 1
//cl_pred_optimize 2
//cl_smooth 0
//cl_smoothtime 0.01
//cl_updaterate 40
//rate 35000[/quote]
still there is a lot of wrong info here,
// Good connection
cl_cmdrate 66 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
cl_interp .0303 // change to whatever you like for certain classes projectiles/popping uber/flames = .0152 hitscan = .0303 on bad connections = .045
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 66 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
rate 60000
you should use cl_interp_ratio to control your interp, the values are in natural numbers, 1 in ratio equals 0.0152 in regular interp, and every value is multiplying the interp value, so the next one is not 0.033, but 0.0303 and then 0.0455.[/quote]
to bad cl_interp_ratio is/(was?) locked to 1/0 on esea.
[code]sv_client_max_interp_ratio "1"
sv_client_min_interp_ratio "0"[/code]
I won't go any further into the mostly trivial nuances of interp.
[quote=Ungirthed]Turns out it doesn't work on 0 either.
It's stuck on 50ms :/[/quote]
The only reason I can think of for you being stuck on 50ms is either the servers you're playing on are only 20tick are you have your client set to 20tick.
From chris/comanglia's configs:
// Good connection
cl_cmdrate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
cl_interp .033 // change to whatever you like for certain classes projectiles/popping uber/flames = .0152 hitscan = .031 on bad connections = .062
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 67 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
rate 62000 // anything above 62,000 is completely useless, anything above 48,000ish is useless in HL
// Bad connection
//cl_cmdrate 40
//cl_interp 0
//cl_interp_ratio 2
//cl_lagcompensation 1
//cl_pred_optimize 2
//cl_smooth 0
//cl_smoothtime 0.01
//cl_updaterate 40
//rate 35000[/quote]
still there is a lot of wrong info here,
// Good connection
cl_cmdrate 66 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
cl_interp .0303 // change to whatever you like for certain classes projectiles/popping uber/flames = .0152 hitscan = .0303 on bad connections = .045
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 66 // The tricks to get 1.4ms lerp are placebo you're still forced to .0152
rate 60000
you should use cl_interp_ratio to control your interp, the values are in natural numbers, 1 in ratio equals 0.0152 in regular interp, and every value is multiplying the interp value, so the next one is not 0.033, but 0.0303 and then 0.0455.[/quote]
to bad cl_interp_ratio is/(was?) locked to 1/0 on esea.
[code]sv_client_max_interp_ratio "1"
sv_client_min_interp_ratio "0"[/code]
I won't go any further into the mostly trivial nuances of interp.
[quote=Ungirthed]Turns out it doesn't work on 0 either.
It's stuck on 50ms :/[/quote]
The only reason I can think of for you being stuck on 50ms is either the servers you're playing on are only 20tick are you have your client set to 20tick.
Please
sign in through STEAM
to post a comment.