DPI Wizard

There's a small amount of negative acceleration, expect some discrepancy. View full update

Unsupported.

Enshrouded is added.

The sensitivity slider is not accurate, expect some discrepancy. Use the config file for best accuracy. View full update

The in-game sensitivity has a quite limited range, if you use the config file instead you should be able to match it without changing DPI.

Yes, that should solve the issue

You have to add the header as well, it should be: [/Script/Engine.InputSettings] bEnableMouseSmoothing=False

250 Hz should be stable, but if it's not then you have to go even lower to 125 Hz. This is just workarounds though, disabling smoothing in the config file is highly recommended as it completely fixes the issue and you can use any polling rate you like.

No, the sens you get with 1000 Hz without disabling smoothing is pretty much random, so there's no way of calculating it.

Correct!

The recoil, and any other forced movement like sway and head bob, are based on set parameters that move you x degrees up, down, left and right. It is completely detached from your sensitivity setting. If that is what you were asking

No, the recoil would be the same. And as far as accuracy goes, while there is a theoretical advantage of having as low pixel/count as possible, the benefit of going below 1 is increasingly low. The movement will be smoother, but the actual aim/accuracy will not increase at the same rate (depending on the game).

The conversion you linked is correct, unless you are converting to or from a stretched 4:3 aspect ratio.

Ok, with the AWP sight, zoom 1 is pretty much in between ADS and 2X in PUBG. So there's no aim in PUBG that even remotely resemble it, but based in the FOV of the scopes the calculated value should be correct. For AWP zoom 2, it's pretty much the exact same as the 6X in PUBG so the comparison there should be easier.

Does the output of the calculator for PUBG match your current settings for all scopes? I.e. 50.276332 for all of them?

In classic Assassin's Creed fashion this has some obvious issues with the sensitivity, it will take some time to analyze to see if it's even possible to add!

This is not related to the discrepancy shown by the calculator. This discrepancy shows you what the sensitivity/360 distance is with the calculated sensitivity is compared to the target sensitivity/360 distance, and is caused by the lack of decimal support by the game. The inaccurate slider note means that when you set the slider to say 3.3 it might in reality be anything from for example 3.21 to 3.39. This is the case for a lot of games unfortunately, and if there's no config file option there's not much you can do about it. This will make the actual sensitivity differ from the calculation, but usually not by a significant amount. Although this will vary depending on your sensitivity. If your target sensitivity is for instance 0.2, and the actual sensitivity is 0.29 due to the slider being inaccurate, you will get a significant difference since it's 1.45 times higher.

Both are added!

Just added! View full update

Just added! View full update