DPI Wizard

You are using the wrong FOV/location in Apex. The config file FOV is completely different from the in-game FOV, so switch location to "In-game" and it should work better

When you reverse the calculation, you also change the source for the calculation from FOV 103 to 120, and if you're using 360 distance for hipfire you will get the wrong sensitivity for scopes.
If two scopes are the same FOV you would expect them to also have the same 360 distance, so they are identical.
Since you can change the Zoom FOV in QC it's quite easy to show what's going wrong. Here's I've set the Zoom FOV the same FOV as Ashe ADS:
https://www.mouse-sensitivity.com/?share=b5a237f18164a96df153c2ddcfe3f9e9
So the FOV and 360 of Ashe ADS and Zoom FOV in QC is the same at 40 vdeg and 82 cm.
But if you reverse the calculation, both will change to about 101.5 cm since you change the source:
https://www.mouse-sensitivity.com/?share=e621b3807a008120fd609a583691649d
So the scopes are no longer like you want them in OW2, but completely different. Using the same source is key to keeping the scopes the same between games. But yes, you will get some weird results when the hipfire FOV is locked, especially when it's very low compared the the other game.

Actually I forgot how this game works. It will force 16:9 regardless of aspect ratio, so you should choose 16:9 in the aspect ratio field if you are playing with a different aspect ratio. There are workarounds to stretch the image though, like through the driver, so you have to choose the correct aspect ratio option.

There was a bug introduced with the latest update, try again now and it should work.
Thanks for reporting!

Monitor Distance - Dynamic is now live, let me know if you find any issues!

You can do like this: https://www.mouse-sensitivity.com/?share=511a55e13315803937c4b13988a5414d
This will keep the aim you convert from the same, and the hipfire and everything else will be adjusted to the conversion you select.

Fixed!

This will match most of your settings: https://www.mouse-sensitivity.com/?share=f77da539e687de6d6f346d4a1a960d92
But this is converting all scopes based on their FOV, and not 360 distance like in the previous example for the 1x.

Copy the entire calculation output using the blue copy button in the top right.
Find the correct part of the config file, it's towards the bottom of the huge text blob in the middle of the file. Select the text from "SensitivityMap" to the "MouseVerticalSensitivityMultiplierAdjusted=1.000000" part and paste the calculations. Note that the copied text will have a blank space (enter) at the end, remove this so everything is on the same line.

Start the game and verify that the sensitivity settings looks like this:

That should be it!

The "Language" button on the bottom the page

For that you have to select the scope you want to see the 360 distance for and enter the settings for it, like in this example.
👍

You have set the scale to 0%, this doesn't work. Usually you want to use 100% here.

It currently doesn't give you a warning though, this will be fixed in the next version.

You can get this in the calculator like this:
https://www.mouse-sensitivity.com/?share=d4e5f8e7c99df81f2701f8b8e02ae0b4
See the MouseVerticalSensitivityMultiplierAdjusted for PUBG here is calculated to 1.217395.

I tried now, and it does go above 1.55. However it maxes out at 1.642857, which might seem like a weird number, but it's equal to exactly 115 hdeg in 4:3. Going above this does not increase the FOV, unless I'm doing something wrong  I've updated the max FOV for the config file calculations.
It used to go down to 0.01, but it does indeed reset to 0.2 now so I've updated the minimum.

Actually I think I misunderstood, I though you wanted your R6 settings to Valorant since you posted them first, but I see it's the other way.
That's a lot easier if you have 0.5 for both hipfire and ADS in Valorant:
https://www.mouse-sensitivity.com/?share=3175d45e675c7aec2722431719f8ee9c

FOV=2*(cot^(-1)*((2*viewer distance)/screenwidth))  

That game has indeed been updated, and no longer registers sensitivity values lower than 0.1 in the config file, so I've updated this as minimum in the calculator.

There was a small bug with the hipfire conversion, "All" and ADS worked fine. The bug is fixed now!

Ok, this looks good. Setting the sensitivity in the PUBG config file can be a bit of a pain though, does your in-game general sensitivity show 36?

Correct, games like this are unfortunately so controller focused that any issues with mouse and keyboard gets basically no priority.
The calculations you get from the calculator are correct for the base sensitivity though, I can see this very clearly in the data. But the random acceleration throws it off completely in certain cases, so it might feel completely off

Be sure to always check the games notes, it's explained there:
You need to enter the total change in turning speed according to your armor as "Sensitivity 1".
Some armor directly affects the hipfire 360 distance, so you need to add all the "Change turning speed" values from your equipped gear. If you for instance are wearing these two:

You should enter 32 in Sensitivity 1.

If depends on how you want to convert. The default setup of the calculator uses MDV 0% for ADS and scope conversion. This keeps the tracking speed identical between aims.
It seems like you want the same 360 distance, but note that this will making aiming precisely very hard as the scopes will be very sensitive and skip over 6 pixels at the worst.
https://www.mouse-sensitivity.com/?share=465b715d451b1eddd26780c9503f47ba

You were right, updated it now

Yes, but it's close to what you had before with 1080p.
This will get you close to what the cursor speed is without 125% zoom yes. But reducing by 25% is not the same as increasing by 25%, so it's slightly off. Reducing it by 20% would be a perfect match.
Some games are affected by WPS, so it depends. If they are affected, the WPS field in the calculator is unlocked.

Thanks for the screenshots, I found the error now. osu with raw input on was tagged as a vertical sensitivity by mistake, this affected only Jedi's Trick since it uses both axis.
It is fixed now!