Several times now I’ve had this issue where the game would not recognise my control bindings after an update, or the game seemingly deleting my control bindings at random. I’ve finally figured out what the reason is and how weird of a reason it is. I suppose this may also be the cause for many other people losing their bindings over the past 4 years.
I have several input devices connected to my PC that have a hardware switch that changes the mode of the device, this will likely also change it’s GUID. For instance I have a gamepad that can switch between PS3 controller mode and generic analog input mode. Also I have rudder pedals that can switch between driving/racing mode and flying mode. There are probably also other factors that could change a device GUID that may affect other people, such as a driver change.
My complaint is basically how the game handles a change in GUID in the .binds file. When a GUID in the .binds file is not recognised the game will proceed to make a backup .binds file and ignore all control bindings in the file with the unrecognised device GUID. Basically the game will not recognise any bindings. Before I discovered this I had to redo all of my control and key binds again which is always very time consuming. In my specific case, only the device GUID of the yaw input (my rudder pedals) had changed which caused the .binds file to be ignored all together, despite all the other bindings being perfectly fine. I managed to correct the issue by manually resetting the affected bindings using Notepad++, after which the .binds file was once again recognised by the game and my most of my bindings were restored. In any case I find this a really illogical and frustrating way of handling this issue.
My suggestion would be for the game to simply recognise and reset the bindings associated with the unrecognised device GUID and keep all the other bindings intact. As an optional ‘would be nice’ you could even let the user know on starting the game that several bindings were reset due to a changing or faulty device ID.
Fixing this issue would make life a lot easier for the not so tech savvy among us. Thanks in advance.
I have several input devices connected to my PC that have a hardware switch that changes the mode of the device, this will likely also change it’s GUID. For instance I have a gamepad that can switch between PS3 controller mode and generic analog input mode. Also I have rudder pedals that can switch between driving/racing mode and flying mode. There are probably also other factors that could change a device GUID that may affect other people, such as a driver change.
My complaint is basically how the game handles a change in GUID in the .binds file. When a GUID in the .binds file is not recognised the game will proceed to make a backup .binds file and ignore all control bindings in the file with the unrecognised device GUID. Basically the game will not recognise any bindings. Before I discovered this I had to redo all of my control and key binds again which is always very time consuming. In my specific case, only the device GUID of the yaw input (my rudder pedals) had changed which caused the .binds file to be ignored all together, despite all the other bindings being perfectly fine. I managed to correct the issue by manually resetting the affected bindings using Notepad++, after which the .binds file was once again recognised by the game and my most of my bindings were restored. In any case I find this a really illogical and frustrating way of handling this issue.
My suggestion would be for the game to simply recognise and reset the bindings associated with the unrecognised device GUID and keep all the other bindings intact. As an optional ‘would be nice’ you could even let the user know on starting the game that several bindings were reset due to a changing or faulty device ID.
Fixing this issue would make life a lot easier for the not so tech savvy among us. Thanks in advance.
