X52pro DX button profile via Keymapping.
-
Hello Pilots! I made direct DX binding using Alt Launcher Keymapping as seen in the attachment. Is there a way to make an other profile? I understand that shifted layers can not be done in this way. I tried to make an other profile when loaded in BMS UI the BMS-Basic instead of BMS-Full. I L-clicked Full and properties and checked to Read Only and unchecked the same in Basic before loading it. However I could not make an other different profile. Both keyfiles after loading had the same button responses. Help would be appreciated if more experienced pilot has got an idea and share it with me.
-
@Louis-0 there isn’t any sort of “multiple profile” feature built into BMS or the Alt Launcher…
I’ve heard of people keeping separate subfolders of the Config directory, as “profiles” and simply copying everything down before launch.
This may become a more pressing need, if BMS begins to develop a/c-specific callbacks for new jets like F-15C. (There are already a few Harrier- and Hornet-specific callbacks… but the primary hotas switchology is still F-16y.)
-
@airtex2019 Thanks Airtax2019 for replying. IMHO that is what I was doing, but may be doing sg wrong. I made this profile when BMS-Full was loaded. This is enough for taxy-takeoff-nav-landing ils/pls. However I wanted to make an other one for AA or AG with BMS-Basic loaded. But it did not work. I either made a mistake or the AL overwrite the new profile in spite of checking Basic’s Read Only when finished new button bindings. When reloaded BMS-Basic the button responses were the same what I binded under BMS-Full loaded. What did I do wrong? Perhaps I should try with BMS-Full-Copy?
-
@Louis-0 sorry it’s not very clear to me, what you’re doing or what’s going wrong.
Couple things to understand, when using the new Alt Launcher – from BMS pov, your key file will always be “BMS-Auto.key” which is what the launcher emits.
When you select an existing key file (in the upper-left corner of the Launcher key binding window) all you’re doing is “importing” that table of command descriptions and default key bindings.
Whatever changes you make, will be saved as BMS-Auto.key (in addition to some xml files).
That’s why you need 2+ directories to store different “profile” of config. The xml and key filenames are always going to be the same.
(ps. don’t ever make changes to files like BMS-Basic.key and BMS-Full.key … they are very likely to be overwritten, by the next software update.)
-
@Louis-0 this is a good idea, however with the profile switching the X52 is capable of, having DX inputs makes the multi profile system useless, the rotary knob only works inside the the X52 driver creation system.
I had thought repeatedly about tracking down the DX codes for the rotary but it makes it so that every command on each button has to be a dual or triple key press starting with
- Rotary switch mode position
- Pinkie state, (Yes / No position)
- Keypress on the stick.
Then you have the multi hat switches as 8 way / 4 way to consider. Personally using this stick X52 Pro presents a whole new pair of issues the rotary knobs on the Throttle stick base,
My solution is to use the Keypress full keymap, or the Basic map and use the X52 profile software for keypresses outside of the game menu. Assign the keys to the switches in the profile creator works as fast as the DX settings and is far easier to swap around on the fly using the rotary switch, just remember to assign the rotary switch to switch the aircrafts modes. Each setup NAV / AA/ GRND has a keypress to swap modes around and I use the Unlatched i button on the throttle to perform the main switching task once the knob is turned to whatever mode you want.
Its worked since first taking to the air the year the X52 was first made and still works using this method today.
Nice idea to be sure and great job.
-
@Diguelo said in X52pro DX button profile via Keymapping.:
My solution is to use the Keypress full keymap, or the Basic map and use the X52 profile software for keypresses outside of the game menu. Assign the keys to the switches in the profile creator works as fast as the DX settings and is far easier to swap around on the fly using the rotary switch, just remember to assign the rotary switch to switch the aircrafts modes. Each setup NAV / AA/ GRND has a keypress to swap modes around and I use the Unlatched i button on the throttle to perform the main switching task once the knob is turned to whatever mode you want
May be you are the pilot who can help me out.
I started making profiles with Joy2Key (see earlier submit). All buttons could be programmed very easily and with a selected button I could surf around within J2K to change to any selected profile. However, I could not get BMS to fully understand the profiles.
Next I worked with SST, made several profiles, on the throttle mfd I could see what button I pressed and the name of the profile what I made. The problem was that POV1 Up and DN were buttons and profiles could be searched with them. But L and R could not be programmed as buttons, they were only as mouse wh. Consequently I could not select profile with pressing POV Right.
The 3rd try was DX button profiling via Keymapping. I quickly made a profile which works very well, but can not make any additional profile to change to.
Actually SST profiling would be best if I can make it work: I could have number of different profiles - change profiles easy during flight - can takeoff and use missiles and gun and continue with AG action and land in the closest airfield - not even have to worry about mode selector swich. But everybody opin that SST is a crap and can not be used. What do you think? -
Hello Diguello, I made a new profile now. I loaded Full key in bms ui and used key responses from Full key to make a profile in sst, saved the profile, pasted it in bms user/config as pro file , pasted the file name to Full Key. Using POV1 loaded the pro file from sst prog into the mfd. Before start checked and all buttons seen on the mfd were correct when pressed. Checked in Full key wordpad and all key responses of my new profile were listed in it at the end. Started the sim as navigation. All single keys (A. G, B) were correct in the fly but all keys with modifiers were missing the modifier and the responses were wrong. What did I do wrong? I delated all shift states with pinky before.
-
@Diguelo said in X52pro DX button profile via Keymapping.:
My solution is to use the Keypress full keymap, or the Basic map and use the X52 profile software for keypresses outside of the game menu. Assign the keys to the switches in the profile creator works as fast as the DX settings and is far easier to swap around on the fly using the rotary switch, just remember to assign the rotary switch to switch the aircrafts modes. Each setup NAV / AA/ GRND has a keypress to swap modes around and I use the Unlatched i button on the throttle to perform the main switching task once the knob is turned to whatever mode you want.
Hello Diguelo, This answer of yours halped me to have better understanding of the issue. The direct binding buttons are controlled by the profile written in the bms key file. The sst bindings are outside of the bms-keyfile and residing in the sst file. I was trying to force these binding into bms and naturally could not do it.
What I am doing now making different SST profiles with different names and forget about pinkie shift. I SST programmed even the pinkie button and made the following profiles without shifting: Gnd-NAV-Lng, Dogfight, AA-Aim9-120, AG. These 4 profiles contain only keybindings necessary for that profile only. If an AG misson finished and I want to land I have to change over in flight to Gnd-NAV-Lng to land. The change over will be done by the i-button (have to be kept unprogrammed or programmed or just to do the selection with pov1?). This way I can overcome the button number limitation on my x52pro.
As you said I have to assigne the mode selecting swich to select mode 1-2-3.
Question: how to assigne this task ? Up-right click only shows unprog-fallback-bands-directional exes. Now if the 4 profile created and saved in MODE1, I still have to assigne Mode1 to select ? Sorry for this long scribblings. -
sexy template graphic
-
@Diguelo Hello Giguelo,
As you said you were using sst profiles I wonder if you can help. I programmed POV1 UP button as Shift-Np9 and same button with Pinkie as Ctrl-Home. In the sst window it works as intended. However, BMS can see only the second input as 9 or with pinkie as Home without seeing the Shift and Ctrl inputs. Same problem with other profile without pinkie shift. May I ask you to help? -
@Louis-0 If you avoid using modifiers in your SST keybindings, like “Shift”, “Alt”, “Win”, and “Ctrl”, you can avoid all of these headaches. Use simple, single keypresses that contain just the action needed to perform, and alter your keyfile to swap the modified keypress actions with the non-modified actions for that key, when needed. (alternatively, check out the alternative launcher now included with BMS)
Best wishes and good luck!
-
@SemlerPDX
How can that be used in flight with DMS-TMS-CMS-NWS STEP and the rest of the modified button responses? Only G, B, D, M, C, K, A among the more important keys can be programmed? You see by now I figured out how to make shifted profiles (with the stupid pinkie button) which are working nicely in the sst window. There got to be a way to make it work in BMS! Thanks for your comment. -
@Louis-0 Yeah, the best way to make it work if binding keypresses to button presses in the SST programming software is to use simple and single keypresses, no modifiers. The issues you have experienced are common, and a result of these conflicting modifiers in Windows. Would be the same as if you wanted to take a screenshot with WIN+SHIFT+S, but you are already holding down CTRL+C to copy something. Windows can’t handle that.
Due to the sheer number of keypress commands in BMS, pretty much every key is covered with functions which involve each modifier key. Every one of these has a “unmodified” button press option, too - my suggestion was to rebind or remake the keyfile such that all the keys you want to bind to HOTAS buttons are single key events. Then you only have to worry about Pinky Shift Lock.
The alternative is to use DX button assignments in a keyfile, rather than direct keypress mapping when making a joystick profile for BMS. The alternative launcher can help make things much easier, too.
-
im using BMS x52 profile which i changed by myself
-
@GhostDog-0
Are you using SST prog for that? Can you give a bit more details? Have you been able to use these profiles and if yes how? -
@Diguelo said in X52pro DX button profile via Keymapping.:
Its worked since first taking to the air the year the X52 was first made and still works using this method today.
Hello Diguelo,
You seem to have the knack to use profiles made with SST. Can you let me in this secret? I am unable to overcome a problem. -
@Louis-0 said in X52pro DX button profile via Keymapping.:
@Diguelo said in X52pro DX button profile via Keymapping.:
Its worked since first taking to the air the year the X52 was first made and still works using this method today.
Hello Diguelo,
You seem to have the knack to use profiles made with SST. Can you let me in this secret? I am unable to overcome a problem.Was there any reason you didn’t want to use (or modify) any of the existing X52 Pro profiles and control setups available for download here already? I certainly can appreciate a challenge, but it does seem a little painful to reinvent the wheel in this manner. The included Alternative Launcher makes things SO much easier, to make that point again, too. Just saying I’d sooner do a lot of things before trying to make a joystick profile of keypresses only unless there was very good reason. More power to you, just want you to know there are easier ways and existing ready-to-use profiles.