February 5, 20215 yr I have been using Warface default 15 sens to calc my new sens in other games because I realized I never changed it. In the past I had used it to calculate my siege sens. I recently bought a new computer and calculated new sens for siege and it is insanely high now. I am using the same mouse at the same 400 dpi with the removed windows 10 acceleration mod. I was using the config file and I don't know what changed. Any help would be appreciated.
February 5, 20215 yr Some pictures of the intended calculation and what you put into the config file would be helpful. It sounds like maybe you changed the MouseYawSensitivity without changing the MouseSensitivityMultiplierUnit. You can get finer granularity by setting your intended sensitivity lower than the default 50 in the calculator to get a more accurate calculation with less discrepancy (I set mine to 1). As another aside, your sensitivity may feel slower or faster depending on what the FOV of the game is. Warface has a locked fov of 60 vertical degrees. Siege has a FOV slider in the options menu which is in vertical degrees aswell, so setting that to 60, or using one of the Viewspeed calculation options will give you better results.
February 5, 20215 yr Author Attached is the calc im getting now. I managed to find a backup of my siege config file and was confused as to why the calculation changed.
February 6, 20215 yr It seems you were doing different calculations in the past. By leaving the FOV in the R6 sections of the input as default (60) and Selecting Hipfire instead of ADS in the Warface section, you get your expected calculation of .003487. Keep in mind that the calculator settings above the inputs will also change the output (matching to viewspeed instead of 360 distance etc.) It may be helpful for you to read through the conversion options section of this post.
February 6, 20215 yr 11 hours ago, Readesu said: Attached is the calc im getting now. I managed to find a backup of my siege config file and was confused as to why the calculation changed. you should set xfactor to its default value of 0.02 unless the site gives you something different , after the scope changes the calculations often don't use that slider anymore further 4:3 stretched and 16: wont feel the same no matter what you do even if you weren't using stretched going from 60fov to 90 fov is a huge jump that will end up over complicating life this is much more helpfull than a simple picture ┬┴┬┴┤(･_├┬┴┬┴┬┴┬┴┤ ͜ʖ ͡°) ├┬┴┬┴
Create an account or sign in to comment