Friday, December 18, 2015

Reflex mouse accel configuration wizard

Confused by Reflex's mouse acceleration options? Completely understandable - there's a lot going on with all of the variables. Even worse - acceleration settings deeply depend on your mouse's DPI, so you can't just copy/paste someone else's settings and hope they work for you!

So, I wrote this little tool to give you a starting point. First, enter your mouse DPI and reflex game sensitivity (aka m_speed in console). Then go to into Reflex's "Options" menu, then "Mouse Settings" and copy the outputs this tool spat out (you'll need to check the box for "Enable Advanced Options").

DPI
Reflex Sensitivity

Acceleration
Sensitivity Cap
Offset
Power
Post-Scale X
Post-Scale Y
Angle

Now that you've copied those settings into the menu, before you go in game do some quick wrist flicks and see if the little white circle can make it to the flat part of the curve at the top. Hopefully it can (and hopefully it doesn't reach it with very slow mouse movements). If not, tweak the acceleration value up or down until you can make it hit the flat part.

Next, go in game and see how it feels. It might feel like it's terribly high sensitivity. If so, change both of the post-scale settings to something like 0.6. If it's still too high, change it to 0.5 or something lower. Basically, tweak those values according to your preference and try to leave the other values alone. The "x" value is for horizontal movement, and the "y" value is for vertical. I have come to appreciate higher vertical sensitivity (I have 0.31 X and 0.5 Y) for easier rocket jumps.

If you end up liking the in game mouse acceleration options, keep in mind that povohat wrote an awesome driver that lets you have the same feeling in Windows and any other game. And this tool will let you copy your Reflex settings directly to the driver for the same acceleration curve and feeling.

Tuesday, December 15, 2015

Copying your accel settings between the driver and games.

Are you using mouse acceleration settings in Reflex or QL and want to get the same feeling in the other game or driver? Do you want to take your driver settings and use them in a game where the computer doesn't have the driver installed? I can help (if QL is involved, I'm assuming cl_mouseaccelstyle 1). First, here's a table of the equivalent options/commands between the driver, Quake Live, and Reflex:

DriverQuake LiveReflex
Sensitivitysensitivitym_speed
Accelerationcl_mouseaccelm_advanced_acceleration
Sensitivity Capcl_mousesenscapm_advanced_sensitivity_cap
Offsetcl_mouseacceloffsetm_advanced_offset
Powercl_mouseaccelpowerm_advanced_power
Post-Scale Xm_yawm_advanced_postscale_x
Post-Scale Ym_pitchm_advanced_postscale_y


Use this calculator if you want to convert from Quake Live to Reflex or the driver:

SettingDriverQuake LiveReflex
Sensitivity
Acceleration
Sens Cap
Offset
Power
Post-Scale X
Post-Scale Y

Note: Once you've set post-scale values to work as m_yaw and m_pitch values, you will want to set m_yaw back to 0.022 and m_pitch back to 0.022 or -0.022 (depending on if you use inverted mouse).


Use this calculator if you want to convert from Reflex to Quake Live or the driver:

SettingDriverQuake LiveReflex
Sensitivity
Acceleration
Sens Cap
Offset
Power
Post-Scale X
Post-Scale Y


Use this calculator if you want to convert your driver settings to a specific game:

SettingDriverQuake LiveReflex
Sensitivity
Acceleration
Sens Cap
Offset
Power
Post-Scale X
Post-Scale Y


There are multiple ways to perform these conversions. If you want to do any math yourself, keep in mind that sensitivity is multiplied in before the acceleration, offset, and sensitivity cap calculations are performed, whereas post-scale values are multiplied in after.

Friday, December 4, 2015

New method for the mouse acceleration!

Good news, everyone!  Povohat found another method to perform mouse acceleration!

Using the interception library/driver, povohat wrote a program that reads in mouse inputs and modifies them using the same variables and math as his other driver.  Basically, this means we now have a mouse acceleration driver that no longer requires test mode.

We've been testing the acceleration program/implementation for a few weeks now, but I only got around to adapting the GUI for it yesterday.  I've been passing out builds to people looking for any issues, and so far it seems good.  Here is the latest test build.  If you find anything wrong, let me know!
(01/03/16 fixes: Added support for 2000hz mice in graphing, fixed crash that happened during Windows startup, and tweaked timing of starting new instance of interaccel.exe when using global hotkeys (to avoid short duration of all accel being off). Thanks nGolf and The Man for the troubleshooting!)
(12/19/15 bug fix: opening profiles no longer makes the GUI become useless. Thanks nGolf for the troubleshooting!)

Installation instructions are contained in the readme.txt.  The only hiccups we've noted so far are when the driver doesn't install properly.  Some antivirus products seem to sandbox the download and prevents it from installing, so keep an eye out for error messages.  Notable changes to the GUI include:
  • Added tooltips for all numeric inputs.
  • Added hyperlinks to this blog and www.mouse-sensitivity.com.
  • Added customization wizard to help newcomers have a starting point. (Calculates accel and post-scale values based on your DPI, sets sens-cap to 2).
Ewh from esreality was kind enough to test the input lag of this method of acceleration versus not having it installed.  The raw data is here, and we were happy to discover that the interception driver doesn't add any input lag!  His methodology for testing is the same as this post on esreality.

Next steps to take are: further testing to verify that the GUI isn't broken horribly, get feedback from people on how the wizard settings feel (they aren't too far off from what I'm using, just that they scale to your DPI), and contact anticheat vendors to make sure that the intercept library isn't on a blacklist of sorts for them.  The last thing I want is to have anyone get banned for using our mouse accel implementation, but it seems unlikely that it would happen.

Note regarding anticheat:  It has been over a year since we put this out, and many people have been using it on many games and anticheat services.  None have detected any cheats related to the interception driver (nor should they).  There was a DM on a forum in Feb 2015 of an ESEA admin suggesting to not use this driver, but I know multiple people who have been using the driver on ESEA for multiple months without issues.  Absolutely no problems have been reported with Blizzard's Warden, VAC, Punkbuster, Fairfight, or anything else.

Any and all feedback is very welcome!