Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments)
-
@Icer Nothing makes sense to a computer illiterate like me. Maybe C modified AL2.0 very recently to chase bugs ( as I think he said he would )so that whilst AL 2.0 worked at first, now it has a bug.
-
@danster said in Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments):
@Icer Nothing makes sense to a computer illiterate like me. Maybe C modified AL2.0 very recently to chase bugs ( as I think he said he would )so that whilst AL 2.0 worked at first, now it has a bug.
I would say the creation of the 4.33 U1 folder is not intended and totally useless, yes. When you (don’t reinstall BMS) uninstall AL you are using the Falcon.BMS.Alternative.Launcher.Setup.msi program, correct? It is the proper way to uninstall it. IF it leaves the C:\Falcon BMS 4.33 U1 folder intact I would delete that manually. My next step would be to go back to regedit and search for any reference to “BMS 4.33” and delete them (I just did a run, all mine are still gone). Then do a clean install of AL with Falcon.BMS.Alternative.Launcher.Setup.msi … see what you get.
-
Did you uninstall 4.33U1 from Setup.exe, not the windows control panel?
BMS reg remains if you uninstall BMS from windows control panel, then,
If there were 4.33 reg remain AL will create a setup for the 4.33U1 folder, or if there were no 4.33 folded AL will create the folder. -
@Icer You’re a genius. I hope I haven’t spoken too soon, but at least now AL runs. Thank you!!
-
@chihirobelmo said in Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments):
Did you uninstall 4.33U1 from Setup.exe, not the windows control panel?
BMS reg remains if you uninstall BMS from windows control panel, then,
If there were 4.33 reg remain AL will create a setup for the 4.33U1 folder, or if there were no 4.33 folded AL will create the folder.@chihirobelmo - In my case I had remnents of 4.33 in the registry when I installed AL 2.0 and it (thinking 4.33 was installed) created the 4.33 U1 folder, but I had no errors. I just went ahead and uninstalled AL, deleted the 4.33 folder (knowing the registry was clean) and reinstalled. No 4.33 U1 folder was created and all is well. I’m hoping @danster has the same result.
-
@danster said in Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments):
@Icer You’re a genius. I hope I haven’t spoken too soon, but at least now AL runs. Thank you!!
Cool, I tested out my theory and it worked so I was hoping you were ok…
-
@Icer Thanks to you both!! The regedit was the trick
-
Not sure this is the right place for this, but I’m having an issue with binding. Sometimes dx signals that alt launcher will list at the bottom in the key bind page will not be seen in the bind menu. In this case it is my ww f16 stick, the paddle switch switches from 7 to 8 when pressed in. 8 shows attention bottom of alt launcher, but 8 will not bind. Is there a way to bind using bms and have alt launcher not override it again? Or some other workaround? I might just set it to 7 release to get
the same effect. Slt launcher has this issue with toggle switches too sometimes, although with persistence they will work. -
@Cloudless
Created an issue on GitHub but you can continue here or on Github either one you want.
https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/issues/55In this case it is my ww f16 stick, the paddle switch switches from 7 to 8 when pressed in.
I’m not sure this part. You mean your F-16 stick deactivate DX7 then activate DX8? What has been activating your DX7 till then? What is your joystick product name, WARTHOG, WINWING or FSSB?
-
@chihirobelmo said in Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments):
@Cloudless
Created an issue on GitHub but you can continue here or on Github either one you want.
https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/issues/55In this case it is my ww f16 stick, the paddle switch switches from 7 to 8 when pressed in.
I’m not sure this part. You mean your F-16 stick deactivate DX7 then activate DX8? What has been activating your DX7 till then? What is your joystick product name, WARTHOG, WINWING or FSSB?
Sorry I abbreviated, it’s the Winwing F-16 ex. DX7 is simply activated until the switch is pressed activating 8 as far as I can tell. So it’s acting a bit like a toggle (except it’s half-virtual).
-
Is there any ETA for the 2.1.0? I am waiting to udpate for that one.
-
@javo Unless you need over 32 DX , the 2.0 works fine without any issues, as written above and tested here as well.
-
Hi @chihirobelmo, firstly, I can’t live without AL - you have delivered a superb tool - 2 releases in a year and a half is a testament to the stability and feature set.
One thing that is causing some issues is that AL is reordering the “theater.lst” entries and specifically placing base KTO at the bottom - this is causing problems for Mission Commander users.
Wondering why AL has to reorder and if it’s a real need then perhaps reverse ordering it, so KTO is at the top.
Again, thanks.
CriticalMass
-
@tiag Is there another way to use all the inputs of Virpil Joystick and Winwing throttle?
-
@Virus said in Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments):
@tiag Is there another way to use all the inputs of Virpil Joystick and Winwing throttle?
I believe VirPil can break the throttle down into two 32DX devices but have no firsthand knowledge. For the Warthog you simply use the “Release” function to get switch positions without a DX# to show up/work.
-
Love AL Thanks Chihirobelmo!
-
@Icer yeah but I have a winwing throttle and a virpil base and grip
-
@Virus SimAppPro will also split your device into 4x32, but I personally think you’d be better off waiting for AL’s update to use all buttons.
-
@chihirobelmo I pushed “launch” today and my computer crashed out to a reboot. After that I can’t start alt launcher anymore, I’m getting errors.
I’m thinking reinstalling might fix this? My xml files probably got zapped. Where are they usually stored? -
@Cloudless In you User config folder where the Falconbms config file is located.