I see your post is dated 2014. I made a shittalk.cfg in 2009. I should be used to the wider TF2 scene taking things I created and using them without credit.

http://ozfortress.com/showthread.php?p=568245#post568245
http://drok-radnik.com/junk/povo_tf2cfg_21-12-09.rar - contains shittalk.cfg (which relies on a wait checking mechanism in aliases.cfg)

The alias naming convention you chose to use is highly similar to mine. Essentially find->replace 'smiley' with 'trashcan'.
The actual output and script logic itself is quite different and I'm not suggesting that it isn't original work. Enjoy your donations.

Also for reference, the inbuilt 'custom' crosshairs are located at vgui/crosshairs/, i assume you can reference these in the weapon scripts if you really enjoy them.
eg: "file" "vgui/crosshairs/crosshair7"
They are all 64x64, and don't forget theres a 'default.vtf' in that folder which is a slight variation on the inbuilt ( • ) crosshair

4 boobs nice!

I'm guessing a size is set incorrectly somewhere. Set the width and height in the weapon script to the size of the crosshair in the source file. Use cl_crosshair_scale to resize it in-game.

Made a big vtf (2048x64) with all the current Quake Live crosshairs (1-29). They are in 64x64 blocks, including crosshairs 20-29 which originated in Q3 but were added to QL officially at some point (I have preserved their original dimensions of 32x32 but centred them in a 64x64 block)

http://drok-radnik.com/junk/ql_xhairs_tf2.zip
http://drok-radnik.com/junk/ql_xhairs_preview.png

edit: added preview image
edit2: fixed weird shit on edges at high crosshairscale values, added ql_xhairs_point.vtf which you can use if you don't want them to be smooth

Really Fucking Cool!

I just cut it with a sharp flat blade and then used a lighter on the edge to singe off any stray strands and fuse the rubber to the cloth a little. I've only had it for a week and its been fine so far. I face the cut side furthest away from me so only the mouse cable touches it. Maybe it will turn to shit in a few months who knows!

I've owned a couple of these pcgamingrace pads, they are quite good for the price. I recently got the 3XL version and ended up cutting it in half to make two 600x600mm pads (pic).

Update

I've been working on an alternative method of implementing good mouse accel at the driver stage that doesn't require test mode or paying a lot of money for an EV code signing certificate. I discovered a driver/library called Interception which enables such a thing to happen.

Interception installs 2 upper filter drivers (keyboard.sys and mouse.sys, fully signed) for kbdclass and mouclass devices, which allows user-mode applications (which have no signing requirement) to manipulate keyboard/mouse events at the driver level. I wrote a very simple console application which interfaces with the interception mouse filter driver and applies the quake live accel algorithm.

Kovaak (author of the amazing GUI for my previous kernel mode filter driver) has updated his GUI to support this new method. He has also started up a blog about mouse acceleration for gaming, which includes information and downloads for accel driver related things. Here's a link to this new /!\ TEST /!\ version.

http://mouseaccel.blogspot.com.au/2015/12/new-method-for-mouse-acceleration.html

Kovaak has some concerns about this interception library triggering anti-cheat scanners. There is certainly no guarantee that anything is safe from triggering VAC, but logically this new method is significantly less 'dodgy' than the previous driver which to my knowledge never triggered any anti-cheat. Use at your own risk. Also the source is provided so check it out if you want.

stay safe poverty ghost

taken to meme school

Thanks! I really like this HUD, glad somebody is maintaining it.

Well that sucks. Maybe Valve can put a working version of accel into their game.

edit: maybe its possible to implement accel via rinput?

I have seen reports on esr and overclock.net that the EC1-A/EC2-A have about half the click latency of the older Zowie mice (eg: FK1).

I didn't really 'write' a driver. I took the moufiltr example code which has all the important stuff already written. I just added some code that reads some registry values and manipulates each packet of mouse data that has movement information in it. The source for the previous version is up on the site.

I should mention that I'm not a legit programmer and don't really know much about drivers or C or anything like that. I sorta fumbled my way through using the internet and bouncing some ideas off other ppl in irc.

The QL Accel filter driver I made is based on some example code from MSDN (moufiltr). There is a similar piece of example code for keyboards called kbdfiltr (located here). I'm not sure if theres anything I can offer regarding specifics from this point on. Keep in mind if you are using 64-bit, you will need to enable test signing, create/import your own certificate and self-sign your driver or it will not load.