Solved 4.37 - Alternative Launcher (AL)
-
I need to assign a callback which is not available in the AL key mapper list, to a button .
For example the OTWRadioMenuStep callback which his not available in the key mapper list.
If I edit the “BMS - Auto” keyfile and manually add the callback and save it, then when I restart using the AL, the added callback is not assigned in the key mapper list and it deletes the edit from the keyfile.
How can I add callbacks so that they appear in the key mapper list ?
-
@Dee-Jay Thanks DeeJay, I tried using the legacy launcher with 4.37 and using my old keyfile.
In the legacy Setup screen for the controllers all the buttons are working but when I go into 3D none of my control buttons are working in the cockpit.
***Edit: I got it working finally. I had to completely uninstall 4.37 and then reinstall and then set it up using the legacy launcher from the beginning WITHOUT EVER using the Alternative Launcher.
I used the legacy setup screen, my 4.36 key file and 4.36 device sorting file and it works well now.***
-
I am afraid that you cant use the BMS - Auto that way.
You will have to activate the option “Launch Without Any Setup Override” … modify/edit one of the existing .key (you can copy/paste, rename then edit the BMS - Auto) … then load it in Setup.
The point with AL, is that it automatically set the BMS - Auto key at launch, so you cant use AL and having your personal .key (or you’ll have to load it anytime you launch the soft) … So you have to use the legacy launcher
… :\Falcon BMS 4.37\Launcher.exe
or
activate the “Launch Without Any Setup Override” option (but in that case, AL is almost useless and you’ll have to redefine axis in Setup like before.
or
simply proceed as before 4.37, and use the legacy launcher.
Be aware that AL is also changing you .cfg to add the 128 buttons / USB device option.
So … it will make your .key different than before using the classic on without the 128 button / device option.
… It tooks me several hours to understand that AL was the cause of all my troubles yesterday.
Yo are lost? …
Normal.
-
So we have to hope that AL NEVER be made mandatory.
Progress is good… if there is not a part of regression. -
@Rouge1512
AL is not a regression … but needs probably adjustments.
Or … needs to remain “alternate”. -
@Dee-Jay Thanks DeeJay, I tried using the legacy launcher with 4.37 and using my old keyfile.
In the legacy Setup screen for the controllers all the buttons are working but when I go into 3D none of my control buttons are working in the cockpit.
***Edit: I got it working finally. I had to completely uninstall 4.37 and then reinstall and then set it up using the legacy launcher from the beginning WITHOUT EVER using the Alternative Launcher.
I used the legacy setup screen, my 4.36 key file and 4.36 device sorting file and it works well now.***
-
@zap737 said in 4.37 - Alternative Launcher (AL):
For example the OTWRadioMenuStep callback which his not available in the key mapper list.
That’s a pretty weird/special callback … and, obviously it works somehow – it’s in all our BMS-Auto.key files by default and everyone’s comms menus work ok…
What exactly are you trying to do … just change the key which opens a particular comms menu? Or make a duplicate (eg. a dx button assignment)?
AL definitely still has some limitations… eg. support for dx press/release bindings, and multiple hats, and chorded key-sequences, etc. Tweaking the radio comms menus, might be another such known-limitation, for now. (not sure)
-
@airtex2019 That is just one example of callbacks that I use but are not in the AL list.
I have multiple controllers with a complicated keyfile that use these callbacks. For example, I use a shift button on my thottle along with most of the buttons on my ICP controller to control the comms menu (QWERTY) and the OTWRadioMenuStep to move through each sub menu.
I think the AL is fine for very simple setups, but it falls well short for my requirements.
-
-
@zap737 yes I think folks with highly specialized pits, are going to need to continue to hand-manage their key and cfg files, for the near future.
in the far future? my vision would be, no need for a “launcher” at all – just start BMS from a simple desktop shortcut, and everything you need is in there – like any other windows game or program.
-
@zap737 said in 4.37 - Alternative Launcher (AL):
I think the AL is fine for very simple setups, but it falls well short for my requirements.
I use at least 9 USB devices that have DX/some keyboard/Axis mapped and 2 USB devices more that are keyboard mapped. I don’t think that’s a simple setup, but I get that there are some .key tricks I’m not using. But I switched to the AL since that anytime accidentally didn’t have one of those plugged in, chaos would ensue with my device sorting and then the keyfile offsets. Once I got used to it, it’s been far less of a headache than my old .key editing and has a lot of other nice conveniences like quick theater switching.