DPI Wizard

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

Not that I'm aware of, it's tied to the hipfire sensitivity.

Added

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

Currently the sensitivity is affected by framerate so it can't be added, but since this game is in development it will hopefully be fixed in the future, so I'll keep an eye on it.

Like this should work: https://www.mouse-sensitivity.com/?share=598ee2e60b31d9226578d809f7380a09 But note that for 2x and 3x the correct settings would be Scale 90% for Scope: It won't affect the DPI conversion though, as just changing the hipfire sensitivity will also change all scopes accordingly.

For this game the scope sensitivity is based on the hipfire sensitivity, so when you change hipfire you also change the scopes You should also ideally use the "All" aim so it's easier to do everything at once. And using the simple mode might not match your current setup, if so you should use the default mode and adjust the conversion setup to match you settings. If for instance all your scopes are set to 0.74, this would be correct: https://www.mouse-sensitivity.com/?share=ca266104db09e4695064e71fa0e462ea

Unsupported.

This mod is already supported:

I tested both the smallest amount of movement (1 count) and full 360 distance, they're all absolutely the same. I don't have the equipment to test latency in millisecond accuracy other than by feel though, so if it's i.e. 20 ms vs 25 ms I wouldn't know. But if it's significant I would definitely detect it by hand. I would definitely know 25 ms from 100 ms etc. So if this tweak does improve it from say 25 to 20 ms (note, these are just random numbers put up by me), it's probably worth it, but as far as I can tell there's no discernible difference. A caveat though: These tweaks might for all I know affect some hardware/software/drivers differently, so if your setup has an issue, this might solve it.

All are added now

In CSGO, right? Tested it now, everything is exactly the same with or without these settings.

This game lacks any sensitivity setting, so it can't be added.

There's seemingly no sensitivity setting in this game, so it can't be added.

Correct, the only movement that is consistent between different FOVs when using MDH 100% is the exact distance you have to move the mouse to aim at what's at the edge of your monitor. While MDH 0% keeps the continuous tracking consistent, meaning you have to move your mouse at the same speed to to track a moving target.

That's the in-game sensitivity, switch location to "In-game" to calculate this.

Some games are missing the FOV range and rounding precision since they were added before this was supported by the calculator. Doom 2016 is one of these games. Doom Eternal and Half-Life one are registered with no decimal support though. You can still enter multiple decimals, but if you use the Auto FOV function, or switch the FOV Type to the default from another FOV Type, the rounding will be applied.

I've added support for FOV change now.

PUBG scales the sensitivity to MDH 100%. Meaning that half the FOV is twice the 360 distance distance etc. This is not the same as the Viewspeed calculations, they work in a completely different way than a fixed monitor distance, so what you are seeing is expected. If you want to set up the calculator to match how PUBG works (so you get the same value for all aims), set the ADS and Scope conversions to Monitor Distance Horizontal 100%.

There is too much smoothing in this game, so it can't be added.

I've added the horizontal and vertical sensitivity values now, clarified what the ADS is and added ACOG. Let me know if you want a specific weapon added https://wiki.killingfloor2.com/index.php?title=Useful_Console_Commands_(Killing_Floor_2)#Weapon_Class_Names

Updated it now, note that you have to enable Relative sensitivity.