Migrating binds from X55 to X56 HOTAS

[CMDR JONNYMAC]

Hi, my X55 died and I've ordered an X56

What is the best method for migrating my existing X55 binds to the X56?

e.g do I edit the .binds file and change all instances of X55 to X56?

Thanks and stay dangerous
CMDR JONNYMAC

 

[STRONTIUM DOG]

I am not sure how different the inputs etc are(PID) or weather your existing binds are even compatible see my guide for backing up an swapping out binding folders
so your existing binding folder and files are renamed and stored safely away before experimenting with the new stick
if the old binds don't work use the N.B. method so you have a default folder and default custom3.0 bind file ready for rebinding at least then you will have a good old backup to maybe do the go compare thing as you say......

lost your binds? want hasstle free backed up binds look no further

keybindings can reset if you visit the control section without one of your usual devices used to play the game ie hotas , xbox pad etc not plugged in or at that present moment is undetected by windows as it thinks your just using keyboard and mouse it simply rewrites your binds for you...

forums.frontier.co.uk

hope all goes well...…………..

 

[CMDR JONNYMAC]

I am not sure how different the inputs etc are(PID) or weather your existing binds are even compatible see my guide for backing up an swapping out binding folders
so your existing binding folder and files are renamed and stored safely away before experimenting with the new stick
if the old binds don't work use the N.B. method so you have a default folder and default custom3.0 bind file ready for rebinding at least then you will have a good old backup to maybe do the go compare thing as you say......

lost your binds? want hasstle free backed up binds look no further

keybindings can reset if you visit the control section without one of your usual devices used to play the game ie hotas , xbox pad etc not plugged in or at that present moment is undetected by windows as it thinks your just using keyboard and mouse it simply rewrites your binds for you...

forums.frontier.co.uk

hope all goes well...…………..

Thanks I'll back up existing binds prior to X56 installation but hoping someone can answer my question.

 

[Bravo17]

If the button and axes numbering is the same between the two sticks then in theory you should be able to update all of the device ids in the file and it should work.

You can find out the device id of the x56 by creating a temporary custom binds file and binding one button and axes from each controller and then work out what needs replacing from the old x55 binds file

 

[STRONTIUM DOG]

Thanks I'll back up existing binds prior to X56 installation but hoping someone can answer my question.

yea hopefully someone has taken the same upgrade route just an x box pad user myself so it would be pure speculation on my part

 

[CMDR JONNYMAC]

If the button and axes numbering is the same between the two sticks then in theory you should be able to update all of the device ids in the file and it should work.

You can find out the device id of the x56 by creating a temporary custom binds file and binding one button and axes from each controller and then work out what needs replacing from the old x55 binds file

Thanks for the suggestion; certainly worth a try thanks.

 

[STRONTIUM DOG]

what I find strange about myself is by the time if i did copy device ids over to another bind file etc
I could actually rebind all my controls faster from just muscle memory inc all my flight sims too ect as I bind the controls basically the same for every game I own
I find the re binding process hardly taxing at all ,but for most it does seem to be a major pain and thus I is strange

 

[Bravo17]

what I find strange about myself is by the time if i did copy device ids over to another bind file etc
I could actually rebind all my controls faster from just muscle memory inc all my flight sims too ect as I bind the controls basically the same for every game I own
I find the re binding process hardly taxing at all ,but for most it does seem to be a major pain and thus I is strange

You can use the editor replace function, so once you have the values it should be just one operation per controller, or two if they have split out the axes from the buttons for some reason'

 

[STRONTIUM DOG]

whilst far more efficient to just use a backup and or file manipulation
I could completely rebind elite from mem in under 10 mins anyway so no big deal for me either way I suppose

 

[SMcA]

You can use the editor replace function, so once you have the values it should be just one operation per controller, or two if they have split out the axes from the buttons for some reason'

For editing I use XML Notepad free from M$. It is chock full of tools. It has a compare function which will highlight changes. (When you select the file to compare with. You need to select view all files as it does not recognise binds as a default.)
I think you should be okay with replacing SaitekX52Pro with SaitekX56 (I have a pro)

 

[CMDR JONNYMAC]

Thanks Guys for all your suggestions; yes I was able to use an editor "WinMerge" to rename all instances of X55 to X56 and all appears as before but will need to test fully.
Strangely my old hotas was a Saitek X55 and the new hotas is a Logitech X56 but the new binds refer to Saitek X56 and not Logitech X56, no matter as it works anyway but just an observation.

<Binding Device="SaitekX56Joystick" Key="Joy_RZAxis" />

 

[SMcA]

Thanks Guys for all your suggestions; yes I was able to use an editor "WinMerge" to rename all instances of X55 to X56 and all appears as before but will need to test fully.
Strangely my old hotas was a Saitek X55 and the new hotas is a Logitech X56 but the new binds refer to Saitek X56 and not Logitech X56, no matter as it works anyway but just an observation.

<Binding Device="SaitekX56Joystick" Key="Joy_RZAxis" />

Thanks for reporting back. It is good to know.
The Saitek X5n has a history of changing manufacturers. I bought mine from Mad Katz but it was branded Saitek. I imagine Logitech wanted to get away from the reputation of a bad build quality. So changed the name but the ID is the same.