Duke Turbine controlling condition lever with Spad.next
-
I believe the B:Vars should allow the one-press control that you're looking for, but _Cut_Off is used for shutting the engines down, and _High_Idle is used for the run position. If you can't get the B_Vars to work, the L:Vars I provide should work no matter what. Since the Turbine Duke only has cutoff and run position condition levers, the value only ranges from 0 to 1. Let me know if you can't get this to work, and I can see if the support team has any suggestions, since they work with hardware a lot more than I do.
-
@Burnhaven hey Randy, just checked, and it works for me from AAO, setting the var
L:BKSQ_ConditionLever_1
and 2 to values 0 and 1 with a button sets the condition levers accordingly. Check that you don't have any other conflict, maybe with the native in-sim bindings for condition or mixture levers. -
@Randolf Thanks I'll try again. Actually I do have Space bar + 1 or 2 setting mixture/condition to high idle and Shift + 1 or 2 setting them to cutoff. So I should remove any such references in msfs controls. ?
The tricky part is that I had 4 buttons available :
one is used for start up, turning on a few things and cutting off throttle/condition in preparation for hitting the starter. ( condition didn't respond to this)
Another is for shutdown. A third activates the inertial separators and the fourth deactivates inertial separators.But during actual startup the condition levers need to go to high idle at specific points ( rpm) in the start process. It may be the path of least resistance to just use my keyboard bindings for condition.