Evening all been playing via steam now for about 4000 hours and thought I grab a second cmdr via the free epic version, I was wondering will the Epic version store its own binding or will it overwrite my steam ones if I use a different controller for each account
Epic and Steam
- Thread starter kinglemo2000
- Start date
I not sure as the binding are stored on my C drive in my pc user profile and not in the game folder on the drive it is installed
Indeed, that would be my guess too - the bindings and journal files all live in the user profile directory, so those will probably be the same across all installs.
I'm still waiting to hear if anyone manages to get EGS and Steam to use a common install location though. I'd just as soon not have two parallel copies of ED taking up space on my computer.
Back up your original bindings. When I launched epic version for the first time it messed them up, but once I replaced them both versions are using the same bindings correctly
I run both steam and epic accounts on my laptop. No issues with binds whatsoever. They are identical
But today was a particularly bad day to multicrew the 2 accounts. The main account (the host) crashed with purple python or purple cobra on like 80-90% of the drops from supercruise to a massacre mission uss
But today was a particularly bad day to multicrew the 2 accounts. The main account (the host) crashed with purple python or purple cobra on like 80-90% of the drops from supercruise to a massacre mission uss
Still having issues with this.
I deleted (after backing up) my bindings in %LOCALAPPDATA%\Frontier Developments\Elite Dangerous\Options\Bindings) .
Launching my steam version, all is well with the default control scheme and my XBox PC controller. Epic Games however still results in a very confused controller that selects and cancels in the UI (lobby menu is fine, ingame not), with my 'A' selection button acting as comms panel focus; it works fine as the default select button in Steam ED.
More to the point, when I go to redefine controller binds in Epic Games ED, setting anything results in it creating that button/stick/whatever with a modifier. E.g.trying to set 'panel select' to button A results in it being defined as Button A + Enter. Pic attached.
I deleted (after backing up) my bindings in %LOCALAPPDATA%\Frontier Developments\Elite Dangerous\Options\Bindings) .
Launching my steam version, all is well with the default control scheme and my XBox PC controller. Epic Games however still results in a very confused controller that selects and cancels in the UI (lobby menu is fine, ingame not), with my 'A' selection button acting as comms panel focus; it works fine as the default select button in Steam ED.
More to the point, when I go to redefine controller binds in Epic Games ED, setting anything results in it creating that button/stick/whatever with a modifier. E.g.trying to set 'panel select' to button A results in it being defined as Button A + Enter. Pic attached.
Attachments
Finally fixed this. I had to set up the Epic Games launcher to run through my Steam library ('add a non-Steam game'), which resolved the controller conflict. EG has next to no controller support options, so this is the only way to sort out the issue for now. No more weird modified binding issues or double-bound controls.
I found the cause for this.
I've had this issue with PS4 and PS5 controllers on PC and finally identified the problem. Epic and Steam use different IDs for the same device.
They do use the same folder in the windows user profile and access the same files, but in the game it only shows binding profiles that match available devices.
For example, my PS5 controller is identified as "054C0CE6" by E
in Epic, but as "28DE11FF" in Steam. Therefore, the key binding I created in the Epic version, which references the device ID 054C0CE6, will not show when I launch E through Steam, where the game identifies the very same controller as 28DE11FF. Here an excerpt of the bindings file:
<YawAxisRaw>
<Binding Device="28DE11FF" Key="GamePad_LStickX" />
One possible solution, depending on the controller device, is to create a copy of the bindings file, open it in Notepad and replace all references to the device ID with the ID used by the other service. A quick ctrl+h and Replace all does that in 5 seconds.
This solved it for my PS4 controller, but not for the PS5 controller. A second layer of inconvenience can be the "Key" variable. In my case, for the PS5 controller Steam and Epic also use different labels for the keys/buttons on the controller.
Example YawAxisRaw
<YawAxisRaw>
<Binding Device="054C0CE6" Key="Joy_XAxis" />
<YawAxisRaw>
<Binding Device="28DE11FF" Key="GamePad_LStickX" />
You can see in Epic the same axis of the right stick is called Joy_XAxis, while Steam gave it the less than identical label GamePad_LStickX. Further complicating the transition. In this case the binding profile is visible in the other service, but empty where gamepad buttons were defined.
I went on to manually set up my steam binding and make sure backup both versions for my Epic and Steam profile, but it seems an easier way to workaround these differences in the services it so simply run them both via Steam.
This has driven me crazy for many months now and I couldn't find a clue to this anywhere. So, I hope this gives some insight to those with the same problem.
I've had this issue with PS4 and PS5 controllers on PC and finally identified the problem. Epic and Steam use different IDs for the same device.
They do use the same folder in the windows user profile and access the same files, but in the game it only shows binding profiles that match available devices.
For example, my PS5 controller is identified as "054C0CE6" by E
in Epic, but as "28DE11FF" in Steam. Therefore, the key binding I created in the Epic version, which references the device ID 054C0CE6, will not show when I launch E through Steam, where the game identifies the very same controller as 28DE11FF. Here an excerpt of the bindings file:<YawAxisRaw>
<Binding Device="28DE11FF" Key="GamePad_LStickX" />
One possible solution, depending on the controller device, is to create a copy of the bindings file, open it in Notepad and replace all references to the device ID with the ID used by the other service. A quick ctrl+h and Replace all does that in 5 seconds.
This solved it for my PS4 controller, but not for the PS5 controller. A second layer of inconvenience can be the "Key" variable. In my case, for the PS5 controller Steam and Epic also use different labels for the keys/buttons on the controller.
Example YawAxisRaw
<YawAxisRaw>
<Binding Device="054C0CE6" Key="Joy_XAxis" />
<YawAxisRaw>
<Binding Device="28DE11FF" Key="GamePad_LStickX" />
You can see in Epic the same axis of the right stick is called Joy_XAxis, while Steam gave it the less than identical label GamePad_LStickX. Further complicating the transition. In this case the binding profile is visible in the other service, but empty where gamepad buttons were defined.
I went on to manually set up my steam binding and make sure backup both versions for my Epic and Steam profile, but it seems an easier way to workaround these differences in the services it so simply run them both via Steam.
This has driven me crazy for many months now and I couldn't find a clue to this anywhere. So, I hope this gives some insight to those with the same problem.