DPI Wizard

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

There's no numerical sensitivity value in this game, but it can be set accurately by clicking! View full update

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

The 360 distance for arcminute per count is 360/(pi/10800)=21600 counts. You can do this in the calculator like this: https://www.mouse-sensitivity.com/?share=7720a8dfbe278a63d6bc052c301e350c If you don't like the units set to counts, you can then just use this CSGO sensitivity as a base for your conversion and switch to calculate from sensitivity and units to inches or centimeters: https://www.mouse-sensitivity.com/?share=f3b908a5a6fe1efc513d4eab9b6b37a9 Then make sure hipfire conversion is set to 360 distance and you're good to go!

Since it's a bug in the game you just have to try different settings to see if you find something that makes it work better.

I've updated all the aims now, added missing ones and removed those that are no longer in the game.

I'm going through all the aims now to see where they fit and will update when done.

What problems exactly?

In your examples you also convert between different monitor sizes, so converting from a 4:3 22" will be different than a 16:9 22".

It depends on how the game handles FOV and how you match sensitivity. For instance if the game has a resolution based horizontal FOV and you use MDH 100% you will get a difference.

4:3 Black Bars will calculate the sensitivity based on the whole monitor, including the black part. So for instance if you match MDH 100% using black bars you will match the movement to the edge of the monitor (i.e. beyond the image) as if the image filled the black bars. To put it another way, on a 16:9 monitor CSGO in 4:3 with black bars will be identical to CSGO in 16:9.

Your settings for Destiny 2 indicates that you have set the FOV to 76.366893 (this is a multiplier, true vertical FOV is 45.42), while you have it set to 90 in Extraction which is almost twice as high. With these settings a 2x scope in Extraction will have the same FOV as your hipfire in Destiny 2, which is not ideal. You should whenever possible match the actual FOV for hipfire, which makes the calculation more sensible: https://www.mouse-sensitivity.com/?share=2e2438bfa7d4a1a39a04f9ea08f455b7

Fixed now.

I think the distance calculation is ignoring the display scale, I'll look into it.

Yeah, as mentioned there's issues with the older versions. It's probably a bit different depending on your system, but here it was vsync and polling rate that messed it up.

You can do that when you save a default entry as a premium member. While I use metric myself, the US has the biggest userbase here so it's more natural to default to inches. But I will see if I can set it based on geolocation in the next update

The DPI should be calculated, but there was a bug with the input. Try again now

This is already added.

This is already added.

Have you tried disabling vsync and using a low polling rate? The sensitivity isn't different, it's an issue with the earlier versions having smoothing.

Both these are added.