Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments)
-
For those of you that transfer over logbooks between versions, friendly 4.37 reminder: if you transfer your logbook and then use the same callsign and name for the Alternative Launcher, it will overwrite your old logbook. In general, back it up anyway in another folder altogether, but I did this one recently.
Edit to add:
@chihirobelmo Can I copy over my 4.36 BMS-AUTO.key and carry over my keyboard command mappings too? -
@Snake122 you can but then no callbacks for VR and ECM
-
@chihirobelmo DId I notice that the native 4.37 launcher no longer asks for logbook? I actually tried the 2.1.3 first, then hit the 4.37 desktop icon and noticed 2.2.0 and the logbook is no longer a thing for it.
Is there anyway to add new callbacks to old BMS-AUTO.key before the carry over (I have a lot of experience editing the .key over the years)?
In past experience, it seems like AL makes the .key each time and will overwrite any manual changes to the .key. I couldn’t find where the .key commands are kept in an attempt to find a workaround of that DX 28 issue previously mentioned which is still present in 2.2.0 but still a very minor issue of course,
-
@Snake122 no logbook ask for now…there was an issue when it’s integrating to 4.37…but I try fix it for U1
-
First time user for this alternative launcher with 4.37
I assigned my HOTAS Warthog axis in the launcher, that works fine in BMS. But there are no keys assigned to either the stick or the throttle.
How do I load the Warthog-keyfile in the alternative launcer? Or this done as in previous versions in the BMS-controller-setup itself?Do I miss any functions or such a thing when I load the keyfile in BMS itself?
(Sorry for the probably rather dumb questions… )
-
When I tried to use my DX key file, the new launcher messed up my device order.
-
I just realized you can use the launch without setup override. I did not see that option and it appears many did not.
-
Sorry for the lame question, I started using alternate launcher only because of 4.37, and I am stuck with the option of load and save keymaps. I want completely empty keymap list, because I use my own keys, I don’t even know the originals, and I don’t want to switch anything accidentally.
Could anyone help me in this, how can I load the BMS-Empty.key, or how can I delete the alternate laucher keys with a few clicks? Going through on the list and delete every keys manually is very far from how I planned to spend my evening, so anyone who know any solution, please help.
Thank you in advance!
-
@VO101_Tom said in Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments):
Sorry for the lame question, I started using alternate launcher only because of 4.37, and I am stuck with the option of load and save keymaps. I want completely empty keymap list, because I use my own keys, I don’t even know the originals, and I don’t want to switch anything accidentally.
Could anyone help me in this, how can I load the BMS-Empty.key, or how can I delete the alternate laucher keys with a few clicks? Going through on the list and delete every keys manually is very far from how I planned to spend my evening, so anyone who know any solution, please help.
Thank you in advance!
I think you can copy and rename
BMS - Empty
asBMS - Full
(back it up first). AL takesBMS Full
and createsBMS - Auto
. This is my understanding - makes backups and try and see if it works for you. -
@CriticalMass Thanks, but I started with this Overwrite the BMS - Full.key with the “Blank” in the Config folder. Doesn’t work, AL start with the same keysets as before.
-
@CriticalMass Thank you it’s working now. I deleted the BMS - Auto.key, and restarted AL, and it’s empty now. Thank you
-
@VO101_Tom said in Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments):
@CriticalMass Thank you it’s working now. I deleted the BMS - Auto.key, and restarted AL, and it’s empty now. Thank you
Ah, maybe you need to delete the XML files too; AL maybe builds BMS Auto from the XML…black magic
-
@CriticalMass It seems this is enough, delete Auto key meantime replaced the Full with the Blank, and next restart the key list was empty in AL. I already set my keys, and works well in BMS.
-
@VO101_Tom @CriticalMass from what I can see, the XML files contain the device-axis mappings, and dx button-mappings … but the keyboard bindings are only stored in BMS-Auto.key
-
Happy new year!
Launcher is great! I’m not sure if this has been discussed previously. I’m an owner of an old cougar throttle with analog cursors microstick, antenna and range pots with a lot of dirt at center positions. My rudders and for some reason warthog stick have the same problem too. Using dead zones is critical for me and maybe for others too. So it would be helpful if dead zone capability is added for the axis. Also axis shaping may be useful for those that fly other aircrafts than F16. Do you plan to add such options later on?Keep up the good work! -
@lgbomber there is a deadzone option on every axis.
-
Hi
I can see only ECM On switch but no Off for some reason
-
@danaos75 blind old man needs help…
thanks… -
So I tried the AL with the .37 download and loved how easy it was to setup the HOTAS and set the DX shift. Once I got into BMS though realised it kept swapping my POV hats between my throttle and stick, so I gave up and went back to the stock launcher.
Today I investigated it further and tried swapping the POV numbers in the user cfg I imported from .36……… BINGO!!! It now keeps my throttle POV hat on the throttle and the stick POV hat on the stick.
The AL is a huge bonus, easy to use and I wish I’d looked at it prior to this new release. Great addition to the standard install!
-
Ok, after giving a try to the “soon to be the official one” but still “alternative” launcher today, I’ve to say that I really appreciate the controller setup, very friendly and easy to interact with. Thanks a lot. I also appreciate the philosophy of writing/back-up under the hood Falcon BMS.cfg according to the user selection.
I’ve a question btw, is there a way to set a module as default to turn on? Like, I know that with my configuration I’ll always fly with the RTTClient on, is there a way to launch it always (beside clicking on it every time before flight)?
Thanks