you sir are a champion of the highest order. Friends and I have been waiting for something like this for god knows how long. Can finally use accel again. ++++++++++++

If I set up the accel parameters to exactly what I use in quake and leave my quake settings unchanged, will I have the same level of acceleration or will the quake accel be exaggerated?

Like if I use 0.25 accel in your driver and cl_mouseAccel 0.25 in quake will I get 0.25, or will I get 6.25/something crazy like that?

I understand you say to use the same sensitivity value if you want to replicate settings but is it the same for accel settings.

Sweet. Gonna give it a try.

i wish there were a driver that let me use arbitrary math to do my accel :<

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.

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.

thanks ,this is very useful
dumb question: offset and power are the equivalents of what tf2 commands?

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 can't even get this to work. The driver comes up as unsigned at driver installation no matter what I do.

mmm...I got used to tf2's accel...
I guess I'll try this out.

Thanks mate!

(i just noticed that signatures are disabled now)

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.

I get all of that but if I try to install the driver on my first of 3 HID mice listed in the manager, it works but on the other 2 it fails. The last one failing causes my mouse to stop working so I assume the last one is my actual mouse. Windows just says something like it can't authenticate the driver even though I did sign the sys file and verified that it was signed.

works great
feels a little bit weird but it helps a lot to snipe

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.

I'm trying to get it to work on Windows 8 64bit but I get the error that 'The third-party INF does not contain digital signature information.'

Any help?

edit: I think it's because DSEO doesn't support windows 8. Nevermind, then. :(

I'm getting the same problem as Drew, please post a fix if you come up with a solution.

Grape/Drew, when you go to your mouse device and manually select moufiltr.inf, it's normal for the Windows box to say it's not signed, but it actually is. <- This only matters if what you mean by "like it can't authenticate the driver even though I did sign it".

If you're getting a yellow triangle error icon next to whatever mouse driver you assigned moufiltr.inf to, it's probably because you're not in test mode anymore. I'm assuming you're still in test mode, though. If not, then that's probably the issue.

I am in test mode and the driver is signed, when I try to install the driver it just gives me this http://i.imgur.com/6NtYILm.png and my mouse stops working, same as drew.

I can install a different unsigned mouse driver that I've been using for several months perfectly fine, however.

Try completely uninstalling the changes that you made to the one that isn't working and do the exact installation to another mouse driver. If it works, great. If not, I'm not sure what the issue is and pv will have to step in and help you.

1. Device Manager -> Mouse Driver -> Update -> Let it find updates
2. CMD as Administrator -> enter in: pnputil -d oem9.inf
2. Regedit -> HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Services -> delete moufiltr

^^ So you don't have to watch the video over

I had a different issue. My mouse wouldn't stop responding, nor would I get that error message, but I would get the yellow triangle error icon and the (Code 52) error (which you can check by going to the properties of the mouse driver you installed to).

Pasting the whole file literally crashes the tab on chrome so I uploaded it to mediafire.

http://www.mediafire.com/?x7tva6s7ltgc46p

I'm out of testmode now if that's a problem.

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

and so I take it there's no way for me to use it with windows 8?

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

Just tried this, still doesn't work. I've been in test mode every time I've tried to install the drivers.

Would someone be kind enough to explain what each of the parameters does for someone who's never played quake or used accel in TF2? Everything seems pretty self explanatory except for offset and power.

EDIT: Just saw the post above, nvm, should really read threads in full before posting.

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

what this guy said, I think......yeah.. what this guy said! yeah!

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

Yup realised after I posted.