PMDG 737 HiddenLvars?

[Scotfleiger]

Hi John

I have been able to get a LINDA module working with the PMDG 737 for MSFS and FSUIPC 7.3.3 / WASM 0.5.8. This work has been based on earlier PMDG releases.

Some 1700 Lvars are accessible but there are a number of key ones which are not listed (via WASM List Lvars) but are accessible. These include a number prefixed with ngx_, namely ngx_SPDwindow, ngx_HDGwindow, ngx_ALTwindow and ngx_VSwindow for the MCP display.

Is there a possible reason for this? Are some Lvars 'hidden'.

[John Dowson]

1 hour ago, Scotfleiger said:

but there are a number of key ones which are not listed (via WASM List Lvars) but are accessible.

What do you mean by 'accessible'?  If they are not listed, how can you know they exist and their value?

1 hour ago, Scotfleiger said:

Is there a possible reason for this? Are some Lvars 'hidden'.

Not that I know of... The FSUIPC WASM scans for lvars by asking for the lvar name in a loop on the lvar id (using the gauge API function get_name_of_named_variable) and stops when either a null name is returned or the maximum number of lvars that FSUIPC can handle (currently 2044) are found. I guess if an lvar was registered with a null name (if possible...I would expect/hope not!) then this would stop the scanning and any further lvars would not be found.

Another possibility is that they are created some time after aircraft load, but a new scan is performed when listing lvars (from the WASM menu) and so they should still be seen if created later when you list them.

How do you know these lvars exist, and how are they accessible? Do you know their ids?

[Scotfleiger]

Hi John

By accessible I mean I can access these Lvars reading their values and use them in my code. I know the names of these Lvars from previous use in P3D versions of the PMDG aircraft. It is just that they don’t appear in the Lvar list.

I am waiting after starting MSFS and loading the PMDG737 ready for flight before starting FSUIPC7/WASM and LINDA to ensure that the Lvars are exposed.

[John Dowson]

57 minutes ago, Scotfleiger said:

By accessible I mean I can access these Lvars reading their values and use them in my code.

How are you using them? Can you provide an example?
If they are not listed by FSUIPC, I cannot see how they can be used via lua.

59 minutes ago, Scotfleiger said:

I am waiting after starting MSFS and loading the PMDG737 ready for flight before starting FSUIPC7/WASM and LINDA to ensure that the Lvars are exposed.

It doesn't matter when you start FSUIPC7/LINDA, and the WASM is always started by MSFS, regardless of whether FSUIPC7 is running - it is in your Community folder. And the lvar list is provided by the WASM, and will be generated (i.e. the scan for lvars performed) LvarScanDelay (WASM ini parameter, default value of 5) seconds after leaving the MSFS main menu (when the PLANE IN PARKING STATE simvar changes to false), regardless of whether FSUIPC7 is running or not.
Try increasing the LvarScanDelay parameter, or perform a WASM Reload() at some point to see if they are picked-up.

 

[Scotfleiger]

Hi John

Issue solved. The LvarScanDelay setting had disappeared in a recent update/reconfiguration. I can now see around 100 more Lvars for the PMDG737 listed.

[John Dowson]

10 minutes ago, Scotfleiger said:

The LvarScanDelay setting had disappeared in a recent update/reconfiguration.

The FSUIPC_WASM.ini file under your Community folder will get overwritten when you re-install FSUIPC7. For this reason, it is recommended to copy the FSUIPC_WASM.ini file to the WASM persistent storage area and make any modifications there. This ini takes precedence over the one in the Community folder. From the Advance user guide:

Quote

WASM module ini file and parameters
The WASM module takes its default settings from ini files. These are named FSUIPC_WASM.ini and can be located:
  1. In the WASM folder, under your Community/fsuipc-lvar-module folder
  2. In the WASM persistent storage area, which is:
      For Steam installs, in the following folder under your user account:
          AppData\Roaming\Microsoft Flight Simulator\Packages\fsuipc-lvar-module\work
      For MS Store installs, in the following folder under your user account:
          AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\fsuipc-lvarmodule\work
      The FSUIPC WASM log file (FSUIPC_WASM.log) can also be found in this location.

Parameters found in location 2 (WASM persistent storage) will take president and overwrite any parameters found in
the first location. A default ini file is installed with the WASM and can be found in location 1. It is recommended to
leave this file as is, and copy to your persistent storage area and modify as and when needed from there.
 

Glad you solved the problem though!

John

[Scotfleiger]

Hi John

As stated there is a limit of 2044 Lvars at present. I have been helping LINDA users with multiple add-ons who have reached this limit and it is causing faults. I have just installed the new Fenix A320 and also hit 2044. I have 2 other aircraft installed - FBW A32NX and PMDG737 for MSFS. I would support your suggestion that the upper Lvar limit may need to be increased.

Is there a way of emptying the Lvar list between aircraft loads? I have tied the FSUIPC-WASM.INI RemoveLvarsWhenParked=Yes switch but can not see any effect.

[John Dowson]

10 hours ago, Scotfleiger said:

Is there a way of emptying the Lvar list between aircraft loads? I have tied the FSUIPC-WASM.INI RemoveLvarsWhenParked=Yes switch but can not see any effect.

No - I added that ini parameter which, when activated, will try to do thus by calling the unregister_all_named_vars function, but this doesn't seem to make a difference.
It should really be up to MSFS/Asobo (or maybe the aircraft developers) to do this - I don't think there is anything else I can do.

10 hours ago, Scotfleiger said:

As stated there is a limit of 2044 Lvars at present. I have been helping LINDA users with multiple add-ons who have reached this limit and it is causing faults. I have just installed the new Fenix A320 and also hit 2044. I have 2 other aircraft installed - FBW A32NX and PMDG737 for MSFS. I would support your suggestion that the upper Lvar limit may need to be increased.

I will look into increasing the maximum no of lvars available for the next release. However, there has to be some limit. It is recommended to clear your Community folder of (especially) aircraft that you are not using before starting MSFS. Many people use the MSFS addons linker for this. This also improves load times.

[Scotfleiger]

1 hour ago, John Dowson said:

I will look into increasing the maximum no of lvars available for the next release. However, there has to be some limit. It is recommended to clear your Community folder of (especially) aircraft that you are not using before starting MSFS. Many people use the MSFS addons linker for this. This also improves load times.

Thank you for the feedback. I have moved all not-in-use Add-ons out of my Community folder. FYI Fenix A320 alone exceeds 2044 Lvars.

[John Dowson]

Hi Andrew / @Scotfleiger

On 5/20/2022 at 10:06 AM, John Dowson said:

I will look into increasing the maximum no of lvars available for the next release.

I have now implemented this and allow for up to 3066 lvars if you would like to try:
    FSUIPC7 Installer (including updated WASM): http://www.fsuipc.com/download/Install_FSUIPC735d.zip
    WASM/WAPI package: http://www.fsuipc.com/download/FSUIPC-WASMv0.5.9.zip

I am planning on releasing this version at the weekend or early next week.

NB: those links will most probably not work correctly when you click them - copy and paste then into a new browser tab  to download

[Scotfleiger]

2 hours ago, John Dowson said:

I have now implemented this and allow for up to 3066 lvars if you would like to try:

Hi John

Thank you. I have successfully downloaded both files (clicking links produced a Firefox block which I could bypass). After installing FSUIPC 7.3.5d, all the options on the Add-ons/WASM menu were grayed out except disable. The FSUIPC7.log reports WASM 0.5.9 is starting. No Lvars can be listed or accessed.

FSUIPC7.log

[John Dowson]

Did FSUIPC7 crash? I ask as the log is not complete...i
If not, then you didn't wait long enough (what is your LvarScanDelay set to?) - the log ends after 42 seconds and the lvar/hvar data has still not been received in FSUIPC7 from the WASM.

Maybe try initially without LINDA...

[Scotfleiger]

No. FSUIPC7 was still running. I just copied the log while it was still running.

5 minutes ago, John Dowson said:

what is your LvarScanDelay set to?

Delay set to 60 secs. I waited several minutes to check for Lvars.

6 minutes ago, John Dowson said:

Maybe try initially without LINDA...

 LINDA was started by [programs]. I will edit .ini and see how that works. It will be later this evening before I can do this.

[John Dowson]

Just now, Scotfleiger said:

No. FSUIPC7 was still running. I just copied the log while it was still running.

But the last entry in the log you posted is at 42344 - 42 seconds after FSUIPC7 started...

[Scotfleiger]

Roger. I promise to be more patient. I will try again later.

[Scotfleiger]

Hi John

Edited fsuipc7.ini to stop LINDA GUI starting and renamed ipcready.lua to stop LINDA LUA as well. Started 7.3.5d and waited 2 mins. FSUIPC7 menu still has all items grayed out except Disable. If I disable and enable WASM I get the same result. Carried out un/reinstall with no change.

FSUIPC7.log

PS Reinstalled stable 7.3.4 and all functionality restored.

[John Dowson]

12 hours ago, Scotfleiger said:

Started 7.3.5d and waited 2 mins. FSUIPC7 menu still has all items grayed out except Disable. If I disable and enable WASM I get the same result. Carried out un/reinstall with no change.

Strange - I have no issues here...You did have an aircraft loaded and ready-to-fly (i.e. not in the MSFS menu) I presume...
It seems that FSUIPC7 isn't receiving the lvar/hvar config data (which is why the menu items are disabled). You could try disconnecting and reconnecting yo see if that triggers the config data (do not enable/disable!).

Could you activate Debug level logging in the WAPI and WASM and show me your FSUIPC7.log file again, and also show me your FSUIPC_WASM.log.
Maybe also try with a different aircraft - although this shouldn't make any difference.

I have done several tests here with various aircraft, starting FSUIPC7 with MSFS and also starting it after an aircraft is loaded and it is working every time....

John

[Scotfleiger]

MSFS and aircraft (Fenix A320) fully loaded and ready to fly. Waited a full minute before starting 7.3.5d. Even did a full restart with same result.

One thing to note. I only installed FSUIPC7 and not the attached WASM 0.5.9. The log showed 0.5.9 loaded and running.

9 minutes ago, John Dowson said:

Could you activate Debug level logging in the WAPI and WASM and show me your FSUIPC7.log file again, and also show me your FSUIPC_WASM.log.
Maybe also try with a different aircraft - although this shouldn't make any difference.

Will do this.

[John Dowson]

2 minutes ago, Scotfleiger said:

One thing to note. I only installed FSUIPC7 and not the attached WASM 0.5.9. The log showed 0.5.9 loaded and running.

Then you must have installed the WASM 0.5.9 as well - this is installed with FSUIPC7, unless you manually uncheck this component during installation, in which case the log would report a WASM mismatch...

[Scotfleiger]

After re-installing 7.3.5d as requested, the menu is now active and Lvars accessible. Logs attached. I am not sure what I did differently but thank you for your time.

A total of 2211 Lvars loaded for Fenix A320. This suggests new limit is satisfactory. Your previous suggestion of removing not-in-use aircraft from the Community folder causes unwanted issues. Errors occurred when copying back aircraft due to protected directory issues. I would not recommend this procedure. I have found that changing the selected aircraft, exiting MSFS to the desktop and restarting clears unwanted Lvars so that WASM only loads those for the wanted aircraft.

 

 

FSUIPC7.log FSUIPC_WASM.log

[John Dowson]

1 minute ago, Scotfleiger said:

Your previous suggestion of removing not-in-use aircraft from the Community folder causes unwanted issues. Errors occurred when copying back aircraft due to protected directory issues. I would not recommend this procedure.

Strange - this works fine here and for many people, without issues. You have to do this BEFORE you start MSFS (of course...). Have you tried the MSFS Add-on linker - many people use this to manage the contents of their Community folder - seems to work well - I also use it occasionally but more often I do this manually.

4 minutes ago, Scotfleiger said:

I have found that changing the selected aircraft, exiting MSFS to the desktop and restarting clears unwanted Lvars so that WASM only loads those for the wanted aircraft.

I find that it loads lvars for some aircraft just with having the aircraft in my Community folder (e.g. the FBW A320). I can get > 3000 lvars when I have several add-ons in my Community folder...

But whatever works for you...

6 minutes ago, Scotfleiger said:

I am not sure what I did differently

Nor am  I, very strange... 

[Scotfleiger]

Just now, John Dowson said:

Have you tried the MSFS Add-on linker

I have not been successful with this.