X52 Pro bindings copied over to X52 standard - Anyone know how?

[Andalyn]

So, I got my young son ED. I was able to buy the cheaper X52 from a friend (didn't want to spring for new X52 Pro in case son doesn't get into the game).

I figured that it would be a simple matter of copying my much cherished and hard worked bindings for my X52 Pro over to his computer - and I'd have no problem explaining the controls.

Man, was I wrong. Apparently, there is a conflict. When the custom bindings are selected, it kills the throttle and stick on the son's computer. The X52 doesn't work with those bindings. Select standard ED bindings, and it works.

All of the same buttons are present EXCEPT the programmable buttons on the throttle, so I guess that's the conflict.

But I'm not sure. I've opened up the file in Notepad++ and snooped around, but nothing I modify there seems to do the trick.

Anyone know how to make an X52 Pro bindings file work with the X52 standard? Is there some known method or action to get it to work?

It's gotta be something simple, just can't put my finger on it.

 

[Borgkube]

I have a Saitek X35 (that goes back to pre-windows days), X52, X52Pro, and an X65F. They may look similar but they are not. Personally, I have tried a bunch of things to share/copy profiles between joysticks, and I have never found a way. Eventually, I cut my losses and print out the old profile and then just program the new stick. I have spent way more time trying to copy a favorite profile from one stick to another with no success. Just do it once and make a backup copy.

Maybe someone out there does know how to do it, But I have never found any answer either on the internet or the Saitek web site. Good luck

 

[Valethar]

No known way that I'm aware of, other than the one Borg mentions. The 52 and Pro are separate animals, and there's probably a bunch of internal stuff between them that's not readily apparent that keeps the profiles from one from working on the other. Best advice would be to take a few minutes to rebind the controls on the 52 to match what you have on the Pro.

If you're changing anything from within ED itself, remember to save that binds profile with a unique name. If you don't, you risk losing anything you changed the next time ED updates.

 

[Andalyn]

I had the bright idea just now of using http://www.mcdee.net/elite/ as a visual reference for the Pro binds, and then bring up a separate tab for the X52 binds. Mcdee.net won't even work with the standard X52 binds. Suffers an internal 500 error.

But... I guess I can use the reference page for my binds to copy them manually. *sigh*. I see a lot of alt-tabbing in my future. Might as well get to work.

Thanks guys. If anyone else knows a way feel free to enlighten.

 

[Shadowdancer]

The binds file references devices by name, so replacing all occurrences of "SaitekX52Pro" with "SaitekX52" should make most things work.

 

[Andalyn]

The binds file references devices by name, so replacing all occurrences of "SaitekX52Pro" with "SaitekX52" should make most things work.

Thought I did that via notepad++. Seemed too easy, and it was. Didn't work... but if you have had luck with that - I'll double check and make sure find/replace didn't miss one or muck something up.

 

[Andalyn]

Checking back in - Shadowdancer had the answer. I had incorrectly named the top line "name" on the .binds file. Apparently, the old file lists the name of the HOTAS, but newer files list the name as "Custom".

Renaming all other instances from SaitekX52Pro to SaitekX52 worked. There were a few mismatched binds, where the X52 inexplicably gives different number designations to buttons, but those where easy to chase down.

Thanks for reaffirming the editing of the binds file Shadowdancer!

 

[Shadowdancer]

The "name" attribute for the document is what the profile appears as in the preset selection and gets saved back to disk as. So you could put "My Cool X52" in there and name the file accordingly (should be "My Cool X52.2.0.binds" AFAICT) and you get it as a selection in the dropdown.