DPI Wizard

Use the config file for best accuracy. View full update

Use the Auto FOV function in the top and set it to the same FOV and FOV Type as Valorant, and the correct FOV for Apex will be automatically calculated: https://www.mouse-sensitivity.com/?share=56f1fa78e9ba6a60a81609dad670654c

Some feels that it does make a difference, others don't. It's down to your personal preference, so try with your original sensitivity first to see.

Feel is a relative term, it depends on what you mean by feel. Same tracking? Same flicking? Same 360 distance? Try this one, hipfire here is Widowmaker with 3.66/37.89, ADS is the 6X scope from CW with 3.66/0 coeff/1 ADS sens and they have the exact same tracking speed: https://www.3daimtrainer.com/mouse-sensitivity/?dpi=800&360dist1=49.1658&360dist2=166.3032&fov1=30&fov2=9.058387&pov=first This is what the sensitivity in the games should be like. I haven't seen any bug in CW myself after hours and hours of testing, but if you encounter a bug there's not much we can do other than hope they fix it.

What exactly is your expectation btw, what is your current aim sensitivity in Overwatch? With the first conversion what you get is this, exactly the same tracking speed for every scope: Now this isn't necessarily what works for everyone, so you need to adjust the conversion setup according to what you want. If it feels too slow and you instead want the same flick movement to say the edge of the monitor, set ADS and scope to MDH 100% instead: https://www.mouse-sensitivity.com/?share=1f02f061cff46e7fa7bfa41386a667d5

How is this wrong exactly? This calculation provides you with the same tracking speed for all scopes. Here you have not filled in your current sensitivity as I said, you have default values for both the Overwatch scope sensitivity (30, unless that's what you use?), and 12 for CW hipfire instead of 3.66. The calculator can't know your exciting values from the beginning, any field that requires a value will load the default value when you select an aim the first time. Consequent aim changes will keep the value you provided as long as the field is the same.

Can you provide a link to your calculation? Use the purple share button.

If you select an aim with multiple sensitivity values you need to provide your current sensitivity for all fields that are available in the calculator, as it doesn't know what sensitivity you have. So the default value will be filled out as a placeholder. The exception is when you use the "All" aim (which is always recommended), then missing values will be calculated (but still default values used for some fields). The supported games category has one topic for each game, so find the topic for the game you have a question about (just click the game name in the game info section of the calculator) and post in it

Might be possible, if someone can find out exactly how to find and set the sensitivity I can do the calculation for the value easily.

This calculator is converting from old R6 to new, like this: https://www.mouse-sensitivity.com/?share=c272a3124cc028c9a2f90f596518b76c The old R6 scope scaling was inherently flawed, but some might have gotten used to it.

Added, but note that the FOV varies between games and it affects the sensitivity.

Note that different game modes use different FOV which will affect the sensitivity! View full update

It's the same as all the other MCC games, updated the entry now

This game only have a sensitivity slider without any value or notches so it can't be added.

No sensitivity value in this game so it can't be added.

Very limited range in this game, but it is added

Mmmm, bacon! View full update

0% is the slowest matching method, and the 1X is so close to hipfire that it barely changes when you change to 75%. So if 75% works for you at 2.5X you should try it for all the scopes

Not detecting any issues here, what exactly are you testing and how is it inconsistent?

DoD is added!

You can enter 6 decimals in the in-game menu, even though it will only show 2! View full update