Has anyone had a look at the Bro and Mins knobs in the new 777 yet? In the 737 there was a nice easy rotor brake value to use but doesn't seem to be the case ion the 777. Looks like some mad code in the xml...

You could use the numeric K: events from the PMDG SDK. They are not in the AAO lists yet, but you can calculate the required event ID from the .h header file in the Documentation/SDK folder inside the 777s addon package in your Community directory and then use them in AAO scripts as (>K:#nnnnn). Make sure to read the chapter about PMDG planes in the AAO manual!

The events are in the bottom half of the file. PMDG starts with a baseline number for user event IDs (THIRD_PARTY_EVENT_ID_MIN = 69632) and the actual events are listed as offsets from that base. 

Example:
#define    EVT_EFIS_CPT_MINIMUMS                            (THIRD_PARTY_EVENT_ID_MIN + 182)
=> 69632 + 182 = 69814

Using the PDMG mouse codes for wheel up and down the scripts are

16384 (>K:#69814)
and
8192 (>K:#69814)

Another example:
#define    EVT_EFIS_CPT_BARO                                (THIRD_PARTY_EVENT_ID_MIN + 191)    

16384 (>K:#69823)
and
8192 (>K:#69823)

And another one:
#define    EVT_EFIS_CPT_BARO_STD                            (THIRD_PARTY_EVENT_ID_MIN + 192)

536870912 (>K:#69824)
(that is the code for the left mouse button)

Please note that this is off the top of my head, I can't test this at the moment. Should be about right though.

Edited June 26, 20241 yr by Lorby_SI

Thanks, unfortunately couldn't get this to work. Added in the SDK broadcast data and added the repeating script. The 777 uses the same event numbers as you described, but doesn't seem to work for left or right mouse wheel on the baro or mins

 

I tried using this method for the IFE button and it works OK

536870912·(>K:#69649)

 

so perhaps there's something different about rotary knobs...

Edited June 26, 20241 yr by daan_vb

57 minutes ago, daan_vb said:

Added in the SDK broadcast data and added the repeating script.

Not necessary and dangerous. You are sending events, not reading anything. There is no repeating script for the 777 yet. Do not run the one from the 737, that can crash the app. The data structure is different.

57 minutes ago, daan_vb said:

so perhaps there's something different

Try other mouse codes ( left-right button), and double check that the codes haven't changed, they are in the .h file too. Look for other events too.

Edited June 26, 20241 yr by Lorby_SI

58 minutes ago, daan_vb said:

so perhaps there's something different about rotary knobs...

Well, the heading selector works (+2180)
16384·(>K:#71812)

8192·(>K:#71812)

Apparently the .h file is not final - and the event IDs are different from what is listed in there (they are actually identical to those from the P3D 777). Guess there will be an update soon, and/or an official release of the 777s SDK.

Edited June 26, 20241 yr by Lorby_SI

Thanks for looking into it. I got it working like this. Its a bit basic but seems to work

1·(>L:CAMinsKnob,·number)·(WAIT:100)
0·(>L:CAMinsKnob,·number)

-1·(>L:CAMinsKnob,·number)·(WAIT:100)
0·(>L:CAMinsKnob,·number)

1·(>L:CABaroKnob,·number)·(WAIT:100)
0·(>L:CABaroKnob,·number)

-1·(>L:CABaroKnob,·number)·(WAIT:100)
0·(>L:CABaroKnob,·number)