DPI Wizard

Using MDV 133.3333% instead of MDH 75% circumvents the issue, and is the correct way of doing it for now when not using stretched resolutions. The fact that you mostly aim horizontally in the game is irrelevant though, the goal is to keep the conversion consistent.

It will be in the next major update that is being worked on right now, but no ETA as of yet. Note that this change won't necessarily be of any significance depending on your setup. The change will be that the option "Native" under Aspect Ratio will be renamed "Ignore" since it technically ignores the aspect ratio in the sensitivity calculation (but not the FOV) and assumes everything is as physically the same. The new "Native" option will correct for aspect ratio change in the calculation. As an example when converting from 4:3 to 16:9 using MDH 100%, the calculator now converts from 100% of 4:3 to 100% of 16:9. The correct way would be to convert to 75% of 16:9 instead, so this example should result in the same ADS sensitivity for both input and output: https://www.mouse-sensitivity.com/?share=aa2754ffc50112185be46d03e6257d0d

ADS is added

Added this option to the game now

If you want to scale the sensitivity to monitor size, simply enter a different monitor size for the output: https://www.mouse-sensitivity.com/?share=f76db10c429b0ba7d128576e51b8ae3a

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

No numerical sensitivity available for this game, so it can't be added. Added the enhanced version now. Added! Too much smoothing in this game to be added, even with it turned off.

Even with smoothing turned off this game has too much smoothing to be added.

Be sure to include the scientific notation in the sensitivity value. View full update

Added the enhanced version now

If all your zoom sens in Apex is set to 0.816412 this would be the technical proper way to convert it: https://www.mouse-sensitivity.com/?share=675fe7be0f030a125e5ee590e20b2d13 But it depends on how you got to 0.816412 in the first place.

This is doing the right thing, but for ease the correct way would be to simply use the exact target FOV and FOV type from the game you are converting from (110 hdeg 16:9) and the calculator will convert this into the correct config FOV for any game you select: https://www.mouse-sensitivity.com/?share=beb529869f99e866e49143c8126a129f

https://www.mouse-sensitivity.com/?share=54a5310ae3ee865efa083676f834109a

You have to disable smoothing or use a polling rate lower than 250 Hz for the sensitivity to work correctly, I've updated the game notes.

Everything was updated and verified about a month ago, the updated date you see is in the game info is for that specific aim. If you check for instance the Walther MRS reflex sight you'll see that it was added 22nd of July, and VOMZ Pilad 4x32 was updated on the same day.

Added this now, thanks for the help!

New Chinese game added! View full update

If that works for you, stick with it The issue with Minecraft is not consistent, it probably depends on both your settings and hardware.

No, I'm sure it was the base sensitivity that was 1.3% lower (not the actual sensitivity, it will vary slightly), so it was a tiny difference (I still have the old entry available). Also note that a multiplier doesn't make sense in Minecraft. Let's say your sensitivity is 0%, multiplying that by any number still gives you 0. Just like 0.1 is not half the sensitivity of 0.2, it scales completely different than that. Half of 0.2 is actually 0.08997361. Did you try the sensitivity matcher program?

Ok, and what polling rate is your mouse set to?

No, 1.3% not 130%, so a 1.013 multiplier. It sounds like your issue is related to the vsync problems, do you have it off?