March 2, 20251 yr Im in Fs2020 and tried guenslis new AAO scripts for teh inibuilds A350 which all work except push and pull knobs on the FCU.. he says he wrote them for FS2024 and he couldnt check FS2020 I found the Lvars documented... on the inibuilds forums they are for example INI_FCU_MANAGED_SPEED_BUTTON Bool Push Airspeed Knob INI_FCU_SELECTED_SPEED_BUTTON Bool Pull Airspeed Knob INI_FCU_MANAGED_HEADING_BUTTON Bool Push Heading Knob INI_FCU_SELECTED_HEADING_BUTTON Bool Pull Heading Knob How would I make these work in AAO to use with an xtouch mini (im sure its simple but i tried a few things with no success ) thanks !
March 2, 20251 yr Commercial Member Sounds weird. Why would inibuilds use different variables in those two sims? I don't have that aircraft, sorry. Did you compare the variables with guenselis scripts? Are they really different? Also, the variable name is not enough, you also need the value(s) that the variable has to be set to. I would recommend taking a look at the behavior code of these knobs, using the MSFS developer mode Tools->Behaviors and Ctrl-G Edited March 2, 20251 yr by Lorby_SI LORBY-SI
March 2, 20251 yr Author 37 minutes ago, Lorby_SI said: Sounds weird. Why would inibuilds use different variables in those two sims? I don't have that aircraft, sorry. Did you compare the variables with guenselis scripts? Are they really different? Also, the variable name is not enough, you also need the value(s) that the variable has to be set to. I would recommend taking a look at the behavior code of these knobs, using the MSFS developer mode Tools->Behaviors and Ctrl-G Guenslis scripts has for example 1 (>IE:AIRLINER_FCU_SPD_KNOB_Pull) 1 (>IE:AIRLINER_FCU_SPD_KNOB_Push) and 1 (>IE:AIRLINER_FCU_HDG_KNOB_Pull) 1 (>IE:AIRLINER_FCU_HDG_KNOB_Push) Totally different as you can see, but that doesnt seem to have any effect in FS2020 ...havent tried it in FS2024 will have a look with FSdev mode, but thats not something im familiar with .. BTW the inibuilds post with those lvars I posted have a linked PDF and this info " You can view a list of the key LVARs on the iniBuilds A350 Airliner via this sheet here or via the attached PDF for reference. What are LVARs? LVARs are "Local Variables" which are used to read/set various switches or system behaviours in the aircraft. How to use LVARs? You can bind the listed LVARs to various hardware switches, axis or buttons to control their virtual counterparts on the iniBuilds A350 Airliner externally using 3rd Party software (e.g. Mobiflight, Axis and Ohs, SPAD.Next or FSUIPC etc.)" appreciate the help
March 2, 20251 yr Commercial Member 3 minutes ago, wakevortex said: Totally different as you can see, These are InputEvents, not LVars. Those assets are't related at all. Maybe FS20 simply has different ones? You can find the IE that are valid for your current aircraft in AAO on the normal event selection dialog, on the tab "MSFS IEs". IEs can also sometimes be written as BVars. For example, the heading knob for the A300 (also inibuilds) was bound to this: 1·(>B:INSTRUMENT_HEADING_KNOB_Push_Mode) and 1·(>B:INSTRUMENT_HEADING_KNOB_Pull_Mode) Edited March 2, 20251 yr by Lorby_SI LORBY-SI
March 2, 20251 yr Commercial Member 5 minutes ago, wakevortex said: How to use LVARs? You can bind the listed LVARs to various hardware switches I wish that was true. IMHO LVars are the worst possible option for this. I would first try them in the RPN editor 1 (>L:INI_FCU_MANAGED_SPEED_BUTTON, Number) or 1 (>L:INI_FCU_SELECTED_SPEED_BUTTON, Number) If those will indeed work, go to "Scripting->Read Lvars from sim". Let the process complete. Then the current LVars will also be listed on the normal events selection dialog in AAO (use the Filter box at the bottom to find them) so you can assign them to buttons directly. LORBY-SI
March 2, 20251 yr Author 5 minutes ago, Lorby_SI said: I wish that was true. IMHO LVars are the worst possible option for this. I would first try them in the RPN editor 1 (>L:INI_FCU_MANAGED_SPEED_BUTTON, Number) or 1 (>L:INI_FCU_SELECTED_SPEED_BUTTON, Number) If those will indeed work, go to "Scripting->Read Lvars from sim". Let the process complete. Then the current LVars will also be listed on the normal events selection dialog in AAO (use the Filter box at the bottom to find them) so you can assign them to buttons directly. Thanks !..will try that and see how I get on ... will let you know
March 2, 20251 yr Author Sadly they didnt work as RPN s (1 (>L:INI_FCU_MANAGED_SPEED_BUTTON, Number) or 1 (>L:INI_FCU_SELECTED_SPEED_BUTTON, Number) difficult I know for you as you dont have the aircraft ...but thanks for trying ! Ive asked guensli if he has any ideas.... or maybe someone else here has it working?
March 2, 20251 yr Commercial Member 40 minutes ago, wakevortex said: Sadly they didnt work as RPN s (1 (>L:INI_FCU_MANAGED_SPEED_BUTTON, Number) or 1 (>L:INI_FCU_SELECTED_SPEED_BUTTON, Number) difficult I know for you as you dont have the aircraft ...but thanks for trying ! Ive asked guensli if he has any ideas.... or maybe someone else here has it working? Make sure to not only look at the animation of the knob, but instead what it is supposed to do. The movement and the "action" are not the same thing, one can work without the other. Also, these LVars may need a different sequence of values (first 1 then after a short pause 0, or 1 on key down and 0 on key up) - that kind if thing. Did you try the BVars hat I posted above, those from the A300? They sound similar enough. Also, IEs can usually also be triggered as BVars, you should try that as well For example: 1 (>B:AIRLINER_FCU_SPD_KNOB_Pull) 1 (>B:AIRLINER_FCU_SPD_KNOB_Pull_Pull) 1 (>B:AIRLINER_FCU_SPD_KNOB_Pull_Set) 1 (>B:AIRLINER_FCU_SPD_KNOB_Pull_Inc) Edited March 2, 20251 yr by Lorby_SI LORBY-SI
March 2, 20251 yr Author 18 minutes ago, Lorby_SI said: Make sure to not only look at the animation of the knob, but instead what it is supposed to do. The movement and the "action" are not the same thing, one can work without the other. Good point... was just watching the knob for push or pull.... will do some more experimenting and try those A300 vars.... again thanks !
March 3, 20251 yr Author Guensli came back with an answer..it seems the variables ARE different, but only by Capital/small letters ! what a strange one ! below from Guensli " I just have discovered that 2020 and 2024 use different variables. so, e.g. for SPD Knob in 2024 it is: 1 (>IE:AIRLINER_FCU_SPD_KNOB_PULL) and for 2020 it is 1 (>IE:AIRLINER_FCU_SPD_KNOB_Pull) So, 2020 users have to change in the AAO script editor this for BARO, SPD, HDG, ALT and VS from PULL/PUSH to Pull/Push Thats just a workaround, I "officially" do only support 2024"
Create an account or sign in to comment