New controller and the keybind file madness.. help

Hi Emanuelom,

It sounds like the game is still validating the controller's GUID in addition to the device numbers, which would explain why simply changing the binding device IDs isn't enough.

A couple of questions:

• Is the new controller the exact same model as the old one, or a different model/manufacturer?
• When you open the newly generated binds file, does it contain a different GUID than the old file?

I've seen cases where Elite Dangerous refuses to load a custom binds file if the device GUID in the file doesn't match the hardware currently connected, even if the button mappings themselves are valid.

One thing I would try is comparing the old and new binds files side by side and looking specifically for any GUID or device name entries that still reference the old controller. Sometimes there are more references than just the obvious device numbers.

If the new controller is a different model entirely, the game may consider it a completely different device and reject the old profile unless all references are updated correctly.

Out of curiosity, what controller are you moving from and to?