DPI Wizard

It only does that if you calculate horizontal hipfire for in-game sensitivity. If you do the "All" conversion it will instead use the default values and adjust the sensitivity with the MouseSensitivityMultiplierUnit since it's way more accurate.

No, you don't need to change it unless your calculation is out of range. Using the default value will work perfectly fine in most cases.

They probably keep it in for a couple of reasons I can think of; to read the old value and convert it to new, and while they had the test server up the same config file had to work with both versions. When you convert to any aim that have more than one value, you have to provide an existing value to the calculator. It will in most cases fill in the default value as a placeholder since it can't know what your value is. Just replace this placeholder value with your actual value if it isn't correct. Using the "All" aim will calculate several of these values for you, so it's generally recommended to use this. But even with the "All" conversion you have to provide some existing values, but the default values will work fine in most cases.

Paint the Town Red and Haydee are both added.

Note that this game uses comma (,) and not period (.) as the decimal separator in the config file! View full update

Config file and in-game sensitivity added. View full update

Added 1st person camera and config file sensitivity.

It only changes the weapon render FOV, see this animation (this is 60 and 90):

Both these are added now.

Fast paced shooter is added! View full update

This is the viewmodel FOV and not the display FOV. Meaning it is what FOV weapons etc are rendered at.

Make sure to disable smoothing in this game. View full update

Added now!

Scavengers is in! View full update

Already on it

You have to account for the FOV in the game. If your 360 distance is 40 cm but your FOV is 20 it wouldn't make any sense to divide by four.