fps lag = low fps in general
fps drop = hitches, stutter, etc

lag does not exclusively refer to latency even in the networking sense. all it means is that in general something is behind what it should be in some way, which low fps *does* cause. if you're adamant about it then you're just a bigot (lit.).

/ot

i'm literally autistic

no, seriously

restart your computer. make sure your usb connection isn't unplugging/replugging. if all else fails uninstall the DA drivers and deal with having plug-and-play ones forever instead of just reinstalling. if that doesn't help you probably have a defective mouse.

your mom is bad form xd

tf/cfg still works but there's an ever so slight chance that an update which changes a file you have in there will overwrite what you have in there, so you should back stuff up if you decide to put it there.

Can you run them with wine? The normal vpk .exes and vtfedit

A "compare to/diff with vanilla file" functionality would be very useful.

No. The only ways to avoid vsync on win7 with a modern AMD card are to run TF2 in proper fullscreen mode or to disable aero.

gib 768x480 & 600x480 pls (16:10 and 5:4)

there is absolutely no reason to treat this conversation like a bloody crusade against mice with imperfect sensors is taking place. there is nothing wrong with having or using a mouse with an imperfect sensor but there's everything wrong with pretending that it's not inherently worse than an identical mouse with a perfect sensor would be.

-fragging facts when nobody's being rude or snide, such a smart thing to do

Also: You can't adjust for hardware accel in software because it's slightly different for each individual sensor made and difficult to model mathematically, so whatever function you have you'll end up with more or less of an S shape for the movement -> response curve. HW accel is a flaw to a very extreme vast majority of users for this and many other reasons.

stop arguing about extremely particular things oh gosh

STOP BUMPING THIS SHIT JESUS CHRIST IT'S DEAD STOP REMINDING US ABOUT IT

#18:
Nothing perfect, but there's some general stuff I learned from people studying quake and tf aimbots (humanized ones)

- Inhuman consistency (keeps doing the same things with the same level of success, no overall variation)
[that is, if they keep landing the same kinds of twitches and twitch the same way all the time. if they never have highlights or bad skill moments. if they always do really well right when they're gonna get fucked over. just examples of the underlying idea. this is an extremely specific underlying concept and I just want to make sure people know I'm not saying "they always do well".]
- *Extremely* high accuracy in general with really really really really bad movement
- Perfect tracking
- Crosshair following extremely subtle movements on the target all the time which a legitimate player wouldn't consistently be able to focus on
- Constant sub-100ms reflexes (really hard to tell because of how lag compensation works in spectating. be wary of isolated instances because real people can have special prediction.)

obviously anything that can identify a hack w/ visual testing is iffy, and different things are worse or better at telling and depending on the person doing the test different methods can be essentially subjective.

When someone is using a naive/simple aimbot though it's just fucking blatant.