So the MD-11 is out and they have published their events and variables Integration Guide | Invernyx Docs. They provide an event ID, does something need to be done in AAO in order to use these ID's?

Thasnks,

Mike

Edited July 3, 20241 yr by mrm0508
Fixed link

I don't see a list for the MD-11...only the B717.  Are they supposed to be the same?

Wrong list, sorry: Integration Guide | Invernyx Docs

The "Variables" are LVars apparently, used like this:
(L:MD11_AFS_SPD, Number)
You can also make AAO read all their names from the sim when the plane has been loaded ("Scripting->Read LVars from simulator")

The "Events" look like standard custom K: events, like those from PMDG. You use them like this:

Quote

Event Name	Event ID
EVT_MD11_PED_CPT_RADIO_PNL_XFER_BT_LEFT_BUTTON_DOWN	69644
EVT_MD11_PED_CPT_RADIO_PNL_XFER_BT_LEFT_BUTTON_UP	69645

Translates into this code:
0 (>K:#69644)
and
0 (>K:#69645)

Be mindful that there is a space character between the 0 and the event. I'm not sure about the "0", could be "1" as well, or any other number. But 0 is the standard for a K-Event.

Wrap the code into RPN scripts and assign the scripts to your buttons. I would strongly recommend to always assign both the Down and Up events. Otherwise it may happen that the aircraft logic will get stuck.
If you only have momentary buttons, that don't send an "up" event, wrap both down and up into a single script:
0 (>K:#69644) (WAIT:100) 0 (>K:#69645)

(To add: normally it should be possible to import/enter the events to the AAO lists, but something doesn't want to work there. I will look into it.)

Edited July 3, 20241 yr by Lorby_SI

Edit:
I just read the documentation again. Apparently you are supposed to write the event-ID to a special LVar to trigger it. But I would suggest trying the method mentioned above first!

The document says that you should do this:

Quote

To trigger a custom event, you can write the value of the event ID to the L:VAR named CEVENT and our code will translate it. 

69644 (>L:CEVENT, Number)
and
69645 (>L:CEVENT, Number)
or
69644 (>L:CEVENT, Number) (WAIT:100) 69645 (>L:CEVENT, Number)

Edited July 3, 20241 yr by Lorby_SI

Bought the plane, installed and tested:

0·(>K:#90236)·(WAIT:100)·0·(>K:#90237)

This is working fine for me, this is the dome light button, down/up wrapped in one script. The (WAIT:100) is not necessary, it just sounded nicer on my computer to leave a little gap between button down and up.

Edited July 3, 20241 yr by Lorby_SI

As the K-Events are toggles, you have to work with the variables if you want deterministic behavior.

Example: scripts for the IRS1 selector:
1. set IRS1 to OFF:
(L:MD11_OVHD_IRS_1_KB,·Number)·1·==·if{·1·(>K:#90112)·}

2. set IRS1 to NAV:
(L:MD11_OVHD_IRS_1_KB,·Number)·0·==·if{·1·(>K:#90112)·}

Hi, happy to see somebody is working on AAO for MD-11.

Is there an option to convert streamDeckProfile to AAOscripts.xml?

The first is published on flightsim.to , but I don't have streamdeck - only Touchmini Behringer.

 

Edited July 11, 20241 yr by MarcinEr

18 minutes ago, MarcinEr said:

Is there an option to convert streamDeckProfile to AAOscripts.xml?

Normally the authors provide the scripts that they made in a separate file that you can install in AAO?

Yeah, but not this author...

Can I upload here the file and ask somebody to make it into AAO scripts?

The file is here:

https://flightsim.to/file/77522/tfdi-md-11-streamdeck-xl-wip

 

 

Edited July 11, 20241 yr by MarcinEr

26 minutes ago, MarcinEr said:

Can I upload here the file and ask somebody to make it into AAO scripts?

That SD profile does not use scripts. It only uses the K: events and LVars that are listed on the TFDi integration documentation:

Integration Guide | Invernyx Docs

You can do the same in AAO too. As shown above.

You can make your life a little easier by extracting the events from that page and import them in AAO using the existing file import. Here is the import file if you want to try that:

https://www.dropbox.com/scl/fi/hbmmfx8yj60oqhyj3q2m1/TFDi_MD11_Lvars_and_Events.csv?rlkey=fhqsybtcc90wgdruriy3qssgv&dl=0

Download it, then use "Scripting->Import Events and Variables from file" to load it into AAO. Make sure to provide a meaningful group name, like "TFDi_MD11" in the lower right corner of the dialog before importing.
But that is only marginally better: you can select the Event codes directly from the AAO list, but the description is missing - you still need the web page from TFDi to figure out which code to select. Remember to configure the "UP" code too if there is one! It still saves you from the trouble of typing the codes into a script first.

In the next version of AAO (4.40) you will be able to enter these numerical codes directly on the button assignemnts too, so you no longer have to create scripts for everything. The import feature will be expanded too, so it includes the description. And there will be a hard coded list of variables and events for the MD-11. 

Edited July 11, 20241 yr by Lorby_SI

I tried to make some scripts - no success 😞

I only need HDG, SPD, ALT knobs to work with Behringer. TFDi made us scroll the mouse, which is really annoying.

Will have to wait till somebody make AAO scripts - these I can handle 🙂

Thanks

26 minutes ago, MarcinEr said:

I tried to make some scripts - no success 😞

I only need HDG, SPD, ALT knobs to work with Behringer. TFDi made us scroll the mouse, which is really annoying.

Will have to wait till somebody make AAO scripts - these I can handle 🙂

Thanks

To repeat - you don't need scripts to operate the MD-11.

• Import my file from above
• Assign the event #86074 to the Right Turn
• Assign the event #86075 to the Left Turn
• Done, there's your heading knob.

Use the "Filter" box below the event list to find the events. It remembers your last search too and you can find events quickly using it.

On the TFDi web page they are called EVT_MD11_CGS_HDG_KB_WHEEL_UP and EVT_MD11_CGS_HDG_KB_WHEEL_DOWN, but those are just names, you cannot use this string in AAO (or anywhere else).

Here are the other wheel codes:

SPD: #86066, #86067
ALT: #86080, #86081
VS: #86086, #86087

Edit: to add, if you insist in creating scripts, they would look like this:
1 (>K:86074)
actuates the EVT_MD11_CGS_HDG_KB_WHEEL_UP action. 
Etc.
As shown in this thread further up.

 

 

Edited July 11, 20241 yr by Lorby_SI

Another advice: the MD-11 knob/button etc. events can be observed in AAO using the event observer dialog

1. Open "Scripting->Watch simulator events"
2. Activate "Ignore spam" in the lower left corner
3. Now click on a button in the cockpit or use the mouse wheel - the triggered event codes should appear in the dialog.

This may be easier than browsing through TFDi's web page.

Remember that the MD-11 "_BUTTON_" events have two codes and they need both Key Down and Key Up assigned to the appropriate event code

For example, for the "AUTO FLIGHT" button you have to assign

• #86094 to Key Down
  and
• #86095 to Key Up

Edited July 11, 20241 yr by Lorby_SI

That helped me a lot! Thank you very much 🙂

Easily programmed 4 knobs now working on some switches.