Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments)
-
@jc1
I had the same issue. AL mixed up the device names. As long as it works correctly, everything is fine. -
@Razor161 Yeah, I heard that. I have been working with chihirobelmo on this for many posts in this this thread. I still can’t get the afterburner to kick in after I pass my AB physical detent.
-
@chihirobelmo I wanted to get AL to work with my devices, but that AB detent issue just won’t go away. I will stay with my TARGET key assignments in the Warthog forum at https://forum.falcon-bms.com/topic/22643/jc1-dx128-profile
-
@jc1 said in Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments):
@Razor161 Yeah, I heard that. I have been working with chihirobelmo on this for many posts in this this thread. I still can’t get the afterburner to kick in after I pass my AB physical detent.
So you go through this process:
Click “Assign” next to Throttle: CHPPP:RZ
Move the throttle to the AB Detent (~3/4 travel)
Click “AB Detent” (it should show a green AB bar if you push it past the detent now)
Click “Save”
Move Throttle past the AB detent - the whole bar should turn green, but no?Sure looks like the throttle itself is working fine, have you tried setting AB in the Setup\Controllers\ (select your throttle in the pull-down) in BMS?
-
@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.
-
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.