hello, my friend has been trying to help me get 14.2 ler in game (and be white, not orange or yellow) but we cannot figure it out.
// Balance Network settings
cl_interp 0.0142
cl_interp_ratio 1.4
cl_updaterate 67
cl_cmdrate 67
rate 100000
////////////////////////
////////Movement////////
////////////////////////
bind w +mfwd
bind s +mback
bind a +mleft
bind d +mright
alias +mfwd "-back;+forward;alias checkfwd +forward"
alias +mback "-forward;+back;alias checkback +back"
alias +mleft "-moveright;+moveleft;alias checkleft +moveleft"
alias +mright "-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 ""
those are the net settings i am using and it gives me 20.9 lerp in game which is orange, what should i fix?
hello, my friend has been trying to help me get 14.2 ler in game (and be white, not orange or yellow) but we cannot figure it out.
// Balance Network settings
cl_interp 0.0142
cl_interp_ratio 1.4
cl_updaterate 67
cl_cmdrate 67
rate 100000
////////////////////////
////////Movement////////
////////////////////////
bind w +mfwd
bind s +mback
bind a +mleft
bind d +mright
alias +mfwd "-back;+forward;alias checkfwd +forward"
alias +mback "-forward;+back;alias checkback +back"
alias +mleft "-moveright;+moveleft;alias checkleft +moveleft"
alias +mright "-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 ""
those are the net settings i am using and it gives me 20.9 lerp in game which is orange, what should i fix?
There is nothing to fix.
Interp_ratio 1.4 means an interpolation time of 1.4 packet intervals. Because a packet might be a late a value slightly above 1 guarantees that there will always be a packet to interpolate with.
14.2ms interp on a 15ms/66 tickrate server means unless a packet somehow arrives early there will always be a small window where TF2 must extrapolate instead.
TF2 always uses the higher value out of ratio/updaterate and flat interp.
If you want to do it properly set cl_interp_ratio to 0.95 because that's what you're doing.
If you want to lie to yourself that this isn't stupid or need to bypass the sv_client_min_interp_ratio 1, which is set to stop you from doing stupid shit you need to lie to the server and set cl_updaterate 70 (even though a server that runs at 66.6666 ticks per second will never be able to send you 70 updates per second) because 1/70 = 0.0142857 so that's the interp TF2 will use even though it's bullshit.
FYI orange = effective ratio less than 2
yellow = lerp lower than server framerate
Also curious why you'd think movement scripts would affect interp.
There is nothing to fix.
Interp_ratio 1.4 means an interpolation time of 1.4 packet intervals. Because a packet might be a late a value slightly above 1 guarantees that there will always be a packet to interpolate with.
14.2ms interp on a 15ms/66 tickrate server means unless a packet somehow arrives early there will always be a small window where TF2 must extrapolate instead.
TF2 always uses the higher value out of ratio/updaterate and flat interp.
If you want to do it properly set cl_interp_ratio to 0.95 because that's what you're doing.
If you want to lie to yourself that this isn't stupid or need to bypass the sv_client_min_interp_ratio 1, which is set to stop you from doing stupid shit you need to lie to the server and set cl_updaterate 70 (even though a server that runs at 66.6666 ticks per second will never be able to send you 70 updates per second) because 1/70 = 0.0142857 so that's the interp TF2 will use even though it's bullshit.
FYI orange = effective ratio less than 2
yellow = lerp lower than server framerate
Also curious why you'd think movement scripts would affect interp.
SetsulThere is nothing to fix.
Interp_ratio 1.4 means an interpolation time of 1.4 packet intervals. Because a packet might be a late a value slightly above 1 guarantees that there will always be a packet to interpolate with.
14.2ms interp on a 15ms/66 tickrate server means unless a packet somehow arrives early there will always be a small window where TF2 must extrapolate instead.
TF2 always uses the higher value out of ratio/updaterate and flat interp.
If you want to do it properly set cl_interp_ratio to 0.95 because that's what you're doing.
If you want to lie to yourself that this isn't stupid or need to bypass the sv_client_min_interp_ratio 1, which is set to stop you from doing stupid shit you need to lie to the server and set cl_updaterate 70 (even though a server that runs at 66.6666 ticks per second will never be able to send you 70 updates per second) because 1/70 = 0.0142857 so that's the interp TF2 will use even though it's bullshit.
FYI orange = effective ratio less than 2
yellow = lerp lower than server framerate
Also curious why you'd think movement scripts would affect interp.
i just decided to put my full autoexec in there, when i change my interp ratio it says my interp is .014925, idk what im doing so i added you for furthur help. also as a followup question, what interp or interp ratio would you reccomend that i use?
[quote=Setsul]There is nothing to fix.
Interp_ratio 1.4 means an interpolation time of 1.4 packet intervals. Because a packet might be a late a value slightly above 1 guarantees that there will always be a packet to interpolate with.
14.2ms interp on a 15ms/66 tickrate server means unless a packet somehow arrives early there will always be a small window where TF2 must extrapolate instead.
TF2 always uses the higher value out of ratio/updaterate and flat interp.
If you want to do it properly set cl_interp_ratio to 0.95 because that's what you're doing.
If you want to lie to yourself that this isn't stupid or need to bypass the sv_client_min_interp_ratio 1, which is set to stop you from doing stupid shit you need to lie to the server and set cl_updaterate 70 (even though a server that runs at 66.6666 ticks per second will never be able to send you 70 updates per second) because 1/70 = 0.0142857 so that's the interp TF2 will use even though it's bullshit.
FYI orange = effective ratio less than 2
yellow = lerp lower than server framerate
Also curious why you'd think movement scripts would affect interp.[/quote]
i just decided to put my full autoexec in there, when i change my interp ratio it says my interp is .014925, idk what im doing so i added you for furthur help. also as a followup question, what interp or interp ratio would you reccomend that i use?
SetsulIf you want to lie to yourself that this isn't stupid or need to bypass the sv_client_min_interp_ratio 1, which is set to stop you from doing stupid shit you need to lie to the server and set cl_updaterate 70 (even though a server that runs at 66.6666 ticks per second will never be able to send you 70 updates per second) because 1/70 = 0.0142857 so that's the interp TF2 will use even though it's bullshit.
The server is stopping you from being an idiot.
If you still want to be an idiot why bother with 14.2? Is that some magic value where the interpolation is only slightly broken but the 0.8ms you gained are more than worth it? Why not break it harder? Why not use updaterate 100 and get that sweet sweet 10 ms interp? You save a whole 5ms compared to working interp, which is almost noticeable on 50 ping and it only breaks interp 1/3 of the time. Or go all the way with updaterate 100000000. Just get rid of that pesky interpolation. Give me the full eye-bleeding jittery extrapolation experience. Ignore the server telling you that anything lower than ratio 1 is monumentally stupid.
Hell, just disable lag compensation alltogether. Play in HARDMODE.
https://www.youtube.com/watch?v=hP9yrLSL-G0
[quote=Setsul]
If you want to lie to yourself that this isn't stupid or need to bypass the sv_client_min_interp_ratio 1, which is set to stop you from doing stupid shit you need to lie to the server and set cl_updaterate 70 (even though a server that runs at 66.6666 ticks per second will never be able to send you 70 updates per second) because 1/70 = 0.0142857 so that's the interp TF2 will use even though it's bullshit.[/quote]
The server is stopping you from being an idiot.
If you still want to be an idiot why bother with 14.2? Is that some magic value where the interpolation is only slightly broken but the 0.8ms you gained are more than worth it? Why not break it harder? Why not use updaterate 100 and get that sweet sweet 10 ms interp? You save a whole 5ms compared to working interp, which is almost noticeable on 50 ping and it only breaks interp 1/3 of the time. Or go all the way with updaterate 100000000. Just get rid of that pesky interpolation. Give me the full eye-bleeding jittery extrapolation experience. Ignore the server telling you that anything lower than ratio 1 is monumentally stupid.
Hell, just disable lag compensation alltogether. Play in HARDMODE.
https://www.youtube.com/watch?v=hP9yrLSL-G0
Jesus setsul must be having a bad day hahaha
Jesus setsul must be having a bad day hahaha
Nah, it's just that I literally wrote "don't do that, it's stupid, it's so stupid that most servers will stop you from doing it" and he went and did it anyway and the server stopped him and he didn't follow the instructions I gave him in case that happened to "fix" it.
Nah, it's just that I literally wrote "don't do that, it's stupid, it's so stupid that most servers will stop you from doing it" and he went and did it anyway and the server stopped him and he didn't follow the instructions I gave him in case that happened to "fix" it.
yea bro this shit was experimented with and concluded in 2009 lol
yea bro this shit was experimented with and concluded in 2009 lol
SetsulTF2 always uses the higher value out of ratio/updaterate and flat interp.
Wait is that true? It never hit me like that when people were always saying interp and interp ratio did the same thing.
So are you telling me there's no difference between
cl_interp .0152 + cl_interp_ratio 2
and
cl_interp .0303 + cl_interp_ratio 1
?
so only having cl_interp .0152 and cl_interp_ratio 1 would lower it that amount?
[quote=Setsul]TF2 always uses the higher value out of ratio/updaterate and flat interp.[/quote]
Wait is that true? It never hit me like that when people were always saying interp and interp ratio did the same thing.
So are you telling me there's no difference between
cl_interp .0152 + cl_interp_ratio 2
and
cl_interp .0303 + cl_interp_ratio 1
?
so only having cl_interp .0152 and cl_interp_ratio 1 would lower it that amount?
Yep, try it.
Assuming 66 rates the first two will both result in 0.0303 and the third in 0.0152.
Of course there is the issue of 66 vs 66.66666 vs 67 rates.
Yep, try it.
Assuming 66 rates the first two will both result in 0.0303 and the third in 0.0152.
Of course there is the issue of 66 vs 66.66666 vs 67 rates.