DoritoSlayer

Thanks, you're a legend!

Hope it's fixed for these guys but for me saving it (if you didn't click outside of the entry field) always saved correctly to the config file. Now after the update of an hour ago (1.10 hotfix 2), in the worst case, it rounds to 4 decimals. Indeed as you note, the UI will always round the number regardless of the precision that is saved in config file. Are you able to add a config file option with the data I provided?

@Carlos Resurreccion Yes you can, check the information below and it should be pretty self-explanatory, let me know if you need any help. Please also read my post before yours, where I explain an in-game workaround. @DPI Wizard It would indeed be great if you can add a "config" option for Insurgency Sandstorm. To help you out, here is some information to reference: Config file path (main game) %localappdata%\Insurgency\Saved\SaveGames\Profile Config file path (CTE version of the game) [SteamLibrary]\steamapps\common\sandstorm_beta\Insurgency\Saved\SaveGames\Profile Config file name Controls.json Translation of your website name for multiplier to the config file tag name: Look Sensitivity --> mouseSensitivity Aim Down Sights Sensitivity --> aimingSensitivityScale Scope Sensitivity --> scopeSensitivityScale Focus Sensitivity --> focusSensitivityScale 1.0X Sensitivity Scale --> OneX 1.5X Sensitivity Scale --> OneHalfX 2.0X Sensitivity Scale --> TwoX 2.5X Sensitivity Scale --> TwoHalfX 3.0X Sensitivity Scale --> ThreeX 4.0X Sensitivity Scale --> FourX 6.0X Sensitivity Scale --> SixX 7.0X Sensitivity Scale --> SevenX Note that all these sensitivity value tags except the first one ("mouseSensitivity") exist inside both the mouseSensitivityModifiers "group" as well as gamepadSensitivityModifiers "group". Obviously these need to be adjusted in the mouseSensitivityModifiers part. I've attached the first part of my Controls.json file for reference. Hope this helps SandstormControlsSensitivitiesPartOnly.json

The game will actually write the correct value to the Controls.json file (which can be found here: %localappdata%\Insurgency\Saved\SaveGames\Profile) if you enter the value in the sensitivity entry field and then immediately clicking apply settings. It will always show the rounded value however. Do not click outside of the sensitivity entry field before you click apply settings, then it will save the rounded value. So that's a workaround for now. I've sent the developers a bug report on this issue so hopefully it gets fixed in the near future.

I believe you can select the faction in the training mode and also chose a different training ground (to get two other factions) might be too much but that could give you the ability to do some quick assessment as to what you want to use to do the calculations with.

Haven't played squad in a while, but I don't understand what you mean. I assume you want to show that the magnification is bugged with the screenshots? Can you explain in some more detail what you mean, what is incorrect and what would you expect for instance?

Spawn into Jensons Range, a test range where you can choose faction / role (pick marksman of course)

@DPI Wizard The config file path has changed. From: %LOCALAPPDATA%\Squad\Saved\Config\WindowsNoEditor To: %LOCALAPPDATA%\SquadGame\Saved\Config\WindowsNoEditor

My bad for not understanding correctly in the first place. Thanks for the clarification and for updating this game.

Thanks for the reply. Thanks for pointing me to auto FOV, hadn't tried that feature before. Although I do tend to set this a little narrower for slower paced games. I understand and agree with what you're saying. I was checking the ini just to confirm the "config FOV" is the same value as what you set in-game. Which isn't always the case. To clarify my question is about FOV type, not FOV value. This because the post of @DPI Wizard saying that Insurgency Sandstorm uses vdeg, but it is still set to multiplier. Shouldn't the game be set to FOV type vdeg (so under Game Info header)? Since that is set to multiplier, I'm wondering if the calculations are correct now.

@DPI Wizard Could you please check my previous reply. As I'm now unsure whether to use vdeg or Multiplier as FOV Type since the calculator uses Multiplier but you said it should be vdeg. Unless I'm misunderstanding something. Thanks!

Thanks for the swift reply @DPI Wizard I have my FOV set to 90, couldn't find it in the config files. Turns out it's only in the GameUserSettings.ini if set to something other than default of 90. So, set it to 91 and the line "SoldierFOV=91.000000" appears in the GameUserSettings.ini and set it back to 90 and the line is removed. Anyway, the ini value is the same as what it shows in-game. This has me confused, because under game info I see: "Default FOV: Field of View 90 | Multiplier" So, if I'm understanding you correctly, under input I should set this: FOV 90, FOV Type vdeg (since my FOV is 90 in-game). See screenshot. But the calculation shows: "Config FOV: Field of View 120.000000" Does this just mean you forgot to change the data to say "Default FOV: Field of View 90 | vdeg"? Also there is a note mentioning "set "Scope Setting" (under advanced) to Normal". However changing this setting to Picture-in-Picture does not seem to impact the sensitivity in my testing.

@DPI Wizard First off, thank you for looking at this game! Can you help me understand what happened after the update though? Should I set the FOV Type to vdeg to get accurate results? The readings I now get are in the attached screenshot (or this link) With the same settings I got there readings before the update: Sensitivity 1: Look Sensitivity 0.188571 Sensitivity 2: Aim Down Sights Sensitivity 1 Multiplier 1: Scope Sensitivity 1 Focus Sensitivity 0.800002 1.0X Sensitivity Scale 1.000002 Multiplier 2: 1.5X Sensitivity Scale 1.000002 2.0X Sensitivity Scale 1.000002 3.0X Sensitivity Scale 1.000002 4.0X Sensitivity Scale 1.000002 7.0X Sensitivity Scale 1.000002 Just trying to understand what happened