Hmm, I am having the utmost difficulty converting my Overwatch sensitivity to my siege sensitivity. I have already gone into the config and adjusted the "MouseSensitivityMultiplierUnit" and found everything else to be wayyy too fast. I honestly have no clue what is going wrong with it.

6 hours ago, Kotori_alpha said:

 I have already gone into the config and adjusted the "MouseSensitivityMultiplierUnit" and found everything else to be wayyy too fast. I honestly have no clue what is going wrong with it.

You have to set all the values in the config file exactly as they are in the output of the calculator.

9 hours ago, Kotori_alpha said:

Hmm, I am having the utmost difficulty converting my Overwatch sensitivity to my siege sensitivity. I have already gone into the config and adjusted the "MouseSensitivityMultiplierUnit" and found everything else to be wayyy too fast. I honestly have no clue what is going wrong with it.

given the large difference in fov those two games have this is to be expected

give this a try that should make your hipfire feel "the same " distance and speed wise

if you match 360 distance at different fov's you end up with the same distance at different perceived speeds

Edited May 9, 20215 yr by fortunate reee

7 hours ago, fortunate reee said:

given the large difference in fov those two games have this is to be expected

Hmm, if all else fails I'll just put my FOV down to match it.

The 1x sens feels way too fast for this conversion even with the FOV match @DPI Wizard

Edited May 9, 20215 yr by Kotori_alpha

17 minutes ago, Kotori_alpha said:

The 1x sens feels way too fast for this conversion even with the FOV match @DPI Wizard

That's probably because 1x with your settings in R6 has a wider FOV than hipfire in Overwatch. The calculations are correct, but the perceived and expected sensitivity might be wrong because of the FOV difference. If you instead match hipfire FOV of R6 with Overwatch (70.5628) you will get better and more consistent results.