DPI Wizard

See the notes for instructions on how to disable smoothing. View full update

There's been a few questions as to why the request queue is growing and not being processed as quickly as usual. We could blame it on the summer , but the short answer is that we are in the middle of migrating almost 20 TB (and almost 4 million files) of games from one storage to another, and that takes quite some time as the old storage is... old. While not exactly slow, the amount of files and the fact that we had to degrade the RAID 6 by moving some disks over to the new storage makes it take several days. During this process (and a few days leading up to it) the games that can be analyzed is a bit limited, but we're soon back on track This is the largest volume at pretty much max speed at the start: And this is after over 1 day showing a more average speed:

Who are you replying to?

I got to test it now, and everything is exactly like in Overwatch 1. The only issue I found was that low monitor refresh rate might cause some input lag so it feels "floaty". There might be other issues like this, if it feels "floaty" it's probably an optimization issue.

I didn't get in on the beta, but I will add it as soon as I get access!

You are pretty close, this is perfectly matching it: https://www.mouse-sensitivity.com/?share=f4c47fc93c29b5648e2b83f0f9d33ac5 We don't have an actual FOV reverse calculation for scopes at the moment, but it's something considered for the future

It's not in use. No, you have to set each scope individually.

This file should generally not be overwritten when saving settings in-game, just tested it here to be sure. However I know some users have issues with this on various Unreal Engine games for some reason, not sure what the cause is. If setting it to read-only helps, definitely do it.

You just need to do it in the [GAME FOLDER]\ShooterGame\Saved\Config\WindowsNoEditor\Input.ini file.

You should also get a new recommended DPI to get the sensitivity in range: If you then enter this DPI for the game, you will get a valid calculation.

It does Select Advanced Mode And the output will show you the DPI for a perfect match, as well as the multiplier you need to apply to you current DPI:

Added

The sensitivity slider is not accurate, use the config file for best accuracy. View full update

You have done it correctly in the screenshot, MDV 133.3333% with scale 90%. If you enter the same monitor size (like you have with 27 in the screenshot), the size will be ignored in the conversion. I think most people prefer it this way, but some do want to convert between sizes. So if you enter 17 for CS 1.6 and 27 for the other game and use a conversion method other than 360 distance for hipfire, there will be a conversion based on monitor size.

Updated this now.

If you use more aims in Valorant and hipfire in CSGO when you shoot, you could try to convert from a specific aim in Valorant to hipfire in CSGO instead.

The FOV is not very different between these games, is your 360 distance actually in CSGO the same as in Valorant if you test it?

The game is showing you the 4:3 FOV, and not your actual FOV based on your resolution.

Correct. It means that you need to pay attention to the special options and make sure you set them on/off in the calculator according to what you have in the game.

Vehicle sensitivity is just the transport vehicles, while the tank driver sensitivity is based on both this sensitivity and its own tank sensitivity. Due to how the plane sensitivity works it can't be added.

We had some database issues so some posts got deleted. Here's the link to the conversion: https://www.mouse-sensitivity.com/?share=8a9fddc8d3d41c2152191bb04a6aa6db

We had some database issues so we had to restore a backup that was a few hours old, so let me know if your subscription is missing! Send me a PM or create a support case here.

Because if you are changing the CPI on both sides, you keep the exact same relation between the two. Just like converting say sensitivity 3.6 from CSGO to Overwatch will give you the exact same result with 400 DPI as with 4000 DPI. The 360 distance will obviously change, but the sensitivity will stay the same.