DPI Wizard

It already has 20 steps in the calculator, make sure you select the correct version:

The FOV slider is not new, it is already in the calculator The config file settings will reset only if you enter the options menu, as long as you don't do that they will remain with all the correct decimals in the config file. I've added this info to the game now.

Feels decent here, maybe some optimization issues? I'm working on getting the missing scopes. There is seemingly no connection between zoom level and sensitivity, so I need to analyze each of them manually.

Nice, this is updated now.

You have to enter your actual resolution for Minecraft Bedrock Edition because it directly affects the sensitivity. 2 is listed as the minimum because the sensitivity below that scales completely wrong compared to the rest.

Can you please share the conversion using the purple share button?

Just for hipfire (and in some cases maybe ADS), but scopes should use one of the other conversion methods that are FOV based. The conversion methods are explained here

It's showing you the vertical distance since the conversion setup selected is vertical. Switch it to horizontal and it will show you the correct value for this axis: Converting from Windows does not necessarily feel correct for everyone, even though it's mathematically correct. There are many different ways to go about the conversions, the best is probably to base everything off of a game you are comfortable in, that have proper sensitivity settings for different aim levels. If you don't have this, basing it on Windows is a good option. However, as you found out, the 360 distance for hipfire will be different based on the FOV. So a good workaround is to find one game that are converted from Windows that feels good, let's say MW3, and use this as the source for all future conversion, but then do 360 distance for hipfire and MDV 0% for scopes. For scopes you can never expect the same 360 distance, so they will with this setup still be based on Windows.

This is not what converting from Windows does, it converts based on monitor distance, i.e. how far you have to move your mouse to hit a certain point on your monitor. For instance MDH 100% matches the distance you have to move your mouse in Windows from the center of the monitor to the edge, to the movement in-game to aim at something at the edge of your monitor. For MDV 0% it matches the same tracking speed, which for Windows is how fast the pixels are moving under your cursor. So this is all based on the FOV of the games, so with a different FOV you will also get a different 360 distance. This is indeed just a coincidence, but I guess it can seem weird at first.

Added this now.

The Zoom Sensitivity option does not work. View full update

This is updated now, along with the config file name and in-game sensitivity.

I just tested these exact settings, and the calculations are spot on with the Red Dot A sight at least. What sight and weapon are you testing with? And is your FOV set to 73.739792?

Are you testing this in first person or third person?

First of all, thanks a lot for the video, this helps immensely in understanding what the issue is! 1. Shoulder Fire: This is an ADS aim, and with the setup you have in the calculator, 360 distance is not the target for the conversion. Tracking speed is, which is the speed at which you have to move your mouse to track a moving target: If you want the same 360 distance as hipfire, you need to set the ADS conversion to 360 distance: 2. Ashe vs Marksman Rifle Again, the conversion is based on the tracking speed of your Overwatch hipfire sensitivity, so it's not expected to have the same 360 distance. Matching 360 distance between hipfire and scopes will in most cases make the scope insanely sensitive and practically impossible to aim with, if not just plain impossible to configure due to the sensitivity range in the game. Also matching 360 distance between scopes in different games makes no sense, as they in most cases will have a completely different FOV. The main goal of a scope sensitivity is to keep the aim the same, i.e. the movement to what you can see on the screen. You can turn on the advanced mode in the calculator to see the full details of the conversions, where the actual 360 distance is displayed. I don't know your exact conversion, but if it's something like this: https://www.mouse-sensitivity.com/?share=b18c43ccc759ec230f1ba67d20f8dad8 - then the expected 360 distance for Marksman Rifle in Strinova is 109.5059 cm, while Widowmaker is 125.6535 cm. Since these values are based on the goal of achieving the same tracking speed, doing 360 rotations will only make sense if you use the calculated 360 distance for each scope.

You need to provide both FOV, aspect ratio, perspective and DPI to these numbers. Which is why I ask you to share the conversion using the purple share button. This way I can check if the exact numbers are correct. I know 100% that the PUBG conversions are correct because we know exactly how the game engine works. Any discrepancy is down to hardware issues like the wrong DPI being applied due to automatic profiles, or the sensitivity in the config file not being applied properly etc.

This can't be added because when you zoom in to aim, the sensitivity has so much negative acceleration due to the turning speed limitation that calculating the sensitivity for it will not work.

The PUBG conversion is 100% correct, there is no doubt about this. It is however affected by FOV, perspective and aspect ratio, so maybe you have a mismatch there between the conversion and actual settings? Can you share your conversion using the purple share button so I can see what you are trying to do?

If you mean the Targeting ADS vs Ashe, they are not exactly the same by design, you can't change this. Ashe has a FOV of 65.810435 hdeg, while Targeting ADS has a FOV of 65 hdeg. The conversion itself is a exact is it can be within the limitations of the games.

All these six are added! GUN has a lot of acceleration because the mouse input emulates an analog stick, so it can't be added.

Here's how to set the sensitivity in the config file!

Set the sensitivity in the config file for best accuracy. View full update