Frequently Asked Questions:
Q: Everyone tells me mouse accel is bad, why should I believe you?
A: Because every other form of mouse accel out there IS bad, and most people aren't familiar with linear acceleration with a sensitivity cap. See this post for my take on other types of accel versus this driver. As for why you should believe me, I guess that's up to you. I've mentioned elsewhere that more pro players in Quake3/QuakeLive use acceleration than not. They have among the best aim in the world, and it clearly works for them. The driver talked about in this blog does the same thing as the acceleration options from those games, and a number of those Quake players (including ClampOK and Noctis) have made the switch to this driver so that they can be at home in other games too.
Q: Does the driver work with direct input? Raw input?
A: Yes, and yes. The only games that I've had issues with were Farcry 3 and Farcry: Blood Dragon. They have some silly settings that clip mouse input when it is too high (effectively a built in negative accel). Fortunately, there's a fix for that issue.
Q: What's the deal with signed/unsigned drivers? Why do I have to jump through so many hoops to install your driver?
A: This discussion is no longer relevant. The current version of the driver doesn't need to be signed (it uses the interception library, which isn't kernel-level). The old response to this question is as follows:
Every computer hardware manufacturer out there makes drivers that allows their devices to communicate with computers. Drivers are tested by the software engineers in Windows Test mode, and once they have a working product, they get them signed.
Microsoft explicitly doesn't allow unsigned kernel-level drivers to run on machines under normal circumstances since these drivers have more permission than a typical application/exe. When malware finds a way around this protection, it's a bad thing. That said, povohat's driver (and my GUI) have the source code included in the zip files. Feel free to audit it and compile it yourself - we have nothing to hide.
In order to get a driver signed, Microsoft has a list of certificate authorities (CAs) that they trust, and companies who make drivers will purchase a signing certificate from a CA. Typically it costs a few hundred dollars to have a signing certificate, and it lasts for one year. Luckily, once you sign a version of a driver, it stays signed even if your signing certificate expires after the first year.
Simply put, we haven't coughed up the money to get a signing certificate. See also: "When will the driver be signed?"
Q: Does the driver work play nice with anticheat?
A: For the interception driver - Yes, but argh.
To date, (6/16/16 as of writing), not a single anticheat vendor has responded to my attempts to contact them. I've addressed VAC, Punkbuster, Fairfight, Blizzard/Warden, and ESEA in various emails, forum posts, and "contact us" type things. Also to date, not a single person has been kicked, banned, or harassed for using this driver under any of these anticheat vendors. There was one instance of an ESEA employee suggesting that you shouldn't use this driver, as it could be used to cheat (wtf?), but he only responded to someone on a forum's direct message, and didn't speak to me.
If you are using the old driver, the requirement of Windows Test mode will block you from using ESEA anticheat.
Q: Would I be able to use this on LAN?
A: Depends on whether the tournament organizers will help you get the driver installed. Since you need administrator privileges to install it, you'd definitely need to coordinate it with them. When I was planning on attending Quakecon 2016, I contacted a tournament organizer, and they were fully on-board with having it installed on all tournament machines. (I ended up deciding to not go though)
Got any more questions? Let me know in the comments, and I'll add to this post!