DPI Wizard

There's a small amount of smoothing and the sensitivity slider is not accurate, expect some discrepancy. View full update

Just added! View full update

Ok, I see what you mean now. There is no reason why, it's just different ways of implementing this.

There was an error with the FOV handling when converting back to hex, it should be fixed now. Thanks for reporting!

You can do this in CSGO to, what exactly do you mean? In most cases it doesn't change the calculation, but you should always enter your native resolution in the resolution field, and select the forced aspect ratio in the aspect ratio field.

It means that the sensitivity is directly affected by framerate, so you will get a different sensitivity when your framerate is e.g. 76 than you will at 77 etc. This means that calculating the sensitivity is almost impossible since it will fluctuate a lot.

Already requested a few posts above yours, not added as it currently is affected by framerate.

It works for everything except Gunner Aim Sensitivity (Look only, it works for Zoom) and Transport Vehicle Freelook Sensitivity.

No, there's too many variables since the vehicles use a separate FOV settings, so it's not possible. But converting from "All" to "All Vehicles" is essentially the same.

Unsupported as it has too much acceleration.

Nice, updated it now.

Enter the correct resolution The calculator tries to auto-detect your resolution, but for some reason your browser is reporting 1943x2087, which is definitely not correct.

Unfortunately these emulated mobile games have terrible mouse input, so they can't be added.

Flawless Widescreen is already supported, see the FOV notes

You have to increase your DPI if you want 11 cm with a lower pixel/count. If you double it from what you have now (and keep the 360 distance at 11 cm) you will get just about 1 pixel/count.

Only if you also have the same FOV.

About 0.14.

As the output says, it's not possible since it's out of range. The hipfire sensitivity is too low, so the tank sensitivity can't match it. Note that the sensitivity values in the error can sometimes be wrong simply to avoid division by zero since the target distance in the calculation is out of range.

You are using 360 distance to match ADS and scopes, and this is generally not recommended for this reason, in addition to it being impossible to achieve for the 4x to 12x in this game. To fix this use instead one of the other matching methods for ADS and scopes. MDV 0% will actually match the pixel ratio to your hipfire.

I see the issue, 0 is technically not a valid sensitivity, so while it's possible to set it in the game, it will lead to a division by zero in the calculator. So the reason you get the seemingly same result was due to a protection to avoid this. I've instead adjusted the minimum allowed sensitivity now.

Can you please share links to the two conversions?

Both these are added.