It doesn’t seem to work however. The ones I’ve tried so far are:
Bindings=(Name=“F11”,Command=“SetFovSensitivityScale 30”)
Bindings=(Name=“F11”, SetFovSensitivityScale 30)
I’ve been using the ShooterInput file to add these bindings and I’ve tried both Read only checked and unchecked, so I think I’ve made an error in the binding code. Anyone could help me out?
P.S. I know I’ve used incredibly high numbers, but that’s just the easy way of checking if the binding works ingame.
Bindings=(Name=“F11”,Command=“SetFovSensitivityScale 1”)
Make sure to replace any and all F11 bindings.
Also, only values between 0 and 1 can be used. ie. 0.1, 0.3, 0.7
Yeah that’s the exact line of code I used before, but it isn’t working. Also checked for other F11 bindings, but there are none. Anyone else with any input why my binding isn’t working?
I use this:
Bindings=(Name=“F10”,Command=“BloomSize 0 | FogDensity 0 | ColorGrading 2 | SetFOVSensitivityScale 0.15 | RawInputUpdateTest true | Stat FPS”,Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False)
It goes at the very bottom of [ShooterGame.SGPlayerInputPawn]
You cannot use a number exceeding 1. You can use between 0 (mouse doesn’t move) and 1(equal to your non iron-sighted sensitivity. For some reason, Unreal Engine zooms you in but doesn’t reduce sensitivity, essentially increasing it. The number you choose is multiplied by your sensitivity and thus lowers it. 0.1 seems like it will decrease it a lot, but it really doesn’t due to how UE works. Anything above 0.3 is barely noticeable.
Guess I placed it at the wrong section of the config, seems to work perfectly now. Thanks @Harlot.
But you can change the fovsensitivityscale to numbers exceeding 1, it just gets ridiculously fast. Or at least the high numbers work for me, but might be different for you. But then again, I only used the number 30 to easily check if it worked. I actually also normally use 0.15 so could just copy paste yours. 
Also didn’t know about the colorgrading stuff before, also really liking that one. So thanks for that aswell.
[quote=“EdSir;57776”]Guess I placed it at the wrong section of the config, seems to work perfectly now. Thanks @Harlot.
But you can change the fovsensitivityscale to numbers exceeding 1, it just gets ridiculously fast. Or at least the high numbers work for me, but might be different for you. But then again, I only used the number 30 to easily check if it worked. I actually also normally use 0.15 so could just copy paste yours.
Also didn’t know about the colorgrading stuff before, also really liking that one. So thanks for that aswell.[/quote]
Anytime. You just need to press that binding once at the start of a game and it will carry through your entire session, up until you close DB. And yes, colorgrading 2 is much needed to remove that awful blue/red filter they put over everything.
[quote=“Harlot;57784”][quote=“EdSir;57776”]Guess I placed it at the wrong section of the config, seems to work perfectly now. Thanks @Harlot.
But you can change the fovsensitivityscale to numbers exceeding 1, it just gets ridiculously fast. Or at least the high numbers work for me, but might be different for you. But then again, I only used the number 30 to easily check if it worked. I actually also normally use 0.15 so could just copy paste yours.
Also didn’t know about the colorgrading stuff before, also really liking that one. So thanks for that aswell.[/quote]
Anytime. You just need to press that binding once at the start of a game and it will carry through your entire session, up until you close DB. And yes, colorgrading 2 is much needed to remove that awful blue/red filter they put over everything.[/quote]
Yeah no worries, I know how bindings work. I’m familiar with bindings in Quake III Arena, but the coding is way different here which is why I asked 
And yeah, the color difference is huge.
I might hook that bind onto an existing command - such as pulling out my knife - like I have with hide minimap tbh. Luckily the command is remembered from previous launches but it is still slightly annoying.
Many people do this as well. I considered just applying it to my knife, but I’m now trained to see that my FPS counter missing and press it.
… and you never know, what’s beyond next patch.
Is RawInputUpdateTest working now correct on every launch? (Didn’t test it anymore, but recently found out, the game now saves setting of mousesmoothing below 0.3 correctly g.)
Btw: @Devs … Stuff like this could be something to increase the size of your patchnotes.