DPI Wizard

Time to convert! So where do you start? First of all, do you want to calculate the sensitivity for a game based on a 360 distance, or do you want to calculate the 360 distance and sensitivity based on existing settings?
A key point either way is that all the sensitivity calculations for hipfire (for the output game) and aims (for both games) will be based on the hipfire or distance for the input game. For this reason it is highly recommended that you always use the same source for all your calculations to maintain the best consistency.
All numbers and selections in these instructions are examples only, you need to find the correct ones for your games.
Using distance as input
Select "Distance" in the "Convert from" dropdown, and enter the 360 distance you want in the "Distance" box. This distance will either be inches or centimeters depending on you unit selection. Select a game and aim, enter your DPI and set the special options (if any) to match your settings. Make sure the resolution is the same as you are using, and input the FOV as you have it configured in the game. Finally select the location you want the sensitivity calculated for if there are multiple options.
If you select an "All" aim, the hipfire sensitivity will be calculated to match the distance, while all the aims will be matched to this hipfire sensitivity using the conversion methods in the setup.

If you select an ADS or scope aim, the calculation will show you the sensitivity for this specific aim to be the distance you input.

Converting to a game is the same for both distance and sensitivity input, so that will be covered in the next section.
Using sensitivity as input
The most common way to convert sensitivity is by using the settings from a game you are happy with the sensitivity in, so you want this transferred to other games. Start by entering all the settings from the game you want to use as a source, then select an output game and fill in the necessary information. FOV is again very important to get exactly right, either enter the FOV exactly as you have it in the game, or calculate the FOV and configure it in the game.

In the this example the FOV's of the games are  matched, which is highly recommended when it is possible.
But for games with a very narrow FOV range or no FOV options at all, beware that everything is matched to hipfire of the input game, so in this case:

The Targeting and Scope sensitivity in Fortnite are not matched to Fortnite hipfire, but CSGO hipfire. This way the scopes will feel the same as in CSGO which is what you want for consistency.

So you're ready to convert, but you have a few questions. Here are the most common questions answered!
Q: What is the best conversion method?
A: The simple answer is that there is no best method. Everyone is different and have their own preference, so the best we can do is to give some general guidance. The default conversion setup should work well for a lot of people, but it doesn't suit everyone. Try the different methods if the default selections does not work for you.
Q: How do I get hipfire and scope 1:1?
A: A 1:1 sensitivity match is only possible if the actual horizontal FOV is identical. If it's different, as it will be with ADS and scopes, you can only match one specific property between them. If you match 360 distance, aiming will be different. If you match MDH 0% tracking will be the same, but flicks and 360 distance will be different. If you match MDH 100%, tracking will be different as well as any other MDH percentage and of course 360 distance.
Q: Why is the calculator asking me to input sensitivity or multiplier values? Aren't those supposed to be calculated?
A: Many of the sensitivity calculations require multiple different input values to calculate the sensitivity. These values can be a secondary sensitivity value like here, where you basically can use any valid number. The default value should work, but lower values will give you better calculation accuracy.
So the output here is telling you to enter a value into the Sensitivity 1 field, what the variable is called in the config file and the valid range.
The second type is an already calculated sensitivity you need to enter. For instance if you try to convert your CSGO AWP zoom sens and want it based on Overwatch hipfire, it will look like this:

Sensitivity 1 is the hipfire sensitivity for CSGO, so you need to calculate that value first:

Then you can do the zoom calculation:

For a lot of these values (except for hipfire), the default values for the game will be filled in as placeholders.
This is also a great way to show how the "All" conversion works, as it does all this in a single go:

Q: Why is the calculated ADS/scope sensitivity wrong compared to what I actually have when I select an "All" aim for the input game?
A: This means that the conversion setup does not match your current game settings. You need to adjust the conversion setup for the aims so it lines up with your preference. Do this by adjusting the percentage values until it matches. If you can't get it to match it means that your preference is beyond the scope of the conversion methods, and you need to convert ADS and scopes separately. 

Game Info
The game info section lists a lot of important information about the game and sensitivity.
Config file
This is the file you need to edit to set the sensitivity.
Path
The location of the config file, a lot of the times with a Windows variable like %USERPROFILE% which is automatically resolved to a specific path on your computer. If an absolute path is used, C is used as the drive in the path, but you need to replace this if you use another letter for the drive the game is installed on. Sometimes the path will only say something like INSTALLFOLDER, where you have to find out where the game is installed.
Location
If the sensitivity is set in-game, the location will point the where in the menus you can find the sensitivity.
Sensitivity 1, Sensitivity 2, Multiplier 1 and Multiplier 2
The default, minimum and maximum values for each sensitivity variable is shown here, along with their respective name. 
Notes
Any important information regarding the game and sensitivity will be mentioned here. This can be specific instructions on how to set the sensitivity or information regarding sensitivity issues with the game.
The following icons will indicate what kind of informations is listed:
 = Some configuration you have to do to make the sensitivity work correctly.
 = Information about limitations, bugs or similar regarding the sensitivity.
 = Information about how to set the sensitivity or FOV, or some general useful information.
Default FOV
The FOV variable name, default value and FOV Type will be shown here.
FOV Notes
This will show you instructions on where to set the FOV, or if the FOV is locked and cannot be changed.
Affected by
This sections will tell you if the hipfire sensitivity will change 360 distance based on the FOV, and if the sensitivity is affected by the sensitivity settings in Windows (WPS).
Engine
Shows you what game engine the game uses.
Added
Date the game was added to the calculator.
Updated
Date the game was last updated.

Calculations
The calculations section will show you all the sensitivity, FOV and distance output for both the game you are converting from and to.
Sensitivity 1, Sensitivity 2, Multiplier 1, Multiplier 2

The sensitivity and multiplier output displays the name of the setting and the calculated or entered value. Blue numbers represent values that you have entered into the fields or default placeholder values. Green numbers represent calculated values based on the conversion setup. Your game configuration must match all these numbers exactly for the sensitivity to be correct.
If the blue text in parenthesis is shown after the sensitivity, it indicates that the same sensitivity setting is used by two different scopes (like 6X and 7X in the screenshot both use the 6.00x Zoom Aim Sensitivity value). In this case, you must choose which scope you want to match the sensitivity for.
The blue text may also indicate that two scopes with different stated magnification powers are actually identical, as with the 3.4X and 3.5X in the screenshot.
 
 
 
If you use Monitor Distance for the calculation you will see what this distance is equal to in degrees, crosshair movement and mouse movement.The mouse movement is what the calculator attempts to match between the games, so for the output game you will also see a discrepancy tell you how far off the calculated sensitivity is. This discrepancy (if any) is due to the lack of precision/decimals in the game. Using 0% monitor distance will not show any of this as it's impossible to calculate for 0%.

When using Viewspeed Horizontal or Vertical you will instead see a Base Length. This is the value that is being matched, and is not a physical property you can test and measure.

If 360 distance is what you use, you will along with the 360 distance calculation also see the discrepancy.

The last three lines are FOV calculations. Config FOV show you the FOV value you must configure in order to get the FOV you have entered in the input. This can either be the exact same value as your input, or a calculated value based on a different FOV type. The Actual VFOV and Actual HFOV tells you the real vertical and horizontal FOV.

I haven't looked at it yet, but for now I guess using the default value makes everything as before while just adjusting the ads sensitivity.
It will probably possible to set one sens for ads and one for scope with this new setting, but i'm not sure exactly where the cutoff is.
And the "All" calculations probably has to split in two. 

Works like a charm, I've added it now.

If you switch from in-game to config file you will get conversion that is with 6 decimals and exact :)

These four are added!

Painkiller Hell & Damnation already has a proper config file calculation, you just have to change the location from in-game to config file.
I will look into updating Bulletstorm.

I need the SPT version to be updated before I can update the scopes, as I need the AIO trader to access everything.
As soon as it is updated I will go through the changes!

Nice, it's updated now.

These four are added.
Sensitivity in this game is affected by frame rate, so it can't be added.
The way the mouse control in this games works makes it impossible to add calculations for, in addition to this the game lacks any numerical sensitivity value.
Sensitivity is affected by frame rate, so this game can't be added.
This game is also unsupported.

The display sometimes slows down (about 1/4 slower).This may only be a problem with my environment.When that happened, setting it to borderless fixed it.
I have no evidence, so if there are any problems I will delete this post.
I hope this will be helpful to someone.

These two are added. System Shock 2: 25th Anniversary Remaster is added as a special option for System Shock 2.

These four are added.
Sensitivity in this game is affected by frame rate, so it can't be added.
The way the mouse control in this games works makes it impossible to add calculations for, in addition to this the game lacks any numerical sensitivity value.
Sensitivity is affected by frame rate, so this game can't be added.
This game is also unsupported.

These four are added.
Sensitivity in this game is affected by frame rate, so it can't be added.
The way the mouse control in this games works makes it impossible to add calculations for, in addition to this the game lacks any numerical sensitivity value.
Sensitivity is affected by frame rate, so this game can't be added.
This game is also unsupported.

It was indeed changed, the calculations are updated now.

These four are added.
Sensitivity in this game is affected by frame rate, so it can't be added.
The way the mouse control in this games works makes it impossible to add calculations for, in addition to this the game lacks any numerical sensitivity value.
Sensitivity is affected by frame rate, so this game can't be added.
This game is also unsupported.

Unsupported.

These three are added.

I'll get around to reporting it to their lead dev, Dondi when I get a chance. No idea the timeframe, but if I catch his attention, I'll put it through.
If not, I'll get it in Punchpacket's inbox. Their community manager.

The scale is mostly used to replicate game settings. Say you for instance have ADS and Scope in Valorant set to 0.8 and you want to replicate this behaviour to other games, you would set the calculator to MDH 100% (the coefficient that Valorant uses) with Scale 80% (to match ADS and Scope 80%).
In reality this example will make all ADS and scopes slower by that percentage, while still keeping their relative distances the same to the edge.

These four are added.

Nice, makes the list a bit more manageable. Although we still have a couple of outliers with the Minigun and Recurve Bow iron sights.

Calculator updates
Added support for Nintendo Switch 2
Games added
Fortnite (Nintendo Switch 2)
Nintendo Switch 2 HOME Menu