Hi. I bought AAO mainly for the Behringer X Touch mini. I have to say that I am really happy with AAO software: I can use some templates (like A32NX, and it works really nice) that I find at flightsim dot to, and I'm doing my first steps to create my own templates.

I started with Cessna CJ4 Citation and I managed to make a few buttons and knobs to work (Baro, VS, HDG and ALT knobs and buttons, FD, NAV...), but there are a couple that I couldn't get to work: VNAV button and screen map "RANGE" knob.

I tried filtering all scripts with VNAV or RANGE or MAP words and assigning each of them, but it doesn't work. I tried with "Scripting -> Watch simulator events", but nothing is detected when i activate VNAV button or RANGE knob.

My question is not so much about how I can do these assignments but about whether they can be done with the scripts present in the AAO. I know that it is not possible to include each and every one of the necessary scripts for each plane, but I assumed that both the plane and the buttons or knobs were not very specific and I would find them among those included in the software; my fault, I understand the impossibility of including every detail and it doesn't stop me from thinking it's a great piece of software.

So, getting the point: the fact that I can't find, for example, the assignment of a button or knob (not recognizable by "Watch simulator events"), does it mean that it can't be done? Or should it be done making a new script? (which it would be a very difficult task for me, since I don't have any experience on it).

Thank you for your attention.

 

Edited August 18, 20223 yr by barbaryto

1 hour ago, barbaryto said:

So, getting the point: the fact that I can't find, for example, the assignment of a button or knob (not recognizable by "Watch simulator events"), does it mean that it can't be done?

No, not at all. Those lists are just for your convenience, and they actually can't contain every single control item - because every aircraft developer can invent them at will. Only some aircraft will make use of the default events - there are many more options. LVar, Hvars and BVars, up to entire scripts also need to be considered. In your case, take a look into the "HTML Variables" group, specifically those named "AS1000_". The Asobo and the WT G1000 are controlled by HVars, and a selection of them you will find in here. AAO can't show you those in the Observer, because they aren't events at all. The app cannot watch for variables changing in the sim - when it doesn't know what their name may be.

Any other HVars, LVars and BVars that are not present in the lists in AAO can either be added manually (bottom of the menu "Scripting") or you simply wrap them into an RPN script and call that. A script could for example look like this: "1 (>L:anlvarnamethatIfoundsomehwereonline, Number)"
AAO doesn't have to know them to make use of them. That being said, BVars are a lot more involved - there is a special chapter about those in the AAO manual (LVar to BVar mapping)

Unfortunately there is quite the learning curve regarding these things with MSFS - because the aircraft developers don't seem to adhere to any standards. Every plane is different, using different methods (even more than one) - there are even aircraft that don't allow any external controls.

Some aircraft developers publish the names of the LVars/HVars/BVars that are available, but many don't. Luckily you can (kind of) seek them out using the Developer Mode of MSFS (behavior debug), by looking into the behavior definition XML files of the plane or in some cases by letting AAO collect the LVars from the sim (if the plane is controlled with those)

Edited August 18, 20223 yr by Lorby_SI

Thank you very much Lorby_SI for your quick and detailed reply. I'll try to get used to all that complex terminology.

Meanwhile, I found some answers in the AAO thread on the official MSFS forum. As indicated there, I learned to solve the RANGE knob issue (for CJ4) by adding H variables and it worked.

I just couldn't find the way for the VNAV button, but it's ok, it's just one button.

Thank you!

Edited August 18, 20223 yr by barbaryto

44 minutes ago, barbaryto said:

Thank you very much Lorby_SI for your quick and detailed reply. I'll try to get used to all that complex terminology.

Meanwhile, I found some answers in the AAO thread on the official MSFS forum. As indicated there, I learned to solve the RANGE knob issue (for CJ4) by adding H variables and it worked.

I just couldn't find the way for the VNAV button, but it's ok, it's just one button.

Thank you!

Is that with the WT mod active? Then you need a script for VNAV
(L:WT_CJ4_VNAV_ON, Number) ! (>L:WT_CJ4_VNAV_ON, Number) 1 (>H:WT_CJ4_AP_VNAV_PRESSED)

Asobo default is different:
Either (L:XMLVAR_VNAVButtonValue, Number) ! (>L:XMLVAR_VNAVButtonValue, Number)
Or 1 (>H:AS01B_FMC_1_AP_VNAV)

 

Edited August 18, 20223 yr by Lorby_SI

23 hours ago, Lorby_SI said:

Is that with the WT mod active? Then you need a script for VNAV
(L:WT_CJ4_VNAV_ON, Number) ! (>L:WT_CJ4_VNAV_ON, Number) 1 (>H:WT_CJ4_AP_VNAV_PRESSED)

Asobo default is different:
Either (L:XMLVAR_VNAVButtonValue, Number) ! (>L:XMLVAR_VNAVButtonValue, Number)
Or 1 (>H:AS01B_FMC_1_AP_VNAV)

 

Hi. Thank you. I didn't even know there is a CJ4 mod! I will try the WT mod right now.

And I will try to learn how to handle and insert the scripts that you kindly gave me.

(My last challenge is FLC button).

Thank you very much for your priceless and patient support.