BMS Key File Help
-
A .key file contains callbacks’ assignments in sections.
The first section is the keyboard’s one and the following according to your hardware.
The keyboard’s section can have all the commands if you choose the Full option or some if you use Basic.
Then we deal with the hardware:
First configure all of your different hardware in the DX settings tab.
Then assign your callbacks to buttons in each hardware’s specific tab.
(Check the graphical map in each tab to make sure you assigned as needed).
After you chose your local keyboard, your keyboard extent, configured DX settings and assigned each hardware you go to the output tab and copy paste. -
Thanks Polaris,
I’ll give it another try once I get home tonight.
I thought that when I add the cougar for instance, all the callbacks should be correctly assigned for this device already or do I need to that manually for each button? Same for the MFDs.
All the best,
Uwe
-
hoover use the Dunc_DX files provided. Cougar & MFDs are all set up for you. Just add the G25 buttons in SETUP > CONTROLLERS.
-
hoover,
You’re welcome !
As Darkman said most is already assigned (unless you wish to personalize it more, add shifted layers…).
The tabs you need to check are TM Couger and L&R MFSs.
What I think happened is you didn’t set your devices in the DX Settings tab: TM Cougar as Primary and enter the correct Windows controller numbers.
The MFDs, both, in the second line (1st additional device) and their windows controller numbers respectively.
And so on and so forth for other devices.
Don’t forget to choose the Full keyboard in advanced settings in the Keystrokes editor tab.Good luck
-
Thanks again… I’m tearing my hair out on how to get a default “basic” keyfile into the left part of the keystroke editor table 8(
I’m using libreoffice 4.5, I have allowed macros globally but when I click on “import file”, I do not get an open file dialog, instead nothing happens.
I’ve tried importing a keyfile the “non macro users” way (opening a keyfile in notepad++ and pasting it on the “import” tab), but the only keys that get picked up from the key files are in the very first section of the keyfile (“UI & 3rd party software”), nothing else shows up below.
I’m feeling extremely stupid ATM but then again I have only very basic spreadsheet knowledge, my expertise lies elsewhere I guess. 8(
Cheers, Uwe
-
No need to feel stupid!
Well…I did when I first got into BMS…or any other sim for that matter.
What I know about Kolbe’s work is after reading his manual and dealing with his DX generators for the past 2 years.
But…why would you need to import anything?
Just get into the Keystrokes tab and choose the Full keyboard as I explained by left clicking the grey Advanced push button (the same tab where you choose your locale).
The output tab shall build itself automatically as you proceed.
As for libreoffice…,I work with Microsoft so I don’t know if it has anything to do with it, or if some of the macros don’t work with it.
Make a copy of the excel file and mess around with it until you get to know it…or break it in the process
When finished… Make another copy…for work and not training and implement what you learned. -
Either modify the BMS - Full keyfile or go to \Falcon BMS 4.33\Docs\Key Files & Input\Dunc_DX and use that. Why are you making life more difficult than it needs to be?
-
Thanks again Polaris. My best bet is that I indeed broke the sheet with earlier experiments, I think I’ll start from scratch. The manual mentions the sheet is optimized for use with libreoffice, so I think this should not pose a problem.
When I go to the keystrokes tab, select “default” and then any of the layouts (basic, full, etc), the left part of the table never changes, only the middle part.
Cheers, Uwe
-
Either modify the BMS - Full keyfile or go to \Falcon BMS 4.33\Docs\Key Files & Input\Dunc_DX and use that. Why are you making life more difficult than it needs to be?
Actually I’m wondering that too.
Thanks, Uwe
-
hoover,
You should choose Full on the left in the opened section when you click the advanced settings button.
As for why deal with it…because it’s not complicated (not knowing how to doesn’t mean it’s difficult) and…what you gain is the understanding of how to better configure your system as you progress with BMS and make it suit your needs better.
It will take you a few more minutes…and for that you shall gain a tool you could mold to your needs and gain so much more.
Just my two cents -
hoover use the Dunc_DX files provided. Cougar & MFDs are all set up for you. Just add the G25 buttons in SETUP > CONTROLLERS.
So is it safe (again) to use the in-game UI to assign buttons? I remember reading somewhere that it’s not advised to use this part of the controller setup (esp. saving the file from there), but that may have changed with 4.33 (the new manual also doesn’t contain any notes on this matter).
It’d be great if the dunc_dx profile set up the mfds correctly, too, I guess it can’t hurt to give it a try, yet I’m with Polaris here that I’d actually like to know what’s going on w/r to Kolbes tool.
I’ve edited keyfiles in emacs in the past, assigning buttons to callbacks and so on, so at least I know this part of the equation a bit, but with recent changes in 4.33 it looks like I’m forced to start fresh.
All the best,
Uwe
-
hoover,
You should choose Full on the left in the opened section when you click the advanced settings button.
That’s part of my problem right there: No section opens when I click the “advanced settings” button, I’ve also tried ctrl-clicking it with the same (non- result.
Uwe
-
Well…one culprit found…
Take the file and put it under the desk>mark it>change to A-G>and release a simple MK-82 even with a CCIP.
Watch it with the TGP to make sure it’s destroyed.
Go back to the BMS folders and make a new copy…play with it and then destroy it as mentioned before.
Go back the last time (hopefully ) to making another copy and implement what you learned. -
So is it safe (again) to use the in-game UI to assign buttons? I remember reading somewhere that it’s not advised to use this part of the controller setup (esp. saving the file from there), but that may have changed with 4.33 (the new manual also doesn’t contain any notes on this matter).
I’ve had no problems assigning buttons from my G25 shifter (and wheel) and additional buttons on my MFDs.
It’d be great if the dunc_dx profile set up the mfds correctly…
It’s great, it does, so does the Full keyfile. Just make sure your Cougar is #1 controller as usual.
-
Hi Kolbe
I have the curser StopMovement issue but I’m not sure what you mean by Shift Y. I have tried using Shift Y in game with no results. Can you please expand on the instructions so I can get this cursor working? Thanks in advance
-
Hi Kolbe
I have the curser StopMovement issue but I’m not sure what you mean by Shift Y. I have tried using Shift Y in game with no results. Can you please expand on the instructions so I can get this cursor working? Thanks in advance
The StopMovement callback is currently not implemented correctly -> doesn’t work atm.
Will be fixed in U1 -
It’s great, it does, so does the Full keyfile. Just make sure your Cougar is #1 controller as usual.
Hoover,
or just do the math in case your devices are not sorted the way it is assumed in the key files. -> change button numbers
Feel also free to use the tool AND have a look at the manuals. -
Try to make new locale Azerty BE NL
No joy cause we dont have 0X2B and i need to fill in that cell -
we have an additional key in front of the American Z key
Own local still Yellowand import not working
-
Try to make new locale Azerty BE NL
No joy cause we dont have 0X2B and i need to fill in that cellManta, you can fix that problem with autohotkeys, same way I did with the budget ICP project.
Edit…good find! nevermind my post