DPI Wizard

You must set the FOV to what you use, but be sure to select the correct FOV Type and check the output for the correct Config FOV for the config file. So if you for instance want the same FOV as in say Overwatch, select Hdeg Res, enter 103 and see the output. It will say Config FOV: <Attr name="FieldOfView" value="70.53"/> So set this in the file.

Config file since it supports more decimals.

In-game uses Hdeg 16:9 FOV while config file uses vertical degrees. So if you use the same numerical value without changing FOV Type you will get different results

It can, but it uses the ADS conversion setup and not the scope setup.

Just ignore the R6 settings for the calculation. The ADS in Overwatch is much more zoomed than in R6, on par with a scope.

Overwatch should work I think? Destiny 2 has a really limited range on the ADS sensitivity, MDH 0% will be too low and 360 distance is too high in your case. The default in Destiny 2 (ADS modifier 1) is MDH 100%. Then it goes 0.5 up and down from that. When you're matching to a different FOV (since it's matched to R6 with 90 vdeg FOV) you'll get out of range easily. You could increase the FOV in Destiny to get within range for MDH 0%.

Show me a screenshot and I'll see why. Sometimes the calculations are simply out of range though. Not that Destiny 2 is only calculating using the ADS setting, not scope.

360 distance is only suitable for hipfire and in some cases ADS. Matching scopes using 360 distance makes no sense in most cases, and will result in either a ridiculously sensitive scope or an out of range error like you are getting. Use monitor distance or viewspeed instead. MDH 0% will match the tracking speed to your hipfire, while MDH 100% will match flicks to the edge of the monitor.

It's too inaccurate in-game. You need to know the exact FOV value for the calculations to be correct, so use the FOV multiplier in the config file.

Armor in this game affects your sensitivity, are you testing with or without armor on?

Try this script with the Logitech software and see if it turns exactly 360 degrees when executed. It will bind to the back side button. This is for hipfire: function OnEvent(event, arg) if (event == "MOUSE_BUTTON_PRESSED" and arg == 4) then for i = 0, 568 do MoveMouseRelative(12,0) Sleep(2) end end end This is for ADS: function OnEvent(event, arg) if (event == "MOUSE_BUTTON_PRESSED" and arg == 4) then for i = 0, 166 do MoveMouseRelative(51,0) Sleep(2) end end end

You can set these values to anything in the calculator, 50 is just the default value loaded as a placeholder. What keyboard and mouse do you have? I might be able to give you a test script.

ADS should be different with your settings, around 12.5 inches. But the calculations looks correct, are your settings in the config file exactly as the calculator outputs for all four values?

For hipfire or ADS? Or both?

One of those folders should be 632360, which is Risk of Rain 2's ID. Under that folder you should find \remote\UserProfiles and then the config file.

The FOV value in the config file is a multiplier for the vertical radians. You can select a different FOV Type like Hdeg Res and enter a desired FOV, then check the output for the config FOV you need to enter in the config file to get this FOV. Note that it must be less than the default value of 0.95993, any value above will not work as it maxes out at this value. The FOV is correct for both 1st and 3rd person.

Scope is done!

ADS and scope for Remnant is done!

ADS added as well, scope next! 0 is quite high, but far from the worst I've seen. The game has ADS and scope sensitivity too. No FOV option though, locked to 90 hdeg.

They need to be calculated separately, but just use the "All" option to calculate them both

I finally cracked the formula, Remnant hipfire is added! Gonna play to find some weapons now

All aims are updated for this game now!

Both, the config file value is just 100 times smaller (0.5 instead of 50 etc).