DPI Wizard

Check the video on the front page Monitor match is replicating the same movement to one point on the monitor. 100% means the same movement to the edge of the monitor, 50% means the same movement to 50% of the distance between the cross hair and the monitor and so on. When the FOV is different you can only match the movement to one specific point. There is no such thing as 1:1 for scopes however, you have several different ways of matching them depending on your preference. Games commonly use 0%, 75% or 100% as their default match.

0 is 100% monitor match. Negative is slower than this, positive is faster.

That would be awesome, pm me the key!

This just in

Oldie added.

Some acceleration in this game, will see if I find a way to disable it.

Make sure you have the latest version:

I can only find the Rotation Speed slider without any numerical value (same with the FOV). It's very hard to add anything sensible without numbers, do you have any idea if there's another way to set the sensitivity? I couldn't find anything in the config file.

You should not do it this way, the scopes have different FOV's even though they are named the same. You should either use hipfire or one scope as the source for all the scopes, and use Monitor Distance or Viewspeed.

Scoping is just the override sensitivity for all scopes when you select override. It sets all scopes to the same value. No new calculation is needed for this, if you want to use the override just calculate the sensitivity for one scope and set the Scoping sensitivity to this value. It's about the same as the Soldier Zoom Sensitivity in BF1 when you have all the scopes to 100%. Are you converting from scope to scope (i.e. 4X in BF1 to 4X in PUBG) etc?

Is, the values can be change slightly by the game even when set directly in the config file. This rounding error is negligible though, the difference in the example is about 0.03 inches/360. And the error is actually in the game, the calculator produces the correct numbers but the game messes it up.

They are, you can use the in-game calculation for the LastConvertedSensitivity value in the config file. Yes, using this method you need to enter all the values without pressing enter, then click Apply. Changing anything at a later point rounds all the values.

Finally added! The acceleration issues are fixed in the Reloaded version.

The reloaded version worked fine, just added it now! Note that it actually uses the same sensitivity as the classic version, but the acceleration issue is fixed.

Testing it now.

I cleaned up the PUBG entries in the calculator now: Config file 2 is removed. In-game calculation now has six decimals. Updated notes on how to enter the decimal number in-game (i.e. do not press enter). If you still want to use the config file, use the in-game calculation for the "LastConvertedSensitivity" value.

Ok, did some tests now and figured out what's going on... If you enter a decimal number and press enter it rounds the value to the nearest whole number. But if you just enter the number and click apply the decimals are conserved. This method probably renders the config file sensitivity redundant as you have the same precision in-game and it's a lot easier to set it.

You mean in the calculator? In-game doesn't support decimals, that's why there's a separate calculation for the in-game value in the config file where it supports decimals.

First of all make sure you are select the correct perspective for PUBG. TPP and FPP are very different if you play with FOV 103. If FPP and FOV 103 is what you are playing with in both games, it doesn't matter what conversion method you use as they will all produce the same result. If you used hipfire in Overwatch to convert to Widowmaker, you can use the same method to convert to PUBG scopes from hipfire. The result will actually be about the same whether you use hipfire or Widowmaker, but to avoid rounding error preferably use the same source.

They just renamed ADS Sensitivity to Iron-sight Sensitivity and added an override option which in effect sets all the scopes to the same value. The format of the config file is also slightly changed, but this is already updated in the calculator. All sensitivity calculations are exactly the same as before.

Yes, the variables in the .ini is changed. The calculator is updated to reflect this, but you need to make sure you have the correct variables if you are just copying the values into the file. Just checked this in-game, and it doesn't matter what the Scoping value is set to when you select Override.