Headache Saver - Alt Launch Override
-
We have to start calling it “New Launcher” not “Alt Launcher”.
I think it’s expected that it will be a bit awkward, for a while … it still feels “bolted on” when it comes to things like overwriting stuff in cfg … esp for people who have complex setups… trying to port older key files with 32 buttons-per-device … or supporting multiple pov hats etc.
But it is the way forward, definitely!
-
Yes…it’s different. But I can’t say that I hate it…
-
@MaxWaldorf said in Headache Saver - Alt Launch Override:
@Zeus we will move forward with AL…
The old ways won’t stay forever…Easy Max easy.
Ensure that EVERYTHING is working nicely foe everyone before considering doing so.BTW … Where is the close button on ALT LAUNCHER?
-
@Dee-Jay hi mate
It’s located on the top right of the AL Launcher window (black cross) -
@Bad-Boy said in Headache Saver - Alt Launch Override:
@Dee-Jay hi mate
It’s located on the top right of the AL Launcher window (black cross)Just found right at this time. … Thank you BB!
-
@Zeus
I also found out the hard way but since I switched to the 128 buttons per device for the cockpit and needed to consolidate some settings between 4.36 and 4.37 it was better for me to start assigning again from scratch although I could have restored from my local git. Anyway the 4.37 Feels really nice! now back to 4.36 config to get the exact same key bindings and axis mapping. Is there a way with the new launcher to also get the same keymapping easily instead of doing the manual assignments again for my old 4.36? I tried copying the BMS - Auto from 4.37 but no luck. What would be the proper way and then remove the new added 4.37 bindings? -
@ohommes I just copied over my 4.36 key file to 4.37 … works within BMS.
I haven’t tried replacing ‘BMS-Auto.key’ to see if AL will “import” it… but I’ve done that in the past, with AL, it has worked.
I don’t think any callbacks have been deleted/deprecated in 4.37, except for
SimEcmPower
. Try manually yanking that line, and see if you have better success? -
I’ve got a very fast glimpse at 4.37 and found out this annoying reconfiguration at every ( two in my case ) new starting. I admit that have had not time to rtfm, just downloaded, installed, reconfigured the cockpit and took off. The second time I’ve launched BMS and must to reconfigure Joysticks and pots, I’ve had thought to make some mistake somewhere. Tuesday I’ll be again at home and I’ll give it a try, checking that box. many thanks for info. Thanks a million for that update and for the “new horizon “ Best wishes for new year everyone.
G -
@airtex2019 said in Headache Saver - Alt Launch Override:
I haven’t tried replacing ‘BMS-Auto.key’ to see if AL will “import” it… but I’ve done that in the past, with AL, it has worked.
I did the migration yesterday. To me it seems like AL (or just L :-)) imports the xml-files Setup*.xml, and then builds+exports a key file when the Launch button is pressed.
I’m a bit mystified about how and when the Full and Auto key files are built though. I can see that the Auto file is from when my BMS session stopped yesterday (not when it launched). Perhaps the Full is not really used or built, but just works as a template for all available callbacks.
I took a diff of the Full key file between 436 and 437 and I concur that only the SimECMPower callback is gone. Other than that its new additions. One can probably run without those
-
@MaxWaldorf said in Headache Saver - Alt Launch Override:
@Zeus we will move forward with AL…
The old ways won’t stay forever…It’s a true move forward for keys indeed. The current system is quite obsolete.
Wrt axes we need a way to assign virtual axes though, since (unless I missed something) AL doesn’t enable it. I guess you may re-write AL files to circumvent the limitation but it’s not really what it’s designed to be.
-
@MaxWaldorf said in Headache Saver - Alt Launch Override:
@Zeus we will move forward with AL…
The old ways won’t stay forever…I fear my comment was misunderstood. I didn’t mean to imply that we shouldn’t move forward…I think we have to. My only point was that I think many pilots (certainly myself) didn’t understand or missed the fact that not checking the “launch without override” would wipe out changes. Hence the wish that the default state was checked so that at least it wouldn’t have clobbered my work (which after digging more sounds like it may have been saved to the backup folder anyway).
Regardless, I hope the New Launcher / BMS Launcher (I like that name) continues to evolve and also allows for easy migration from version to version. While there will always be a need to address deprecated and new callbacks / functions, importing over any previous mappings is really a simple task (most of us I think do it in a semi-automated manner now using file compare tools). Anyway, if the Launcher mapping data can be stored in an accessible format, I have no doubt that a) it will be better than today and b) allow those with larger, more complicated setups, to have an easy way to upgrade.
-
Seems to be no way now to store your throttle AB position but needs re mapping every session
-
@Dee-Jay - yes…I only found the Close Buttons in the Launcher on “instinct”. A change in the color for these buttons (or a highlight?) might be in order, as they are very difficult to pick out from the blue background as they are now.
Also - the Close buttons for RTT don’t seem to work - I ended up having to use Task Manager to kill the windows to get them to close and disappear.
-
@airtex2019
I copied the .xml files from 4.37 to 4.36 folder and all works like a charm!! This is very very nice!! Finally found the love for the new launcher and keymapping config! I find it really really nice! Awesome!!! -
@ohommes You were already using AL with 4.36 ?
-
@CheckPoint
No I was not but now I am using the launcher to also start 4.36 -
If you could have a checkbox to disable the pop-up while launching BMS from the new launcher when the “override” option is checked, that would be VERY appreciable
The best would be to have the possibility to upload other keystroke (such as BMS_BLANK), or at least, to be able to SAVE it with an other name.
Whithout these options, i’m forced to use the old launcher or the be VERY annoyed be the pop-up and sound when i’m launching falcon.
Also, if i miss-click and de-check the overide option, i will be forced to reconfigure all my pit… Really Frustrating. -
I really like the Alternative Launcher integrated into BMS, I think its fastest way for new players to set their HOTAS but I have noticed that two options are missing in AL.
-
Selecting Mirrors is missing in the AL
-
Ability to use the right foot pedal as an option to apply both brakes, in AL it only allows you to use the left (which I hate)
I can get around this problem by setting those two options in the Setup page of BMS, selecting the check button on the launcher so they remain when I launch. So a little bit more work in those areas would be nice, overall though love the Launcher.
-
-
What does the new Launcher bring to the table aside from assigning axis/button callbacks? As someone who has never used the AL before, and just maps axis via UI and assigns callbacks directly through the .key file, what else does the Launcher offer?
-
@Atlas First and foremost it is a “launcher” … a one-stop shop for (downloading and) launching all the various processes in our ecosystem… WDP/MC, RTT, IVC, TacView, etc.
The axis/button/key binding stuff, is a bit orthogonal.
If I’m being honest, that would be best if factored out into a separate tool… let’s call it “Alternative Binder”. With a clear [Save] button that would write the axisMapping and deviceSorting and key file, etc… (and not just do that invasively/unexpectedly, eg. every time the launcher starts up).
Some of the checkbox options in AL are overlapping with stuff in Config.exe tool too… which is definitely showing its age and should be replaced. There could be an “Alternative Configurator” tool to provide a one-stop shop for tweaking all config (stuff in cfg params plus also the green checkboxes in-game, like pilot-model and smart-scaling).
Again, with a clear explicit [Save] button that would write those cfg/dat values. Never applied accidentally, or implicitly, when you’re just trying to start WDP or TacView or something.
/my 2c