December 1, 20196 yr Using these settings currently: 400 DPI MouseSensitivity=50 MouseYawSensitivity=50 MousePitchSensitivity=50 MouseSensitivityMultiplierUnit=0.003750 XFactorAiming=0.020000 AimDownSightsMouse=83 (With testing 83.33* is perfect 360 on 1x scopes, reason I use it) This is the highest sensitivity I have ever had that has had so much control and precision with fast mouse movement. However I am having trouble having it feel the same in any other game. Modern Warfare (2019) is the closest where a 360 distance is applicable. CS:GO for example, the trace aim with hipfire is incredibly unsteady when a 360 distance conversion (400 DPI, 2.44 In-Game) is used and flicks are off too. I have meddled with Monitor Distance 0-100%, but have not received any results that look anything remotely like it should be. So my question is how do I use monitor distance settings properly to get a 0% MM for example. Are there any problems with R6S on this calc in particular? Are there any other sens matching techniques based on FOV? Thanks if you can help or add clarity Edited December 1, 20196 yr by REYOU
December 1, 20196 yr 14 hours ago, REYOU said: Using these settings currently: 400 DPI MouseSensitivity=50 MouseYawSensitivity=50 MousePitchSensitivity=50 MouseSensitivityMultiplierUnit=0.003750 XFactorAiming=0.020000 AimDownSightsMouse=83 (With testing 83.33* is perfect 360 on 1x scopes, reason I use it) This is the highest sensitivity I have ever had that has had so much control and precision with fast mouse movement. However I am having trouble having it feel the same in any other game. Modern Warfare (2019) is the closest where a 360 distance is applicable. CS:GO for example, the trace aim with hipfire is incredibly unsteady when a 360 distance conversion (400 DPI, 2.44 In-Game) is used and flicks are off too. I have meddled with Monitor Distance 0-100%, but have not received any results that look anything remotely like it should be. So my question is how do I use monitor distance settings properly to get a 0% MM for example. Are there any problems with R6S on this calc in particular? Are there any other sens matching techniques based on FOV? Thanks if you can help or add clarity csgo uses 73.740000 vertical fov ( if you set your siege fov in your ini to that things should be closer) ┬┴┬┴┤(・_├┬┴┬┴┬┴┬┴┤ ͜ʖ ͡°) ├┬┴┬┴
December 1, 20196 yr Author 2 minutes ago, fortunate reee said: csgo uses 73.740000 vertical fov ( if you set your siege fov in your ini to that things should be closer) issue is, i like what siege is currently and want that to apply to other games.
December 1, 20196 yr 15 minutes ago, REYOU said: issue is, i like what siege is currently and want that to apply to other games. if you are on 16;9 use 0% match for ads if you want to stay at 1;1 360 distance for ads you will have to match the fov for ideal tracking ┬┴┬┴┤(・_├┬┴┬┴┬┴┬┴┤ ͜ʖ ͡°) ├┬┴┬┴
December 2, 20196 yr Author i tried 74 fov on r6s with current setup, it has the same feel as cs on same 360 so there is some correlation. maybe vfov is important for me. 74 is very hard for me to aim.
December 2, 20196 yr 10 hours ago, REYOU said: i tried 74 fov on r6s with current setup, it has the same feel as cs on same 360 so there is some correlation. maybe vfov is important for me. 74 is very hard for me to aim. ideally you should use the config file for your fov, sieges 90 fov would be 120 in csgo they just use different fov methods , you will get used to it and your aim should be good in both games ┬┴┬┴┤(・_├┬┴┬┴┬┴┬┴┤ ͜ʖ ͡°) ├┬┴┬┴
Create an account or sign in to comment