Hello,

I have the following variable from the file PMDG_777X_SDK.h:

float FUEL_QtyCenter; // LBS

Using AAO Observer, I have the variable (PMDG:FUEL_QtyCenter), but it returns no value.

How can I use these PMDG variables that have an entry (PMDG:XXXX)

 

Edited August 2, 20241 yr by ezkampf

Make sure to use AAO version 4.40. The data structures have been updated to the latest PMDG SDK

 

On 8/2/2024 at 11:57 AM, Lorby_SI said:

Make sure to use AAO version 4.40. The data structures have been updated to the latest PMDG SDK

 

Hello. Yes, I was using it, but then I noticed that I made a mistake by putting the automatic scripts for the PMDG DATA and PMDG CDU, fixed now.

Currently, I've been having trouble setting the flaps. There are some sim events as shown in the attached images, but they don't work.

Can you provide guidance on this or is it a limitation of PMDG?

58 minutes ago, ezkampf said:

but they don't work.

How and where are you using them exactly?

In general they are all supposed to work when used correctly. The custom events of the new 777 are more partial to what value they are operated with.

Edited August 3, 20241 yr by Lorby_SI

23 minutes ago, Lorby_SI said:

How and where are you using them exactly?

In general they are all supposed to work when used correctly. The custom events of the new 777 are more partial to what value they are operated with.

In the image, you can see a script where the event is called, but nothing happens. You can see in the observer window that the script was executed.

Im trying to call flaps 5

Edited August 3, 20241 yr by ezkampf

1 hour ago, ezkampf said:

In the image, you can see a script where the event is called, but nothing happens. You can see in the observer window that the script was executed.

Im trying to call flaps 5

That is because you are calling it with the value "1". With the PMDG 777 the events are very sensitive to what value you are sending to them. Many of those events that used to work with just 0 or 1 now require the PMDG Mouse Codes instead:

536870912·(>K:#74705)·131072·(>K:#74705)

(left mouse down - left mouse release)

The PMDG Mouse Codes are in the events treelist too, in their own group (and in the AAO manual, and the PMDG SDK doc). In this case, you can probably get away with just the left mouse down code. But I wouldn't count on it, it is possible that the PMDG logic will lock up at some point when you always only send the Down events. That goes for the ROTOR_BRAKE codes too.

Edited August 3, 20241 yr by Lorby_SI

41 minutes ago, Lorby_SI said:

That is because you are calling it with the value "1". With the PMDG 777 the events are very sensitive to what value you are sending to them. Many of those events that used to work with just 0 or 1 now require the PMDG Mouse Codes instead:

536870912·(>K:#74705)·131072·(>K:#74705)

(left mouse down - left mouse release)

The PMDG Mouse Codes are in the events treelist too, in their own group. In this case you can probably get away with just the left mouse down code. But I wouldn't count on it.

The code provided works.

How can I understand which mouse code I should use for each type of script? So far, I have only had issues with flaps, but I am just wondering.

1 minute ago, ezkampf said:

How can I understand which mouse code I should use for each type of script? So far, I have only had issues with flaps, but I am just wondering.

I have no idea, you would have to ask PMDG. The PMDG SDK docs don't mention any of this. It's always trial&error. I always try 0 and 1 first, then the left down/up. With some events it seems obvious that they require mouse wheel codes (rotary encoders). And some require actual values. The only indication is their name or associated control in the VC.

1 minute ago, Lorby_SI said:

I have no idea, you would have to ask PMDG. The PMDG SDK docs don't mention any of this. It's always trial&error. I always try 0 and 1 first, then the left down/up. With some events it seems obvious that they require mouse wheel codes (rotary encoders). And some require actual values. The only indication is their name or associated control in the VC.

Got it.

Thank you for your prompt help. It solved a problem that seemed significant to me. I will be more attentive to alternatives beyond numerical values.