DPI Wizard

Added!

Same issue with this one unfortunately

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

Still issues, small movements are not registered and there's quite a bit of acceleration so still not possible.

If you want to keep the horizontal pixel ratio the same, you can calculate it like this: https://www.mouse-sensitivity.com/?share=206ff4da8ff6c5dd0658083c2b5c0554 For games with a regular sensitivity scaling like CSGO it's just to set it to 75% of the original value.

Correct, fixed this now The Holo Sight calculation is for all the sights named holographic without any magnification power mentioned in the description.

Do you mean 4:3 stretched to 16:9? If so the vertical sensitivity actually stays the same, but the horizontal will feel faster.

Unsupported.

Mouse input emulates an analog stick in this game, so it can't be added.

Mouse input emulates an analog stick in this game, so it can't be added.

That depends on where you want to set the sensitivity and FOV, if you set it in-game, select in-game. Note that Hunt also has a different FOV Type in-game and in the config file. As long as the Hipfire conversion is set to 360 distance, yes

You are using the wrong FOV/location in Apex. The config file FOV is completely different from the in-game FOV, so switch location to "In-game" and it should work better

When you reverse the calculation, you also change the source for the calculation from FOV 103 to 120, and if you're using 360 distance for hipfire you will get the wrong sensitivity for scopes. If two scopes are the same FOV you would expect them to also have the same 360 distance, so they are identical. Since you can change the Zoom FOV in QC it's quite easy to show what's going wrong. Here's I've set the Zoom FOV the same FOV as Ashe ADS: https://www.mouse-sensitivity.com/?share=b5a237f18164a96df153c2ddcfe3f9e9 So the FOV and 360 of Ashe ADS and Zoom FOV in QC is the same at 40 vdeg and 82 cm. But if you reverse the calculation, both will change to about 101.5 cm since you change the source: https://www.mouse-sensitivity.com/?share=e621b3807a008120fd609a583691649d So the scopes are no longer like you want them in OW2, but completely different. Using the same source is key to keeping the scopes the same between games. But yes, you will get some weird results when the hipfire FOV is locked, especially when it's very low compared the the other game.

All scopes are added

Thanks, that works!

Seems you have to level up the gun to unlock optics, but then all optics are available. Still a lot faster

Doh, I didn't even check that yet, just jumped into the firing range It will be a bit quicker to add the scopes then!

Config file settings are updated, will add more scopes when I get them unlocked!

Valorant and the typical UE4 sensitivity referenced by the "UE4" entry in Kovaaks's is not the exact same if that's what you're getting at, this is not an error in the calculator (The "UE4" in Kovaak's is the same as Tiny Tina's Wonderlands config file hipfire). Kovaak's also has a difference here, but is using a slighly wrong formula for both.

All aims are added now! Some seem to have different zoom depending in the tier, will update as I find them.

Not here, changing the config file and setting it to read-only does not change the in-game sensitivity. Try setting it to a low number like 0.1 yourself and see if it's applied in-game.

I've added support for it now

Can you please share a link using the purple button to what you have done so far, so it's easier for us to use the correct values?

Actually never mind, the game ignores any changes to the config file and overwrites them with old in-game values. So setting the sensitivity in the config file doesn't work.