DPI Wizard

Haven't had too much to time to play yet

What gun/aim are you using for ADS, and are your sensitivity curves default?

Just set the Win/2D conversion to MDH 100% and you got your sensitivity

Warband is added

Warband is in!

Monitor distance is counts*(atan(monitordistance*tan(inrads/2))/atan(monitordistance*tan(outrads/2))) 0% is simply counts*(tan(inrads/2)/tan(outrads/2))

Aye, I will update this soon.

Added this now. Completely unique sensitivity actually, never seen it before.

Just added with in-game sensitivity!

Lot's of TLC for KF2! Added zoom sens, correct FOV multiplier and in-game settings!

Turns out 360 distance maxes out at fov_cs_debug 10, so I've updated this in the calculations now And as far as I know fov_cs_debug does not support decimals btw, so setting it to 1.33 would result in just 1.

I just checked the game, and it's no longer needed as they have fixed acceleration. I've also updated the sensitivity formulas so they are 100% correct now. (The file is located at %LOCALAPPDATA%\PWND\Saved\Config\WindowsClient btw, but it's useless now).

They are the same, but most games do not use this scale. What you want to do is convert directly from ADS to ADS. First convert hipfire to hipfire to get the base sensitivity (this is just an example, adjust your values according to your settings): Then convert from ADS to ADS using the calculated hipfire sensitivity: As you can see in this case you will get 0.65 in both games. For PUBG it would be like this: And for BFV like this (will also work with 0.65/65 if you set USA to 0) Zoom sens is 104% because of lack of decimals for hipfire.: No, this method does not work for Apex, but it does work for some games.

Bedrock (Windows 10) edition is added now! The sensitivity scaling is really weird, so expect calculations to be up to 1.5% inaccurate. I've also set the minimum sensitivity to 0.02 since it becomes very inaccurate below that. In-game sensitivity is also added for both editions, and the config file calculation for the Java version now supports the FOV multiplier for better accuracy.

0.03 in Windows 10 edition? I.e. 3 in-game, or setting ctrl_sensitivity2_mouse:0.03 in %LOCALAPPDATA%\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\minecraftpe\options.txt? The sensitivity I get with that number is close to the same as 0 in the Java edition, or about 6.3 times the 360 distance in Windows 10 edition. 0.3 in both games are actually quite close, but that is just by chance. Are there more versions out there that's confusing us? I'm using "Minecraft for Windows 10" from the Windows Store, in-game it says version v1.10.1.

Just to confirm your post: It just uses the size to calculate the relation between the mouse movement and the crosshair movement. It is not used for sensitivity calculation at all as of now. The calculator also assumes the FOV reaches the edges of the monitor, regardless of aspect ratio and size (i.e. stretched). So matching sensitivity between different monitor sizes is not currently automatically supported, you have to do it manually.

Based on what I've analyzed previously there's absolutely no connection between the sensitivity in Java and bedrock version. And the bedrock version is one of the most difficult ones I've come across. Still working on it, finding the correct formula is very hard as the numbers don't add up in any conventional way.

This turned out to be very complicated for a Unity game, but it's added now

Use regedit to set the sensitivity in this game.