InBetweenNames

It looks like if you leave the sliders at 50, FOV at 103 (horizontal), and use default 0.02 ADSMouseMultiplierUnit , you actually get correct focal length matching (monitor distance 0). Not sure if that's a coincidence or not. I'm very pleased about the changes.

Thanks for the @! Wow, this is exciting. It's about time we got real options!

Thank you!

My numbers are wrong? Could you elaborate? EDIT: It's 57, not 54, for ACOG. That may have been a typo in my post but I'm sure I corrected it ages ago.

@DPI Wizard The Overwatch mouse sensitivity allows you to go below 1 now in the slider, down to 0.01. So the new range is actually [0.01,100] instead of [1,100] as previously. Could you update the calculator to reflect this? Thank you.

The R6Fix entry is here: R6Fix Anyone who is interested in having this fixed once and for all should upvote that topic.

Argh! Thanks @DPI Wizard for taking the time. I'm going to file a bug on R6Fix to get this sorted out once and for all.

Agreed completely. If I were more nefarious, I would consider making a "user patch" to just automatically scale the sensitivity based on your FOV using the MDV 0 formula, patching the values in memory on the fly. That would be considered cheating though. Honestly, this behaviour should be default.

Indeed -- but I have a method for at least being able to handle 1x and ACOG. The trick is to pick scale values that make the computed XFactorAiming extremely similar. For example, at 70.53 FOV, set your XFA to 0.015509 and set your ADS slider to 54 when you use ACOG, and set it to 93 when you use 1x. You can leave it as 54 for Glaz as the value is pretty close to where it should be. But for the new operator, the zoom is significantly more and so it will need adjustment. My method isn't perfect, because it requires you to mess around with the slider depending if you want to use ACOG or not, but it is a lot better than nothing. I agree, they *really* need to add separate multipliers and sliders for the different scopes. The default scope multipliers just suck regardless of the FOV. I find myself using 1x all the time just so I can at least have consistency.

@DPI Wizard The new update for Siege introduces a new operator, Kali, with a variable zoom scope that is higher in strength than the previous scopes in the game. Could we get an update to the aim calculator to handle these?

@DPI Wizard I had a scheme before that would allow you to just adjust the slider between the different FOVs for your ACOG and 1x sights. Using 0% MDV, it relies on these settings: In all cases: Base FOV: 74 XFactorAiming=0.016143 MouseSensitivityMultiplierUnit=Anything MouseYawSensitivity=1 For 1x scopes: AimDownSightsMouse=90 For ACOG: AimDownSightsMouse=54 These produce similar XFactorAiming values in the calculator (off by only 0.000003, so can be treated as being practically the same). Are you saying that the game engine itself would be capping AimDownSightsMouse to 83 even though it's set to 90? I always noticed something a little off about it, but could never quite tell.

@DPI Wizard I really, wish I knew about that sooner! God, they messed up sensitivities in this game. How are we supposed to match our hipfire and 1x sensitivities then?

@DPI Wizard Well that explains a lot -- and this is taking into account the FOV reduction percentage as well for 1x sights?

@SpeedySteve @DPI Wizard Hold up -- where is that behaviour documented?

Thanks for the quick response! Below is a screenshot of what the configuration is. Using viewspeed_v2 for everything.