DPI Wizard

Outriders added!

Setting the sensitivity in the config file does not currently work.

Be sure to disable acceleration in this game. View full update

Fixed this now, sorry for the bug!

You're not far off, in fact you're right in the middle for all scopes. But since Valorant scales the sensitivity differently from CSGO, you have to choose one scope to match perfectly. This is the correct setup: https://www.mouse-sensitivity.com/?share=afe579a480683ec593770798bd9baac6

Already on it, will be done tomorrow

You had some corrupt save entries, I've fixed it now so try again.

2.009 means it will move 2.009 resolution pixels for every count from the mouse. The game renders sub-pixel images so this is no issue. This is all based on FOV, resolution and sensitivity. 360 distance is irrelevant in this case, and since your 2 pixel/count sensitivity results in an uneven 360 distance it will not line up if you spin 360. This is correct and expected.

The idea is to keep the sensitivity you are used to in 2D like in Windows etc and somehow translate it to 3D sensitivity. So when you react to something on the screen your movement to aim at it will best match the equivalent movement to move a cursor the same distance.

See the instructions for a brief explanation of Viewspeed. If you want to get really technical, see this and this. With 0% you remove any coefficient and just use the FOV in and FOV out directly against each other. This results in the sensitivity being identical in terms of speed and not distance.

To some extent yes.

See the instructions thread, videos and everything there

Correct.

MDV 0% is basically the slowest method of the normal conversions. You can try MDV 100% or MDH 100% instead to see if they feel better.

360 distance is useful because it matches your sensitivity based on how far you turn. So you will always know how far to move your mouse to turn around a corner or look behind you. However it will feel/look visually different when the FOV is different, so some might prefer to match it based on what you see on the monitor instead. So this conversion (MDV 0%) is matching the tracking speed of your crosshair, so if you were to track a moving target the speed you have to move your mouse would be the same.

Just change the Hipfire/Look setup to "Monitor Distance Vertical 0%"

Try MDV 0% instead of 360 distance for hipfire. You can test it here, hipfire is BO2, ADS is MW3. Same 360 distance (as you have it now) MDV 0% (same tracking speed)

The FOV in MW3 is lower, so it's more zoomed in and will feel faster with the same 360 distance. If you use the same FOV or match the sensitivity using a monitor distance conversion instead it will feel more similar.

Changing DPI is the best way to get a more precise sensitivity for those games that lack fine adjustment. Beware that your mouse driver might allow DPI increments of 1 or 10 while actually rounding up to the nearest 50. It depends on the mouse and driver, some do support all the way down to 1.

How exactly are you testing? Sensitivity 4.977720 will actually give you a 360 distance of 3254.5 counts, so it's impossible to line it up perfectly with scripts if that's what you're doing.

Good idea!

Good to know! Be aware that in most games the focus is on how low the sensitivity can go, and not how high (as you want it). So if you find another game where you can't go high enough just let me know. If the sensitivity is in-game is usually limited by the interface though, but if it's in a config file or registry it might go higher than the current max in the calculator.

Tested it now, and this game seems to accept basically any value in the registry, so the max now is increased to 100. Do note that as previously mentioned the sensitivity will reset if you change any setting in-game when it's outside of the in-game slider range. So make sure to do all settings before setting the sensitivity in the registry.