DPI Wizard

The sensitivity slider is not accurate, expect some discrepancy. View full update

These four are added.

Which weapon are you using in Crossfire? I've added a few snipers now, but the sensitivity relative to your conversion is about the same. Also, how is the sensitivity too slow? Are you expecting the same 360 distance for the zoom in crossfire as in CS2?

See the game notes for instructions on how to disable smoothing. View full update

See the game notes for instructions on how to set the sensitivity. View full update

In simple mode, converting from Hipfire Horizontal for Killing Floor 2 should output an error saying it's not supported: Are you not getting this error? This is by design and unrelated to the order of the sensitivity parameters. Any aim with two or more parameters are unsupported to convert from in simple mode. The naming of the fields are not really referring to the absolute function of the variable they represent in each case. In some cases the Sensitivity 2 field might the FOV for ADS. Sometimes a game uses four equally weighted multipliers spread across Sensitivity 1, 2 and Multiplier 1 and 2. What each field actually represent is mentioned in the game info section. That's what you see in the calculation output. Renaming the header of the input fields is not possible since some games have sensitivity parameters that look like this: <root> <scriptsPreferences> <controlMode> <arcadeMode> <camera> <sensitivity> 1 </sensitivity> </camera> </arcadeMode> </controlMode> </scriptsPreferences> </root> Or this: { "Name": "Control.MouseXSensitivity", "SettingType": 2, "FloatValue": 0.236478898 }, The calculator will always calculate the rightmost value of the input fields. So if the game is using Sensitivity 1 and Multiplier 1, Multiplier 1 is the value that will be calculated. If the order of MouseSensitivity and MouseLookRightScale are switched, the MouseLookRightScale is the value that is being calculated instead. Now that will work as well, but it makes more sense to actually calculate the sensitivity rather than the axis scale. 100 and 500 is so high no sensible calculation will ever reach them.

See the game notes for instructions on how to disable smoothing. View full update

Just added. View full update

They have changed pretty much everything from the sensitivity to the ADS zoom. I've updated it all now, and added both sighted and scoped ADS.

It makes more sense to calculate the actual sensitivity rather than the horizontal axis multiplier, and it gives you slightly better precision for the in-game sensitivity, that's why they are in that order. These are already the defined minimum and maximum values, and the MouseLookRightScale does go below 20 in the config file. For in-game sensitivity: For config file sensitivity:

It still the same as far as I can tell. Make sure ADS - Zoom Scaling Enabled is set to No though.

Using the standard WPS for the desktop and adjusting your DPI, then using this DPI for the games is generally better for a few reasons. Using your desktop DPI in the game will make menu navigation and inventory management etc easier since you have the same 2D sensitivity for the cursor as in Windows. By using the standard WPS you don't have to worry about whether games are affected by it or not. It's theoretically more accurate, but this is probably something you won't detect.

This is correct.

This game is already added.

I've updated Tarkov now, I'm assuming they'll also give the main game three decimals soon I've also verified a few scopes and hipfire, and everything seems to be the same.

There is no camera control in this game as far as I can tell, so it can't be added.

There is no camera control in this game, so it can't be added.

These five are added!