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.

@DPI Wizard The calculator seems to be working fine for all soldier aims, but it seems to have problems with vehicle aims. In particular, very low sensitivities (81cm/360 at default zoom of 74 FOV, 16:9 aspect ratio), the vehicle aims actually cause the motion to go in the opposite direction as intended. For example, attempting to rotate a turret left makes it go right, and attempting to look up makes aims downwards. I noticed that at these low sensitivities, the soldier aim itself is negative. Inverting it isn't enough to fix the problem unfortunately. I have tried with both USA on and off, and Uniform Vehicle Aiming on and off as well. For now, I'm just trying to approximate what I want manually. Any ideas of what could be going on here? Thanks!

@DPI Wizard Just wanted to let you know that the limits to the sensitivity values in the menu do not apply to the config file. I am able to go well below 0.1 sensitivity for all settings listed by modifying them in the config file only. The menu still lists them as 0.1, but the config file appears unaltered, even after changing some other unrelated settings.

@DPI Wizard @Skwuruhl I figured out what the vFOV percentage reduction is for Glaz's scope! It's 30% of your vFOV. ACOG, as mentioned before by @Skwuruhl, is 35%. Now of course for reasons already discussed, this means different default FOV values will produce different zoom levels in each scope. I'm assuming that the mouse sensitivity multiplier for Glaz's scope is also 30%, since it seems to be 35% for ACOG (same as the vFOV percentage). A quick (but not thorough) test seems to agree. Using the ACOG setting for viewspeed_v2 to match with hipfire with Glaz's scope makes it feel just a tad too slow, in case this might be good to know. With this in mind, could we update the calculator to include Glaz's scope? Also, I have more findings that show how to exactly align your ACOG, 1x, and hipfire sensitivities using viewspeed_v2. It has to do with finding slider values that allow the calculator to produce very close XFactorAiming values. I have a method which is able to do this for any FOV given, and as proof, I encourage posters to try the following with an FOV of 74: Set XFactorAiming=0.015205 MouseSensitivityMultiplierUnit can be anything you want MouseSensitivity can also be anything you want (mine is set to 1, and i do everything in the MouseSensitivityMultiplierUnit) Set your DefaultFOV to 74 and do not change it! Now, in game: Set your ADS slider to 100 if you are using a 1x sight (so most defense operators), and 70 if you will be using ACOG. No, you can't exactly align both at the same time, but the slider method allows you to at least adjust at the start of the round. The above method can be adapted readily to any FOV you choose, but you won't be using the same slider values or XFactorAiming value. It must be computed specifically for the DefaultFOV you are using. The above values are ONLY for a DefaultFOV of 74. I will be able to extend this method to include Glaz's scope too once added to the calculator. This makes aiming much, much easier in Siege! So, what do you say @DPI Wizard? Do you think you could add Glaz in for me?

@DPI Wizard, do you think you could add the Glaz scope setting?

For reference, I took these screenshots with ACOG and Glaz's scope respectively.

Love the calculator for Siege -- it works great. Question: any chance we could get a Glaz scope setting? The zoom level of his scope is not the same as it is for ACOG. It is slightly more zoomed in. Thanks!