Bindings problem since PS4>PC copy

[Bummer]

I copied my PS4 Commander to PC (Steam VR) along side my existing PC (Steam VR) Commander. All seemed to go well. Switching Steam accounts allowed me to play either Commander. A quick test showed no problems evident with either account.

Since the copy I've been playing the exPS4 commander, building a "myHOTAS" binding based on the ThrustMaster4 bindings, using the DS4 for on foot. Works great. Makes both EDO and Voice Attack happy.

When I change accounts and log into the original PC commander I appear to be presented with a generic list of bindings. "myHOTAS" is not there. I modified the Thrustmaster bindings, which changed its name to Custom in the game. I saved out then went to check the file in the standard ED directory - Custom.4.0.bind had been touched. Reloaded EDO, and Custom was not on the list of bindings. That appears to be the directory to which it saves, but it does not appear to include the existing bindings from that directory when loading its list.

I searched posts and found nothing relevant, so, just me?

Am I missing something obvious? Not obvious?

 

[GraphiteGB]

Are you running EDO on both accounts after Paying for the upgrade on both accounts to have Walkies mode...
EDH PC 4.0 does not have EDO functions so once you upgrade to EDO its likely the custom binds can not be down graded so are not loaded in....
thats my guess.. unless you have EDO on both now...

 

[Pharreze]

I don't play in VR so I'm not sure if there are any different considerations... but re-naming my bind files anything other than "custom.4.0" and "custom.3.0" has solved most if not all of my 'confused bindings' problems between accounts & EDO/EDH...

Edit: NB change the filenames and the name in the file itself, one of the very first lines, so they'll show up in settings under the appropriate name.

 

[Bummer]

Are you running EDO on both accounts after Paying for the upgrade on both accounts to have Walkies mode...
EDH PC 4.0 does not have EDO functions so once you upgrade to EDO its likely the custom binds can not be down graded so are not loaded in....
thats my guess.. unless you have EDO on both now...

Odyssey on both accounts. Both accounts load and play Odyssey. It's just the bindings on the one account. I'd be willing to write off not getting out of my vehicle in that copy - I never do anyway. Never cared about first person shooters, so it's easy to ignore. Still, as an old computer nerd who once played in machine code, the problem itches and can not be allowed to continue indefinitely.

I don't play in VR so I'm not sure if there are any different considerations... but re-naming my bind files anything other than "custom.4.0" and "custom.3.0" has solved most if not all of my 'confused bindings' problems between accounts & EDO/EDH...

While in the problem account I changed the vanilla Thrustmaster 4 settings to add the on foot stuff using the DS4. It automatically changed the name at the top to Custom. After I saved I checked in the standard directory and the Custom.4.0 file had been written to at that time. There was no "Custom" choice on the game's displayed list to begin with, though it is in the normal directory. When I reloaded, the game was back to the full original list of options with no Custom, and of course no HOTAS or myHOTAS customized files. Meanwhile the copied account works out of the standard Bindings directory as the game always has, using my custom bindings file.

There is a directory that contains a large number of controller bindings covering quite a few devices. I'm guessing that when a user first launches ED(O) it polls the OS for attached hardware and offers a list from that directory they hope covers the user's stuff. It probably does this each time to catch plug/unplug events. The user picks one which is then used as the default. That file is copied to the Bindings directory, which the game is then supposed to use, but in only one of my accounts actually does. The other appears to start fresh every time.

Or not. Next stop, do it one more time for verification of reproduceability, then Bug Report land. Thanks for the help, folks.

 

[Pharreze]

It probably does this each time to catch plug/unplug events

Yeah, idk about the technical explanations but this certainly fits with my experience, at least. Whenever I forgot to connect the DS4 or didn't have DS4Windows running or whatever, even sometimes after a restart or momentary disconnection, the game forgets. This, among other reasons, has led me to largely abandon the DS4 for this game, but I did get a system in place that worked while I was using it, more below.

There was no "Custom" choice on the game's displayed list to begin with

I found that having any other file in my %LOCALAPPDATA%\Frontier Developments\Elite Dangerous\Options\Bindings called 'custom' anything invariably threw the game(s) off, so I started from scratch:
First, I backed up whatever bindings I thought I might want or need, and then I opened up the preset bindings that you mentioned in ProgramFiles\Frontier\EDLaunch\Products\elite-dangerous-64\ControlSchemes (and the same for EDO) and pasted the old "custom" files that I had backed up, without the ds4 binds, into the preset called "Blank" or "empty," and renamed it "pharreze.FEDS.4" and another copy "pharreze.FEDS.3" [I use FEDS instead of WASD, not the Federation lol]
Then I deleted everything from my %localappdata% bindings folder, including startpreset.start and startpreset.4.start, and added only my two new files. Then I loaded both games, confirmed that they were present, backed out again and added the "Uniquely named and sourced from 'Empty'" bind files with the DS4 bindings to the game and selected them as default. This worked for me, and having a backup uniquely named custom file without DS4 binds seems to allow the game to fall back on that if the DS4 isn't connected, AND recognise when it is connected. If it doesn't I have the unique DS4 files in an easily accessible folder on my desktop so I can just drop the file in to the %localappdata% bindings folder if the game should forget, but I don't think that's happened other than right after update 11 or 12.

So sorry for the disjointed wall of text; think i got everything & i can clarify anything later if needed, just a little rushed. I hope it helps you or any console transferee getting used to the wacky world of EDO bindings. there are also many threads dealing with this issue from the 'old days' when the game would forget custom binds like every other second-all with info that might help.
~07!

 

[Bummer]

Thanks. o7

 

[Bummer]

Yeah, idk about the technical explanations but this certainly fits with my experience, at least. Whenever I forgot to connect the DS4 or didn't have DS4Windows running or whatever, even sometimes ======8<-------EDO bindings. there are also many threads dealing with this issue from the 'old days' when the game would forget custom binds like every other second-all with info that might help.
~07!

Thought I'd mention that I finally figured out what was wrong. Well, I got it working, anyway.

I had been using the DS4 controller emulating an XBOX controller. I retired the DS4 and started using an XBOX controller. I went through my HOTAS binds file and changed the DS4 references to XBOX references. I cleaned up the directory (moved the safety saves) and fired it up with the account that had been working - no problems. Changed Steam accounts and logged into my original PC account where the problems had been. No problems.

I don't really know if it's Steam, the DS4Windows program, or ED itself, but both accounts now work, so it'll do.

 

[Pharreze]

Thought I'd mention that I finally figured out what was wrong. Well, I got it working, anyway.

I had been using the DS4 controller emulating an XBOX controller. I retired the DS4 and started using an XBOX controller. I went through my HOTAS binds file and changed the DS4 references to XBOX references. I cleaned up the directory (moved the safety saves) and fired it up with the account that had been working - no problems. Changed Steam accounts and logged into my original PC account where the problems had been. No problems.

I don't really know if it's Steam, the DS4Windows program, or ED itself, but both accounts now work, so it'll do.

Amazing! Guess it's time for me to invest in that xbox elite controller.... but thumbsticks! gah. glad you got it sorted