Flounder's X52 Pro Keyfile/DX Profile for BMS 4.33
-
Hello,
I am completely new to BMS and really want to thank you for your X52 pro profile. I use it without TIR. It is perfectly set for me.
I just have some questions : How can I activate the padlock with your key file? Is the trim reset switch set to the C button? I am not sure to understand the profile image.
Thanks again,
Best regards,
Pierre
Trim reset is the Shifted state of the ‘Fire C Button’. To reset trim, hold the pinky lever, hit the ‘Fire C’ button, then release the pinky lever. Holding the pinky lever is how you access any of the shift state functions.
Padlock is not included. Below are all of the padlock functions with ‘No Key Assigned’. Using notepad or similar, open the key file. Copy the commands below and paste them in to the ‘External Views’ section. Save the keyfile …. be SURE to have a copy of the original, or give the amended keyfile a different name.
in BMS Setup --> Controllers, load this amended keyfile and ‘Apply’. You should be able to assign keys on the keyboard directly in the UI. Be sure to avoid conflicts with existing keyboard commands.
OTWStepNextPadlock -1 0 0XFFFFFFFF 0 0 0 1 "VIEWINT: Padlock next" OTWStepPrevPadlock -1 0 0XFFFFFFFF 0 0 0 1 "VIEWINT: Padlock previous" OTWStepNextPadlockAA -1 0 0XFFFFFFFF 0 0 0 1 "VIEWINT: Padlock next AA" OTWStepPrevPadlockAA -1 0 0XFFFFFFFF 0 0 0 1 "VIEWINT: Padlock prev AA" OTWStepNextPadlockAG -1 0 0XFFFFFFFF 0 0 0 1 "VIEWINT: Padlock next AG" OTWStepPrevPadlockAG -1 0 0XFFFFFFFF 0 0 0 1 "VIEWINT: Padlock prev AG" OTWSelectF3PadlockMode -1 0 0XFFFFFFFF 0 0 0 1 "VIEWINT: Padlock" OTWSelectF3PadlockModeAA -1 0 0XFFFFFFFF 0 0 0 1 "VIEWINT: Padlock Mode=AA" OTWSelectF3PadlockModeAG -1 0 0XFFFFFFFF 0 0 0 1 "VIEWINT: Padlock Mode=AG" OTWSelectEFOVPadlockMode -1 0 0XFFFFFFFF 0 0 0 1 "VIEWINT: Extended FOV" OTWSelectEFOVPadlockModeAA -1 0 0XFFFFFFFF 0 0 0 1 "VIEWINT: Padlock EFOV Mode=AA" OTWSelectEFOVPadlockModeAG -1 0 0XFFFFFFFF 0 0 0 1 "VIEWINT: Padlock EFOV Mode=AG"
-
If I wanted to convert this setup for use with plain x52, I would just need to create a .pr0 with mappings set like yours (empty except for a couple of keybinds) and modify the keyfile for the x52 dx numbers, correct?
-
If I wanted to convert this setup for use with plain x52, I would just need to create a .pr0 with mappings set like yours (empty except for a couple of keybinds) and modify the keyfile for the x52 dx numbers, correct?
Yes, 100% correct.
-
Yes, 100% correct.
Woo-hoo, I have this done and mostly working for non pro, except there’s one switch on the throttle that’s bound to awacs in your setup that I don’t seem to have a dx number for on my throttle.
I’m thinking I might have screwed it up in the pr0 file… That’s what I’ll check tomorrow… Err I mean later today after I’ve had some sleep.
It’s the first switch on the throttle base.
It was kind of a pain… Most (but not all) of the switch dx numbers were off by 32. If it were all of them it would have been really easy. But no. I reckon that’s why no one converted it already. =p
I’m kinda curious if all x52 are detected as controller 1? Or is mine detected that way because I have a Logitech G15 and an x-keys. I’d like to share the files, but I’m afraid it might not work for anyone else.
Edit: Yep. The x52 is detected as the 2nd controller because of my G13 (not G15), which apparently has one button on it’s joystick.
-
Ok, I found something wierd.
I was looking at “Flounder X52 Pro v5.pr0” in vim to see how you set it up (I can’t open X52 Pro files correctly in my version of SST).
Anyway, I found where you configured bands for the mouse x and y, and I found which keys those bands emulate when activated:[actioncommand=c1b5ba68-60e3-4cab-9a30-6648899b0b1b name=‘Radar Cursor Left’
[actionblock
[action device=keyboard [B]usage=0x00000043 page=0x00000007 value=0x00000001]]][actioncommand=116f9add-a3ae-42a5-bbd5-ba5305e5d1d3 name=‘Radar Cursor Right’
[actionblock
[action device=keyboard [B]usage=0x00000044 page=0x00000007 value=0x00000001]]][actioncommand=07e40c8a-33f2-4f7f-a34a-9f430451e706 name=‘Radar Cursor Up’
[actionblock
[action device=keyboard [B]usage=0x00000041 page=0x00000007 value=0x00000001]]][actioncommand=bf6163bd-6312-485f-b96f-97052c5c280b name=‘Radar Cursor Down’
[actionblock
[action device=keyboard [B]usage=0x00000042 page=0x00000007 value=0x00000001]]]The problem is that 0x41-0x44 correspond to F7-F10, not F8-F11. (F11 is 0x57)
Long story short, I think this SST file is mapping the wrong keys, and causes you to lose radar cursor right.
I guess my question is, am I missing something?
-
Woo-hoo, I have this done and mostly working for non pro, except there’s one switch on the throttle that’s bound to awacs in your setup that I don’t seem to have a dx number for on my throttle.
……
That may not be a recognized button in BMS (the layout around the MFD is different between the X52 and Pro). Easy way to see is to go to the BMS Setup UI and press the buttons on your MFD. The one’s that BMS ‘sees’ should show a text line with button number and text description, iirc. Some thing like, “Button 6 CMS Up”
Edit:
Not sure about the XML file, but this is what I see in the SST Programming:
It responds properly to radar slewing (which is mapped to F8, F9, F10 and F11 in BMS).
Just one more reason not to like SST, imho.
-
If it’s working, probably my guess that SST is using the same key codes is wrong.
It sure seemed like a good guess though, considering the other three key codes match exactly!Ah well, I figured out what I needed to. Sorry to be a pest.
When I’ve verified this working for 100% X52 non pro, would you like to post up the files?
I’d be happy to give them to you.
I’m sure there are other poor slobs like me with hoopty non pro sticks. -
…. When I’ve verified this working for 100% X52 non pro, would you like to post up the files?
I’d be happy to give them to you.
I’m sure there are other poor slobs like me with hoopty non pro sticks.If you’d like, I’d be happy to host the files for your X52 DX profile.
-
Really it’s yours. All I did was remap a few buttons!
-
Padlock is not included. Below are all of the padlock functions with ‘No Key Assigned’. Using notepad or similar, open the key file. Copy the commands below and paste them in to the ‘External Views’ section. Save the keyfile …. be SURE to have a copy of the original, or give the amended keyfile a different name.
in BMS Setup --> Controllers, load this amended keyfile and ‘Apply’. You should be able to assign keys on the keyboard directly in the UI. Be sure to avoid conflicts with existing keyboard commands.
Thank you for your answer! I will try to modify the file to include padlock then.
Also, I am having problem with the FOV set on the throttle slider because it jitters a lot. I don’t know if there is a solution to this, otherwise I may try to set FOV with keys on the throttle Wheel instead of “range increase / decrease”…or just buy TIR^^
Pierre
-
Th….
Also, I am having problem with the FOV set on the throttle slider because it jitters a lot. I don’t know if there is a solution to this, otherwise I may try to set FOV with keys on the throttle Wheel instead of “range increase / decrease”…or just buy TIR^^
Pierre
Yes, I have the same problem. That is a Saitek problem. You can see the jitter in the Saitek Control Panel, without BMS running at all. It’s possible that if the pot were cleaned it would improve. Moving FOV to ‘button’ control instead of axis control could work; rearranging axes could also be tried (not sure how good that would be …. it seems like all the axes jitter a little bit). You can also look at setting a deadzone or at changing the FOV increments (in the Falcon BMS cfg file).
-
Really it’s yours. All I did was remap a few buttons!
I understand and I’m saying the same thing …. in reverse … you set it up, tested it, etc.
Regardless, once you’ve got it where you want it, we can repost it and host it somewhere so other can use it if they wish.
-
Hi Agave_blue,
Is the Pinkie switch also working like the normal Pinkie (ie zoom for TGP) on real F16 or is it only the shift function?
Pierre
-
Hi Agave_blue,
Is the Pinkie switch also working like the normal Pinkie (ie zoom for TGP) on real F16 or is it only the shift function?
Pierre
It is FOV on short press (FCR=>Norm/EXP/DBS1/DBS2; TGP=>Wide/Naro; Mav=>Norm/EXP; etc.); Hold = DX Shift.
I’ve updated the pinky description in the stick picture in post #1 for clarity.
The two commands are:
- SimHotasPinkyShift …. this is the one that acts as FOV on short press and DX Shift when held, and;
- SimPinkyShift …. this is the one that is DX Shift only.
-
Hi Agave_Blue.
I am learning Falcon with your profile and i want to turn on the HMCS display but I cannot see how activate it.Is this programmed in your profile?
Thank you. -
Hi Agave_Blue.
I am learning Falcon with your profile and i want to turn on the HMCS display but I cannot see how activate it.Is this programmed in your profile?
Thank you.I use the knob in the 3D pit (Left forward panel, just below the Chaff/Flare/EWS panel).
However, to directly answer your question, Yes, there is a keypress in the profile. Check post #1, the keyboard layout. It is ‘CTRL-[’ to decrease and ‘CTRL-]’ to increase HMCS brightness.
-
Thanks for your profile, I like it very much! But it is possible to use this Software “Two tablet cockpit extractor for Android” with your profile? All keys on the Tablets don´t Funktion. Is it possible to fix it? Since two days I try to change it. Unfortunately without success I’m still not so fit to work with the Keyeditor and SST
Big Thanks for your Support!
Sebi -
Thanks for your profile, I like it very much! But it is possible to use this Software “Two tablet cockpit extractor for Android” with your profile? All keys on the Tablets don´t Funktion. Is it possible to fix it? Since two days I try to change it. Unfortunately without success I’m still not so fit to work with the Keyeditor and SST
Big Thanks for your Support!
SebiSorry, but I’m not familiar with that app or how it uses the BMS keyfile.
-
Thank you Blue , quick question, will this profile work OK, with BMS 4.32, I have used it and have a couple issues which may be my install just checking!
I am flying with 4.33 but it is unstable some times, the frame rate is not real high even at 32 bit so may use older version to get up to speed until I can upgrade.
tux -
Thank you Blue , quick question, will this profile work OK, with BMS 4.32, I have used it and have a couple issues which may be my install just checking!
I am flying with 4.33 but it is unstable some times, the frame rate is not real high even at 32 bit so may use older version to get up to speed until I can upgrade.
tuxHmmmm …. not 100% sure. Some callbacks changed in 4.33 … not many, but a few. It’s possible that one or more of those are included in this keyfile and they would not function correctly in BMS 4.32. That said, I think all of the HOTAS commands should be ok, it would likely be a few keyboard commands that don’t work.
Another alternative is to download my 4.32 DX Profile and use that in 4.32. HOTAS layout is very nearly identical. Keyboard layout is similar for ICP, OSB’s, etc., but contains a lot more default keys as well.