DPI Wizard

There is no connection between sensitivity and FOV in this game, so yes that is normal.

These two games can't be added because of acceleration and smoothing issues.
Correct, this kind of games can't be added.
However, this is supported and added now.
Butcher's Creek is also added.

Kovaak's is wrong, that formula is not correct :)

2x is added.
If you mean how to verify the sensitivity, you can use a tool like this sensitivity matcher to do it.
Support for this is added now.

Try using MDH instead of 360 distance. 100% will match the movement to the edge, while 0% will match the tracking speed:

ADS is added, 0.001 is already the minimum. 0.2 was for the Rivals specific sensitivity, which is now updated to 0.05.

Just added!
View full update

Nice, I've added the config file now.

I've added support for this for hipfire now.

Deadzone indeed fixed!

Added. Note that you have to use a very low polling rate to avoid negative acceleration.

The sensitivity location for Roblox is set to "In-game (New UI)", but your screenshot is showing the old UI. The sensitivity scale in these two are completely different, so that's probably the issue. You have also entered the sensitivity values in the wrong locations, they should be opposite. Select "In-game" and enter the sensitivity in the correct locations, and it should be accurate.

The minimum of 0.2 is the Rivals sensitivity, see the game notes for clarifications on where the different sensitivity parameters belong.

Thanks, they changed the ADS and scope sensitivity for release, I've updated the calculations now.

tried firefox and edge, both with ublock

Outlawed, Blow-up and War Robots are added.

Look sensitivity for Atomfall is added, need to play a bit to analyze the rest.

Updated!

The issue is that the inaccuracy depends on polling rate and DPI etc. Here's a quick example where you can see it's completely inconsistent, this movement should have landed on the same spot every time. I'm doing 4 turns at one speed, then 4 turns at twice the speed. And in this example they are quite close just so it's visually clear. Playing around with polling rate and DPI settings can make the spin just do about a 180 instead of around 360 degrees.
Also, just moving back and forth for instance 100 counts makes the rotation end up at a different spot every time. So there's no consistency here.
 

Assassin’s Creed Shadows is added!

Thanks for letting me know, Freja is added now!

The issue is that the inaccuracy depends on polling rate and DPI etc. Here's a quick example where you can see it's completely inconsistent, this movement should have landed on the same spot every time. I'm doing 4 turns at one speed, then 4 turns at twice the speed. And in this example they are quite close just so it's visually clear. Playing around with polling rate and DPI settings can make the spin just do about a 180 instead of around 360 degrees.
Also, just moving back and forth for instance 100 counts makes the rotation end up at a different spot every time. So there's no consistency here.
 

The FOV range is updated now, but note that it doesn't go any higher than 120, setting it between 120 and 130 makes no difference.

There is no separate sensitivity setting for ADS. ADS sensitivity is affected by the FOV of the aim, and use the same sensitivity setting as hipfire.

Yeah, it seems to have two possible locations. I'll add both to the info.

The sensitivity was indeed updated to a slightly better range, I've updated the calculations now.

I've added special options for perspective and zoom scaling now. Zoom scaling does not affect first person hipfire though.