Jump to content

SOS

This just in: Another survival game!
Read more...

Freestyle GunZ

Revived old shooter just added!
Read more...

TERA

In-game and config file sensitivity added.
Read more...

Warhammer: Vermintide 2

Added.
Read more...

Metro Conflict: The Origin

Free shooter just in!
Read more...
DPI Wizard

Tom Clancy's Rainbow Six Siege

Recommended Posts

hmmm its not working...  using a conversion from cs go with a value of 2.4

 

it states: Too low sensitivity - Minimum is: 1

You must enter your current sensitivity, and the calculated value you get is the coefficient, MouseSensitivityMultiplierUnit.

csgorainbow.jpg

Share this post


Link to post
Share on other sites

is the one for ads XFactorAiming? because there is 2 in the settings.ini and im confused im assuming this xfactoraiming if for the ads?? So is this correct?? Because if i don't change xfactor then its WAY to slow. is this right?

 

InvertAxisY=0
InvertMouseAxisY=0
Rumble=1
AimAssist=1
YawSensitivity=2
PitchSensitivity=1
DeadzoneLeftStick=15
DeadzoneRightStick=15
MouseSensitivity=10
MouseSensitivityMultiplierUnit=0.019199
XFactorAiming=0.266643
ToggleAim=1
ToggleLean=1
ToggleSprint=0
ToggleCrouch=1
ToggleProne=1
ToggleWalk=0
AimDownSights=50
AimDownSightsMouse=10
ControlSchemeIndex=0
ControllerInputDevice=0

Edited by Israel

Share this post


Link to post
Share on other sites

The problem is i'm trying to find my sensitivity.  Not the MouseSensitivityMutliplierUnit...

I've added Hipfire (simple) and ADS (simple) now, they just calculate the sensitivity assuming you have the coefficient set to the default 0.02 :)

 

is the one for ads XFactorAiming? because there is 2 in the settings.ini and im confused im assuming this xfactoraiming if for the ads?? So is this correct?? Because if i don't change xfactor then its WAY to slow. is this right?

Updated it now, it had the wrong variable. "AimDownSightsMouse" is the correct one.

Share this post


Link to post
Share on other sites

i think XFactorAiming is the multiplier for the AimDownSightsMouse value, you seem to not have that linked correctly? lol Also I found out from a post on reddit that Aim Assist in the options under controller option on the last tab somehow effects the input lag on terrorist hunt and i was skeptical at first but when disabled it and moved the mouse in hipfire again the weird mouse smoothing went away somewhat. Very interesting indeed..

Edited by Israel

Share this post


Link to post
Share on other sites

i think XFactorAiming is the multiplier for the AimDownSightsMouse value, you seem to not have that linked correctly? lol

No, both ADS and hipfire use the MouseSensitivityMultiplierUnit as a multiplier. XFactorAiming may be an additional multiplier, I'm not sure.

Share this post


Link to post
Share on other sites

ah ok gotcha, thanks, so do i have to choose between hipfire and ads if i want the same speed going or what?

You probably want the same 2D distance, right? Meaning same movement to move the crosshair to the edge of the screen. The same 3D distance (i.e. 360 distance) will probably feel to sensitive when aimed.

Anyway, the update I'm working on will make this easier :)

Share this post


Link to post
Share on other sites

ok well what i did was i used something like a 0.039584 coefficient and then made mouse sens 7 and the ads sense 97 which gave me 3.6 on both. the math comes out to within .000009 from hipfire to ads or somethin like that, thats how i did it for now and it works. :) curious to see what you have on the update.

Share this post


Link to post
Share on other sites

No, both ADS and hipfire use the MouseSensitivityMultiplierUnit as a multiplier. XFactorAiming may be an additional multiplier, I'm not sure.

Just to verify this as I just did some tests, all three settings affect ADS sensitivity. That is MouseSensitivityMultiplierUnit, XFactorAiming and AimDownSightsMouse. The calculator assumes XFactorAiming is 0.02 for now, I'm working on adding the support for three variables in the calculator.

Share this post


Link to post
Share on other sites

So you talk about matching 2D distance... I'm not sure what you mean by that. Is that how aiming when scoped in CS:GO works? If so, is there any way to replicate that while ADSing that users can do while you update the calculator?

Thanks :)

Share this post


Link to post
Share on other sites

Something just feels a little bit off. I use 1 sens and 400 dpi in CSGO. I used the normal conversion "not the simple one you added" which with 50 ADS sens gave me

MouseSensitivityMultiplierUnit=0.00256 

I found out that with a Hipfire sens of 30 converted from the same 1 sens and 400 dpi also gave me MouseSensitivityMultiplierUnit=0.00256

 

So i tried to use 30 Hipfire sens, and 50 ADS sens ingame with the MultiplierUnit of 0.00256... The hipfire sens feels right, however when i aim down sights, it just feels waaay too slow. I can't wrap my head around what could be causing this?

Edited by Traxilla

Share this post


Link to post
Share on other sites

Okay, I've been using this tool for a while, and I've noticed a weird issue. Well, basically your calculator doesn't seem to work for this game specifically. I'm trying to convert from CS:GO to this game. In CS:GO, it takes the length of my mousepad (28.9cm or 11.37795 inches) to turn roughly 350 degrees (I shot one bullet at my starting point, and 1 bullet on my end point, and they are roughly 2 bullet marks away - Glock), your engine says 12.1212 inches to turn 360 degrees. This shows that there is some inaccuracy in your calculator, but that is to be expected - especially considering the sensor might be picking up more distance than from edge to edge on my mousepad.

 

The thing is, in Siege using the values provided by your calculator, it is anything but accurate. My GameSettings.ini reads as such under [iNPUT]:

 

 
InvertAxisY=0
InvertMouseAxisY=0
Rumble=1
AimAssist=1
YawSensitivity=2
PitchSensitivity=1
DeadzoneLeftStick=15
DeadzoneRightStick=15
MouseSensitivity=4
MouseSensitivityMultiplierUnit=0.051836
XFactorAiming=0.020000
ToggleAim=0
ToggleLean=0
ToggleSprint=0
ToggleCrouch=1
ToggleProne=1
ToggleWalk=0
AimDownSights=50
AimDownSightsMouse=56
ControlSchemeIndex=0
ControllerInputDevice=0
 
I've bolded the values that are relevant. Your settings give a MouseSensitivityMultiplierUnit (MSMU) of .051836 for a Hipfire sensitivity of 4. This already is inaccurate - my sensitivity is much lower, the turning radius is roughly 320 degrees instead of 350 degrees (with the same distance as mentioned above). Not off by much, but enough. The thing is, the ADS calculation is where it gets really off. Your calculator says that an ADS sensitivity around 55/56 should yield the same MSMU as a Hipfire sensitivity of 4 (with my settings - 500 DPI, 90 FOV, 1920x1080). Using an ADS of 56, the turning radius is barely 200 degrees for a whole mousepad sweep. (Also, the faster I go, the less distance the crosshair ends up covering, strangely - is this an FPS issue?)
 
I have to turn the ADS sensitivity up to 85 in order for it to roughly match - but again, even aiming at the exact same spot at the beginning provides results that vary by as much as 5 degrees in either direction (at the end point). I chalk this up to my mouse sensor picking up signals from the desk as it travels off the pad sometimes but not others. But it also doesn't make sense that speed would negatively affect the distance traveled, specifically in ADS.
 
Any reason why any of this would be happening to me? Here's an imgur gallery of my CS:GO test of sensitivity distance, and R6 tests with and without ADS (with the settings specified above - I am turning clockwise/to the right, as I said the distance traveled by the mouse sensor is roughly 11.3780 inches): http://imgur.com/a/SZOiW

Share this post


Link to post
Share on other sites

Dear DPI Wizard,

 

I figured out where to get all the information about the sensitivity settings but englisch is not my first language and I can't get it to work.In the reddit thread below a Dev explains. I think especially the last part where he goes into detail how ADS works is helpful as he explains xfactoraiming and its relation to the other values:

 

https://www.reddit.com/r/Rainbow6/comments/3vl3yn/calculating_your_exact_mouse_sensitivities/

 

 

My goal is to have the same mouse sensitivity for hipfire and ADS?

 

My current settings for correct hipfire sensitivity is:

 

Tom Clancy's Rainbow Six Siege - Hipfire
Sensitivity:
MouseSensitivity=9
Coefficient:
MouseSensitivityMultiplierUnit=0.016686
360° rotation:
47.2314 cm
Discrepancy:
0 cm

 

The problem for me at the moment is I can either set my hipfire or ADS sensitivity as in CS: GO because I have to set the settings via MouseSensitivityMultiplierUnit in both cases.However from what I understood xfactoraiming is the main multiplier for ADS.

 

 

Here is an explaination of the Dev post by a Youtber called xfactor who was a Beta Tester and responsible that the ADS slider got added (xfactor value in cfg)

 

Edited by reZal-

Share this post


Link to post
Share on other sites

ok, that means ironsights/1x optics have a 0.9 fov multiplier and a 0.6 sens multiplier.

 

imho it's best for muscle memory when fov multiplier and sens multiplier are identical.

in order to achieve this the calculation is:

 

0.9/0.6/0.02=75

 

AimDownSightsMouse=75

XFactorAiming=0.020000

 

the only difference to csgo is that r6 siege uses vertical fov, whereas csgo scales with horizontal fov based on 4:3, but the difference is miniscule.

Share this post


Link to post
Share on other sites

I'm working on an update to the 4.0 alpha calculator now to support three variables, so the XFactorAiming can be accurately calculated.

I was talking with you on converting my BF 4 ADS 360 rotation, which should be 7.81452 based on my understanding [7.0 inch Hipfire 360 x 1.116360 multiplier, using a Coyote sight with non-uniform aiming enabled].  I am using a 800 dpi with a GstInput.MouseSensitivity 0.023050

 

I am trying to achieve the same thing in R6 Siege, using a standard Holographic sight.  I now understand the difference between simple and non-simple for the calculator.  That said, can you confirm if the following settings would achieve my goal.

 

DPI=800

MouseSensitivity=50
MouseSensitivityMultiplierUnit=0.004488
AimDownSightsMouse=50
XFactorAiming=0.055835
 
Thanks... Odedge

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.

×