Monitor Distance Matching Across games/sights

[jabbothehut]

Just a quick question. When MM% across games, what is the correct process? Do you match from game A hipfire to game B ADS or do you matrch from game A hipfire to Game B hipfire and then from game B hipfire to game B ads? 

Asking because I have noticed different multipliers being given when converting from csgo to rainbow six siege. If I convert from csgo hipfire straight to rainbow six ads I get a higher  multiplier tahn if done from rainbow six hipfire to ads. Hope this makes sense and any help is appreciated.

[potato psoas]

Well you should really match from Game A hipfire to Game B hipfire first because otherwise your hipfire will be wrong. Then you can convert from Game A hipfire to Game B ADS because you usually have to input the hipfire sensitivity into the calculator to find the ADS sensitivity. If you want your hipfire to be converted differently then you can still convert from Game A hipfire to Game B ADS as long as the hipfire is what you want it to be.

Edited April 10, 2018 by potato psoas

[Drimzi]

It shouldn't matter. The whole point of monitor match is that a sensitivity is tuned in such a way that it always takes the same mouse distance to rotate to a certain screen distance away from the crosshair. Any difference is likely due to the discrepancy of the input game.

[jabbothehut]

Ok I understand what you guys are saying but then why do I get such large differences between matching different fov's of the same game. For example if I match R6s hipfire (73.74 vfov) to iron sights (66.37 vfov)  I get 0.726617 as my xfactoraiming. However if I match hipfire fov at 73.74 vfov to hipfire fov but at 66.37 fov I get a 360 value that would require an xfactoraiming multiplier of 0.726647 to achieve. 

I don't understand why the value changes so much if that makes sense. Any help would really be appreciated.

[Drimzi]

Ok I am seeing the same thing. Maybe it's an error in the code or just discrepancy. In the end it probably doesn't matter much.

edit: Nevermind, had typo in calc. Here are my results. They are all the same. Any difference is just discrepancy.

 

Edited April 10, 2018 by Drimzi

[jabbothehut]

Glad it isn't only on my end! Which one would you recommend? Matching at 0% between game A hipfire and game A ads?

[DPI Wizard]

It's not an error, but down to what the calculator is matching. For Drimzi's examples the first two calculations are matching 4.2203 cm for 56.25% MM, while the last one is matching 4.2204 cm.

@jabbothehut can you post screenshots of your conversions?

[jabbothehut]

1 hour ago, DPI Wizard said:

It's not an error, but down to what the calculator is matching. For Drimzi's examples the first two calculations are matching 4.2203 cm for 56.25% MM, while the last one is matching 4.2204 cm.

@jabbothehut can you post screenshots of your conversions?

It'll have to be tonight when i get home but it is essentially what Drimzi posted in the 2nd and 3d screenshots. Csgo to r6 irons is faster than r6 to r6 irons.

 

Edit: it is just discrepency and I think I'm being too picky in this case. 

Edited April 10, 2018 by jabbothehut

[jabbothehut]

@potato psoas @Drimzi @DPI Wizard Just wanted your opinion on this guys; 

When I convert my hipfire to rds at 0% screen matching on rainbow six siege using the formula which DPIWizard provided me with (tan(106.26degrees/2)/tan(98.6degrees/2))*77.3461, I obtain an answer of 88.7038584629

This comes out as needing a multiplier of 0.726632 when inputted into the calculator as a "360 distance answer" as follows:

 Tom Clancy's Rainbow Six Siege - Iron sight

Sensitivity 1:

MouseYawSensitivity=1

Sensitivity 2:

AimDownSightsMouse=2

Multiplier 1:

MouseSensitivityMultiplierUnit=0.012896

Multiplier 2:

XFactorAiming=0.726632

Ratio:

1 cm mouse movement = 1.6091 cm crosshair movement

360° distance:

88.7039 cm

 

Discrepancy: 0% (0 cm)

Config FOV:

Field of View: 73.74

Actual VFOV:

66.37 degrees

Actual HFOV:

98.6 degrees

However when I convert purely using the calculator I get these results:

 Tom Clancy's Rainbow Six Siege - Hipfire

Sensitivity 1:

MouseYawSensitivity=1

Multiplier 1:

MouseSensitivityMultiplierUnit=0.012896

Ratio:

1 cm mouse movement = 1.6091 cm crosshair movement

360° distance:

77.3461 cm

Config FOV:

Field of View: 73.74

Actual VFOV:

73.74 degrees

Actual HFOV:

106.26 degrees

 

 Tom Clancy's Rainbow Six Siege - Iron sight

Sensitivity 1:

MouseYawSensitivity=1

Sensitivity 2:

AimDownSightsMouse=2

Multiplier 1:

MouseSensitivityMultiplierUnit=0.012896

Multiplier 2:

XFactorAiming=0.726617

Ratio:

1 cm mouse movement = 1.6091 cm crosshair movement

 

Discrepancy: 0% (0 cm)

360° distance:

88.7058 cm

Config FOV:

Field of View: 73.74

Actual VFOV:

66.37 degrees

Actual HFOV:

98.6 degrees

I know that the discrepancy lies within the decimal places and that I am maybe being too picky but when you get used to a sensitivity, any slight deviation is noticeable so it would be nice to invest effort into the more accurate multiplier. Thanks for your time guys.

[Drimzi]

Your manual conversion is low precision. 73.74 vfov is not exactly 106.26. Also the sensitivity value and DPI combo is not exactly 77.3461 cm circumference.

 

Edited April 11, 2018 by Drimzi

[jabbothehut]

5 minutes ago, Drimzi said:

Your manual conversion is low precision. 73.74 vfov is not exactly 106.26. Also the sensitivity value and DPI combo is not exactly 77.3461 cm circumference.

 

Gotcha! So the calculator method is the way to go then?

 

Edited April 11, 2018 by jabbothehut

[Drimzi]

Just now, jabbothehut said:

Gotcha! So the calcumator method is the way to go then?

 

Yes, it will have full precision, not using rounded numbers as a base for calculations.

[jabbothehut]

Awesome thank's so much for your time! 

[Drimzi]

No problem