New key files vs old key files
-
Hey guys I recently upgraded BMS to the latest version and dived in to check out all the new improvements. While I was impressed with some of the things I’ve seen, I ran into an issue where my joystick mapping was way off. What I figured out is that the key file was completely remapped from the old default version. I would like to use the old default version but can’t seem to locate it with the game files in order to load it (it looks like it wasn’t included in the new update). This creates the problem of having to remap most of my joystick, which I am hoping to avoid. Can anyone direct me to a place where I could download the old default key file? Or offer some assistance to help me resolve this? Thank you in advance.
Drix
Oh yeah I should mention that it is a X52 Pro, and I use the Saitek programming software to map the entire joystick.
-
In the Docs folder there is keyfile document that explains some of the difference …. out-dated/remove callbacks, etc.
However, it may be a device ordering issue if things seemed to be mapped where they shouldn’t. There’s a new file in the config folder where you can set the device order. I’d check that first to make sure your x52 is in the correct place on the list. It may have been mis-placed by rudders or some other device.
-
Hey guys I recently upgraded BMS to the latest version and dived in to check out all the new improvements. While I was impressed with some of the things I’ve seen, I ran into an issue where my joystick mapping was way off. What I figured out is that the key file was completely remapped from the old default version. I would like to use the old default version but can’t seem to locate it with the game files in order to load it (it looks like it wasn’t included in the new update). This creates the problem of having to remap most of my joystick, which I am hoping to avoid. Can anyone direct me to a place where I could download the old default key file? Or offer some assistance to help me resolve this? Thank you in advance.
Drix
Oh yeah I should mention that it is a X52 Pro, and I use the Saitek programming software to map the entire joystick.
never use old keyfile else you will loose many new functionalities.
-
Which file in the config folder is that, and how do you use it. There is no information that I can find to explain this. Thanks, for the help.
-
Hi Drix….
DON’T DO IT .
And Agave has a good point. The Device order may be messed up, User/Config/ DeviceSorting.txt
I might be a bit weird but I actually found it a pleasure to work with the new Key file, as I refined a few of my assignments.
-
Which file in the config folder is that, and how do you use it. There is no information that I can find to explain this. Thanks, for the help.
x:\Falcon BMS 4.33 U1\User\Config\DeviceSorting.txt
See x:\Falcon BMS 4.33 U1\Docs\Key Files & Input\BMS Key File Manual.pdf. Start with Chapter 8 “THE DX DEVICE ORDER”.
-
Thanks for the info guys. I checked on the device sorting first and I only have the X52 Pro listed, so no issues there. I decided to read through the key file docs a bit and just go the route of remapping the joystick. After spending a couple hours with it, it’s mostly back to how I like it. I am sure I will learn about some of the new goodies I don’t know about when I get back into multiplayer though!!
-
So now that I have some more things figured out I am still struggling with a couple key commands and could use some guidance.
Specifically ‘guns’: it used to be “/” and now it looks like I should try to use 1st Trigger Detent and 2nd Trigger Detent. I’ve set those keys up, but still can’t seem to make the gun fire? I’ve also tried just using my keyboard for those and that doesn’t work either. And before you ask, Master Arm is in the Arm position, and I tried in A-A, A-G, and DogFight modes with no luck.
The other 2 things I couldn’t figure out until just now (I just read through the “BMS Keystrokes old vs new” pdf) were Radar to Standby and Cycle A-A Weapons. Are these just not implemented in the real F-16 and so they are being omitted? Anyway thanks again for the help, it is appreciated.
-
So now that I have some more things figured out I am still struggling with a couple key commands and could use some guidance.
Specifically ‘guns’: it used to be “/” and now it looks like I should try to use 1st Trigger Detent and 2nd Trigger Detent. I’ve set those keys up, but still can’t seem to make the gun fire? I’ve also tried just using my keyboard for those and that doesn’t work either. And before you ask, Master Arm is in the Arm position, and I tried in A-A, A-G, and DogFight modes with no luck.
The other 2 things I couldn’t figure out until just now (I just read through the “BMS Keystrokes old vs new” pdf) were Radar to Standby and Cycle A-A Weapons. Are these just not implemented in the real F-16 and so they are being omitted? Anyway thanks again for the help, it is appreciated.
you must learn that some of the real F16 HOTAS buttons have different functions depending on the mode you are
for example : the NWS button
can activate the NWS but can also cycle weapons or pylons, depending on the time you press it., it cal also disconnect AAR …RTFM 
, this is why this is called NWS/ A/R DISC / MSL STEP buttonBig advice : USE strictly real HOTAS configuration with DX coding…so that you have exactly the F16 functionalities on your HOTAS like the real, forget old fashioned HOTAS programming…real men use REAL HOTAS CONFIG
-
I might be a bit weird but I actually found it a pleasure to work with the new Key file, as I refined a few of my assignments.
You aren’t the only one Shadow. I really like the new keyfile and the way Kolbe set up key/switch groupings. For example, the numeric keypad numbers match the numbers on the ICP, F1-F6 for the Master Mode buttons, cursor keys for the Data Entry Switch, etc.
-
…. Specifically ‘guns’: it used to be “/” and now it looks like I should try to use 1st Trigger Detent and 2nd Trigger Detent. I’ve set those keys up, but still can’t seem to make the gun fire? I’ve also tried just using my keyboard for those and that doesn’t work either. And before you ask, Master Arm is in the Arm position, and I tried in A-A, A-G, and DogFight modes with no luck.
….You have to be in the right mode. In AG choose Gun from the weapon SMS page. Gun should be active in Dogfight Override mode.
I don’t know the keystroke for it, but it should be the command ‘SimTriggerSecondDetent’.
Mav-jp’s advice about using the RL HOTAS commands as BMS DX commands is the best HOTAS advice there is …. period.
-
I have been trying to read up on how to do DX programming and it’s advantages, but am still unclear a bit on it. To my understanding, the way I have my joystick programmed, the game should see keyboard presses. Isn’t this the same thing the DX programming would do? I still have things like TMS, DMS, CMS, Trim, etc all programmed and working properly. So when you guys say that using the DX commands makes it more like the real F-16 I am not sure that I understand that. For example, doesn’t pushing “Ctrl + /” input ‘SimTriggerFirstDetent’ into the game? And doesn’t DX programming just input ‘SimTriggerFirstDetent’ into the game. So why would that be different?
With that being said, I am definitely in the right modes for the gun to work: A-G or Dogfight…master arm is set to on, gun is selected on the SMS MFD page. If I press “Ctrl + /” on my keyboard, it does nothing. Same goes for second trigger detent. So regardless of which method of joystick programming I use, the keyboard functions are not functioning properly for me. I can verify through the in-game settings GUI that Ctrl+/ and Alt+/ should be first and second trigger detents, respectively, but I still don’t get a response in game.
Believe me, I RTFM a lot, and I have not encountered this type of issue before. It almost seems as if it is something to do with the key input rather than the way the joystick is programmed. If it is not a programming issue then I would think it’s a procedural issue while I am in the pilot’s seat. But the guns are simple: master arm - on, go to a mode which utilizes guns (A-G w/ guns selected on SMS page or Dogfight Override mode), key press Alt+/. Is there something I am missing to that procedure?
Thanks again for any help you guys can offer.
-
DX programing is simply highlighting a input in the keyfile ( it turns blue) and then pressing the button on the joystick /throttle, that you want to activate that function. It cuts out the middleman (keyboard).
Making shore that your Joystick profile is clear of that function you just set to be evoked by the Hotas directly.
-
Ok - I think I understand you Shadow. You are saying that literally you go through the in-game GUI to set up the DX stuff? Much like you would for other games out there? If that is the case are all the excel files that are included just a back door way of doing what the GUI does? I try to read through the Key File Editor excel doc and figure it out and I am confused. I don’t know enough about what I am doing in the Key File Editor and am afraid of screwing something up. Maybe we could chat through TS Shadow? But if all I need to do is go through the in game GUI then that is a piece of cake.
-
You still have our TS3 details ? Most days I’m on, if you check the web site it shows the TS there. http://forum.801sttfw.com/
-
Yeah Shadow I have the TS3 info. I will try to be logged in some over the next few days to catch you.
Good news though, I have resolved most of my issues with programming the joystick and I did it all with the SST software. The nice thing is that because of the remapping of the keys, I adjusted my stick around a bit and got rid of redundant buttons. Now it is much more efficient and makes a lot sense the more I use it. Since I was able to resolve the more difficult issues using the SST software, I don’t really see the advantage to DX programming? I’m guessing I don’t fully understand it, but the SST software was much more intuitive (I didn’t have to read a single manual), so I am not sure why you would want to go the route of DX programming? Anyone have thoughts on this?
-
…. I’m guessing I don’t fully understand it, but the SST software was much more intuitive (I didn’t have to read a single manual), so I am not sure why you would want to go the route of DX programming? Anyone have thoughts on this?
Just like with SST, DX can be easy or complicated (in SST, for example, creating macro’s with key timings, etc.; in DX press and release separate functionality). Nothing gets much easier than going to the UI clicking a function to highlight it, then clicking a button on the joystick to assign that command to that button. That’s DX.
But with minimal additional understanding of the keyfile in DX you can have:
- Long press/short press functionality;
- Press multiple keys at the same time (Hold TMS up for spotlight mode, for example, AND talk on comm1 AND extend the speed brakes) …. try that with SST;
- No need to rely on drivers, driver updates or worry about key conflicts with, for example, Teamspeak or TrackIR;
- One program to manage a keypress change, instead of two (if you change a key assignment in BMS, you have to deconflict in SST and vice-versa). DX = not a key press; manage HOTAS and keyboard in one place;
- You can fully incorporate additional devices, like MFD’s, or an ‘ICP’ without adding still ANOTHER button press interpreting piece of software …… it’s all in the keyfile in DX;
- No ‘key modifier’ issues …. which are common with SST … with DX, because there are no keys being ‘pressed’ by keyboard simulation.
I have had pretty much everyone of the issues listed above with SST …. but not with DX. IMHO you cannot get 100% of the primary HOTAS functionality (i.e. programmed RL functionality) out of SST, but you can with DX.
Not to mention, mix & match on the HOTAS … Warthog stick and X52 Pro throttle? No problem … in DX. 1/2 of a solution (if that) in SST.
-
DX is much safer with no interaction during key press.
To make the OP understand better : when you assign joystick axis in BMS you just do it and you dont have to program anything, those are DX axis, well this is the same with DX buttons…. BMS keystroke are coded Dx native. just assign DX buttons to your joystick and press them, you will see in the UI what commands they activate.
BMS keystoke is built so that you can mimic 100% the real hotas using only DX buttons
-
Ok, thank you for the explanations. I think I understand a bit better now. I guess I ran into issues when I wanted to use the pinky switch (on the X52 pro) as a shift button, and trying to use the in game GUI to program that did not work. So in that instance I would use the key file editor and map it out. Which is something I need to read more up on to understand. But again thank you for everyone’s help. I look forward to dogfighting some of you in the future!
-
Hi guys!
Iam using a dx -setup and have been for years now. I really try to convince as many as I can to use it as that will make that pilot a higher likely troublefree and in that, more flyingtime and –-more opponents or wingmen to fly with instead of waiting for them to try to fix the hotas-setup :-). One thing I havent figured out with binding in the ui or within the keyfile is that very many functions lack the corresponding sound that comes with the manipulation of the vcockpit knob, switch etc. I´m missing switchsound for master arm, laser arm - trim-sound, even next waypoint as it has a sound, clicking on the icp. Is there a way to add code to the dx-line to retrieve it?
Oh and since the wizard is looking here: Is there a breakout force in the real jet on the fcc? Is the deadzone set to small in Falcon trying to simulate that?
/Falcon lover
