DPI Wizard

What is your scoped sensitivity multiplier in Valorant?

Try lowering your polling rate to 125Hz, the game might have issues with high polling rates.

This is a common mistake, but 68 is the weapon render FOV (viewmodel_fov), it is not the FOV for your actual view (which is fov_cs_debug ). fov_cs_debug is 90 by default. Just enter your current settings (and be sure to match your ADS and Scope sensitivity which for CSGO at 1 will be MDV 133.3333%), then select the game you want to convert too and change the DPI: https://www.mouse-sensitivity.com/?share=8ef4046b0ee5ffb776de852495df853b For hipfire I've used 360 distance here, but if it suits you use MDV 133.3333% there as well.

I haven't found a multiplier in Dead by Daylight, where did you find it? Either way, anything you multiply by 0 will be 0 so I don't see how it helps. How would you calculate say twice the 360 distance for sensitivity of 0 using that?

Note that you can not necessarily apply the multiplier directly to the sensitivity. It works for some games but not all, as in this example with Elder Scrolls Online where you obviously can't multiply anything by 0 to get a new sensitivity: https://www.mouse-sensitivity.com/?share=9c5f556e01511bfac56983b4f8db0a50

Are you sure it's set to 1.7? Apex will reset it to 1.55 if you do any changes in the settings, and the game maxes out at around 1.64 anyway, you won't actually get 1.7. This is correct, Apex with ADS multiplier 1 will scale all scopes using MDV 0%. Rainbow six will scale all scopes using MDV 0% when they are set to 50. So the games use the same base scaling, but different number. But this means that you will get the same sensitivity value for all scopes if you use MDV 0%, this is just showing the calculator doing it correctly. In your case it should be like this if the fovscale is 1.55: https://www.mouse-sensitivity.com/?share=9e9a3ddd6b4402ea1e987c806a57f596 The scale for ADS and Scope is adjusted slightly to 99.0827% to account for a rounding but in Apex (the bug is in the game, not the calculator).

Most games (including Valorant) use raw input, so sensitivity will not be affected by changing WPS. For those games that are affect (meaning the WPS field in the calculator will be enabled) you can simply convert from 4/11 to 6/11 like this example: https://www.mouse-sensitivity.com/?share=5512d1a71f1c5c6657df8020433e7c35

I've updated the game now to correctly use the config file multiplier instead of in-game FOV.

Correct, use MDV 133%. This will ensure any conversion is matching your Warzone setup.

The calculator does support negative monitor distance, this will make the higher scopes relatively slower.

Unsupported I'm afraid, tons of smoothing.

They are all related to your hipfire sensitivity, so it might be that they don't change at all. But it depends on all your settings, so we need to know ADS FOV, USA, Coefficient, FOV etc, and most importantly how you got those numbers in the first place. What did you convert from, and what conversion method did you use?

Config file is added now, and it supports a much wider FOV!

Try again now, targeting and scope needed an update indeed.

Can you share a specific conversion not working correctly?

What this means is that the aim/scope will not changed 360 distance when you change FOV. So if you are convert using 360 distance, the sensitivity will stay the same. But as soon as you use a conversion method that involves FOV (e.g. any other than 360 distance), the sensitivity will change because a new 360 distance has to be calculated based on the FOV. Hope that made sense

The calculator will account for this by using the conversion setup, so you should use 1.33.

This happens because CSGO with 3.340715/0.019542 is based on Windows. By converting this to PUBG you have a different source so the output will be different. Just like using the same numbers converting back to CSGO Vertical will not result in 3.340715: https://www.mouse-sensitivity.com/?share=bfc87f71fae6eab73d2059bd4d376e9f Because the calculator will never know what your original source was. I think this is a bug indeed, and are looking into it.

The field of view is exactly the same between the games. BFV shows you the horizontal 4:3 FOV to the right, not the FOV based on your resolition. You should in most cases keep the same USA setting. Say you go from a 4:3 monitor with USA 133 which means same movement to the edge of the monitor. You replace it with a 16:9 and keep the USA. You will now still have the same movement to point on the new monitor where the edge of the 4:3 monitor would have been, so in essence you keep the same sensitivity, but see a bit more on the sides.

All you need is the output to tell you the ideal DPI and multiplier, correct? I could do something like this mockup for the advanced output:

Added the FOV Constraint option now

It's added now.

Added.

The sensitivity slider is not accurate, expect some discrepancy. View full update