DPI Wizard

It depends on what you want to achieve. As you can see here, the Actual VFOV/HFOV of the aim is different (because of the aspect ratio change), and you are using MDH 0% as the conversion method. That means that the current conversion will keep the horizontal tracking of targets exactly the same, like this:

Confirmed it's the same exact issues. The sensitivity is directly affected by the framerate, making it very unstable and any sensible calculation impossible. Good job on the beta by the devs...

And now for release it's the same exact issues. The sensitivity is directly affected by the framerate, making it very unstable and any sensible calculation impossible. Good job on the beta by the devs...

Unsupported, I will check if anything changed in the release.

MDH 75% for 16:9 is the same as MDH 100% for 4:3, which both are equal to MDV 133.3333%. In all cases it is only this exact movement that is equal, unless the FOV is equal; then every movement will be the same. If you compare MDH 100% on 16:9 to MDV 133% you will get a different result.

That works!

I depends on if it's 4:3 stretched or black bars. If it's back bars, the sensitivity stays exactly the same, the only difference is that you don't see what's behind the black bars. It it's stretched, then the vertical sensitivity stays the same, while the horizontal will be faster. The 360 distance stays the same, but you will get an increased movement over your monitor (compared to the vertical axis) since the image is stretched.

Finally got access now, updated the sensitivity and added all weapons.

Hyenas is updated now, and all weapons are added.

When you enter the same (or no) monitor size, the monitor size is completely ignored in the calculation. But as soon as there is a difference in the monitor size, it will be accounted for based on your conversion setup. So for 360 distance, nothing changes as it will stay the same regardless of monitor size. But for any other method, the FOV is used in the calculation to account for the monitor size difference, and since you don't have the exact same FOV in R6 and Warzone you get this difference.

When you configure the Hdeg 4:3 fot to fov_desired "86.631971" using 6 decimals to get as close as possible to 103 Hdeg 16:9 , you get 70.532801 degrees instead of 70.5328 degrees. Those 0.000001 degrees are 100% negligible, you can't even measure it using scripts so it's in essence exactly the same.

It has zero effect, and the tiny difference is because of rounding. With more decimals the difference would be even smaller. The Auto FOV gives you the closest match within the limitations of the game.

Thanks for letting me know, they changed from MDV 100% to MDV 0%, also hipfire stops scaling to FOV above 80 (the FOV still changes, but the 360 distance remain the same). All is updated now!

Sensitivity 2 is the Coefficient (you can see this in the output), and the 0.68 is the scale for the ADS conversion, where also enter the coefficient so it matches, like this: https://www.mouse-sensitivity.com/?share=f42f0a7af910c8457de15d13bdc1db5a

These four are added!

Just added. View full update

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

Just added. View full update

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