Recently, I just moved from the Saitek (MadCats) X-55 Hotas to the newer Grey Model of the Saitek X-56 (Logitech) Hotas.
One of the things I realized immediately was that the "default" Elite ControlShemes for the Saitek X56 was missing one important thing. It has no "keyboard" mapped keys at all. This meant that I would have to reprogram the binds file from scratch, looking up all of the "keyboard" default control keys. Nuts to that.
I also realized that I had been using the "default" ControlScheme provided by Elite for the SaitekX55. The "default" ControlSchemes are located at (depending on your installation) in one of two locations.
1) Drive:\SteamLibrary\steamapps\common\Elite Dangerous\Products\elite-dangerous-64\ControlSchemes
or
2) Drive:\Program Files (x86)\Elite Dangerous\Products\elite-dangerous-64\ControlSchemes
Trick#1
So, rather than reprogram the SaitekX56.binds file from scratch, or allow it to create a "custom.binds" file and keep track of that one as well as backing it up, I decided to create a new binds for the SaitekX56 by using the "default" ControlScheme for the SaitekX55.binds, which will save a ton of work on my part.
To do this, I deleted the copy of the "default" ControlScheme for the SaitekX56.binds file and then made a copy of the SaitekX55.binds file, renaming it to SaitekX56.binds.
Now, the only things left to do were to edit the new SaitekX56.binds file, as well as edit the "StartPreset.start" file.
The first thing to change is the files header, which identifies it as a "default" ControlScheme for Elite.
To do this, edit the new copy of the file you made and renamed to "SaitekX56.binds"
Open the file in notpad or your favorite text editor and change the following line.
1) <Root PresetName="SaitekX55" SortOrder="0"> (Before)
2) <Root PresetName="SaitekX56" SortOrder="0"> (After)
Now, while the file is open for editing, in notepad, using the "Edit/Replace" function on the menu, replace all occurences of "X55" with "X56", then save the file.
Now, in Elite's control menu, you will see the new "default" ControlScheme called "SaitekX56".
The new "default" ControlScheme" for the SaitekX56.binds will be availabe to Elite for further modifications.
Of course, since this new bind file came from the "default" ControlScheme for the SaitekX55.binds file, it will only be missing the settings for the two new thumb control hats which the X55 does not have. You can now program them to suit your needs, but you will not have to program the "default" ControlScheme for the SaitekX56.binds with all of the missing default "keyboard" key mapping which the SaitekX55.binds had. This will save you a ton of programming and since you edited the copy in Elite's ControlScheme's directory, any custom binds file you make from it, will contain both the default keyboard key mapping and any changes you made to it.
Trick#2
So, you can now make a "custom.binds" file, program it to your liking, make a copy of it, rename it to "SaitekX56.Binds" and replace the "default" ControlScheme with your new file.
Trick#3
If you use VoiceAttack, the Customizer will allow you to select the SaitekX56.binds file from Elite's "default" ControlSchemes, for which it will then make a custom.binds file and rename it to "HCS SaitekX56.3.0.binds" and copy it to the proper location for use by Elite's control menu. By having Elite's "default" ControlScheme copy of the SaitexX56.binds file programmed with your changes, you can now select the Elite "default" ControlScheme file directly for the changes HCS will make.
Tip: ALWAYS, ALWAYS, ALWAYS, back up your binds files, as well as editing the file called "StartPreset.start" with the name of the binds file you want to use before Elite starts. This file can be found at Drive:\Users\User-Profile-Name\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings. This location is also where the HCS Customizer will store a copy of the HCS edited copy of the "default" ControlScheme binds file it uses to make it's custom.binds file.
Hope this helps someone......
o7....
One of the things I realized immediately was that the "default" Elite ControlShemes for the Saitek X56 was missing one important thing. It has no "keyboard" mapped keys at all. This meant that I would have to reprogram the binds file from scratch, looking up all of the "keyboard" default control keys. Nuts to that.
I also realized that I had been using the "default" ControlScheme provided by Elite for the SaitekX55. The "default" ControlSchemes are located at (depending on your installation) in one of two locations.
1) Drive:\SteamLibrary\steamapps\common\Elite Dangerous\Products\elite-dangerous-64\ControlSchemes
or
2) Drive:\Program Files (x86)\Elite Dangerous\Products\elite-dangerous-64\ControlSchemes
Trick#1
So, rather than reprogram the SaitekX56.binds file from scratch, or allow it to create a "custom.binds" file and keep track of that one as well as backing it up, I decided to create a new binds for the SaitekX56 by using the "default" ControlScheme for the SaitekX55.binds, which will save a ton of work on my part.
To do this, I deleted the copy of the "default" ControlScheme for the SaitekX56.binds file and then made a copy of the SaitekX55.binds file, renaming it to SaitekX56.binds.
Now, the only things left to do were to edit the new SaitekX56.binds file, as well as edit the "StartPreset.start" file.
The first thing to change is the files header, which identifies it as a "default" ControlScheme for Elite.
To do this, edit the new copy of the file you made and renamed to "SaitekX56.binds"
Open the file in notpad or your favorite text editor and change the following line.
1) <Root PresetName="SaitekX55" SortOrder="0"> (Before)
2) <Root PresetName="SaitekX56" SortOrder="0"> (After)
Now, while the file is open for editing, in notepad, using the "Edit/Replace" function on the menu, replace all occurences of "X55" with "X56", then save the file.
Now, in Elite's control menu, you will see the new "default" ControlScheme called "SaitekX56".
The new "default" ControlScheme" for the SaitekX56.binds will be availabe to Elite for further modifications.
Of course, since this new bind file came from the "default" ControlScheme for the SaitekX55.binds file, it will only be missing the settings for the two new thumb control hats which the X55 does not have. You can now program them to suit your needs, but you will not have to program the "default" ControlScheme for the SaitekX56.binds with all of the missing default "keyboard" key mapping which the SaitekX55.binds had. This will save you a ton of programming and since you edited the copy in Elite's ControlScheme's directory, any custom binds file you make from it, will contain both the default keyboard key mapping and any changes you made to it.
Trick#2
So, you can now make a "custom.binds" file, program it to your liking, make a copy of it, rename it to "SaitekX56.Binds" and replace the "default" ControlScheme with your new file.
Trick#3
If you use VoiceAttack, the Customizer will allow you to select the SaitekX56.binds file from Elite's "default" ControlSchemes, for which it will then make a custom.binds file and rename it to "HCS SaitekX56.3.0.binds" and copy it to the proper location for use by Elite's control menu. By having Elite's "default" ControlScheme copy of the SaitexX56.binds file programmed with your changes, you can now select the Elite "default" ControlScheme file directly for the changes HCS will make.
Tip: ALWAYS, ALWAYS, ALWAYS, back up your binds files, as well as editing the file called "StartPreset.start" with the name of the binds file you want to use before Elite starts. This file can be found at Drive:\Users\User-Profile-Name\AppData\Local\Frontier Developments\Elite Dangerous\Options\Bindings. This location is also where the HCS Customizer will store a copy of the HCS edited copy of the "default" ControlScheme binds file it uses to make it's custom.binds file.
Hope this helps someone......
o7....
Last edited: