Custom keybindings wiped

Most people only realize the value of viable backups after situations like this occur. Then they face a choice. Start taking responsibility for your files and back stuff up -or- do nothing, complain and blame others.


I have back-ups!

But why should I need them?

If FDev did the job properly, this should not happen.

I mean - we had an open Beta, so quite a lot of people took part.

Then the final release is done, and some random crazy bugs manifest themselves from the get go.

And you think this is a player failure.

Sorry - no.

This is a total incompetence developer situation, nothing else.
 
Same here. Quite irritating. Hope it's fixed soon.

My experience is I enter hyperspace, pull my hotas throttle to zero, arrive in the new system, the ship hesitates, ignores the throttle's position and starts accelerating for the star, I vaguely panic, push the throttle forward from zero, then back to zero, and the ship finally registers the position of the throttle and slows to a 'halt'.

There's a bug report ....https://forums.frontier.co.uk/showt...nges-not-recognised-applied-while-FSD-jumping
 
I also have my custom binding wiped (thanks FD for playing your game and having this for 4th year in a row! )

Also, now I have a strange glitch on pitch axis - it doesn't react on small increments but starting from some point it react WAAY too much.

Who might know what that is?

UPD. It's actually roll as well. Not too sure what it is. Joystick calibration shows everything as it's supposed to be.
 
Last edited:
To a point, and in general, I agree with you. However..

This is not a new issue here. Given the complexity which can go into mapping controls, especially for us VR users, redoing everything is time consuming to say the least. And absolutely irritating. Even if the Custom key bind filename changes between patches, how flippin' hard can it be to include what seems to me a very simple quality of life tweak to the client patcher?!?

Just strikes me as lazy.

I couldn't agree more!
 
To a point, and in general, I agree with you. However.. This is not a new issue here...

I tend to agree. Although the issue is well known I am surprised that this problem persists without some 'belt and braces' work-around/lash-up in place - even something as simple as an automatic backup of the key bindings folder made and dated by the installer prior to installing.

Mind you, it's not just at upgrade time that the file can get 'wiped'. I have an x-box controller specifically for controlling the external camera, and some months back all these bindings just vanished - I never understood why.
 
I seriously wonder if this is an FD issue. Surely it would happen to everyone? My bindings have never been wiped on any update, but I do religiously back them up just in case...

Cheers
G
 
Had this during beta, for me on a PC, it was fixed by having only ONE "custom2.0.binds" file and ONE "StartPreset.start" file in the "Bindings" folder.

I'd been keeping backups in there previously with number added at front and date at end.

Created a folder in "Bindings" called "bindings.old" and shoved them all in there ... been fine since ... still there after update to 3.0.

Hope that helps. It was someone on the forum during beta that mentioned this, so not my ideas, can't recall who though.
 
I noticed a problem with my Thrustmaster HOTAS, throttle doesn't automatically throttle back when entering a new system. A real problem when I'm flying the T9. I have to put the throttle in reverse to avoid a collison with star, not good.

It isn't supposed to. That was a bug. (and in the 3.0 release patch notes)

You need to zero your throttle on countdown if you want zero throttle on jump exit.
 
Goto C:\Users\yourusername\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings and rename (or copy into) Custom.2.0.binds to Custom.3.0.binds and your done.
 
It isn't supposed to. That was a bug. (and in the 3.0 release patch notes)

You need to zero your throttle on countdown if you want zero throttle on jump exit.

Not necessarily, just tried it and can throttle down in the tunnel and still be at zero (well 30) on exit

Cheers
G
 
Not necessarily, just tried it and can throttle down in the tunnel and still be at zero (well 30) on exit

Cheers
G

That doesn't work for everyone. As opposed to doing that during the countdown which does appear to work for all various inout devices.

Goto C:\Users\yourusername\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings and rename (or copy into) Custom.2.0.binds to Custom.3.0.binds and your done.

I checked my bindings folder before downloading the update and I had backups for every Custom binding file in there. I didn't make those. The naming convention would seem to point to the game itself creating a backup when you save the actual bindings file.

Not sure when that started, but even a file from 2 years ago had a backup.
 
I have such precise yet complex controls.
It is going to take me an hour just to get everything right again.
Especially for SRV and what not.
 
Several bugs here. My case:
I have several bindings for different controllers. Game will check ALL bindings files.
If some controller is not connected, game will create error log and load default connected controller bindings.
Still investigating throttle weird stuff.
 
I did the renaming bit suggested by Vandaahl above, but still nothing. What the f*k, Frontier? I mean don't you people test these things?

EDIT: I opened both my 2.0 and new today 3.0 files. I copied all of the contents of 2.0 file into the 3.0 file and saved. That did it for me. I used Notepad++ to do this operation. Off to see the planets now.

@Frontier: SHAME on you people...shame!
 
Last edited:
Goto C:\Users\yourusername\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings and rename (or copy into) Custom.2.0.binds to Custom.3.0.binds and your done.

I've never had the problem of custom binds disappearing, maybe because I use Dr Kaii's E-D profiler...no idea. I checked my options/bindings folder this evening out of curiosity and I have a custom.3.0.binds folder already there even though I'm still downloading the update on my creaky 19th century t'interweb connection. Might be a legacy of the beta....once again, no idea.
 
Last edited:
Well, I don’t understand it at all. Just looked in the bindings folder, all I have is the custom.2.0.binds file. Everything works fine, just as before :S
Oh well, back to flying...

Cheers
G
 
Unless a game is in alpha or beta, control settings back-ups should certainly never be broken by a patch, its about as critical to keep as player status and his ships....

Especially with an insane forest of poorly sorted settings!

Yeah FD, I recognize your effort at sorting, but its rather pedestrian organization results are really inadequate!
 
Back
Top Bottom