DPI Wizard

I just tried it again now, and no decimals beyond what the game writes itself is applied to the sensitivity. They might be in the config file, but have no effect on the actual sensitivity.

Thanks, fixed it now. The "All" conversion contained an invalid reference.

This is a bug, can you share the calculation that causes this?

It depends on what you mean by same sensitivity, matching scopes using 360 distance gives you pretty much no consistency. Ideally you should use the same FOV, but you can keep the same 360 distance and use 90, yes.

It depends on a lot of factors, like your DPI, how fast and far you generally move your mouse, your hardware and the games you are playing. Generally you won't feel much difference between 500 Hz and 1000 Hz, but the aforementioned factors may affect your results both ways.

You are not using 360 distance to convert the sensitivity, you are using MDV 0% in this example. This will keep the tracking speed the same, but the 360 distance will change depending on the FOV. The aim you have selected is using the ADS conversion, but there's also a hipfire option for Shoulder Aim. 360 distance is generally only recommended for hipfire and in some cases ADS. If you want to keep your 360 distance the same, you should select the "Shoulder Aim (Hipfire)" option, and set the "Hipfire / Look" conversion to 360 distance. As for what you should use for ADS and Scope, that depends on you preference. If you already have ADS and scope settings in Hunt you would like to keep, do share them and I can help you set up the calculator to match your settings as close as possible.

www.toyheroes.net does not accept my email domain when registering (great design...), so I'll wait for the Steam release.

These three are added.

There's a small amount of smoothing, expect some discrepancy. View full update

See the game notes for instructions as the config file can easily become corrupted. View full update

Unsupported.

No need to mate

Absolutely, this work fine!

It definitely does not work by setting it in the config file on an unmodded version. I have not tried with a mod though, but if you can set in in the console, can you see a FOV change from 1.65 to 1.7?

The game doesn't support it, 1.642857 is the maximum. Any higher will not make a difference in the game, but calculations will be wrong if you use it in the calculator, hence the strict enforcement of the range.

Ok, it might seem a bit counter-intuitive, but what you have to do is to set the FOV in MW to 65 Hdeg 4:3 for the conversion, since this is the actual source Legacy MW uses. This way all the ADS sensitivity for MW is calculated to 1 as you can see, and the scopes in BF2042 will perfectly match them. Note that I've also set the "Soldier Zoom Aim Sensitivity" to 200 for the scopes to be in range. https://www.mouse-sensitivity.com/?share=c8bbf0ff6161ab5f9aab591312f68a42

What are your ADS Sens. Multipliers in MW, all set to 1?

Can you share what you have tried using the purple share button?

There was a bug where the correct conversion method was not applied, it is fixed now.

Since your settings isn't in line with any of the conversion methods directly, you can play around with the numbers and see how close you can get. This is pretty close: https://www.mouse-sensitivity.com/?share=25e490cc4a0cd7d203fa71c19d806cba

What are your settings in game, and how did you set up the calculator? Use the purple share button to link to your conversion.

These bugs as well as the input bug should be fixed now, but do report in if you see anything else not working!