DPI Wizard

Added!

Indie shooter is added! View full update

No numerical sensitivity value in this game and no config file sensitivity. As long as this is missing it can't be added.

Unfortunately no numerical sensitivity value in this game and no config file. As long as this is missing it can't be added.

Updated. Added all these modes!

You can do this in the calculator. Just distance as input instead of sensitivity: First calculate the sensitivity for your desired hipfire sensitivity, then use this sensitivity when calculating for ADS. MDV 0% is the best place to start as Merinda18 says.

But the distance is already displayed in the calculator, and can be used as an input. Is there really need for this?

0

I'll see if I can make a popup option when clicking to either launch the aim trainer or copy the value! That doesn't really work when you do an "All" conversion though. Every sensitivity is different, and adding a separate button for all the values will be very messy.

We now have a direct integration with 3D Aim Trainer in the calculator, so you can simply click an underlined sensitivity value in the output to test this exact sensitivity instantly! Here's how it works: If you click a hipfire sensitivity, you will get this sensitivity for both hipfire and ADS in the trainer. If you click an aim you will get this sensitivity for the aim in the trainer, and hipfire will either be derived from the sensitivity input or reverse calculated based on your conversion setup. The calculator input (resolution and DPI) must match your current setup for the sensitivity in the aim trainer to be correct. Note that currently the aim trainer does not have access to raw mouse input, so WPS will be applied if you have changed it. This is scheduled to change when browsers begin to support raw input next year.

They are different because they use a different FOV for the calculation. And while X and Y are different for hipfire, it's the same for scopes for some reason.

Ok, then simply select 360 distance in the conversion setup for ADS, and use the value for the ADS you want matched as you have two options. https://www.mouse-sensitivity.com/?share=147e9354af2f7fde131b7e094b6019da

That depends on what you mean by 1:1. With the FOV being different between ADS and hipfire, there is no real 1:1 sensitivity, you can only match one aspect of it. Be it 360 distance or a specific monitor distance which gives you either the same tracking (0%) or the same distance moving to a spot on your monitor (X%).

Correct, set it to 81 both in the calculator and in the game

Set the FOV in Kovaak's to 81 if the goal is to train with the ADS sensitivity.

For 16:9 it is 75% yes, but the basis for the sensitivity is 133% of the vertical field of view. On a 21:9 you still have the same 133% of the vertical FOV, but your horizontal FOV is now wider. This width is just added on with this conversion, keeping the 16:9 portion of your monitor exactly the same as before.

Use the same FOV as in MW.

Keep it independent.

Yeah, that's the biggest drawback of using very high DPI. Some games do have a separate cursor sensitivity, but most do not. Scale is to be left at 100% if you want all scopes to have the same relative scaling yes. 0% coefficient is typically the best place to start, and try higher values if it feels too slow.

Unless you are using Legacy you can use the exact same settings in both games. But it is important to also use the same FOV. https://www.mouse-sensitivity.com/?share=01f83e389ceeabf9c71044df26fa54ca

Correct The config file has a much wider range though, so in-game might just display 0% if it's below the minimum in-game value. It will still be applied as in the config file if this happens.

The in-game value is directly linked to the config file value, so it's enough to just set it in the config file. Use the calculator like this to convert from old to new DPI. The values in this link are just examples, use your own values https://www.mouse-sensitivity.com/?share=bf4f443187f75b6e51e6c058144c948e

Just updated it now.