cl_interp_ratio 1
cl_interp 0
cl_cmdrate 66
cl_updaterate 66

just put that in your autoexec

k thanks

thats wrong

so what interp is the best one?

0 or .0152 for projectiles .033 for hitscan

explain

hitscan: cl_interp_ratio 2;cl_interp 0.0303
projectile: cl_interp_ratio 1;cl_interp 0

further reading: https://www.teamfortress.tv/52942/

The thread you linked recommends putting cl_interp on 0 so not sure why you are going against your own source. Also, I'd recommend using cl_interp_ratio 1 even on hitscan if you have a decent connection that doesn't drop packets. Higher interp ratios mitigates the effects of packet loss, but if there are no packet losses to mitigate it's not really necessary.

that link is just a bunch of pointless jargon, I've never seen a single bit of proof that changing your interp ratio between 1 and 2 actually does anything other than make projectiles appear slightly later, which if anything you don't want

trust me I wondered the same thing years ago and to this day have seen not one bit of evidence from a player that their hit detection was influenced in the slightest by changing between 1 and 2

however, if you want an interp command that actually fucks with hit detection, hit up the thread stark made a while ago about making your interp ratio 1000000000 for sniper and forcing your "lerp" to appear as 0. now that has some interesting results

anyone got a link? sounds like a fun read

https://www.teamfortress.tv/51880/rates-for-making-sniper-easier

personally i use .0152 for everything but sniper, for sniper i use .033

So interp is a personal preference thing much like huds. There are some interp settings that are objectively better than others depending on your pc and connection or could be another factor I'm not familiar or informed with.

cl_cmdrate / cl_updaterate: should usually always be at 66 for a stable packets to the server. You can go to 100 if you wish but that's recommend if you have a god tier connection.

cl_interp_ratio: should be either 1 or 2 (I recommend 1 for projectiles and 2 for hitscan) on the rare occasion 3 for unforeseen consequences

cl_interp: If you put this to 0 that will make it go to the lowest possible interp which can cause some registration issues when you are in a battle. So for projectile 0.01515151 / hitscan 0.0303030303

cl_smooth: Should always be 1
cl_smoothtime: should either be 0.01 (or 0.015)

It's just dependent on what you are capable of handling for your system and game.

If you are wondering my opinion on what you could use I'll put.

rate 100000
cl_updaterate 66
cl_cmdrate 66
cl_interp 0.03
cl_interp_ratio 2
cl_smooth 1
cl_smoothtime 0.1

this thread again huh

Don't spread misinformation. Setting these above the server tickrate (66.666 ticks/second) will not give you any benefits as that is the limit on how many packets can be received/sent. On the other hand, setting these higher than the tickrate can fuck up your other network settings.

I'd recommend using mastercomfig, but if you advocate against using it just for the interp settings, you might as well just take a peak at the presets, but they might not seem as clear as water to you.

If anything, a quick reading on the 0.0303 and 0.0152 values.

so what do I use on hitscan and projectile?

i honestly dont understand where this sort of thing comes from. does everyone just make up random bullshit lol

negligible or no packet loss:
cl_interp 0; cl_interp_ratio 1

non-negligible packet loss:
cl_interp 0; cl_interp_ratio 2