tekk's Profile

Account Details
SteamID64	76561198030383904
SteamID3	[U:1:70118176]
SteamID32	STEAM_0:0:35059088
Country	Australia
Signed Up	April 26, 2013
Last Posted	March 4, 2014 at 1:13 AM
Posts	100 (0 per day)

Account Details

SteamID64

76561198030383904

SteamID3

[U:1:70118176]

SteamID32

STEAM_0:0:35059088

Country

Australia

Signed Up

April 26, 2013

Last Posted

March 4, 2014 at 1:13 AM

Posts

100 (0 per day)

Game Settings
In-game Sensitivity	3.14
Windows Sensitivity	6
Raw Input	1
DPI	800
Resolution	1920 x 1080
Refresh Rate	144hz

Game Settings

In-game Sensitivity

3.14

Windows Sensitivity

Raw Input

DPI

800

Resolution

1920 x 1080

Refresh Rate

144hz

Hardware Peripherals
Mouse	Thermaltake Black Gaming Mouse
Keyboard	Thermaltake Challenger
Mousepad	Roccat Taito King Size
Headphones	Thermaltake Shock One
Monitor	BenQ XL2411T

Hardware Peripherals

Mouse

Thermaltake Black Gaming Mouse

Keyboard

Thermaltake Challenger

Mousepad

Roccat Taito King Size

Headphones

Thermaltake Shock One

Monitor

BenQ XL2411T

Setsul#2/#7
You got the right idea, there are just some minor mistakes.

With updaterate/cmdrate 66 and interp_ratio 1 the interp is 0.0152 but you've corrected that in the quote. However with interp_ratio 2 it would be 0.0303 not 0.033 (probably a typo). Using interp 0 and interp_ratio 1/2 is easier anyway.

Choke means that your or the servers rate is too low, not to high. Basically the server has to hold packets back because either the bandwidth you allow or the bandwidth itself allows for each client is not high enough to send the packet immediately. Just set "rate" to 60000 (you can use 100000 to be sure, if you have more than 100kbits upload, otherwise it might increase your ping). If you still get choke it's the server. If you still want to/have to play on that server lower cmdrate and updaterate to 40 and bump up the interp to 0.025 (instead of 0.0152) or 0.05 (instead of 0.0303). You don't have to change the interp if you use interp 0 and interp_ratio 1 or 2.

If you have a good connection and get loss it's the server. If you get loss on every server you should call your ISP, it means your connection is shit.

Your explanation of interpolation is decent but a bit inaccurate at some points. For interp 0.0303/interp_ratio 2 TF2 isn't using the previous packet/snapshot to interpolate it uses the next one. With 0.0152/ratio 1 TF2 uses the snapshot previous to what you see and the next one to interpolate where everyone is in the frames between those two packets. Because you are only one tick behind the server you don't have any snapshots left that are newer than what you see atm if you miss one packet. Now the TF2 uses the two previous packets to extrapolate/predict/guess the player movements. If a guess was wrong the player(s) get(s) warped into the right place as soon as the next packet with the correct information arrives. When you are two ticks behind the server (0.303/ratio 2) and lose one packet you still got another, even newer snapshot. Instead of interpolating between the snapshot before and after your current time it uses the previous and the snapshot two ticks after the current time. Interpolating over two ticks instead of one is slightly less accurate but there won't be any warps.

Now comes the only thing that is just plain wrong.frownySince hitscan is hit detected locally and the hit confirmation is simply sent to the serverThis is just wrong. There's no other way to say that. All the hit registration is done by the server so no one can just sent random hit confirmations and kill everyone from across the map.

The reasons why some people use 0.0303/ratio 2 for hitscan and 0.0152/ratio 1 for porjectiles are the following:
0.0303 for hitscan:
No warps. If you lose just one packet with 0.0152/ratio 1 you might get a prediction are error and therefore a small warp. This little weird looking stutter can throw your aim off.
More accurate hitboxes. Again if you lose one packet and get a prediction error the enemy's model is slightly out of place. Now if you hit that model directly you are not necessarily hitting the hitbox because the hit registration is server side and the server doesn't know that for you the model was in that place. Most of the time you won't miss the shot completely but it's often the difference between hitting 10 bullets in the center for a meatshot or hitting that scout slightly to the side and just hitting 7 bullets and BAM that scout kills you because he survived that shot with 10 HP.

0.0152/ratio 1 for projectiles:
Less delay. Most players find the delay between firing a projectile and the moment it spawns on the server and you can see it far more irritating than the occasional small "stutter" after a lost packet. Prediction erros occur every now and then but the delay is there every single time you fire a projectile so most players want to minimize it. Plus projectiles are prediction-aimed and use a way bigger hitbox so it won't really affect your aim and hitreg.

tl;dr
//netsettings
//change these if necessary
rate 100000
cl_cmdrate 66
cl_updaterate 66
cl_interp_ratio 1

//don