BMS Key File Help
-
Hi Killer.
I just wanted to let you know that I followed your directions, and it worked! No problems whatsoever….no crashes like I had while using duncs profile.
I am pretty excited - now I can at least start to learn BMS - and there seems to be alot of things in BMS that arent in AF, which is what I am used to.
So thank you so much - and maybe sometime when you have some time could you please show me how to modify keyfiles? I understand where the codes for the keystrokes come from (at least I think so) - but I am not so sure about where the codes for the joystick buttons come from.
Take care,
Mike -
Hi Mike
Thats great news. We didn’t do anything special other than run a minimalist Cougar configuration stating that all axis/buttons should be DirectX.
Which of Kolbes keyfiles did you use, so I know what you are working with?
Let me know what additional functions you want on the HOTAS when “Shifted” and I will show you what to do and how to do it. -
Thank you Kolbe, Really love this keymap - Just starting out with Falcon4 so the layout is very intuitive.
Also really made binding my Saitek X-45 Buttons a breeze. Got it setup very similar to the actual HOTAS now. -
Hi Killer - sorry I havent gotten back to you earlier - busy week.
Anyway, I am pretty sure that I have finally figured out how to put shifted functions onto the HOTAS.
Please tell me if I am correct:
To find the shifted button number, I take the Windows DX number for the button, subtract 1 from it, and then add 256 to it……
Then using kolbes keyfile I find a function assigned to the keyboard that I would prefer be assigned to the HOTAS…
So for example if I wanted to put “Assign Near Labels” to button 7 shifted…I would put the following in my keyfile:
OTWToggleNames 262 0 0X2 2 0 0 1 “SIM: Labels Near”
Is this correct?
Thanks!
Mike -
Hi Killer - I spoke too soon.
I still need some help with assigning a non-default shifted function to my HOTAS……
I noticed that all of the shifted and non-shifted codes in kolbes keyfile (and duncs) are the same with the exception of the DX button number (i.e. the prefix which contains the DX button # differs, but the remainder of the code on each line is the same). Why is it this way? If the “suffix” of each code is the same…then what exactly do these lines do? Just activate the buttons with their default functions?
Can I assign something else that I want to one of the HOTAS buttons, either in shifted mode or unshifted mode? And if so, how?
For example, could I assign a button (either shifted or unshifted, doesnt matter) to turn the autopilot on? Or how about toggling labels on and off with a HOTAS button? Can I do that?
Thanks again for all of your help.
Mike
-
Hi Killer - sorry I havent gotten back to you earlier - busy week.
Anyway, I am pretty sure that I have finally figured out how to put shifted functions onto the HOTAS.
Please tell me if I am correct:
To find the shifted button number, I take the Windows DX number for the button, subtract 1 from it, and then add 256 to it……
Then using kolbes keyfile I find a function assigned to the keyboard that I would prefer be assigned to the HOTAS…
So for example if I wanted to put “Assign Near Labels” to button 7 shifted…I would put the following in my keyfile:
OTWToggleNames 262 0 0X2 2 0 0 1 “SIM: Labels Near”
Is this correct?
Thanks!
MikeHi Mike,
I think the easiest way is to work in this section of the keyfile
#=============================================================================================== SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -2 "========== HOTAS SHIFTED ==========" SimWheelBrakes 256 -1 -2 0 0x0 0 OTWTrackTargetToWeapon 257 -1 -2 0 0x0 0 SimHotasPinkyShift 258 -1 -2 0 0x0 0 AFBrakesToggle 259 -1 -2 0 0x0 0 "HOTAS-AP Override" SimFuelDoorToggle 260 -1 -2 0 0x0 0 SimParkingBrakeToggle 261 -1 -2 0 0x0 0 OTWSelectF3PadlockModeAA 262 -1 -2 0 0x0 0 OTWStepNextPadlock 263 -1 -2 0 0x0 0 OTWSelectF3PadlockModeAG 264 -1 -2 0 0x0 0 OTWStepPrevPadlock 265 -1 -2 0 0x0 0 OTWSelect2DCockpitMode 266 -1 -2 0 0x0 0 ToggleNVGMode 267 -1 -2 0 0x0 0 OTWSelect3DCockpitMode 268 -1 -2 0 0x0 0 RecenterTrackIR 269 -1 -2 0 0x0 0 SimEWSProgOne 270 -1 -2 0 0x0 0 SimEWSProgTwo 271 -1 -2 0 0x0 0 SimEWSProgThree 272 -1 -2 0 0x0 0 SimEWSProgFour 273 -1 -2 0 0x0 0 SimEmergencyJettison 274 -1 -2 0 0x0 0 SimTransmitCom2 275 -1 -2 0 0x0 0 SimTransmitCom1 276 -1 -2 0 0x0 0 AWACSRequestPicture 277 -1 -2 0 0x0 0 AWACSDeclare 278 -1 -2 0 0x0 0 SimDoNothing 279 -1 -2 0 0x0 0 AFElevatorTrimUp 2 -1 -3 0 0x0 0 AFAileronTrimRight 2 -1 -3 2 0x0 0 AFElevatorTrimDown 2 -1 -3 4 0x0 0 AFAileronTrimLeft 2 -1 -3 6 0x0 0 #===============================================================================================
These are all in order of DX for a Cougar so for me SHifted number 7 button would be
OTWSelectF3PadlockModeAA 262 -1 -2 0 0x0 0
So i would edited it by only replacing the callback name to the one I want
OTWToggleNames 262 -1 -2 0 0x0 0
Depending on your HOTAS the Direct x number for your buttons will/may be different. The important thing is to not change anything after the callback name and its number. The String after that is what defines it as a direct x function.
From the reference article DirectX Shifting Facility
BMS DirectX Button Handling
BMS can handle up to 16 DX devices with 32 buttons each, making a total input of 512 DX buttons possible. To assign DX input, a special type of input line within the BMS keyfile is used e.g.:[color]SimTriggerFirstDetent 0[/color] [color]-1 -2 0 0x0 0[/color] [color]SimPickle 1[/color] [color]-1 -2 0 0x0 0[/color]
The red part of the input lines does never change for DX button definitions and will not be explained here. The green part of the input lines is composed from the name of the function to call and the DX button number that should trigger the execution of the function.
Summary:
You need to know the DX number for each of the buttons on your HOTAS (if its not a Cougar)
Then decide what you want and where
Then just copy the callback name only from the top part of the key file and paste (replace) it over the callback in the corresponding line within the “========== HOTAS SHIFTED ==========” section.
Save and load.Remember that the Falcon 2D UI will not provide confirmation feedback for Shifted DirectX button assignments, only unshifted, so the only way to really know is to launch a flight and see what happens.
-
Well this is certainly an interesting thread around here, especially for me as a profile maker.
At the moment I have one Profile for the standard BMS keyfile finished but, I like Kolbe’s a lot more. So I’m thinking of partially scrapping the old profile and doing one based on Kolbe’s.
If I want to do an X-52 SST-Profile based on Kolbe’s Keyfile, would which of the keyfiles would I need? I’m no Cockpit builder either.Kolbe, if I do that can I upload your keyfile in a package with my profiles?
My work on SST profiles so far:
https://rapidshare.com/files/3220603035/Wolfs_Profile_Version_0.7.1.7zBTW Kolbe’s original link works again.
Clear skies and many happy landings
Wolf
-
Is it possible to have a mix of DX and keystrokes in a profile in both shifted and unshifted modes? For instance the radio switch–- have the UHF and VHF positions DX#s and the in, out buttons as keystrokes. Or perhaps the same switch keystrokes in the unshifted position and DX shifted.
-
Kolbe, if I do that can I upload your keyfile in a package with my profiles?
Hi Wolf,
aber klar dochRegarding to the files, if you don’t need all switch states (which are important for pit builders) then you are fine with the basic key file.
@Doc:
Is it possible to have a mix of DX and keystrokes in a profile in both shifted and unshifted modes? For instance the radio switch–- have the UHF and VHF positions DX#s and the in, out buttons as keystrokes. Or perhaps the same switch keystrokes in the unshifted position and DX shifted.
If you mean a mixture between DX functions set the keystroke file and setting functions with the programming software the answer is yes.
But you have to be careful. Once you set a function with the software you will lose DX functionality for this button. As far as I know only Thrustmaster products can handle this via Target or Foxy which means, they can use DX (keystokes) and programmed functions (software) simultaniously.
Regards
Kolbe
-
Hello
After downloading this, where do I put the files, and which files should I put?
Thanks in advance.
edit - ok, I figured I put it in bms/user/config
right ?
but do I just put one file, there, or many ? what is the difference between basic, blank, full and pitbuilder ? and what is this file, keyfile_options key ?
thanks in advance. Im a noob.
edit - I found out there was a manual with it, so that answered my questions.
-
Kolbe,
super vielen dank für dein keyfile und die tastatur map!!!:bowd: i combined your work with morphines profile (based on DUNC DX profile) to customize the profile for my warthog combo. due to your work i decided to dive deeper into F4BMS. otherwise i would have focused on DCS A10 only. again, your work is much appreciated.
btw how can i change your keyboard overview as i did some smaller changes and i do not have adobe writer. any idea?
cheers
desmo -
When I made this https://www.benchmarksims.org/forum/showthread.php?8247-X-52-Pro-profile-by-53-Pigon profile, I found an .svg file on the net, that can be edited with many different software, also freeware as Inkskape (the one I used). If you want i can send it to you.
-
Hi desmo,
check PM.
Regards
-
Hi Kolbe excllent work this really makes the hole thing much more logical, big thumbs up for dedicating ur time to this project.
I need some help however I am very much in the a noob at keystroke stuff (I have always used gunslingers x52 profile) I have just picked myself up the x65f and Im trying to put togather a profile for it,
I would very much like to assign all the directx callbacks to my hotas but here are may hurdles1, I have no idea how or where to find the botton numbering order for the x65f so i can edit the dx coding.
2, how can i acctully edit the .key file and resave it as a .key fileI hope my questions make sence to someone because im getting kind-of swamped with this issue,
any help guys would be much appreciated
-
Hi snakepit1,
Hi Kolbe excllent work this really makes the hole thing much more logical, big thumbs up for dedicating ur time to this project.
Thank you
1, I have no idea how or where to find the botton numbering order for the x65f so i can edit the dx coding.
The DX buttons are as follows:
Stick:
POV U = POV Up
POV R = POV Right
POV D = POV Down
POV L = POV Left
Trigger = DX1
Button A = DX2
Button B = DX3
Button C = DX4
Hat 1 U = DX9
Hat 1 R = DX10
Hat 1 D = DX11
Hat 1 L = DX12
Hat 2 U = DX13
Hat 2 R = DX14
Hat 2 D = DX15
Hat 2 L = DX16
Hat 3 U = DX17
Hat 3 R = DX18
Hat 3 D = DX19
Hat 3 L = DX20Throttle:
Button D = DX6
Button E = DX7
Button F = DX8
Hat 4 U = DX21
Hat 4 R = DX22
Hat 4 D = DX23
Hat 4 L = DX24
Hat 5 U = DX25
Hat 5 R = DX26
Hat 5 D = DX27
Hat 5 L = DX28
Hat 6 U = DX29
Hat 6 R = DX30
Hat 6 D = DX31
Hat 6 L = DX32Unfortunately the Hat 7, Switch K, Scroll Wheel and Buttons T1 - T4 can’t be assigned with DX commands.
You have to use Saiteks programming software for it, but only for these!2, how can i acctully edit the .key file and resave it as a .key file
Any editor (like standard Windows Editor for example) would do the job.
Personally I use Notepad++. One of the best editors out there…Hope I could help.
Regards
Kolbe
-
Hi snakepit1,
The DX buttons are as follows:
Stick:
POV U = POV Up
POV R = POV Right
POV D = POV Down
POV L = POV Left
Trigger = DX1
Button A = DX2
Button B = DX3
Button C = DX4
Hat 1 U = DX9
Hat 1 R = DX10
Hat 1 D = DX11
Hat 1 L = DX12
Hat 2 U = DX13
Hat 2 R = DX14
Hat 2 D = DX15
Hat 2 L = DX16
Hat 3 U = DX17
Hat 3 R = DX18
Hat 3 D = DX19
Hat 3 L = DX20Throttle:
Button D = DX6
Button E = DX7
Button F = DX8
Hat 4 U = DX21
Hat 4 R = DX22
Hat 4 D = DX23
Hat 4 L = DX24
Hat 5 U = DX25
Hat 5 R = DX26
Hat 5 D = DX27
Hat 5 L = DX28
Hat 6 U = DX29
Hat 6 R = DX30
Hat 6 D = DX31
Hat 6 L = DX32Thanks for the help man that has been mega useful.
I think I am almost sorted as far as programing the DX callbacks. the only thing i’ve got to figure out now is how to make the x65 the 1st device and the 2 mfds the 2nd and 3rd and so on… then make the mini stick into axis so i can use it for radar cursor slew.
But you help has saved me so much time dude
Regards
Snakepit1 -
Hi Wolf,
aber klar dochRegarding to the files, if you don’t need all switch states (which are important for pit builders) then you are fine with the basic key file.
Danke!
Thanks, it will save me a lot of time, so the old profile will be scrapped. As I learned a lot from it its not a total waste. I will see what I want to do, I’ll hope I can get the work done sometime soon. Edit: Sorry for not replying sooner, I was very busy in the RL. -
Looks like the update erased the old keystrokes pdf file. I’ve been using that for my hotas instead of BMS keys…So, does anyone have the pre Update 1 keystrokes.pdf (found in Docs folder)?
Thanks.
-
Hello Breadfan,
I have not studied the new PDF files thoroughly, but I have got the impression that the new file ‘Keystrokes Keymap.pdf’ describes the same layout as the old file, only with different graphics and listing callbacks instead of descriptions.
Nonetheless, I have added the old file as an attachment to this message.
Respectfully,
Thingol
-
^^Yes, that’s it. Thanks!
I am going crazy right now. Using Kolbe’s keystrokes, I was trying for the past hour to set my radar cursor up/down/right/left (Thrustmaster Warthog) and whatever press type I set, it just doesn’t work. “Pulse” doesn’t make it move around while setting it to “Hold” makes the cursor go all over the place even after I released it. I did not have this problem with my previous profile using the default keystrokes. Yes, I’ve remapped commands, cursor controls are now using ALT + Arrowkeys and yes, I’ve loaded the appropriate keystrokes file in BSM but the damn thing just doesn’t listen. Any tips? Except for throwing myself off the balcony…