Alt Launcher 2.1.0
-
@jc1 I think you have to unassign one of the throttles, right think, for single engine, then power is applied to both, weird but it works.
-
@CriticalMass I’ve only assigned one of the throttles. The AL pictures show AB and IDLE.
-
@jc1 said in Alt Launcher 2.1.0:
@CriticalMass I’ve only assigned one of the throttles. The AL pictures show AB and IDLE.
But they should be in the same position/level.
-
@CriticalMass Don’t know what you mean. Are you saying my pictures of AL should show AB and IDLE in the same position?
-
I assume you are flying Viper (single engine) and your throttles are fixed together as a single throttle?
I’m not a my machine right now, so can’t talk you through it, but, the bars should be the same position. If you can decipher the text describing what you need to do, it should work
-
@CriticalMass Yes I fly Viper and the two throttles are locked together.
-
@jc1 so click Assign on Right Throttle and un-assign it. When only Throttle (left) is assigned it moves both bars. Are you setting AB on Left and Idle on Right?
Of course, the issue may be something else, but I’ve never seen the bars at different positions, only when left and right are both assigned and at different postions.
Looks like BMS is picking up the Right throttle.
-
@CriticalMass This is what the throttle picture looks like when both throttles are at IDLE. I’m assigning to the top of the picture that says “Throttle”. I don’t assign anything to the bottom where it says “Throttle Right”.
-
@jc1 said in Alt Launcher 2.1.0:
@CriticalMass This is what the throttle picture looks like when both throttles are at IDLE. I’m assigning to the top of the picture that says “Throttle”. I don’t assign anything to the bottom where it says “Throttle Right”.
Sorry, was away. @CriticalMass is correct, only the “Throttle:” should be assigned, click “ASSIGN” button for “Throttle Right:” and Clear any assignment you may have. Full Throttle (before AB) in the BMS setup will look like this… ignore my Idle Detent, I have my stick custom calibrated to ignore that portion of the throttle travel, my “0” starts at the Idle stop. I use “Alt-I” for Idle position during Ramp starts.
-
@Icer @CriticalMass I never assigned to “Throttle Right”. I only assigned to “Throttle”. At this point I still have the problem with having to do AB for taxing.
-
@icer, @CriticalMass Could you guys post a picture of the AB IDLE part of AL section 2.19. Here’s mine.
-
@jc1 you don’t assign you throttle or AB or Idle Detent in KEY MAPPING, all are assigned on AXISASSIGN. By moving the device and saving the assignment.
-
@Icer Did what you said but still need AB for taxiing.
-
@jc1 Perhaps it’s time to start afresh.
I would move the AL XML and “BMS Auto.key” files somewhere safe, then open AL and see if the problem persists.
If it’s OK you could
diff
the old and new files and potentially copy old stuff back into the new XML/“BMS Auto.key” files.I’ve heard AL might be corrupting files!
-
@jc1 said in Alt Launcher 2.1.0:
@Icer Did what you said but still need AB for taxiing.
@jc1 - have you tried the DX128 script I sent and resetting the throttle up (will need both KEYMAPPING and AL AXISASSIGN as it has a new name) so you have full throw and proper AB implementation, and finally checking it in BMS Setup afterwards to be sure? You are disengaging the parking Brake, yes? Can’t remember if the jet will even move with it on and pretty sure you will get a warning, but anything is possible…
-
@Icer Yes I tried the DX128 script you sent. It’s only for the throttle, not the stick. I did check BMS setup afterwards, not good. And yes I did disengage the brake.
-
@jc1 said in Alt Launcher 2.1.0:
@Icer Yes I tried the DX128 script you sent. It’s only for the throttle, not the stick. I did check BMS setup afterwards, not good. And yes I did disengage the brake.
It’s only for the throttle because the Warthog stick needs no intervention for every position to be seen by AL and/or BMS Setup right out of the box!