Insurgency: Sandstorm

Wow that was fast

Hello, I'm trying to convert my sens from Rainbow Six Siege. In the first image, the Look Sensitivity 0.245553 is good. But I want the ADS to feel the same, so I tried the settings shown in the second image. It lowered the Look Sensitivity which is not what I want -- I only need my aim to feel right when aiming down sights.

As for the last two images, I assumed those settings were for anyone who wanted the 1:1 feel between hipfire and ADS. Since I like my Rainbow Six ADS on 65 rather than 71, I just calculated 65/71 = 0.915 then multiplied that factor with the default 1.0X, 1.5X, etc. sensitivities.

Is this the correct method? Because it still doesn't feel right, but maybe I need to get used to the higher FOV.

Hello again. I like the 1.0X Sensitivity Scale, but 1.5X and up are too slow. Do I just adjust them until they feel right or is there something I can do with the calculator?

Could you add ironsight "Aim" option because pistol ironsight FOV is different than 1.0x?

@DPI Wizard The Cold Blood 1.9 update just released today so now is a good time to revisit Insurgency: Sandstorm. The patch brought some additional field of views and zoom sensitivities with the addition of new sights as well as toggleable zoom levels on some of the existing optics.

@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

14 hours ago, DPI Wizard said:

The FOV Type has changed. It used to be Hdeg 4:3 in the calculator, but this was wrong compared to what the game actually uses. It uses a multiplier for vdeg, so this changes the calculations slightly since the FOV was wrong before.

Your new screenshot is what's correct assuming you also configure the FOV accordingly (98.319727).

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

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!

On 10/12/2020 at 22:36, markvvaals said:

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-sensitiviPicture does not seem to impact the ty in my testing.

1.you don't really have to modify the settings.ini on this case the game lets you use multiple decimals even when entered in game 

2. you should use the fov value you like not the games base fov  this mostly serves as a reference 

----------------------------------------------------------------------------------------------------------------------------

 as a user there is little reason to touch the  setting , if you have 1 game you wish to match with insurgency 

(using apex  as an example , which uses a multiplier since the games in game default values are messed up ie 90 isnt actual 90 

 lets say this is apex 90 an i want the same fov but i dont know the fov type of either game 

we just use auto fov and set it to a fov type like vdeg for which we know the 90 fov value for which in this case is 73.74 and thus we will never have to worry about matching fov ever again (there is no reason not to use auto fov  )

------------------------------------------------------------------------------------------------------------------------------------------

tested the values a couple of days ago and besides of insurgencies horrible in game performance the inputs/fov felt correct when applied through in game 

1 hour ago, fortunate reee said:

1.you don't really have to modify the settings.ini on this case the game lets you use multiple decimals even when entered in game 

2. you should use the fov value you like not the games base fov  this mostly serves as a reference 

----------------------------------------------------------------------------------------------------------------------------

 as a user there is little reason to touch the  setting , if you have 1 game you wish to match with insurgency 

(using apex  as an example , which uses a multiplier since the games in game default values are messed up ie 90 isnt actual 90 

 lets say this is apex 90 an i want the same fov but i dont know the fov type of either game 

 

we just use auto fov and set it to a fov type like vdeg for which we know the 90 fov value for which in this case is 73.74 and thus we will never have to worry about matching fov ever again (there is no reason not to use auto fov  )

 

------------------------------------------------------------------------------------------------------------------------------------------

tested the values a couple of days ago and besides of insurgencies horrible in game performance the inputs/fov felt correct when applied through in 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. 

1 hour ago, DPI Wizard said:

No, I said it uses a vdeg multiplier. Meaning that the FOV value you set in the game is a multiplier for the actual vertical FOV you get. The devs did this to (in a very clunky way) try to get "close" to CSGO in terms of FOV value.

I think their thought process was that CSGO uses a 4:3 based FOV, so if we multiply the vertical FOV by 3/4 we get the same thing... Which is not correct. But it's what the game uses. So if you set a FOV of 100 in-game, what you actually get is 100*0.75 which is 75 vdeg.

My bad for not understanding correctly in the first place.

Thanks for the clarification and for updating this game.

The newest update seems to have ruined the sensitivity slider and automatically rounds up my sensitivity of 0.485571 to 0.5

4 minutes ago, Cyani said:

The newest update seems to have ruined the sensitivity slider and automatically rounds up my sensitivity of 0.485571 to 0.5

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.

@DPI Wizard Hi, Sandstorm now seems to round off sensitivities to the first decimal place. Is there anyway we can set the values in a config file?

1 hour ago, Carlos Resurreccion said:

@DPI Wizard Hi, Sandstorm now seems to round off sensitivities to the first decimal place. Is there anyway we can set the values in a config file?

@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

15 minutes ago, DPI Wizard said:

This bug seems to be fixed now, when I enter 6 decimals and click apply it registers correctly in the config file. The UI rounds to 4 decimals.

Does it work for you now?

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?

1 hour ago, DPI Wizard said:

Just added it 

Thanks, you're a legend!

8 hours ago, DPI Wizard said:

 

This bug seems to be fixed now, when I enter 6 decimals and click apply it registers correctly in the config file. The UI rounds to 4 decimals.

Does it work for you now?

Are the values for TwoHalfX and ThreeX supposed to be the same?