Jump to content


Photo

Rainbow Six Siege calculations inaccurate


  • Please log in to reply
3 replies to this topic

#1 gzv

gzv

    Newbie

  • Premium Members
  • Pip
  • 11 posts

Posted 05 January 2017 - 08:02 PM

I purchased a subscription here because I can usually use the calculator w/ other games to get the discrepancy very low when I fiddle with DPI and/or distance - I'll allow myself at most 0.5in of variation if I can keep the same sens between games - and I had no other way to get an accurate sensitivity in R6 Siege.

 

However, it seems that the R6 calculator doesn't modify the game's MouseSensitivityMultiplierUnit, so calculations are always rather inaccurate. The best results I can get when converting from 14.5in/360 in CS-GO (Hipfire) to R6 (Hipfire Simple) is 15.7in/360, which is a 7.6903% (1.208 inches) discrepancy! In all other games I can get this to less than 0.1% using between 14-14.5 inches per 360.

 

I don't understand R6's (Hipfire Advanced) setting, it asks me to input a sensitivity even when converting from an existing value.

 

Sorry if this is in the wrong area, but it seems like a bug, since I understand from other sources that modifying MouseSensitivityMultiplierUnit can provide a much more accurate conversion than what I'm getting. Please help & thanks in advance.


Edited by gzv, 05 January 2017 - 09:58 PM.


#2 DPI Wizard

DPI Wizard

    Advanced Member

  • Wizards
  • 1,917 posts

Posted 05 January 2017 - 10:55 PM

When you use the simple calculation for Siege, you only calculate the sensitivity you have access to in-game, and it assumes that all the multipliers are at the default setting (0.02). Since this setting only have 100 steps, it is not very useful for fine tuning. This is why you get the discrepancy, it is the closes it can get with this value alone.

 

If you use the advanced calculation however, it is very accurate, as this calculation uses the multiplier too. So what you need to do when using the advanced calculation is fill in the value it asks for. This value (for hipfire) is your already configured MouseYawSensitivity. It doesn't really matter you have set it too. The output will be what you should set the multiplier too to get the desired sensitivity. The reason you have to enter the configured MouseYawSensitivity is that the sensitivity is a product of both MouseYawSensitivity and MouseSensitivityMultiplierUnit.

 

Tell me if you have any trouble!



#3 gzv

gzv

    Newbie

  • Premium Members
  • Pip
  • 11 posts

Posted 05 January 2017 - 11:52 PM

Ahh, I thought I was missing something w/ the advanced hipfire setting. Thanks so much, this worked perfectly!



#4 DPI Wizard

DPI Wizard

    Advanced Member

  • Wizards
  • 1,917 posts

Posted 05 January 2017 - 11:54 PM

Great!






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users