Okay, I've been using this tool for a while, and I've noticed a weird issue. Well, basically your calculator doesn't seem to work for this game specifically. I'm trying to convert from CS:GO to this game. In CS:GO, it takes the length of my mousepad (28.9cm or 11.37795 inches) to turn roughly 350 degrees (I shot one bullet at my starting point, and 1 bullet on my end point, and they are roughly 2 bullet marks away - Glock), your engine says 12.1212 inches to turn 360 degrees. This shows that there is some inaccuracy in your calculator, but that is to be expected - especially considering the sensor might be picking up more distance than from edge to edge on my mousepad.
The thing is, in Siege using the values provided by your calculator, it is anything but accurate. My GameSettings.ini reads as such under [iNPUT]:
InvertAxisY=0
InvertMouseAxisY=0
Rumble=1
AimAssist=1
YawSensitivity=2
PitchSensitivity=1
DeadzoneLeftStick=15
DeadzoneRightStick=15
MouseSensitivity=4
MouseSensitivityMultiplierUnit=0.051836
XFactorAiming=0.020000
ToggleAim=0
ToggleLean=0
ToggleSprint=0
ToggleCrouch=1
ToggleProne=1
ToggleWalk=0
AimDownSights=50
AimDownSightsMouse=56
ControlSchemeIndex=0
ControllerInputDevice=0
I've bolded the values that are relevant. Your settings give a MouseSensitivityMultiplierUnit (MSMU) of .051836 for a Hipfire sensitivity of 4. This already is inaccurate - my sensitivity is much lower, the turning radius is roughly 320 degrees instead of 350 degrees (with the same distance as mentioned above). Not off by much, but enough. The thing is, the ADS calculation is where it gets really off. Your calculator says that an ADS sensitivity around 55/56 should yield the same MSMU as a Hipfire sensitivity of 4 (with my settings - 500 DPI, 90 FOV, 1920x1080). Using an ADS of 56, the turning radius is barely 200 degrees for a whole mousepad sweep. (Also, the faster I go, the less distance the crosshair ends up covering, strangely - is this an FPS issue?)
I have to turn the ADS sensitivity up to 85 in order for it to roughly match - but again, even aiming at the exact same spot at the beginning provides results that vary by as much as 5 degrees in either direction (at the end point). I chalk this up to my mouse sensor picking up signals from the desk as it travels off the pad sometimes but not others. But it also doesn't make sense that speed would negatively affect the distance traveled, specifically in ADS.
Any reason why any of this would be happening to me? Here's an imgur gallery of my CS:GO test of sensitivity distance, and R6 tests with and without ADS (with the settings specified above - I am turning clockwise/to the right, as I said the distance traveled by the mouse sensor is roughly 11.3780 inches): http://imgur.com/a/SZOiW
