DPI Wizard

You are correct, here it is the windowed borderless that works correctly, while unchecking it makes it unstable. But I suspect this is a bit dependent on your setup, so if you get random acceleration when windowed borderless I think it's just the same bug as I get when it's windowed. Here's a video of the issue, every time the camera spins here the same script is executed. So as you can see it does first almost two turns (accelerated), then one turn exactly (which is correct), then almost two again (accelerated), then one exactly (correct).

How are you converting between the games? 360 distance or a monitor distance? I'm assuming by lower you mean that PUBG is too slow? Can you link your exact conversion? (Use the purple share button).

This might be depending on your setup (hardware/software), but here I get a lot of random acceleration when the game is not in fullscreen. Are you in windowed or fullscreen? If you still get this in fullscreen I think it's down to an issue with the game unfortunately.

Is your Windows resolution 1920x1080 as well? It seems like the game is affected by both Windows and game resolution when in fullscreen mode.

If you use the config file calculation, the calculator will use the default value of 50 as a placeholder for MouseYawSensitivity, you can just change the to any other value if you're not using 50. The actual sensitivity is a product of all the sensitivity values, so the others will change accordingly if you change the MouseYawSensitivity value.

It isn't affected by polling rate 1000 Hz and below at least, higher I'm not usually testing since there's a lot of issues with it either way. So calculations are still spot on, what is your exact settings?

Nice, updated the calculations now.

Checked it now, and at 1 it is 1:1 with horizontal.

Just check a few aims now, and everything is the same as before as far as I can tell.

Added this and the original. Added.

Just added! View full update

The FOV can only be set in the console. View full update

I think Battlefield 2042 has the most unique settings, while Warzone has the most entries (where several aims use the same setting).

Be sure to check out the instructions thread and this community guide. It's a bit of a read, but to get the best result it's important to know all the different aspects of a conversion. Don't be afraid to ask for help, but if it's an issue with a specific conversion, be sure to include a link to the conversion (use the purple share button) and specify why it seems wrong.

It sort of is, but it's out of necessity to support "everything". Unfortunately there is no single magic conversion that works for everyone, so while the calculator defaults to a conversion that works for a lot of people, it might need to be adjusted depending on your preference

The default setup of the calculator will use 360 distance for hipfire conversions, and the 360 distance does not change between aspect ratios for these games. If you want to keep a consistent say MDH 100% movement (meaning the same movement to the edge of the monitor), you need to set the hipfire conversion to Monitor Distance - Horizontal 100%.

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

The best way would be to convert directly from your BF4 aim to your BF2042 aim using 360 distance, like in this example (with just example values): https://www.mouse-sensitivity.com/?share=899c16566bbd92301f725fd8400eb4c2

I've done some testing now to see exactly what's happening, and this is part a bug in the game and part mis-configuration. The game maxes out at 105 no matter what you set in the config file and what is displayed in-game. So when you enter 106.990274 the calculations will be wrong since the actual FOV in the game is still 105. USA On will calculate the sensitivity based on what is actually applied in the game (i.e. 105), however USA Off will use the configured FOV (i.e. 106.990274) regardless of whether it is valid or not. So in short, you need to use 105 as the game doesn't support any higher

What's your settings? Are you testing with scripts?

Added!