Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments)

[chihirobelmo]

@jc1 said in Falcon BMS Alternative Launcher (Easy Setup, Keep Joystick Assignments):

@chihirobelmo I don’t assign device. AL seems to do that when I start up AL. This is my DeviceSorting.txt

Try “CLEAR” those CH pedal assigns for “Throttle” and “Throttle Right”, then assign Warthog throttle axis to “Throttle”.

[jc1]

@chihirobelmo I removed CH PEDALS from DeviceSorting .txt. I uninstalled AL. Removed the xml files and reinstalled AL. Also “Clear” Throttle and Throttle Right. And still can’t get the AB to kick in after I pass the physical detent. Get this screen showing the wrong devices for stick and throttle.

[Razor161]

@jc1
I had the same issue. AL mixed up the device names. As long as it works correctly, everything is fine.

[jc1]

@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.

[jc1]

@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

[Icer]

@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?

[CriticalMass]

@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…

[jc1]

@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

[jc1]

@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

[chihirobelmo]

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.

[Icer]

@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?

[mvanderlubbe79]

@chihirobelmo Great! Thanks again for your efforts.