Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments)
-
@ic1 maybe your old device references are stuck in the registry. I had an issue previously where had to reinstall my HOTAS drivers and it made new entries, leaving the old ones intact - this led to multiple areas of confusion.
Maybe your device name =/= device is a product of this and the registry might need some TLC…
-
@Icer I already did everything you said and I still can’t get past the physical detent. I’m staying with TARGET at https://forum.falcon-bms.com/topic/22643/jc1-dx128-profile
-
@CriticalMass I checked the registry in all the places related to Thrustmaster but didn’t find anything. I’m staying with TARGET at https://forum.falcon-bms.com/topic/22643/jc1-dx128-profile
-
release v2.1.1
https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/releases/tag/v2.1.1
- Now supports both 4.35 DX32 and 4.36 DX128 key mapping.
- Fixed AB/IDLE detent when the throttle axis is inverted.
- Removed “resorting device orders by assigned callback numbers” feature as it may cause some issues.
- Avoid assigning Q-W-E-R-T-Y keys to other callbacks not to remove the comm menu assignments.
-
@chihirobelmo said in Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments):
release v2.1.1
https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/releases/tag/v2.1.1
- Now supports both 4.35 DX32 and 4.36 DX128 key mapping.
- Fixed AB/IDLE detent when the throttle axis is inverted.
- Removed “resorting device orders by assigned callback numbers” feature as it may cause some issues.
- Avoid assigning Q-W-E-R-T-Y keys to other callbacks not to remove the comm menu assignments.
@chihirobelmo - Setting up the shortcuts for Mission Commander\Weapons Delivery Planner and MC went fine but WDP gives this error when it starts. Seems like after accepting that it starts normally. Something i’m doing wrong?
-
@chihirobelmo Great! Thanks again for your efforts.
-
I love the AL and I couldn’t live without it. But I am also interested in the F-16 throttle kit from Winwing. Are they fully compatible?
ThanksJudy
-
@Judy130101 said in Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments):
I love the AL and I couldn’t live without it. But I am also interested in the F-16 throttle kit from Winwing. Are they fully compatible?
ThanksJudy
According to the latest update it might be worth to try AL with WinWing Orion throttle again:
“now 3-switch ON-ON-ON button is supported.”https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher/releases/tag/v2.1.3
-
@Razor161 Excellent news, thanks
-
I saw the 3 way switch option check box in AL for the dogfight switch. Is this the only on-on-on support?
I have some of those switches on my ICP that I haven’t been able to fully program since 2.0 I think. I used to be able to manually edit the source .key and add the DX buttons associated manually but now since it appears that AL is creating it’s own .key everytime, I can’t find the source to make those edits.
-
-
D drtbkj referenced this topic on
-
I have been using the Morphine profile for my Hotas Warthog for a long time. Unfortunately, this profile no longer works quite well for 4.36 and, furthermore, its support and improvements are no longer possible, since the creators no longer take care of it.
I have seen that the AL has possibilities to assign keys and practically replicate what I have now.Does anyone know if there is a manual or video that teaches how to do it?
Thanks in advance
-
-
@fvelazdem It is quite intuitive. I would recommend you dive right in, and come back here once you hit a challenge you can’t figure out.
-
Some of the postings in Atlas’s VR in 4.37 thread and mentioning AL has me thinking of a few questions @chihirobelmo and/or anyone else in the know.
First, while there are rumblings of some potential UI changes (obviously VR compatible UI, but also someone offered to work on the UI in another thread and multiple BMS members said, thanks but no thanks, don’t waste your time), I’m still assuming that the Alternative Launcher will still be an option. My big question, is there a way to carry over my current assignments from 4.36 to 4.37 even if new callbacks are created for the 4.37 .key? I remember spending weeks of what would have been BMS flight time on my remapping for 4.36 partly because I wanted to lay every thing out again, but I would like to be up and going faster this time.
Second is a issue I’ve had on the back burner for awhile, so no big hurry and hopefully some one else can give me a hand too. My ICPs Drift C/O switch are the DX buttons 24 up /28 middle /25 down. AL 2.1.3 detects all three in the lower left hand part as I press them. I can assign commands to 24 and 25, but after being mapped interestingly AL will detect them in the bottom but not bounce to their assignment entry line like other assigned commands. It will detect the 28 middle button state when switch is in NORM but it is not assignable at all. Overall I get that this is a similar issue to a 3 way slider switch like dogfight or even speedbrake on some throttles. My work around is to just leave the switch physically in “NORM” and mapped DX 24 up to Tog. ON/NORM! but if I ever forget I’m out of sync with the BMS switch state. Overall, very minor inconvenience that I can work with but is there a way to get the DX 28 middle mapped?
-
is there a way to carry over my current assignments from 4.36 to 4.37 even if new callbacks are created for the 4.37 .key?
copy XMLs to 4.37 as usual but not the key file…AL will copy 4.37 FULL.key to AUTO.key,
-
2nd one: like in my case WINWING F-16 THROTTLE has DX13/14/15 for SPD BRAK OPEN/NEUTRAL/CLOSE but I can assign them no problem…I fixed it for 2.1.3 after I get WINWING THROTTLE… just set button UP/DOWN before go to small key mapping window then after open the window, back the switch to NORM.
-
@chihirobelmo said in Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments):
2nd one: like in my case WINWING F-16 THROTTLE has DX13/14/15 for SPD BRAK OPEN/NEUTRAL/CLOSE but I can assign them no problem…I fixed it for 2.1.3 after I get WINWING THROTTLE… just set button UP/DOWN before go to small key mapping window then after open the window, back the switch to NORM.
Thanks for the replies! Will do on the 4.37 upgrade I know that was a feature you added recently and I am using 2.1.3. However, it for some reason doesn’t work with the middle position, lower left hand reporting state shows DX 28 being pressed but if I open up the assignment box and have the switch up or down and move either way into the middle DX 28, it still says awaiting input in the assignment dialog box. Don’t spend lots of time on this though, I have a fine work around. If you need I can put a ticket in at GitHub for further tracking in the future if it is a bug and not operator/hardware issues.
-
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,