Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments)
-
Hi i have a problem with my VKB MCG Pro Stick.I have 4.34.4,AL 1.51.
In the AL 1.51 I set up 2 hat switches but the game only sees 1.in version AL 1.4 everything was normal,2 binded hat switches and 2 hats in game.Here are screenshots of my bms-full.key 1.40 version and 1.50Edit: Now your attachments do show up… I have CH gear and both hats work fine for me using 1.51, use the Pro Throttle for views if my TIR5 is disabled…
-
I only recently discovered this application. It’s great - really makes management of controls a breeze. Thanks!
One suggestion/feature request… How about an optional commandline switch so that after starting, Alternative Launcher would launch BMS automatically? I.e. it would appear to the user like launching BMS.exe directly without any launcher (but still updating the BMS control files)?
-
Sorry if this sounds like a basic question*, but how do I map my Track IR keys of F9 (pause) and F12 (re-centre) in the launcher?
They are listed at the start but are in green, with a message I don’t fully understand and aren’t selectable. I have a Warthog HOTAS (Paddle button is set to a dx shift key) and Track IR. If I can map F9 and F12 keys to a button, Track IR should do the rest…shouldn’t it?
Do I change something in the Full Key file? (If so, do I follow the BMS manual section on this even though I am running the Alternative Launcher?)
Should I use TARGET software to map these buttons? These buttons would be shifted functions. I just switched from a Track IR/TARGET mapping with key presses/BMS to Track IR/AL/BMS.
I could also change them in Track IR…but then they would not work with other control schemes I have.- I’m sure it is - I have been on and off learning the bms “bike” for a few years now, but this launcher got me interested again as it makes control schemes easier and I gave up when I last had to redo mappings in BMS each time I started it!
-
Sorry if this sounds like a basic question*, but how do I map my Track IR keys of F9 (pause) and F12 (re-centre) in the launcher?
You don’t. Simply assign them in TIR itself in the Profiles tab under Hotkeys. Under Action select pause, click the Key button, press a Jstick or KB key. Repeat for Center… done.
-
Ahh.
Thanks. I think I only have a generic profile, but I remember I can select others.
But, if I wanted them as shifted function in AL, how would it know that say, Paddleshift is the dx shift and Hat2 Down is the action button (after shift)?
-
Ahh.
Thanks. I think I only have a generic profile, but I remember I can select others.I don’t believe the Profile matters, the Action Menu is for all profiles AFAIK… In Al TIR “Recenter” (Section 6.06 “SIM:ALTC :J” can be assigned to a DX button press, as can “Reload” (not sure what reload does) at “SIM:ALTC :T”. Not sure why but TIR Pause was not included…
But, if I wanted them as shifted function in AL, how would it know that say, Paddleshift is the dx shift and Hat2 Down is the action button (after shift)?
Setting up Shifted functions is as simple as assigning your DX “Paddleshift” button to “STICK: PINKY SWITCH (DX SHIFT)” in Section 5.11 Flight Stick and then assigning shifted keys to whatever you like. The attachment shows what the button assignments should look like when correct. In my example the TMS and DMS share the same 4 position hat…
-
Thanks, I don’t know how I missed it, Track IR Recenter is indeed in 6.06 (and it works with my shift button).
I also don’t know what TIR Reload does - it doesn’t make a difference for me when my TIR program is already loaded, but I assume if the TIR program stops working for whatever reason, this may relaunch the program. Or perhaps it reloads the TIR profile.
I’m not sure why TIR Pause and TIR Precision aren’t mappable in AL in the same way that TIR Recenter is, perhaps because they get less use? As it is, because they don’t have a line entry in 6.06, they can be mapped to a button in the TIR program, but I don’t think they can be mapped to a Shifted button for BMS. For example, in TIR pause is set to F9. I can’t allocate a switch to it in AL but I use the shifted state to manage all my view settings in AL/BMS. So I have to allocate a button to it in the TIR program. The TIR program (obviously) doesn’t recognize a shifted dx state (or the AL/BMS shift key), so as soon as I press my shift key (eg paddle) it registers “paddle” as pause. With some changes to my Track IR curves I can manage without TIR Pause and TIR Precision in a shifted state, which I am doing now.
-
I agree with you, mypc. It would be really nice to be able to pause TrackIR with a shifted key combo on the HOTAS.
I use a Warthog stick, and I use the “CMS-in” actuation to recenter TrackIR. But I wish I could pause TrackIR, too. Sadly, since “CMS-in” is the only thing on the HOTAS that’s not in the real F-16, I had to choose between recenter and pause.
I’ve started fantasizing about a Realsimulator FSSB base and F-16 stick. I wonder if their stick and software would make this more doable? Hmm… Maybe the fact that it’s not in the AL would still be an issue, though.
-
FYI Reload TrackIR is a key combo callback , so the key combination is ALT C followed by T
-
I downloaded this yesterday after suffering for ages with T.A.R.G.E.T issues; this is so simple to use, so thank you for some great software.
I am using v1.51 with the latest BMS; I am using a TM Warthog throttle and stick, my problem is I can’t seem to properly configure the 3-way switches and also the ‘on else off’ switches as described on the first page. In v1.51 there doesn’t appear to be the option to use ‘Invoke Both’…or am I missing something?
-
I am no expert, but I think you can map two releases to the one switch, so for example with the 3 way dogfight switch:
1. map the mrm button
2. map the mrm release button to the off switch position, by selecting the ‘off switch’ position, select “release” and then pressing the mrm button
3. map the dogfight button
4. map the dogfight release button to the off switch position, by selecting the ‘off switch’ position, select “release” and then pressing the dogfight buttonYou have already done steps 1 and 2.
-
I love the Alternative Launcher. I am building a cockpit and slowly adding input devices. Currently I have TM Cougar setup working fine. Yesterday I added Vipergear’s ICP. It recognized in Windows 7 64bit just fine as Vipergear ICP. I then fired up Alternative Launcher and mapped the ICP. The mapping seemed to record the DX buttons correctly. It mapped for example;
ICP: COM1 Button - Push -> Joy 2 DX1;
This was listed under the column “VIPERGEAR ICP” in AL KeyMapping page
I did the remainder of the ICPJumped in the sim, nothing worked on the physical ICP.
So then I went into BMS setup directly, mapped the first 4 buttons on the ICP to the loaded Key FIle. I applied and saved. Jumped in the Sim and those 4 buttons worked.
What am I doing wrong.
Here is my DeviceSorting.txt file entries.{0400044F-0000-0000-0000-504944564944} “HOTAS Cougar Joystick”
{00F2068E-0000-0000-0000-504944564944} "CH PRO PEDALS USB "
{FFFF06A3-0000-0000-0000-504944564944} “Vipergear ICP”To add more info…
In the BMS - Full.key file, when I put them in directly via BMS I find these entries toward the bottom and the ICP works in the SIM.
For the Keystroke and Sound callbacks I find these 3 lines…
SimICPCom1 122 0 0XFFFFFFFF 0 0 0 1 “ICP: COM1 Button - Push”
SimICPCom2 122 0 0XFFFFFFFF 0 0 0 1 “ICP: COM2 Button - Push”
SimICPIFF 122 0 0X3D 0 0 0 1 “ICP: IFF Button - Push”
And for the DX assignments I find these corresponding lines (I have 3 JOY ID’s with ICP being #3 so starting at 64 is correct)
SimICPCom1 64 8 -2 0 0x0 -1
SimICPCom2 65 8 -2 0 0x0 -1
SimICPIFF 66 8 -2 0 0x0 -1The Physical ICP works in the SIM.
Now if I run AL, it wipes out the DX entries in the KEY file for the ICP only, but shows mapping them in the UI of AL. THE ICP does not work in the SIM at this point, how could it, the DX entries were removed. My Cougar mapping remain working fine and I mapped those USING AL.
I know it must be user error, but I need some guidance.
Thanks.
-Nacman
-
I see on Github there is an open issue that seems like my issue. Can you advise if there is a fix?
_FalconBMS Alternative launcher v1.51
FalconBMS 4.34.4I observed that Keymapping seems to work only on first game controller listed by Windows in USB game controllers window.
I have Thrustmaster Hotas X with which both Axis and Key mappings works great with this alternative launcher, awesome.
However when I plugin second controller (in my case it’s Arduino leonardo where I use two rotary encoders and a few toggle switches), then only Axis mapping works, keymapping does not work at all.
When I unplug my Hotas, then keymappings on my Arduino starts to work perfectly (but I lost my hotas), it effectively makes my Arduino first on the list, thus my suspicion that only with the first one on the list, keymapping works at all.
important note, the keymappings works in the launcher itself for all game controllers but it seems that BMS only honors those from the first game controller listed. As I already mentioned axis mapping works great for all input devices.
@Korneg
Korneg commented on May 17
Hi,
I had a similar problem. I solved it by replacing the break in the file OverrideSetting.cs (SaveKeyMapping - line 900) by a continue. But please be careful, I did not check for any side-effects.The loop is writing the key mapping file. If it finds the primary device pov, it stops the execution immediately, ignoring all devices that are behind the primary device in the list._
-
Nacman, I had a thought but it’s likely not the issue as I don’t think AL would work at all either. Are you using the default “BMS - Full.key” file or have you altered it after installing AL? AL, on installation I believe, replaces the original and saves it as a backup but it does require a BMS - Full.key to work properly. Was just a thought as I know you like to “tinker”… ;). I’m unsure if messing with it after the AL install will matter if its still called BMS - Full…. hopefully the author will pop in.
-
Hmmm I’m not sure what is happening but…
Could you check:1. “Launch without any setup override” checkbox disabled.
2. “BMS - FULL.key” property is not read-only.If still AL doesn’t work then
3. Delete “C:\Users<username>\AppData\Local\chihirobelmo” folder and restart AL.</username>
-
Hmmm I’m not sure what is happening but…
Could you check:1. “Launch without any setup override” checkbox disabled.
2. “BMS - FULL.key” property is not read-only.If still AL doesn’t work then
3. Delete “C:\Users<username>\AppData\Local\chihirobelmo” folder and restart AL.</username>
I will try this. However I found this on your Github issue page. Is this still a valid issue? The guy below recompiled your code to fix it. I can not recompile code to try.
TITLE of ISSUE: Keymapping works only on first usb game controller #28
STATUS: Open
piotrraczynski opened this issue on May 12 · 2 commentsComments
@piotrraczynski
piotrraczynski commented on May 12 •
FalconBMS Alternative launcher v1.51
FalconBMS 4.34.4I observed that Keymapping seems to work only on first game controller listed by Windows in USB game controllers window.
I have Thrustmaster Hotas X with which both Axis and Key mappings works great with this alternative launcher, awesome.
However when I plugin second controller (in my case it’s Arduino leonardo where I use two rotary encoders and a few toggle switches), then only Axis mapping works, keymapping does not work at all.
When I unplug my Hotas, then keymappings on my Arduino starts to work perfectly (but I lost my hotas), it effectively makes my Arduino first on the list, thus my suspicion that only with the first one on the list, keymapping works at all.
important note, the keymappings works in the launcher itself for all game controllers but it seems that BMS only honors those from the first game controller listed. As I already mentioned axis mapping works great for all input devices.
@Korneg
Korneg commented on May 17
Hi,
I had a similar problem. I solved it by replacing the break in the file OverrideSetting.cs (SaveKeyMapping - line 900) by a continue. But please be careful, I did not check for any side-effects.The loop is writing the key mapping file. If it finds the primary device pov, it stopps the execution immediately, ignoring all devices that are behind the primary device in the list.
-
Its really odd because I have 3 separate USB controllers, all with their own addresses and AL doesn’t know they are part of a HOTAS, so why would AL care what you plug in as long as it is identified?
-
A long shot but perhaps check none of your controllers (the ICP?) has more than 32 “buttons”.
-
The controller’s Joy0 is the Cougar Stick and TQS as designed. No TUSBA yet The second Joy1 is the CH Pro Pedals, no DX buttons and the third is the ICP which has less than 32. Maybe I need to remove the pedals and try to make the ICP Joy1. Dunno
I hope @chihirobelmo chimes in anout the open “issue” on his Github about this. Seems easy enough to recompile code if the guy fixed it himself by making a code edit.
-Nac
-
Hmmm I’m not sure what is happening but…
Could you check:1. “Launch without any setup override” checkbox disabled.
2. “BMS - FULL.key” property is not read-only.If still AL doesn’t work then
3. Delete “C:\Users<username>\AppData\Local\chihirobelmo” folder and restart AL.</username>
I tried all of these things. File is not set to Read Only, I launched without checking the checkbox as described and I deleted the Appdata/local folder as described. i also removed the CH pedals and let it find the ICP as Joy 1 and it did. It still does not work. It maps any changes to the Cougar just fine in AL, but nothing after that. Problem is, I can’t use AL at all. Even if I make the edits manually or through BMS directly, they will be erased by AL if I use it to update any other keymaps.
I hope this can get a resolution.
-Nac