Good to hear you managed to get it working somehow. The test mode/dseo combo is supposed to do the same as that startup option but I guess it isn't. I also updated this thing about a week ago to beta3.

http://www.youtube.com/watch?v=wzv8r4UTF9A

This is an unsigned driver from an untrusted third party. Windows has to boot into test mode and store an untrusted certificate in the trusted root certificate store. But apart from that it's not really outside the scope of what a normal mouse driver does.

Also hey I did a little bugfix/feature update recently. Unfortunately it is still just as difficult to install for some people. If you have a Zowie mouse, I have some troubleshooting instructions that were donated by a Zowie mouse user.

It will depend on your TF2 fps, as source engine acceleration is apparently fps dependent. Injx describes the relationship between the two games here http://www.esreality.com/index.php?a=post&id=1903728#pid1903738

Sorry if it doesn't work on your machine, I am having trouble tracking down these issues because I cannot reproduce them on my system.

The driver compiles with no warnings through the microsoft driver rules code analysis pass, it shows no problems in microsoft's driver verifier utility and passes the static driver verifier with the strictest rule set. The whole thing is based on an example driver from microsoft themselves.

+frag if it works on your system
-frag if it doesnt

you could also read the web site and the readme, unless you find those descriptions too vague

Not unless there is a way around driver signing. The drive code itself, however, should be totally windows 8 compliant (not that this helps).

anyone with a code 52 (eg: grape), launch msconfig and select normal startup. a few people have had issues with installing it when some services are not enabled

edit: and yes, you need to stay in test mode or it will stop working. this is due to me not paying $500 a year to sign drivers with a trusted certificate

Add me on steam or get me on IRC, i'll see if I can figure out whats going on, as other people might run into this problem too. You may also need to pastebin me some stuff from C:\Windows\inf\setupapi.dev.log.

The installation video is out of date with the most recent version of the driver. I made a new video about 10 minutes ago which can be seen at http://www.youtube.com/watch?v=ch2J6uYyjvs. This is based on a fresh install of Windows 7 x64 (no service packs). I have done this installation process successfully dozens of times over the last month and I am not sure where things are going wrong for you. Any additional information you can provide about the installation failing would be very helpful.

All I can suggest is to verify you are in test mode, and check that the .sys file is actually getting signed by DSEO by checking the digital signatures tab in the properties dialog for it.

Power would be equivalent to m_customaccel_exponent (with m_customaccel set to 1 or 2), except with 1 added to it (for some reason in quake lives accel scheme, they subtract 1 from power before using it as an exponent). There is no offset in tf2, so setting it to 0 would be equivalent.

I'll probably throw the source up at some point soon, otherwise feel free to do what I did and get the moufiltr driver example code off msdn and hack away at it yourself.

You should turn acceleration off in quake live if you are using the driver for acceleration. Just leave your sensitivity and set cl_mouseaccel to 0.

Check out this new version that doesn't require test mode
http://mouseaccel.blogspot.com.au/2015/12/new-method-for-mouse-acceleration.html

Old OP:
I made a mouse driver for windows that gives you the same parameters as Quake Live's acceleration system. This means you can have fps independent acceleration in TF2 (and any other game too i guess).

http://accel.drok-radnik.com/

http://drok-radnik.com/junk/qlmoufiltr_settings2.jpg

64bit users will have to go through the process of self signing the driver using test mode and dseo (similar to the hidusbf poll rate patch process). It should only work on Vista SP1 and up because it was developed using WDK 8.0.

I have been using it in testing over the past month, and had a few people testing it over the past week or 2. I want to widen the test audience a little bit, so here you go tftv. Any feedback can be directed at my various contact methods listed on the site/readme, or posted here.

for some reason valve decided that values that arent -0.022 and 0.022 for m_pitch are cheating. whats up with that anyway