January 21, 20233 yr I'm finally getting the hang of Axis and Oh's, using it with an XTouch Mini. Thankful that there are many events already available to pick from to assign to the buttons, especially for the PMDG 737. I've now been building an aircraft automated script to set LEDs. That has been working well. I just wanted to check if I'm searching the right way to find an LVar (or other type var) as I find how to detect if the baro is in STD mode. I couldn't find one in the "PMDG737MSFS" category. I did a Read LVars from the sim and have not found one that works in the "Local simulator variables" or other categories. I've looked in the PMDG-NG3_VC_800.xml file and found a few that looked interesting, such as (L:switch_993_73X, number), but none of them are changing their value from 0 in the Observe Variable dialog. Is there anything else I can look through? Or is this likely a case where there is no available Var yet from PMDG?
January 21, 20233 yr Commercial Member Things like that would normally be a job for the PMDG SDK. There is a chapter in the AAO manual about how to configure and use it. Once you've activated their SDK you can access the provided PMDG variables (they are in the lists in AAO). But. In this case, I don't think that there is a variable. The information only exists inside their internal logic. I guess that you will have to do this with a script (=query the current baro setting, and if it equals 2992, show STD. Something like that.) Edited January 21, 20233 yr by Lorby_SI LORBY-SI
January 21, 20233 yr Hello, I have found (and tested on my PMDG 737-800) the two variables (L:EFISSTDRSTPush, Number) and (L:EFISSTDRSTRelease, Number). If STD is active, they have the value 1.0, otherwise they have the value 2.0. I hope, this helps. Regards, Frank
January 21, 20233 yr Author Thanks Lorby for the suggested script idea. I do already have the SDK activated, which apparently was done when I had installed the Fergo Virtual CDU app. Thanks FraSim. Wow nice find! Those are working as you describe. How did you ever find them? The only place I see them, when doing a search in the PMDG files, is Community\pmdg-aircraft-738\SimObjects\Airplanes\PMDG 737-800\sound\sound.xml, which is not where I would have ever thought to look. I wonder why PMDG would not publish ALL their local vars out through their SDK (PMDG_NG3_SDK.h).
January 21, 20233 yr I use this check: (A:KOHLSMAN·SETTING·MB:0,·inHg)·100·*·near·2992·==· Edit: I use this method as it is common to almost every aircraft and I can just copy/paste between scripts. If true the script turns on the LEDs around the baro knob. Regards, Daz Edited January 21, 20233 yr by Dazzlercee23
January 21, 20233 yr Author 6 hours ago, FraSim said: (L:EFISSTDRSTPush, Number) After more testing, this also changes if I push ANY of the buttons on the EFIS panel (RST, CTR, TFC, STD), so can't use this after all.
January 21, 20233 yr Author 6 minutes ago, Dazzlercee23 said: (A:KOHLSMAN·SETTING·MB:0,·inHg)·100·*·near·2992·== Very nice! I will give this a try.
January 21, 20233 yr 5 minutes ago, ParadiseFlight said: Very nice! I will give this a try. This is the actual script: (A:KOHLSMAN·SETTING·MB:0,·inHg)·100·*·near·2992·==·if{·27·(>MIDI:3:CC:1:9)}·els{·0·(>MIDI:3:CC:1:9)} Your MIDI device ID number may be different, and I use the first rotary for baro (this is the 9 in the script). Regards, Daz Edited January 21, 20233 yr by Dazzlercee23
January 21, 20233 yr Author 1 minute ago, Dazzlercee23 said: (A:KOHLSMAN·SETTING·MB:0,·inHg)·100·*·near·2992·==·if{·27·(>MIDI:3:CC:1:9)}·els{·0·(>MIDI:3:CC:1:9)} Thanks yes I have a few other lines already setting the LEDs of some encoders, but thanks for following-up. I see that this is an Avar, listed in the MSFS SDK. I looked there and found (A:KOHLSMAN SETTING STD:1, Bool) but that always reports 0, so I will stick with your code. Thanks!
January 21, 20233 yr Commercial Member 9 minutes ago, ParadiseFlight said: I see that this is an Avar, listed in the MSFS SDK. I looked there and found (A:KOHLSMAN SETTING STD:1, Bool) but that always reports 0, so I will stick with your code. Thanks! This is an indexed variable. The :0, :1, :2 etc. is the index of the altimeter that you want to know this value of. :0 should be the default, and theoretically the same as not using any index LORBY-SI
January 21, 20233 yr Author 16 minutes ago, Lorby_SI said: This is an indexed variable. The :0, :1, :2 etc. is the index of the altimeter that you want to know this value of. :0 should be the default, and theoretically the same as not using any index Thanks. Yea I tried 0, 1, and 2 for index and none of them return anything but 0 for KOHLSMAN SETTING STD. Only (A:KOHLSMAN SETTING MB:0, inHg) is being updated.
Archived
This topic is now archived and is closed to further replies.