DPI Wizard

Are you selecting the correct location? The config file and in-game settings are different.

Your calculations should be correct now

Thanks for the link, I see the issue now. Working on fixing it!

They are equally weighted multipliers, you can verify it by converting between the 1x scope: https://www.mouse-sensitivity.com/?share=252a1adccf37b8a09d1ec117ab99fbe7

No, the scope sensitivity is in the calculation, but you have to make sure you set all the sensitivity and multiplier values to what you have in the game (other than multiplier 2, which is the scope sensitivity that will be calculated). Also, you can use the "All" calculation as well, to get all values calculated.

Unsupported until they fix smoothing.

Multiplier 2 is locked because it is the value that is being calculated. When it comes to the scope FOV, you have to do it manually; Change the Config FOV until the Actual FOV matches hipfire in CSGO. 82 will get you pretty close: https://www.mouse-sensitivity.com/?share=e86ce2385883e75c6e0fe5fcc8cde001

Scripts and sensitivity matchers do not work correctly with this game. The only artificial sensitivity input that works is a hardware emulated mouse like an Arduino.

You can use Aim Down Sight Horizontal Sensitivity 26 and just set 1X Sensitivity to 100 instead of 102. This will give you the same result

If you're not using 360 distance for hipfire, you should ideally use the same method as you use for ADS/scopes. Everyone got different preferences though, so nothing is written in stone. Using MDV 0% will keep the tracking speed consistent between the scopes, and this is one of the most preferred methods.

Set the ADS and scope scale to 99.083: https://www.mouse-sensitivity.com/?share=17de5bb30efe2973a47d30d9f48c41bf

No, 1.01 is the same in the calculator and the game.

Correct, using a FOV based conversion will result in a pretty huge difference in 360 distance when the FOV difference is so big. The target for the calculation is 17.0455, so yes this is a limitation due to the lack of decimals. The ADS 360 distance is too long at 17.3077, so for the 1x this is compensated for by increasing the sensitivity to 102. With a proper amount if decimals this wouldn't be an issue.

That's because of a bug in Apex, which the calculator replicates. Instead of using the actual 4:3 FOV 106 is (104.65), the game rounds the value to the nearest whole number (i.e. 105) and uses this for the zoom calculation.

Correct.

The default setup of the ADS and scope conversion is MDV 0%, which is the same as Apex uses by default. That's why you always get 1. If you want to match specific settings you already have, you need to adjust the conversion setup.

It's still the same as it has always been, the value you configure (90) is vertical degrees, the Horizontal FOV shown of the right side is the horizontal 4:3 FOV (106), regardless of your configured aspect ratio. 74 vertical is about 106 horizontal for 16:9.

This will be the same as ADS 1.0 in Apex: https://www.mouse-sensitivity.com/?share=4a4dde87f32399c8660c5301e02b1fb5

See the game notes for instructions on how to disable smoothing. View full update

Added, more ADS/scope coming soon!

Can you share your calculator setup using the purple share button?

Currently unsupported since both frame rate and polling rate affects sensitivity, but let's hope a fix is coming soon!

It's a special option when you select ME3. It's the default selection though, so you don't have to specifically select it.