DPI Wizard

Since you can only match sensitivity to one specific point at the monitor, the sensitivity will change when converting from Desktop to game depending on the "Match At" value. It seems like you are mixing 50% and 100% based on the numbers you post. Desktop with 400 DPI to Overwatch with default FOV and Match At 50% is 10.15, that is not a bug

Updated the variable name now. Set both horizontal and vertical to the same value for now. Support for vertical mouse sensitivity is planned

Fixed is so it works as long as you don't change FOV Type. Full support will require a code update

That's a first I think. I guess it means that FOV 90 is really 58.72 vertical degrees. I need to make a formula so this happens in the background, I think it should be possible without any code update.

Added!

Just tested this game again, and it's definitely a no-go. Can't even ballpark the sensitivity, it's literally all over the place

Should be doable, I see they are all on Steam

As I said in the other thread, changing the second game's monitor size will only lead to a different ratio and discrepancy calculation atm, it will not affect the actual sensitivity calculation (which is why it is locked). If you want to match physical monitor distance so moving the crosshair e.g. 5 inches is the same on a 19" and 30" monitor, that can be done. But I'm not quite sure this is useful?

Done!

Added now

Took a look at this game now, and since it lacks numeric sensitivity values and are suffering from FPS tied mouse acceleration, it can not be added unfortunately.

This game lacks numeric sensitivity values and are suffering from FPS tied mouse acceleration, so it will not be added.

Actually 1 in CSGO is edge to edge if you play with 4:3 resolution. For 16:9 1 is 75%. 100% with 16:9 is 1.096285, which is 50 in Overwatch

Added Metro 2033 Redux as an alternative aim to the original game Also fixed FOV for all the Metro games!

It's a personal preference where it might feel the best, but 1% is basically the same as 0.81 in CSGO.

Are you first converting CSGO hipfire to Overwatch hipfire using monitor distance 1%? If not, try that, and then use that number for the Widowmaker conversion, that should give you 38 or so. Exactly, matching 360 distance doesn't make much sense for ADS and scopes, so monitor distance is the way to go

0.81 in CSGO is accurate to the hipfire sensitivity at basically 1 pixel movement. This is about the same as 37 for the relative Widowmaker aim, assuming the hipfire is also matched to CSGO. 50 for Widowmaker is is matching the movement to the edge of the screen, so it will be slightly inaccurate around the crosshair.

Updated the decimal places now, along with the FOV setting.

Updated this game now. The FOV slider does not show your actual FOV, but the calculator output will show the correct one. Also the ADS sensitivity was changed, so that formula is now updated.

All these added

Unfortunately this doesn't work as of now. Changing the second monitor size will currently only change the ratio calculation, hence the discrepancy will be wrong. It will not affect the sensitivity calculation. I have though about implementing this though, so you can match i.e. 5 inch movement from a 19" monitor to 5 inch movement on a 30" monitor. But I'm not quite sure if this will be useful?

Added! View full update