Sunday, November 6, 2016

Troubleshooting the Interception Driver installation

So, you are here because you've installed the driver and followed the directions, but for some reason your settings in the GUI don't seem to take effect.  Hopefully this can help.

This is caused when the dependencies didn't install correctly. If you run interaccel.exe directly, does it immediately open and close? If it's working right, it should stay open and look something like this:

If it stays open, it's actually working correctly, and you may not have changed any settings that affect anything (sensitivity is just a scalar for coming from QuakeLive - it doesn't affect anything you'd feel without acceleration turned on.  Try changing the post-scale numbers around instead).

So, if interaccel.exe closed immediately, you will want to make sure that you have the correct MS Visual C++ Redistributable installed, and then after that it's all about making sure the driver_install.bat actually ran correctly. There are a few things that can block it from working:

  1. Sometimes Windows isn't actually running it as admin from the batch file. You can try to run a command prompt as admin by typing "cmd" in the start search bar and right clicking the program then running it as admin.  From there, use the "cd" command to change to the directory with driver_install.bat, and run it directly like that.
  2. Some antivirus products have been known to sandbox the installer, which results in the installer thinking it worked correctly, but it actually didn't get to write the files to the Windows directory. Turn off AV for a minute, run the installer, and turn AV back on.
  3. And sometimes, Windows just gets into a really weird state where it doesn't let the installer do its thing. A simple reboot and try again has fixed it way too many times.
  4. In the worst case scenario, you could try installing it from safe mode.  One user reported that got it to properly install.
And don't forget to reboot once the installer runs.


  1. is broken,can u provide a new link please?

    1. is the current link for downloading the latest version of this driver. used to just link directly to that post (and provide a historical link to the old page with the non-interception version).

  2. Hi,
    Didn't find a guest book so I'm just starting away here:

    First of, very great of you to tackle mouse accel in FPS. I use and tweak accel settings frequently.
    I have a question regarding the Offset setting tho: If I choose higher offset settings it seems to not act as the graph shows me it should be acting. There should be no acceleration until the offset max is hit and then start accelerating from there as though the current mouse speed were 0, right?
    It feels to me, and I'm fairly certain I'm not imagining things, that the offset is appied however acceleration doesn't start at 0 after the offset but at the corresponding accel value it would apply had there been no offset set at all.
    Could this be an issue with how I set the while thing up?

    I hope I got my problem across,
    Greets from Germany,
    leagman1, a random CS:GO player

    1. I think I understand the problem you are stating, but there shouldn't be a significant difference between the graph and the program that actually performs the accel. I started from the algorithm in the accel program's source and dumbed it down from 2 dimensions to 1 dimension, got rid of angle related stuff, then just did an almost line-by-line copy converting from one language to the other. It's very much the same math.

      My suspicion is that since you might have to be moving the mouse pretty fast to get past the offset, a small bump in sensitivity just results in a surprising increase in sensitivity. I've never really liked using offset, personally...

      You could also try closing the GUI entirely (shutting off accel), edit settings.txt so that fancyoutput=1, then run interaccel.exe directly. In that mode, it will show you every frame of mouse input what the input read was and what it sent out as a modified mouse movement, along with an effective sensitivity multiplier. At the appropriate speeds, it should increase as the graph shows it would. Note that interGUI.exe stomps on that setting and forces it to 0 since it has the potential to cause input lag.

      Hope that helps!

    2. Looks like your suspicion is right. Thanks for the quick help!