This may be premature, but does anyone know if the 777 Can use the PMDG 737 scripts and events, or do we have to wait until they are recreated for the 777?

Depends on what you mean. 

The (PMDG:...) type events in AAO are different and the data structure for their SDK variables is too. AAO is being updated at the moment to accomodate these changes, and there will be a Web CDU for the plane too.

If you mean "the other way", going outside the PMDG SDK, = the ROTOR_BRAKE codes and LVars, I haven't checked that yet, but I would expect them to be different too. Most likely those will have to be re-investigated from scratch. 

My primary focus for AAO is mapping to a warthog (seat belts/smoke/xpdr/ext lights/chrono et/trims/gear/flight control axes)

As always with AAO, the rotorbrake events are easy to see. Many of the switch actions I get from here seem restricted to toggle or plus/minus type of events rather than setting a state. From memory this is quite common with some PMDG aircraft. One example, beacon:

Beacon toggle script command: 11401·(>K:ROTOR_BRAKE)
Watching simulator events when physically clicking beacon shows 11401 but then something I have not worked out with 11403 and 11404. I'm sure many will know what I'm failing to spot there. Either way, sending 11401 is enough to toggle the state of this switch. Part 1 figured out. Now I want a switch to only turn on or turn off the beacon, so I'm going to have to read its state somehow.

My thought was to read LVars to verify on/off status of switches. From the P3D days, these were slightly strange collection Lvars, of which the beacon was L_switch_114_a. To find the same in MSFS 777, you need to go to:

\Community\pmdg-aircraft-77w\SimObjects\Airplanes\PMDG 777-300ER\Behaviors\PMDG773ER_VC.xml

Ok finally in here we search for beacon and see that the variable is still indeed 114_a. I grab this bit from line 6240:
<ANIM_CODE>
 (L:switch_114_a, number)
</ANIM_CODE>

and I use AAO to observe (L:switch_114_a, number) and see that it is going between 0 and 100.0 for beaon off and on.

So now to put these together in a script. This is good enough for me - script for beacon turn on:
(L:switch_114_a,·number)·0·==·if{11401·(>K:ROTOR_BRAKE)}

Script for beacon off:
(L:switch_114_a,·number)·0·!=·if{11401·(>K:ROTOR_BRAKE)}

You can repeat the same process for many other switches.

 

12 hours ago, crap_landing_dave said:

My primary focus for AAO is mapping to a warthog (seat belts/smoke/xpdr/ext lights/chrono et/trims/gear/flight control axes)

As always with AAO, the rotorbrake events are easy to see. Many of the switch actions I get from here seem restricted to toggle or plus/minus type of events rather than setting a state. From memory this is quite common with some PMDG aircraft. One example, beacon:

Beacon toggle script command: 11401·(>K:ROTOR_BRAKE)
Watching simulator events when physically clicking beacon shows 11401 but then something I have not worked out with 11403 and 11404. I'm sure many will know what I'm failing to spot there. Either way, sending 11401 is enough to toggle the state of this switch. Part 1 figured out. Now I want a switch to only turn on or turn off the beacon, so I'm going to have to read its state somehow.

My thought was to read LVars to verify on/off status of switches. From the P3D days, these were slightly strange collection Lvars, of which the beacon was L_switch_114_a. To find the same in MSFS 777, you need to go to:

\Community\pmdg-aircraft-77w\SimObjects\Airplanes\PMDG 777-300ER\Behaviors\PMDG773ER_VC.xml

Ok finally in here we search for beacon and see that the variable is still indeed 114_a. I grab this bit from line 6240:
<ANIM_CODE>
 (L:switch_114_a, number)
</ANIM_CODE>

and I use AAO to observe (L:switch_114_a, number) and see that it is going between 0 and 100.0 for beaon off and on.

So now to put these together in a script. This is good enough for me - script for beacon turn on:
(L:switch_114_a,·number)·0·==·if{11401·(>K:ROTOR_BRAKE)}

Script for beacon off:
(L:switch_114_a,·number)·0·!=·if{11401·(>K:ROTOR_BRAKE)}

You can repeat the same process for many other switches.

 

Thank you for this insightful explaination!

 

I was wondering if you can help me here. I have a stream deck and I'm trying to make a MCP out of it. I've managed to use an old profile for another aircraft (737)

 

My issue here is that I'm trying to find the position of the switch and display that on the stream deck. I'm able to turn it on or off using the rotor break values, however if i manually change the switch using my mouse, I wanted it to reflect on my stream deck as well.

Any idea?

 

Thanks

On 6/27/2024 at 9:06 PM, Falconfly said:

Thank you for this insightful explaination!

 

I was wondering if you can help me here. I have a stream deck and I'm trying to make a MCP out of it. I've managed to use an old profile for another aircraft (737)

 

My issue here is that I'm trying to find the position of the switch and display that on the stream deck. I'm able to turn it on or off using the rotor break values, however if i manually change the switch using my mouse, I wanted it to reflect on my stream deck as well.

Any idea?

 

Thanks

Hi, unfortunately I'm not a stream deck user so I can't comment on this. I saw that the AAO topics seemed a lot more active in the PMDG forum itself so maybe you'll get some help there, or if Lorby drops into this thread hopefully.

On 6/27/2024 at 1:06 PM, Falconfly said:

My issue here is that I'm trying to find the position of the switch and display that on the stream deck. I'm able to turn it on or off using the rotor break values, however if i manually change the switch using my mouse, I wanted it to reflect on my stream deck as well.

Any idea?

There are two ways of doing this.

1. Following the instructions provided by @crap_landing_dave above, you can read the animation LVar to determine the position of a switch or the emissive LVar (if there is one) to check if something is lit
Example: The VNAV button is split in two parts (this code is from the behavior file,
\Community\pmdg-aircraft-77w\SimObjects\Airplanes\PMDG 777-300ER\Behaviors\PMDG773ER_VC.xml
 
"<!-- 212A - VNAV Switch "
and
"<!-- 212B - VNAV Annunciator"

The code to operate the switch you can calculate from the <CALLBACKCODE> section in the first item:
21201 (>K:ROTOR_BRAKE) 21204 (>K:ROTOR_BRAKE)
(left mouse button down and released)

The variable telling you whether the button is lit is in the second item:
(L:switch_2121_a, Number)

2. Use the PMDG SDK variables, called "(PMDG:...)" in AAO. This is not possible yet for the 777, you will have to wait for version 4.30. AAO needs to read those values from the aircraft's SDK logic first, before you can use them.
(PMDG:MCP_annunVNAV)

Edited June 29, 20241 yr by Lorby_SI