what's the point of testing standin?

esea should have some kind of an insurance deposit for shit like this

at least that way it's a punishment if you fuck a team over

insecure drive to perform better than people who were better than me at TF2 who happened to be shittalking comp tryhards

those images are forcing a lot, even a few without ?s

Are you sure it's in sound/ui and not just ui?

tf_dingaling_wav_override is deprecated, now you install dingalings like you install HUDs

tf/sound/ui/dingaling.wav

does the deathadder really function best at 3500 dpi? Or, should I use 1800? I know 450 is glitchy from above video but I want to know about the second to highest setting, because I've experienced some weird insensitivity on very fast swipes with it.

what kind of shitty netcode do you have to have to make it so people can kill eachother with hitscan
>smnc

viewmodel_fov 84
dsp_water 30

I play with input prediction and lag compensation disabled when lag is fucking up my airshots

circledot with tf2logo in background and black sidebars

the only multiplayer shooter I know that uses TCP only uses it because they didn't know what they were doing when they made it

Minimize input lag
Make sure your mouse isn't shit
then practice like everyone else says
once you get used to it you'll have a good feeling for its spread and know what ranges it's good against what classes at
whatever you do don't practice pistol with the SMG its spread is like a million times tighter than the pistol

doesn't help tf2 because tf2 uses udp, not tcp

yes, you need to make the whole thing taller and move everything inside of it down.

@9 There should be an entry in scripts/hudanimations_tf.txt that has to do with low ammo pulsing, just clear out the text between the first pair of braces in that section and it should go away.

event HudLowAmmoPulse
{
Animate HudWeaponLowAmmoImage Alpha "255" Linear 0.0 0.0
Animate HudWeaponLowAmmoImage Alpha "0" Linear 0.125 0.075

RunEvent HudLowAmmoPulseLoop 0.25
}

to

event HudLowAmmoPulse
{

}

If that somehow breaks TF2, just put the RunEvent line back.