DPI Wizard

Yes, by using any conversion method other than 360 distance for hipfire, but this will obviously impact how hipfire feel, especially in terms of navigation (i.e. how far you move your mouse to turn around a corner etc).

I does matter, as it enables the ability to set the sensitivity for each scope.

These are all added!

Sensitivity for this game is finally fixed! View full update

This is correct, but since there's a huge difference in hipfire FOV (73.74 vs 120), it might throw the feeling off a bit. Remember that the scopes are matched to the 73.74 FOV of CSGO, not BattleBit's FOV. It might not suite the gameplay of BattleBit as much, but if you set the FOV to 74, everything will be pretty much identical. The end result for the scopes are exactly the same as when using 26, except for as you say Ironsight witch will be very high. The recommended way is using the values from the "All" conversion as that keeps everything matched. The reason the more powerful scopes all come out to the same value is simply because of the lack of decimals.

What you said is correct, and it has to be this way to make any sense. If the scopes were matched to the hipfire of the output game you would not get any consistency unless you also match the hipfire FOV between the games. Consider this example converting from Overwatch with FOV 103 to Overwatch with FOV 80: https://www.mouse-sensitivity.com/?share=43c8dace9347072001b6b2962b254eaf The FOV change only affects hipfire, the zoom FOV stays the same. So the sensitivity (360 distance) for the zoom should also stay the same to keep it consistent. If they were matched based on FOV 80 instead, you would get a completely different sensitivity for identical zoom levels. Click the reverse calculation button between the input and output game

73 FOV (vdeg) in B4B is almost identical to 1.275 in Apex which is 73.021112 vdeg. So they should be pretty much the same.

To match this you need to set the ADS and scope conversion to MDV 0% and Scale 125% (I've used scale 125.547 in this example to account for a bug in Apex): https://www.mouse-sensitivity.com/?share=0204ec50ae1521209e2bf3bf146a44c5

Use the The Punisher Widescreen Fix to fix mouse sensitivity. View full update

I don't have a specific convert, but changing from 0% to 100% makes a huge impact, so it depends on what you want to achieve.

It works, but do note that the "Windows / 2D" setup has a huge impact of the conversion. 100% is vastly different from 0%

Use the unofficial patch to disable acceleration and enable raw input. View full update

There's a small amount of acceleration and packet loss, expect some discrepancy. View full update

This is added now. Due to the lack of raw input, there's a bit of both packet loss and acceleration.

The "Zoom Level: Iron Sight" is also 1.25x, at least on the weapons I've tried so far. Just switch between 1.25x and iron sights and you'll see it's the same. There might be a 1.00x somewhere, but it's really hard to find!

Yes, only the 2.2x scope is added. The different zoom levels are all over the place, and with so many different gun permutations I've only added a general one.

This is correct as far as I can tell. Make sure you configure all the calculated numbers according to the output and is should work as intended.

This game has frame affected sensitivity so it can't be added.

This one has frame affected sensitivity so it can't be added. The sequel works however, and is added!

As the instructions say: The sensitivity parameter binds F8 to set the mouse sensitivity, and must be added to the end of the [WillowGame.WillowPlayerInput] block at the end of the file.