Rainbow Six Siege Ini File
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=0InvertMouseAxisY=0Rumble=1AimAssist=1YawSensitivity=2PitchSensitivity=1DeadzoneLeftStick=15DeadzoneRightStick=15MouseSensitivity=10MouseSensitivityMultiplierUnit=0.019199XFactorAiming=0.266643ToggleAim=1ToggleLean=1ToggleSprint=0ToggleCrouch=1ToggleProne=1ToggleWalk=0AimDownSights=50AimDownSightsMouse=10ControlSchemeIndex=0ControllerInputDevice=0 Edited December 2, 2015 by Israel. Something just feels a little bit off. I use 1 sens and 400 dpi in CSGO.
Mar 18, 2003 Patches. Latest version for the vanilla game is 1.60. Patch for different regions can be found here.If your region isn't in the previous folder (like Czech, Polish and Japanese editions) check here. If you have the Athena Sword DLC, then look here and choose the right version for your game. For other languages check here again. Please beware, that this game is incompatible with MSI.
Rainbow Six Siege Reddit
I used the normal conversion 'not the simple one you added' which with 50 ADS sens gave meMouseSensitivityMultiplierUnit= 0.00256I found out that with a Hipfire sens of 30 converted from the same 1 sens and 400 dpi also gave me MouseSensitivityMultiplierUnit= 0.00256So 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? Kirby's epic yarn wii iso ntsc. Edited December 7, 2015 by Traxilla. 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. 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 had been playing the game fine and when I wanted to play today the settings had reset and I was being put in brazil or us servers rather than my usual eu. I then thought that it could be just not retrieving the settings from the GameSettings.ini file so I tried deleting the Rainbow Six - Siege folder from my games in documents to see if it would create a new one. It didn't which leads me to believe that the game is having some sort of problem accessing my documents and therefore every time I reset the game, the settings also reset.
Rainbow Six Siege Wiki
Rainbow Six Siege Steam
I hope someone can help me on finding a fix to this error as all of my settings reset every time I launch the game.