DPI Wizard

Yes, no rhyme or reason to the scaling at all.

Do you mean on the vertical axis? As it was slightly higher or lower? If so this has nothing to do with the monitor coefficient, it's just very hard to move the mouse straight.

I will hopefully get it done by the weekend!

Added.

There's a lot of negative acceleration with fast movements, expect some discrepancy. View full update

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

8X is based on the beta as I haven't unlocked it yet. If it's significantly changed it will be wrong, so I'll remove it until I get it unlocked.

This game is not available in my region, so it can't be added unless it is released for EU.

That depends. In this case the difference is not huge, so the experience will be quite similar. In other (extreme) cases the FOV might be limited of half of what you have in BattleBit, which will make it feel like running around with ADS zoomed in. If this is the max of the game, there's not much to do about it though, other than adjust to the difference.

The Auto FOV function will match the closest possible FOV to the target within the limits of the game, be it rounding or FOV limits. So in this case, the closest you can possibly get to 100 in BattleBit for Xdefiant is the equivalent of 88.507155 vdeg (which is 120 hdeg 16:9 in Xdefiant, the max it supports).

You should either look at the FOV range in the game notes, or use the Auto FOV function to make sure the FOV you use is within the range the game supports. Like this: https://www.mouse-sensitivity.com/?share=ef7f7f87ab16c838bc2ef011cbff6e82 If you enter an invalid FOV, as in your case with 129.465984, the whole calculation will be invalid as this is currently impossible to configure in the game. The calculator will still give you a calculation output if possible, but this will be wrong since the FOV is not possible to configure hence the error message.

A lot of games released in the 2017-2020 era had the unfortunate issue that they copied the Unreal Engine 4's default behaviour of making the Y axis 70% of the X axis (i.e. slower). Most of these games that have been somewhat regularly updated since has had this issue fixed so the Y and X axis are the same, and this is reflected in any game that has been re-analyzed since their release (as you can see by the "Updated" date).

It doesn't use a specific percentage, it's all over the place.

I know, but stuff is still locked unless you have unlocked them

It is the inner FOV that is being used for what I have access to, others will be updated as I get them.

This game is already in the calculator, but it's spelled Gray, not Grey. Already added.

The 3x and 4x was bugged in the last beta as they didn't zoom more than ironsight. but since they have disabled the practice zone I need to unlock some of the scopes so I've removed them from the calculator until I can get them analyzed. They should be the same as far as I can tell.

Unsupported.

Added.

Not sure where the zoom sensitivity is used, let me know if you know what it is for.

Use the config file for best accuracy. View full update