Editing a bindings file for a replacement controller?
- Thread starter Angus
- Start date
I haven't done that, but that's how I would go about it:
backup your old file, plug in new controller, start the game and change one obvious setting, binding it to the controller, then save.
Open new bindings file and check the modified entry.
I've noticed that every device is identified by a name (like "keyboard")
fex: <Primary Device="Keyboard" Key="Key_E" />
or in case of stick, some kind of code:
fex: <Secondary Device="044FB106" Key="Joy_POV1Down" />
Than it should be just a matter of replacing that code in old bindings file with the code for new controller and replacing the newly created file.
As I said, I haven't done that, so I can't say for sure it would work, but maybe give it a try?
backup your old file, plug in new controller, start the game and change one obvious setting, binding it to the controller, then save.
Open new bindings file and check the modified entry.
I've noticed that every device is identified by a name (like "keyboard")
fex: <Primary Device="Keyboard" Key="Key_E" />
or in case of stick, some kind of code:
fex: <Secondary Device="044FB106" Key="Joy_POV1Down" />
Than it should be just a matter of replacing that code in old bindings file with the code for new controller and replacing the newly created file.
As I said, I haven't done that, so I can't say for sure it would work, but maybe give it a try?
I did this recently by first editing out all the bindings associated with my old stick, then adding my new bindings in-game.
The button assignments etc. won't always be so similar that you can just replace the old device name with a new one; in the long run it's simpler to nuke them from orbit
.
The button assignments etc. won't always be so similar that you can just replace the old device name with a new one; in the long run it's simpler to nuke them from orbit
.Sorry, I'm probably being thick, but how is that different from starting from scratch? Cheers.I did this recently by first editing out all the bindings associated with my old stick, then adding my new bindings in-game.
The button assignments etc. won't always be so similar that you can just replace the old device name with a new one; in the long run it's simpler to nuke them from orbit
Sorry, I'm probably being thick, but how is that different from starting from scratch? Cheers.
It's different if you have one or more other devices, like your throttle, keyboard, or mouse, and you want to keep all those bindings the same.
I (sort of) tried to do this when I swapped my T16000M stick for a VKB Gunfighter. Other peripherals stayed the same, so mappings to KB&M and the TWCS throttle (that was part of the original Hotas).
I guess I could have spent the time to try and edit the file in notepad, but in the end, what I did was back up my existing bindings (just in case), print out my existing bindings to a PDF file, plug in the new stick to see whether I could somehow persuade the game to just let me bind new control mappings that were no longer there... Didn't work, wouldn't see old binds file, nor the one I hopefully renamed to VKBCustom...
In the end, I simply started from scratch, going down the list from the PDF file and setting the new stick up from scratch. Took perhaps an hour or so, so your mileage will vary depending on how much time you want to spend editing the binds file as opposed to just running down the list of what you currently have bound and re-doing it.
Also, some of the things I had bound I realized that I no longer used / needed, and other things changed a bit because the new stick had two additional hats that I could use for things currently bound elsewhere, so basically I cleaned my bindings up as well. This may not be the case for you of course.
I guess I could have spent the time to try and edit the file in notepad, but in the end, what I did was back up my existing bindings (just in case), print out my existing bindings to a PDF file, plug in the new stick to see whether I could somehow persuade the game to just let me bind new control mappings that were no longer there... Didn't work, wouldn't see old binds file, nor the one I hopefully renamed to VKBCustom...
In the end, I simply started from scratch, going down the list from the PDF file and setting the new stick up from scratch. Took perhaps an hour or so, so your mileage will vary depending on how much time you want to spend editing the binds file as opposed to just running down the list of what you currently have bound and re-doing it.
Also, some of the things I had bound I realized that I no longer used / needed, and other things changed a bit because the new stick had two additional hats that I could use for things currently bound elsewhere, so basically I cleaned my bindings up as well. This may not be the case for you of course.