Hey there,

just wondering if you would consider doing a MCDU file for the 777?

Thanks 

I already have a WebCDU for the 777. Just waiting for the actual release, I don't have early access.

12 hours ago, Lorby_SI said:

I already have a WebCDU for the 777. Just waiting for the actual release, I don't have early access.

Hi mate,

Can you confirm when WebCDU will be available for MSFS PMDG 777 please ?

52 minutes ago, raam123 said:

Hi mate,

Can you confirm when WebCDU will be available for MSFS PMDG 777 please ?

I will have to update AAO itself too, so that all events and variables from the PDMG SDK are available. I am aiming for end of the week.  No promises though, that is a very short timespan to test everything new in version 4.30 of AAO.

Edited June 26, 20241 yr by Lorby_SI

1 minute ago, Lorby_SI said:

I will have to update AAO itself too, so that all events and variables from the PDMG SDK are available. I am aiming for end of the week.  No promises though, that is a very short timespan to test everything new in version 4.30 of AAO.

Thank you 🙂

Hello @ll,

if you are willing to help speed things up, please consider sending an email with your proof of purchase to the support address (last page of the AAO manual). Then you can have the 4.30 and the WebFMC in advance to try them out. The more the merrier...

Edited July 2, 20241 yr by Lorby_SI

Email sent.

Thank you,

Mike

7 hours ago, Lorby_SI said:

Hello @ll,

if you are willing to help speed things up, please consider sending an email with your proof of purchase to the support address (last page of the AAO manual). Then you can have the 4.30 and the WebFMC in advance to try them out. The more the merrier...

UPDATE: My mistake, I have to use the Insert sim event button to get to them.

I might be blind but I don't see the PMDG 777 events in the Script Editor. If I search for a variable I see the listing for the 777.

Edited June 29, 20241 yr by mrm0508

7 hours ago, Lorby_SI said:

Hello @ll,

if you are willing to help speed things up, please consider sending an email with your proof of purchase to the support address (last page of the AAO manual). Then you can have the 4.30 and the WebFMC in advance to try them out. The more the merrier...

The event 1 (>K:#69726) should start the number 1 engine but it does not. If I use 9401 (>K:ROTOR_BRAKE) it works. I noticed the PMDG773ER_VC.xml executes the ROTOR_BRAKE event in the callback code. Would that mean the #69726 can't be used?

5 minutes ago, mrm0508 said:

UPDATE: My mistake, I have to use the Insert sim event button to get to them.

I might be blind but I don't see the PMDG 777 events in the Script Editor. If I search for a variable I see the listing for the 777.

Not all of them work, especially the BARO and MINIMUMS encoders are somehow out of order. PMDG apparently uses a different logic on those buttons (as is apparent in the behavior code too) and forgot to update the SDK to match.

34 minutes ago, mrm0508 said:

The event 1 (>K:#69726) should start the number 1 engine but it does not. If I use 9401 (>K:ROTOR_BRAKE) it works. I noticed the PMDG773ER_VC.xml executes the ROTOR_BRAKE event in the callback code. Would that mean the #69726 can't be used?

Be mindful that some of those events require the PMDG Mouse Codes to function, passing "1" as a value might not work.

This turns the engine 1 starter knob to the left:
8192·(>K:#69726)
and this to the right:
16384·(>K:#69726)

Personally I think that the PMDG 777 SDK is still buggy, see my note above about baro and minimums. For the time being, using the ROTOR_BRAKE codes sometimes is the better option.

Edited June 29, 20241 yr by Lorby_SI

15 minutes ago, Lorby_SI said:

Be mindful that some of those events require the PMDG Mouse Codes to function, passing "1" as a value might not work.

This turns the engine start knob to the left:
8192·(>K:#69726)
And this to the right:
16384·(>K:#69726)

Personally I think that the PMDG 777 SDK is still buggy, see my note above about baro and minimums. For the time being, using the ROTOR_BRAKE codes is the better option. At least you know that they work.

Do you want to know which of the AAO events don't work 1 but do with 8192? Is it better to do it through the support email?

The baro and mins implement a "proportional" knob, clicking then holding and dragging increases the increment rate, no idea how to simulate that with a script, probably easier to just use the mouse click event type.

7 hours ago, Lorby_SI said:

Hello @ll,

if you are willing to help speed things up, please consider sending an email with your proof of purchase to the support address (last page of the AAO manual). Then you can have the 4.30 and the WebFMC in advance to try them out. The more the merrier...

The event 1 (>K:#69726) should start the number 1 engine but it does not. If I use 9401 (>K:ROTOR_BRAKE) it works. I noticed the PMDG773ER_VC.xml executes the ROTOR_BRAKE event in the callback code. Would that mean the #69726 can't be used?

6 minutes ago, mrm0508 said:

Do you want to know which of the AAO events don't work 1 but do with 8192? I

Not really, that is not my problem to solve. Nowhere does the MSFS SDK specification say that 1 is the only value that a K: event is operated with, quite the contrary (the default value is actually 0)

As for the PDMG SDK, it is entirely their choice. Make sure to read the SDK documentation PDF and the chapter in the AAO manual about PMDG planes. It is absolutely normal that their events are operated with the Mouse Codes (which are described in the specs and also available in the AAO event list)

\Community\pmdg-aircraft-77w\Documentation\SDK

Edited June 29, 20241 yr by Lorby_SI

12 minutes ago, mrm0508 said:

no idea how to simulate that with a script

@daan_vb apparently did

PMDG 777 Scripts - AxisAndOhs Support - The AVSIM Community

PMDG 777 Baro and Mins Knobs - AxisAndOhs Support - The AVSIM Community

Edited June 29, 20241 yr by Lorby_SI

Well, I will say the CDU works great.