People should get one of those shirts if they donate more than a certain amount.

Good point, should always rule out a possible placebo in these cases.

A decent ammount of TF2 settings are stored in the registry so they would most likely persist assuming you reinstalled TF2 using just Steam. Also did you verify that your whole tf2 folder was deleted along with the uninstallation? iirc the [account name]\team fortress 2\ folder isn't deleted along with the GCF files in the uninstallation, so any scripts or what not which could be affecting your sensitivity will persist through multiple installations.

If none of that was the issue then try this:

1. Open up TF2, go to advanced options, and disable the "Sync with Steam Cloud", or whatever it's called, then close the game.
2. Right click TF2 in your Steam library > click properties > go to the updates tab > uncheck "Enable Steam Cloud synchronization for Team Fortress 2" if it's checked > click close
3. Backup your TF2 launch options in a text file if you'd like, then remove them and just put "-autoconfig - console" and hit OK.
4. Open up regedit and go to HKEY_CURRENT_USER\Software\Valve\Source\tf\ and delete the settings key. If you're unsure it's the correct one it will have many DWORDs starting with the name "mat_" and a few starting with "r_"
5. Remember "Team Fortress 2" folder previously mentioned? Back that up by moving it to your desktop for example.
6. Launch TF2, bring up the console, and type "exec config_default", either that or default_config, I forget. Now close your game and remove -autoconfig from the launch options so that just -console remains.
7. Load up TF2 again, bring up console, and type "map itemtest", when it loads change your "fov_desired" to what you usually play at, as well as "sensitivity" and any other custom mouse movement related CVARs you might use. Then just play for a bit and see how your aim is as you're playing on the closest thing to default TF2. If the issue still arises try playing with m_rawinput 1 (if you don't already), and if that doesn't fix it then it might be a Windows problem in which I would have to research further.

EDIT: Also make sure you're not using an exorbitantly high anti aliasing settings (more than 4x) or anisotropic filtering settings (more than 8x) as they introduce input lag at higher settings since iirc they are done after the main image is rendered and the higher the setting the more AA/AF passes need to be done.

Please excuse my ignorance in the matter but what else has changed which would make it difficult to swap out the fonts? They might have different dimensions so their tall values might be different in clientscheme.res as well as their coordinates in hudlayout.res (as well as their respective dropshadows) but other than that it shouldn't be a huge issue.

I mean since Surface is used throughout the HUD then you could just have the new version used in all elements of the new version except the ammo/health counters where the user could just choose which section to uncomment in in the respective .res file (for health/ammo) for the font of their choosing.

Edit: sorry didn't see the previous post.

The plugin might not be signed, requiring it to be loaded with the TF2 launch option -insecure

yes

Before this guide I played engineer on 2fort and now I'm invite YA