Duke Lvar Values Not Correct
-
Thanks it worked.
For anyone wondering how to do this in FSUIPC:
Page 49 of the advanced FSUIPC manual:
-
Create a file
myevents.txt
in the fsuipc directory -
Create a profile entry there like this:
duke-att-wheel-rst#(A:PLANE PITCH DEGREES, degrees) (>L:var_AP_PitchKnob, number)
bind the duke-att-wheel-rst preset to the button you like.
I assign the
AP_ALT_HOLD
to the press event of the button and theduke-att-wheel-rst
preset to the release of the same button. In that way the AP goes to ATT mode at the current pitch. -
-
Hello! I can’t understand how Left/Right Landing Light works
B:LIGHTING_LANDING_1_Toggle - is this a button to toggle?
(1 K:LANDING_LIGHTS_SET) - is this for the toggle switch? But what does the number 1 (or 2) before the letter K mean? There seems to be no such syntax in Mobileflight.Thank you!
-
@Randolf said in Duke Lvar Values Not Correct:
K:LANDING_LIGHTS_SET is the name of the event, and you should call it with parameter 0 for both OFF and 2 for ON.
If you want to control them separately, you'll need to use the B events.I need one switch for both (left and right) for FSUIPC
I wrote it like this... probably wrong :-( Not workLandingLightOn# (2K:LANDING_LIGHTS_SET)
LandingLightOff# (0K:LANDING_LIGHTS_SET)Can you tell me how to write a correctly?
-
@Rolo-Bach here as I have it done using spad.next for External Power - it's mapped to a StreamDeck button
External Power On
External Power Off
StreamDeck example
-
@Rolo-Bach for the Heater the LVAR:bksq_PreHeater will do the job (0 = OFF, 1 = ON)