For public entertainment powered by sdogg2m.

Why not?
And btw his aim is the same in the fragvid and in the demo, the demo just shows that he misses loads and that he focuses whoever might jump (solly/demo).

Yes, he goes from normal tracking over tracking with a bit of jittering to flicking and wobbling around.

He always seems to go for the pocket instead of the medic in the demo. Nobody knows why.

After watching the demo it seems like he is just flicking A LOT.
It seems to be like 50% flicking in the last moment, 30% bad tracking and 20% not moving the crosshair and then clicking in the right or wrong (most of the time wrong) moment.
His aim is not really good, his tracking is good sometimes and then again just plain horrible. He seems to be really inconsistent.

Unsteady aim, flicks a lot, switches from tracking to flick aim all the time, most of the time bad tracking. For me this just looks like he could have good aim and is just incredibly inconsistent. He starts flicking as soon as his tracking is a bit off. This combined with situations where he hasn't started flicking although his tracking is to bad to hit anything at that moment makes him miss more than half of his shots.

tl;dr
Weird but legit aim, inconsistent, misses >50%
hits some lucky flickshots (misses most of them)

Yes and he did not trade any of his items before the ban. So he either doesn't care about items or didn't want to get banned.

Assuming no one else gets banned for using OpenPlugin there are two options left:
1.a VAC false-positive
2.moose used something that VAC considers a cheat.

So let's wait and see, if there are more bans, neither OpenPlugin nor a VAC getting false-positives would only get one person banned.

Valve deletes all tf2 items, which weren't bought in the shop, from VAC'd accounts.
If you could still move all of your items to a new and pretty much free (f2p + a few cent for premium) a VAC ban would be kinda pointless.

Oh, just to clarify this: If the VAC team adds a new cheat signature everyone using this cheat gets banned. So unless all OpenPlugin users get VAC'd in the next weeks, it wasn't the OpenPlugin that everyone else uses that got him banned.

And of course Valve thinks manually banning ONE random UGC admin (who used OpenPLugin once) without telling why will make everyone stop using OpenPlugin.

inb4 -frags

My keyboard is not insufficient, ', ´ and ü are just next to each other.
I've corrected this mistake, so it doesn't make your eyes bleed.

Your keyboards are insufficient, it's called über.

You should avoid taking those clocks with you when travelling at velocities close to the speed of light.

#25
Yellow means that the server tickrate is less than your interpolation time. This will happen if your cl_interp_ratio < 1 (you shouldn´t use this at all) or if the server uses less than tickrate 66 (->bad server).
Orange is just a warning that you are only using less than 2 packets for interpolation (cl_interp_ratio < 2) -> interpolation issues in case of packet loss.

DO NOT USE cl_interp_ratio 1 (<2, orange) FOR HITSCAN IF YOU GET ANY PACKET LOSS.
DO NOT USE cl_interp_ratio 0.
DO NOT COMPLAIN ABOUT BAD HITREG ON BAD SERVERS (yellow).

cl_updaterate should be set to the same value as cl_cmdrate. Set both to 66, unless you get choke>0, then use 40 or even lower (depending on what the server allows).
It´s way easier to use cl_interp_ratio instead of cl_interp, so just use cl_interp 0.
cl_interp_ratio 2 should give you the best hitreg with "normal" ping.
Some people like to use cl_interp_ratio 1 for projectiles because it minimizes the delay before you see the rocket and for super low ping+stable connection (LAN or living next to the server).

tl;dr
cl_updaterate 66
cl_cmdrate 66
cl_interp 0
cl_interp_ratio 2
you can use cl_interp_ratio 1 for projectiles or ping <40

basically copy chris´ configs
http://fakkelbrigade.eu/chris/configs/

No, i meant the razer drivers. Rawinput bypasses all windows settings anyway.

http://www.funender.com/quake/mouse/index.html#input
m_rawinput 1 uses raw input (aka WM_INPUT) and therefore removes the issue of negative accel.
The stuff about the polling rate is true.

kirby you could try measuring your in/360. Even if it doesn´t feel like 2.9 in/360 it might be correct.
Probably the easiest way to get it pretty exact:
-place the mouse on a sheet of paper
-mark where the right side of the mouse is
-do a 360 to the left
-mark again where the right side of the mouse is
-measure the distance between the two lines

Assuming you use a Deathadder 3.5G you could try the following:
-update the firmware (some versions have a jittering issue)
-set the sens to 10/10 in the drivers (interpolation is not set to 10/10)
-use 1800 dpi, apparently it´s the native dpi setting that works better than 3500 dpi

m_rawinput 1 bypasses the windows mouse acceleration by using the "raw input" form the mouse drivers.
If you´ve checked all acceleration cvars in TF2 there is still the possibility of buil-in prediction/accel of your mouse.
Some mice also have weird issues when used at other than their native dpi settings (usually 400 or 450 and/or a multiple of that).

tl;dr Tell us what mouse you use, it´s probably a hardware/driver issue.

Then just keep using your script if the exec doesn´t cause lag.
German: Dann gehts nur wenig einfacher, lohnt sich meiner Meinung nach nicht das umzuschreiben, wenn es funktioniert.