DPI Wizard

The "Scope Magnification Adapts Automatically" setting makes the low power scopes (ironically those not named something with "Scope") affected by your FOV, just like ADS FOV in BF. Yes, these settings affect everything, including hipfire.

Ok, this is about as close as you can get to that. As previously mentioned, make sure every single setting and value is configured according to the calculation output and the game info.

Yes, are your scopes in BF configured to match this output? Or are the all set to 100?

This is correct, make sure every single setting and value is configured according to the calculation output and the game info.

If you can link you BF settings using the purple share button, I can find the best match for you. Note that this game has a lot of settings and values that must be set correctly for the calculations to be correct.

Correct, vertical is 75% of horizontal (i.e. slower), and as far as I can see there's no way to fix this at the moment.

Sensitivity and FOV in this game was completely changed from earlier, and the smoothing issues are fixed so the entry in Input.ini is no longer necessary. It is all updated now.

This new version has the sensitivity messed up, there's huge random acceleration spikes making it very unstable and not currently possible to even analyze properly. Hopefully they will fix it pretty quickly.

When the calculator is in simple mode it will default to in-game sensitivity if possible, while default/advanced mode will automatically select config file for better accuracy.

Have you disabled smoothing?

Since you are converting from 16:9 to 32:9 using MDH, the 360 distance will be very different. If you instead switch to MDV and match the vertical FOV, you will get a much better result. https://www.mouse-sensitivity.com/?share=c497e83b0e925878048eac436c7cdda2 This will keep the 16:9 portion of the 32:9 monitor the same as it is on 16:9.

Can you share the conversion using the purple share button? The screenshot does not indicate that the hipfire 360 distance was matched, as it is about 42 cm vs 22.5 cm. So if you expect the same 360 distance, this conversion will not do it.

When converting between different DPI's as you do here, pixel ratio is completely irrelevant. It will always be different by default since your are moving the same distance with a different DPI on your mouse, so it is expected to change. The pixel ratio is a direct product of the resolution, FOV, DPI and 360 distance, so if you change any of these factors, the outcome will change.

Unfortunately.

I'm getting a slightly different sensitivity every time I start this game, not sure exactly what causes it. So your mileage may vary...

The current entry is correct, but you need to make sure ALL values are according to the output and game notes. That means six values, two settings and FOV. If any of these are off, the calculation will be wrong.

Speed Freeks is added now, aim coming soon!

Aim sensitivity coming soon!

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

I've flipped the calculation around now, so Sensitivity 1 is just the horizontal sensitivity which defaults to 1, and the mouse sensitivity value is being calculated. This should work a bit better.

The previous workaround to calculate the "Mouse Sensitivity" value broke the "All" conversion when it's the source. I've rolled back this workaround now and will see if I can fix it somehow.

You have to set each zoom level individually. Haven't checked thoroughly in the English client yet, but the Chinese one didn't have a scope in this range.

Scratch this, I found a workaround so all sensitivity values are calculated automatically now so it's way more accurate

What you said earlier was correct. Set "Mouse Sensitivity" to 2.72, then the rest of the settings as the calculator output shows.