BMS Key File Editor
-
When using the BMS Key File Editor how do you properly import a custom file.key that you have already worked with. I know how to input a file.key but every time I import a custom file.key I have to start from scratch because they dont seem to import into the DX Settings/Device gray input fields area. It does show up in the show imported callbacks, well except for any callbacks that i configured to POV?
Is this the way it is supposed to work?
-
POV import for DX devices doesn’t work atm.
Will be fixed in U1.I can only assume that your device order has changed.
Thus you have to set the DX devices in order how it is in your key file, import the callbacks to your devices and than change the device order to the current setting. -
I can only assume that your device order has changed.
Thus you have to set the DX devices in order how it is in your key file, import the callbacks to your devices and than change the device order to the current setting.So when I import a file.key its should put the callbacks in the editor gray area?
I am using the CH stick&throttle and the device number did not change since in the DX setting area they are listed as one device as controller # 1 & 2
-
You have to import the dx stuff seperately because with the current “logic behind” it is not possible to tell, if DX button #1 (for example) is device e.g. HOTAS Cougar.
So once a key file is imported you have to check the DX Settings Tab. Chose your controller, set the DX device order accordingly and import either manually ort via the macro functions.
So, for DX two steps are needed. -
Kolbe i apologize here but I have been doing as you stated. After setting keyboard and choosing DX device I import in the Keystroke Editor. Then I go to the DX Setting tab and select primary input device “CH FS&PT”. I then select controller # 1 and 2 (1=fighterstick & 2=prothrottle).
Then I go into my device setup page with the print layout. In the Device A & B editor area it always shows the default callbacks? I want to know if it should show the imported callback, so I can load and continue to tweak a custom file.key or is it suppose to show the default callbacks. It is a pain in the ars to keep starting from scratch and want to find a solution to just start editing where my last file.key left off…thank for you help.
-
There are two methods of importing key files.
They are described in the Key File Editor Manual.pdf, located in …/Docs/Key Files & Input/ folder.
See pages 8-40 and 10-47. -
i have read this manual 5 times it does not address my question.
It really is a simple question. Imported file.key that have been customized already are not editable? I have to start from scratch every time yes or no?
I may have a corrupted BMS.Key File Editor…
-
i have read this manual 5 times it does not address my question.
It really is a simple question. Imported file.key that have been customized already are not editable? I have to start from scratch every time yes or no?
I may have a corrupted BMS.Key File Editor…
No, you do not have to start from scratch every time. I just imported a custom keyfile and was able to edit the DX buttons on the tab for that HOTAS.
-
No, you do not have to start from scratch every time. I just imported a custom keyfile and was able to edit the DX buttons on the tab for that HOTAS.
Thank you!
Then my BMS.Key File Editor must of gotten corrupted. How can I get a new one without having to reinstall BMS again?
-
Thank you!
Then my BMS.Key File Editor must of gotten corrupted. How can I get a new one without having to reinstall BMS again?
There’s a copy here, with my keyfile/profile: http://firstfighterwing.com/VFW/downloads.php?do=file&id=147
You could download it and then throw all the other stuff away to get the spreadsheet. It does have a custom keyfile in it, but if you import yours and change the main DX devices, it should overwrite all that, I think. Other than getting a copy from someone else, I don’t know any other way except do another BMS install.
Obviously you’ve learned the same way I did (
) to save a ‘good’ copy of Kolbes spreadsheet just in case. -
I just bought you a virtual beer brother… that did the trick. I racked my brain a couple of times trying to figure out why I was such a dumb ass for not figure this out. All this time the file was corrupt… man that sucks I could of been flying instead.
Thank you!