Jump to content

sschw

Frozen-Inactivity
  • Content Count

    12
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    No

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. ok, reading that helps a lot. For other things, too. But right now I fight with "collection failed" when I want to collect the LVars in AAO and I am a bit confused why. I started AAO as admin (as always), the sim is running, ... well, I will figure it out. Thank you very much for your fast help!
  2. Hi Oliver, I want to switch from the Experimental FBW Version to the Dev version with the StreamDeck from Guenseli. Poorly not everything works. Batteries for example. In the Exp version your code works perfectly, but with the Dev version I guess it has to be A32NX_OVHD_ELEC_BAT_1_PB_IS_AUTO and A32NX_OVHD_ELEC_BAT_2_PB_IS_AUTO because the 10 and 11 variables don't change, clicking the battery button. What I don't understand, what does 10·6·(>K:2:ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE) exactly do? I know, it does much (controlled by the variables in front of it), but I can't find a file where I can see what index do what. Is 10 right in this case? Or has to be a 1, when I change the BAT_10 to BAT_1? I don't know what I change, when I change something and so I don't know if it is important or not...
  3. Yes indeed, that's what I was looking for. Nothing special, just pushing back, left, right, etc. Last question (I hope, but it is really exciting :D): Do you know, what the problem is with the Development version of the FBW Airbus, compared with the Experimental version? For example the Batteries, the ADIRS and other Buttons don't work, but the LVars are all there, it just don't work. I can't find the true difference in the html or js, etc files why it works or not.
  4. Oliver, do you know of an attempt to controll the pushback tug via a streamdeck / aao script? I am not sure how to do so because if I send a appropriate value 1372003475 to KEY_TUG_HEADING multiple times (e.g. 10.000 times) nothing happens and I can't find anything at the internet.
  5. ok thank you very much. I will try that out. I see, you are using AAO local variables. I tryed that too to determine if the RWY TURN OFF Lights are on or of (the LIGHT TAXI is not sufficiant). So I wrote the following peace of script: (L:RWY·TURN·OFF)·0·==·if{1}els{0}·(>L:RWY·TURN·OFF)·2·(>K:TOGGLE_TAXI_LIGHTS) This one works for me (if I ensure that RWY TURN OFF is 0 when the runway turnoff light is off). Now I noticed, that after a little while my button turns off again, obviously because RWY TURN OFF gets 0, I guess. So my question would be, how long are local vars stored in AAO? Why are they stored just for a limited time? Besides, why does this syntax even work?? I thought (L:RWY·TURN·OFF)·0·==·if{1}els{0} means if (RWY TURN OFF == 0) then 1 else 0 but when I click "TEST" in AAO it seems (and works) like if (RWY TURN OFF == 0) then 0 else 1 ...
  6. Ok I am sorry, maybe I write too early. I implemented a version of two switches of the taxi switch now. One controlls the taxi position and one the T.O position. Maybe you can have three positions as a Toggle in AAO in the future (and show it correct on the StreamDeck I mean) Thanks anyway!
  7. Ok, now I got my next problem (especeally with RNP I guess): What I want: I have three buttons on my StreamDeck. Landing light 1, 2 and the taxi light. If both landing lights are on, I want to switch the taxi light automatically to T.O. If one of the landing light goes off or retracted, the taxi light should go to the previous position (either off, if the taxi light switch is off or "taxt" if the taxi switch is on). What I have: Turn on and off the single landing lights is no problem, I use the AAO Script, e.g. 2·(>K:LANDING_LIGHTS_TOGGLE)·(L:LANDING_1_Retracted,·Bool)·0·==·if{0}els{1}·(>L:LANDING_1_Retracted,·Bool) for the left landing light. Setting LANDING_1_Retracted allows me to check, if the single left landing light is on or off. Now i want to add the logic (and here I fail): If (LANDING_1_Retracted switches to on and LANDING_2_Retracted is already on) switch 1 LANDING_LIGHTS_TOGGLE (which means switching the taxi light to T.O.). Is this an approach that could work? How do I check multiple conditions in an if-clause? sschw
  8. Hi all of you, I found the soulution by myself: The variable LANDING_LIGHTS_TOGGLE is doing it: 0·(>K:LANDING_LIGHTS_TOGGLE) Toggles both landing lights and the Nose light 1·(>K:LANDING_LIGHTS_TOGGLE) Toggles just the Nose light (to T.O.) 2·(>K:LANDING_LIGHTS_TOGGLE) Toggles just the left landing light 3·(>K:LANDING_LIGHTS_TOGGLE) Toggles just the right landing light sschw
  9. Hi there, still enjoying the AAO Software with the StreamDeck and the FBW Airbus. I am searching more, reading and learning more about LVars, RPN Scripts and Filemanagement of MSFS then actual flying, but now I need help (again). I want to controll the Airbus Landing Light 1 and 2 separatly, but all I can find is the LANDING_LIGHTS_TOGGLE which controls both of them. What I found is "LANDING_1_Retracted" and "LANDING_2_Retracted" and I can controll both Lights if they are Off or Retracted for their own. But I really don't know how to turn them on! What I found is the following, but it has no KEY_ID or other hint how to control it (SWITCH_OVHD_EXTLT_LANDL doesn't work for me). <UseTemplate Name="ASOBO_LIGHTING_Switch_Light_Landing_Template"> <NODE_ID>SWITCH_OVHD_EXTLT_LANDL</NODE_ID> <ANIM_NAME>SWITCH_OVHD_EXTLT_LANDL</ANIM_NAME> <SIMVAR_INDEX>2</SIMVAR_INDEX> <ID>1</ID> <ANIMTIP_0>TT:COCKPIT.TOOLTIPS.LANDING_LIGHT_L_OFF</ANIMTIP_0> <ANIMTIP_1>TT:COCKPIT.TOOLTIPS.LANDING_LIGHT_L_ON</ANIMTIP_1> <ANIMTIP_2>TT:COCKPIT.TOOLTIPS.LANDING_LIGHT_L_RETRACT</ANIMTIP_2> <RETRACTABLE/> </UseTemplate> <UseTemplate Name="ASOBO_LIGHTING_Switch_Light_Landing_Template"> <NODE_ID>SWITCH_OVHD_EXTLT_LANDR</NODE_ID> <ANIM_NAME>SWITCH_OVHD_EXTLT_LANDR</ANIM_NAME> <SIMVAR_INDEX>3</SIMVAR_INDEX> <ID>2</ID> <RETRACTABLE/> <ANIMTIP_0>TT:COCKPIT.TOOLTIPS.LANDING_LIGHT_R_OFF</ANIMTIP_0> <ANIMTIP_1>TT:COCKPIT.TOOLTIPS.LANDING_LIGHT_R_ON</ANIMTIP_1> <ANIMTIP_2>TT:COCKPIT.TOOLTIPS.LANDING_LIGHT_R_RETRACT</ANIMTIP_2> </UseTemplate> When I search for "landing" or similar strings in the ModelBehaviourDebug window in the flightsim all I find is LANDING_1/2_Retracted 0 or 1. Can someone help me? sschw
  10. Wow thank you so much! Perfect. I think the logic of the FSX RPN is not THAT intuitive to learn, but the things you can do with it are great! Thanks a lot!
  11. Oh word not allowed.. I noticed it is the wrong sub forum. Can the mod be so kind to move it to the payware area of Lorbys? Thanks (and sorry!)!
  12. Hi there, I got a new StreamDeck and therefore using AAO to use it with the MSFS. I downloaded a nice Profile for the FBW A320 and cusomized it myself. Now I want to add two buttons to decrease and increase the baro pressure, but can't find any LVar working for me. What I found is this following piece of code from FBW github whitch looks promising but I am to new to the topic to evaluate it adequately. Can someone of you help me? Best regards sschw <ModelBehaviors> <Template Name="FBW_Airbus_FCU_Baro_Knob"> <DefaultTemplateParameters> <ID>1</ID> <ANIMREF_ID>-1</ANIMREF_ID> <ANIMTIP_0>TT:COCKPIT.TOOLTIPS.AUTOPILOT_PANEL_BARO_KNOB_INCREASE</ANIMTIP_0> <ANIMTIP_0_ON_CURSOR>TurnRight</ANIMTIP_0_ON_CURSOR> <ANIMTIP_1>TT:COCKPIT.TOOLTIPS.AUTOPILOT_PANEL_BARO_KNOB_DECREASE</ANIMTIP_1> <ANIMTIP_1_ON_CURSOR>TurnLeft</ANIMTIP_1_ON_CURSOR> <ANIMTIP_2>TT:COCKPIT.TOOLTIPS.BARO_REF_SET_STD</ANIMTIP_2> <ANIMTIP_2_ON_CURSOR>DownArrow</ANIMTIP_2_ON_CURSOR> <ANIMTIP_3>TT:COCKPIT.TOOLTIPS.BARO_ENABLE_SELECTION</ANIMTIP_3> <ANIMTIP_3_ON_CURSOR>UpArrow</ANIMTIP_3_ON_CURSOR> <ANIMTIP_4>TT:COCKPIT.TOOLTIPS.BARO_REF_SET_STD</ANIMTIP_4> <ANIMTIP_4_ON_CURSOR>Hand</ANIMTIP_4_ON_CURSOR> </DefaultTemplateParameters> <UseTemplate Name="ASOBO_GT_Helper_Suffix_ID_Appender"> <TEMPLATE_TO_CALL>FBW_Airbus_FCU_Baro_Knob_SubTemplate</TEMPLATE_TO_CALL> </UseTemplate> </Template> <Template Name="FBW_Airbus_FCU_Baro_Knob_SubTemplate"> <DefaultTemplateParameters> <ANIM_NAME>AUTOPILOT_Knob_Baro_#ID##SUFFIX_ID#</ANIM_NAME> <ANIM_NAME_KNOB>#ANIM_NAME#</ANIM_NAME_KNOB> <ANIM_NAME_PUSH>AUTOPILOT_Knob_Baro_#ID#_push#SUFFIX_ID#</ANIM_NAME_PUSH> <ANIM_NAME_PUSHPULL>AUTOPILOT_Knob_Baro_#ID#_pushpull#SUFFIX_ID#</ANIM_NAME_PUSHPULL> <ANIMREF_ID>-1</ANIMREF_ID> <ANIMTIP_0>TT:COCKPIT.TOOLTIPS.AUTOPILOT_PANEL_BARO_KNOB_INCREASE</ANIMTIP_0> <ANIMTIP_0_ON_CURSOR>TurnRight</ANIMTIP_0_ON_CURSOR> <ANIMTIP_1>TT:COCKPIT.TOOLTIPS.AUTOPILOT_PANEL_BARO_KNOB_DECREASE</ANIMTIP_1> <ANIMTIP_1_ON_CURSOR>TurnLeft</ANIMTIP_1_ON_CURSOR> <BARO_ID>#ID#</BARO_ID> <MODE_BARO>0</MODE_BARO> <MODE_QNH>1</MODE_QNH> <MODE_STD_BARO>2</MODE_STD_BARO> <MODE_STD_QNH>3</MODE_STD_QNH> <NODE_ID>AUTOPILOT_Knob_Baro_#ID##SUFFIX_ID#</NODE_ID> <PART_ID>AUTOPILOT_Knob_Baro</PART_ID> </DefaultTemplateParameters> <Component ID="#NODE_ID#" Node="#NODE_ID#"> <UseTemplate Name="ASOBO_GT_Knob_Infinite_PushPull"> <ANTICLOCKWISE_CODE> (L:XMLVAR_Baro#BARO_ID#_Mode) #MODE_STD_BARO# != (L:XMLVAR_Baro#BARO_ID#_Mode) #MODE_STD_QNH# != and if{ (L:XMLVAR_Baro_Selector_HPA_#BARO_ID#) if{ #BARO_ID# (A:KOHLSMAN SETTING MB:1, mbars) -- 16 * (&gt;K:2:KOHLSMAN_SET) } els{ #BARO_ID# (&gt;K:KOHLSMAN_DEC) } } </ANTICLOCKWISE_CODE> <CLOCKWISE_CODE> (L:XMLVAR_Baro#BARO_ID#_Mode) #MODE_STD_BARO# != (L:XMLVAR_Baro#BARO_ID#_Mode) #MODE_STD_QNH# != and if{ (L:XMLVAR_Baro_Selector_HPA_#BARO_ID#) if{ #BARO_ID# (A:KOHLSMAN SETTING MB:1, mbars) ++ 16 * (&gt;K:2:KOHLSMAN_SET) } els{ #BARO_ID# (&gt;K:KOHLSMAN_INC) } } </CLOCKWISE_CODE> <PULL_CODE> (L:XMLVAR_Baro#BARO_ID#_Mode) #MODE_BARO# == if{ #MODE_STD_BARO# (&gt;L:XMLVAR_Baro#BARO_ID#_Mode) } els{ (L:XMLVAR_Baro#BARO_ID#_Mode) #MODE_QNH# == if{ #MODE_STD_QNH# (&gt;L:XMLVAR_Baro#BARO_ID#_Mode) } } </PULL_CODE> <PUSH_CODE> (L:XMLVAR_Baro#BARO_ID#_Mode) #MODE_STD_BARO# == if{ #MODE_BARO# (&gt;L:XMLVAR_Baro#BARO_ID#_Mode) } els{ (L:XMLVAR_Baro#BARO_ID#_Mode) #MODE_STD_QNH# == if{ #MODE_QNH# (&gt;L:XMLVAR_Baro#BARO_ID#_Mode) } els{ (L:XMLVAR_Baro#BARO_ID#_Mode) ! (&gt;L:XMLVAR_Baro#BARO_ID#_Mode) } } </PUSH_CODE> <CENTER_RADIUS>0</CENTER_RADIUS> <COUNT>36</COUNT> <OVERRIDE_PUSH_ANIM_CODE> 0 100 (L:XMLVAR_Baro#BARO_ID#_Mode) #MODE_STD_BARO# == (L:XMLVAR_Baro#BARO_ID#_Mode) #MODE_STD_QNH# == or ? 50 (O:_PushAnimVar) ? </OVERRIDE_PUSH_ANIM_CODE> <WWISE_EVENT>QNHknob</WWISE_EVENT> <WWISE_EVENT_1>QNHknob</WWISE_EVENT_1> <WWISE_EVENT_2>QNHknob</WWISE_EVENT_2> </UseTemplate> <!--Disables FCU baro knob emissive--> <UseTemplate Name="ASOBO_GT_Emissive_Gauge"> </UseTemplate> </Component> </Template>
×
×
  • Create New...