its been a while but i figured my controls are stored in my backed up ShooterInput.ini file, is this not the case??
i tried replacing the default/patch file with my old backup but my controls are still reset ingame.
am i replacing the wrong file?
can we use an autoexec in order to prevent this stuff from randomly happening every patch?
i dont even feel like playing without my settings :f
Not sure if you checked this already, but delete the shooterinput once again and replace it just like you did before. This time, make absolutely sure it is set to “Read Only” in the file’s properties. That may be the reason that it is changing.
This should work if your binds were actually being read from shooterinput.ini. However, I put in a bug a couple of months ago that showed that shooterinput.ini was not being used by the game for player controls and instead a temp file was being used. I was hoping that was fixed in the more recent update and I haven’t checked if it was but I have an unlisted YT video that shows the bug. I even had a file system checker setup to show that the shooterinput.ini wasn’t being written to or even accessed when you changed binds and wasn’t being read in from after a manual change to the file.
So @capriRocket, you might need to try and rebind everything you had setup in game like normal. And if you had extra stuff in your shooterinput.ini file that you can’t bind with the UI you can still set up your binds through the console.
When I get home I’ll check to see if what I found is still a bug or not.
read only didnt work 
all i find with “sens” in shooterinput is:
m_Options=( OptionType=GameOption_Slider, LabelText=“ShooterGame.SGUIGameOptionsControls.MouseSensitivity”, ID=“mousesens”, Properties=(Min=0, Max=60, Default=40) )
is the sens even stored in there?
This should work if your binds were actually being read from shooterinput.ini. However, I put in a bug a couple of months ago that showed that shooterinput.ini was not being used by the game for player controls and instead a temp file was being used. I was hoping that was fixed in the more recent update and I haven’t checked if it was but I have an unlisted YT video that shows the bug. I even had a file system checker setup to show that the shooterinput.ini wasn’t being written to or even accessed when you changed binds and wasn’t being read in from after a manual change to the file.
So @capriRocket, you might need to try and rebind everything you had setup in game like normal. And if you had extra stuff in your shooterinput.ini file that you can’t bind with the UI you can still set up your binds through the console.
When I get home I’ll check to see if what I found is still a bug or not.[/quote]
Launch the game with ‘-INPUTINI=ShooterInput.ini’ as start option via Steam and place a copy of your ShooterInput.ini in: \Steam\steamapps\common\Dirty Bomb\Binaries\Win32\
This should work if your binds were actually being read from shooterinput.ini. However, I put in a bug a couple of months ago that showed that shooterinput.ini was not being used by the game for player controls and instead a temp file was being used. I was hoping that was fixed in the more recent update and I haven’t checked if it was but I have an unlisted YT video that shows the bug. I even had a file system checker setup to show that the shooterinput.ini wasn’t being written to or even accessed when you changed binds and wasn’t being read in from after a manual change to the file.
So @capriRocket, you might need to try and rebind everything you had setup in game like normal. And if you had extra stuff in your shooterinput.ini file that you can’t bind with the UI you can still set up your binds through the console.
When I get home I’ll check to see if what I found is still a bug or not.[/quote]
Launch the game with ‘-INPUTINI=ShooterInput.ini’ as start option via Steam and place a copy of your ShooterInput.ini in: \Steam\steamapps\common\Dirty Bomb\Binaries\Win32
[/quote]
@fubar That’s awesome if it fixes my issue. The main reason why I found it was because the game is screwing up reloads if you have toggle sprint set to on and you’ve recently sprinted and press crouch while reloading. And I was going to see if there was something I could do with the binds to fix it and that is when I found/tested that shooterinput.ini wasn’t being used at all.
Do you know why shooterinput.ini from the user directory isn’t being used? And I am curious where this fix comes from (you left the [/quote] part in so you snagged it from somewhere). Is it a common issue with UE3 games or is this a DB specific issue?
Thanks!
This should work if your binds were actually being read from shooterinput.ini. However, I put in a bug a couple of months ago that showed that shooterinput.ini was not being used by the game for player controls and instead a temp file was being used. I was hoping that was fixed in the more recent update and I haven’t checked if it was but I have an unlisted YT video that shows the bug. I even had a file system checker setup to show that the shooterinput.ini wasn’t being written to or even accessed when you changed binds and wasn’t being read in from after a manual change to the file.
So @capriRocket, you might need to try and rebind everything you had setup in game like normal. And if you had extra stuff in your shooterinput.ini file that you can’t bind with the UI you can still set up your binds through the console.
When I get home I’ll check to see if what I found is still a bug or not.[/quote]
Launch the game with ‘-INPUTINI=ShooterInput.ini’ as start option via Steam and place a copy of your ShooterInput.ini in: \Steam\steamapps\common\Dirty Bomb\Binaries\Win32
[/quote]
@fubar That’s awesome if it fixes my issue. The main reason why I found it was because the game is screwing up reloads if you have toggle sprint set to on and you’ve recently sprinted and press crouch while reloading. And I was going to see if there was something I could do with the binds to fix it and that is when I found/tested that shooterinput.ini wasn’t being used at all.
Do you know why shooterinput.ini from the user directory isn’t being used? And I am curious where this fix comes from (you left the /quote part in so you snagged it from somewhere). Is it a common issue with UE3 games or is this a DB specific issue?
Thanks![/quote]
I’m confused, what quote part? I snagged it from my own config’s readme 
Whenever someone first figured out you could load autoexec’s I tried and see if UE3 has any other variables that lets you execute configs via launch up. And, it does - been using it ever since. All it took was to figure out which folder it operates in, much like the autoexec it looks for it in Steam rather than Documents, simple enough to test though. -ENGINEINI=loltest.blah and it’ll automatically create the file.
https://udn.epicgames.com/Three/CommandLineArguments.html#User
Sorry, was reading another thread in another tab and it had a quote in it and my brain was braining. My bad. I was wanting to read the resource the info came from and you linked it so my thanks!
