Flounder's X52 Pro Keyfile/DX Profile for BMS 4.33
-
Agawe I found, the culprit is a great program “Alternative Launcher”. After removing “A.L.” Pinky Shift works flawlessly - strange, but true.:drink::spy:
Good news. Computers are so fickle. I hate 'em. :roll:
-
Good news. Computers are so fickle. I hate 'em. :roll:
Hehehehehe … the computer is not guilty here, just “AL” mixes something in DX with Pinky Shift. Because until I enter the HOTAS setting, it is good and does not create a problem, it changes the theaters’ way. Chihirobelmo has made the corrected version, now I have no problem with Pinky Shift in the profile “Flounder X52 Pro v5 - Full”:drink::blah:
-
I’m totally new to BMS Falcon and I thought I would try out this profile for my X-52 Pro. However at least some of the throttle buttons do not seem to work. For example the wheel scroll buttons do not change the radar range. Any idea what I could be doing wrong?
-
@ corvus5624 profile works correctly, you set it::yo:
-
So … it turns out I had the controller set to the X52 HOTAS instead of the keyboard … The config above is working now. Except somehow even if I set the Pitch Axis Deadzone and Roll Axis Deadzone so the joysticks Y and X axes respectively, these axes seem to be inactive. I.e. no response in-game and no response in the config dialog. These axes are kind of important I’m kind of in a jam here.
-
In my case it worked with the latest Saitek drivers, now I have the latest Logitech and there is no problem either:nerd:
-
I have the latest drivers btw. The problem is in setting the “Pitch Axis Deadzone” and “Roll Axis Deadzone” axes. I want to set these to the Y-axis and X-axis respectively. However when I set the Y-axis to pitch, the little axis indicator bar (which should be half blue/half grey with a centered stick) is completely grey. Now if I want to set it back to keyboard, the program does not do that, it just stays at Y-axis no matter what I select from the dropdown box. If I assign the Y-axis to the Pitch Trim, then the axis is recognized. So the joystick is working properly in BMS, it is just the Pitch and Roll axes that are giving me trouble.
Also the axes settings in the “Advanced - Flight Controls” tab are not saved. Even if I save my profile, after a restart the flight controls are all set to keyboard. Maybe I should do a reinstall …
-
You must save the profile:; ; ; :plane:!
-
Agave, I really appreciate the incredible amount of work you put into this. Certainly a different approach to me than just going with the SST software but I’m old, and so far it’s working, and I’m getting the hang of it so it’s all good. Except for one thing. Where in the key file are steerpoints next and previous? Thanks again Bro’.
-
Agave, I really appreciate the incredible amount of work you put into this. Certainly a different approach to me than just going with the SST software but I’m old, and so far it’s working, and I’m getting the hang of it so it’s all good. Except for one thing. Where in the key file are steerpoints next and previous? Thanks again Bro’.
Those are advanced in the pit on the ICP if I recall correctly.
However, in the actual key file they are these commands:
SimICPNext 126 0 0xC9 0 0 0 1 “ICP: NEXT Button - Push”
SimICPPrevious 126 0 0xD2 0 0 0 1 “ICP: PREVIOUS Button - Push”These are on on the home/delete key cluster as part of the keyfile (see the keyboard layout in the first post). However, you can assign them to whatever keys you prefer.
There also used to be ‘short cut’ commands:
SimNextWaypoint -1 0 0XFFFFFFFF 0 0 0 1 “SHORT: Next Waypoint”
SimPrevWaypoint -1 0 0XFFFFFFFF 0 0 0 1 “SHORT: Previous Waypoint”These are in the keyfile, but unassigned. I don’t know if they are still active commands in 4.34. If they are, you can assign them to whatever keys you prefer.
-
Agave, Sry to sound so dense but I’m new to this. Once I copied the commands into the keyfile I had opened with Notepad it only saves the keyfile as a txt document. And I thought I had this :(. Help!
-
Agave, Sry to sound so dense but I’m new to this. Once I copied the commands into the keyfile I had opened with Notepad it only saves the keyfile as a txt document. And I thought I had this :(. Help!
Just rename it in your file browser. Right now it’s, “xxxxx.txt” …. just change it to “xxxxx.key”.
When Windows pops up and says, “Are you sure you want to change the file extension?”, yell at your computer screen, “OF COURSE!!! DO YOU THINK I DON’T KNOW WHAT I’M DOING!!” then choose ‘yes’ or ‘save’ or whatever the affirmative is.
If done effectively Window will never ask you for verification again.
Edit:
Ok. To be honest, yelling that at the computer has never really worked for me. But I keep trying.
Edit II:
Which keyfile are you using? If you’re using “Flounder X52 Pro v5 - Full.key” those commands should be there already. If you’re using “Flounder X52 Pro v5.key” the ICP Next and ICP Previous commands should already be there.
The difference between the “Full” and the other version is that “Full” has all of the available commands (for 4.33), but many are unassigned. The ‘standard’ version only has the relatively small number of commands that are assigned to keyboard keys.
-
Agave, Thanks so much for your patience in explaining the basics. The work you had to have put into the key and profile files is really impressive. And, if I still had it I would say they had saved my sanity. But, what they really did was to keep me from walking away from BMS (for being too time-consuming to learn).
-
Ok Agave, Another stupid question. Why does your keyfile have the second detent of the trigger activate radar dwn rather than guns? And why can’t I find gun in your ‘full’ keyfile at all?
-
Ok Agave, Another stupid question. Why does your keyfile have the second detent of the trigger activate radar dwn ….
It should not.
Do you have other HOTAS functions performing unexpected functions? If so, maybe some kind of device ordering issue?
When you say ‘radar down’ do you mean that it lowers the radar elevation or that it reduces the radar range or that it slews the radar cursor down?
…. And why can’t I find gun in your ‘full’ keyfile at all?
“Guns” is second trigger detent …. DX Button 14 on the HOTAS
SimTriggerSecondDetent 14 -1 -2 0 0x0 -1
As a keyboard function it’s in ‘Full’ keyfile as “SimTriggerSecondDetent -1 0 0XFFFFFFFF 0 0 0 1 “STICK: SECOND TRIGGER DETENT”” where “0XFFFFFFFF” means ‘no key assigned’.
-
Well, I’ve double-checked the key file assignment and as you said all your profiles do assign the second detent to Button 14. But on my rig activating the second detent by pulling the trigger fully activates dx button 15. I’m at a complete loss. FWIW, the first detent activates dx button 1. Got any ideas now?
-
Well, I’ve double-checked the key file assignment and as you said all your profiles do assign the second detent to Button 14. But on my rig activating the second detent by pulling the trigger fully activates dx button 15. I’m at a complete loss. FWIW, the first detent activates dx button 1. Got any ideas now?
Well …. that might be right.
What I mean is, Windows and BMS count DX buttons differently. BMS starts at 0 and Windows starts at 1.
This is the BMS command: SimTriggerSecondDetent 14 -1 -2 0 0x0 -1. The bold part is the BMS DX Button number. If you are looking at the Windows game controller screen it would show up as Button 15.
Similarly, here is the first trigger detent BMS command: SimTriggerFirstDetent 0 -1 -2 0 0x0 -1 . It is BMS DX Button 0, but Windows DX Button 1, which is what you’re seeing.
So, I think the button assignments are OK.
Can you look in your keyfile (opened in Notepad or similar) and find those two commands …… SimTriggerFirstDetent and SimTriggerSecondDetent … and paste those two command lines in a post so we can look at them?
Alternatively, it might be worth replacing the keyfile you currently have with a fresh copy of the “Flounder X52 Pro v5 - Full.key” file and make sure that you ‘load’ that keyfile in the BMS Setup screens (refer to the video in Post #1 at about 1:14 for loading a different key file). Doing that would remove any customization you may have done, so be sure to have a copy of your current key file.
-
Ok, let’s see. From your Flounder X52 Po v5 - FULL key file there’s:
"SimTriggerFirstDetent -1 0 0XFFFFFFFF 0 0 0 1 “STICK: FIRST TRIGGER DETENT”
SimTriggerSecondDetent -1 0 0XFFFFFFFF 0 0 0 1 “STICK: SECOND TRIGGER DETENT”And, from the modified keyfile that I’ve been using there’s:
“SimTriggerFirstDetent 0 -1 -2 0 0x0 -1”, and
“SimTriggerSecondDetent 14 -1 -2 0 0x0 -1”So, when I’m in BMS and testing button inputs with your original FULL keyfile loaded while testing the trigger BMS will tell me “input 1- first trigger indent” and then “input 15 - second trigger indent” (or something similar). And, when I’m using the one I modified and testing button inputs in BMS the first trigger indent says “input 1” and the second indent says “input 15”. Still, no brrrrrt! when I’m ingame.
FWIW, I’m currently using 4.33. But previously I had installed 4.34.
Anyways, for now BMS and I are squared off and just throwing hard looks at each other.
-
Ok, let’s see. From your Flounder X52 Po v5 - FULL key file there’s:
"SimTriggerFirstDetent -1 0 0XFFFFFFFF 0 0 0 1 “STICK: FIRST TRIGGER DETENT”
SimTriggerSecondDetent -1 0 0XFFFFFFFF 0 0 0 1 “STICK: SECOND TRIGGER DETENT”And, from the modified keyfile that I’ve been using there’s:
“SimTriggerFirstDetent 0 -1 -2 0 0x0 -1”, and
“SimTriggerSecondDetent 14 -1 -2 0 0x0 -1”So, when I’m in BMS and testing button inputs with your original FULL keyfile loaded while testing the trigger BMS will tell me “input 1- first trigger indent” and then “input 15 - second trigger indent” (or something similar). And, when I’m using the one I modified and testing button inputs in BMS the first trigger indent says “input 1” and the second indent says “input 15”. Still, no brrrrrt! when I’m ingame.
FWIW, I’m currently using 4.33. But previously I had installed 4.34.
Anyways, for now BMS and I are squared off and just throwing hard looks at each other.
In general a keyfile contains two sections, 1.) keyboard commands that are activated by pushing key on the keyboard (or by a proxy program doing the same thing, Saitek SST programming, for example), and 2.) DX commands that are direct commands from a DX device (HOTAS, Rudder, MFD, etc.). It is possible that a command can exist in both sections. That is you can initiate the command by pushing a key on the keyboard AND you can initiate the same command by using a DX device (HOTAS, etc.).
The first commands you list are keyboard commands:
"SimTriggerFirstDetent -1 0 0XFFFFFFFF 0 0 0 1 “STICK: FIRST TRIGGER DETENT”
SimTriggerSecondDetent -1 0 0XFFFFFFFF 0 0 0 1 “STICK: SECOND TRIGGER DETENT”I understand that is not intuitively obvious, but one clue is the keyboard key hex identification. In this case: 0XFFFFFFFF …. which indicates ‘no key assigned’. So, at the moment, those commands are not functional/active on the keyboard (which is fine if you’re using the HOTAS for them anyway).
The second commands you list are DX commands (i.e. HOTAS commands) and should be working as expected. They look right …
“SimTriggerFirstDetent 0 -1 -2 0 0x0 -1”, and
“SimTriggerSecondDetent 14 -1 -2 0 0x0 -1”In the setup interface, if you press the button/key/switch on your HOTAS and see BMS show something like, “input 1- first trigger indent” and “input 15 - second trigger indent” that further indicates that the keyfile is doing what it is supposed to.
All of that leads me to the question of whether you are engaging the gun with the correct parameters in game. Specifically:
- Master Arm is ON;
- If Air to Air you are in Dogfight Mode (aka SRM Override - Short Range Missile Mode);
- If Air to Ground (AG Master Mode) have you selected the Gun from the SMS Page on your MFD.
The gun is only active/available is certain configurations (as above). Outside of those limited configurations pulling the trigger does nothing.
-
Agave, Thanks for the detailed reply. I’ll let you know when, and how I figure[d] it out. So far, I don’t believe that it’s me trying to do something outside the game’s parameters, but will keep working at it and let you know.:frusty:.