Jump to content
The simFlight Network Forums

FSUIPC WASM not always loading


FlyingDutchman77

Recommended Posts

Hi there, I run into the occasional situation that the FSUIPC wasm module seems not to have loaded when starting the sim. A simple restart of the sim fixes this. So no major issue, but since you only find out when the flight is loaded, it takes another 5-7 minutes to reload which is a bit a shame.

Any hint on where to look to find out why the wasm module sometimes doesn't load?

Link to comment
Share on other sites

On 6/3/2022 at 1:55 PM, FlyingDutchman77 said:

Any hint on where to look to find out why the wasm module sometimes doesn't load?

First, the WASM will always load as that is started with MSFS. What is probably happening is that FSUIPC7 is connecting to the WASM but it is not receiving the config data for some reason. However, I will need to see your log files to diagnose. Could you please activate Debug level logging in the WAPI - to do this, add the line:
    LogLevel=Debug
to the [WAPI] section of your FSUIPC7.ini file. Then, the nect time this happens, please show me your FSUIPC7.log file.

Also, rather than restarting the sim, you could try either
   1, reloading the WASM data, using the Add-ons->WASM->Reload menu option, if available
 or
  2. Disconnecting and reconnecting  FSUIPC7 from the sim, using the MSFS menu options

Either (or both) of those options should work, and be a lot quicker than reloading the sim.

I also experienced this occasionally with earlier versions of FSUIPC but thought I had fixed this occasional issue, so make sure you are also using the latest version, v7.3.6

John

Link to comment
Share on other sites

  • 2 weeks later...
11 minutes ago, FlyingDutchman77 said:

Experiencing it again now. Could you let me know in a bit more detail where I can find both option 1 and 2 in the menu's? I am not using FSUIPC itself, but the WAPI.

Well, they are menu options in FSUIPC7, so you can't use them.
If using the WAPI, set debug (or even trace) level logging and look at the log file - that should tell you what is happening.
There is a reload function in the WAPI:
        void reload(); // This sends a request to the WASM ro re-scan for lvars and hvars, and drop/recreate the CDAs
And to disconnect/reconnect, use the end() and start() functions:
        void end(); // Terminates the connection to the WASM
        bool start(); // Startrs the connection to the WASM. 
 

But it is the log file generated by the WAPI which will tell you what is happening. Use Debug level logging - that should be enough.

If you require more help, post more details...it is still unclear to me what you are doing...by saying 'using the WAPI', what do you mean? Are you developing with this API, or using a client from another developer that is using the WAPI? If the latter, talk to the client developer. If the former, you should be able to log and debug to see what is happening - you can always post the WAPI log file here for me to look at. Also, check the FSUIPC_WASM.log file (and you can also set Debug level logging in the WASM).

John

Link to comment
Share on other sites

  • 2 weeks later...

I have my own program in C#, that uses the WAPI and FSUIPC WASM module to control switches etc. 90% of the time it works fine, but in 10% of the cases, the FSUIPC events do not trigger in the sim. If I then reload the sim, it works fine again.

 

It is not the wasm not loading, as the log says it connects find to the sim and it also retrieves data. Do you see anything abnormal in the log lines below? There are 3 EVENT_LVARS lines which I cannot make sense of. See the bold lines.

 

3-7-2022 14:47:45 -   [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 0.5.10 (WASM version 0.5.9)
3-7-2022 14:47:45 -   [INFO]: Connected to MSFS
3-7-2022 14:47:46 -  [DEBUG]: Config Data 0: name=FSUIPC_VNAME7, size=8176, type=0
3-7-2022 14:47:46 -  [DEBUG]: Config Data 1: name=FSUIPC_VNAME8, size=8176, type=0
3-7-2022 14:47:46 -  [DEBUG]: Config Data 2: name=FSUIPC_VNAME9, size=3976, type=0
3-7-2022 14:47:46 -  [DEBUG]: Config Data 3: name=FSUIPC_lvalues0, size=8192, type=2
3-7-2022 14:47:46 -  [DEBUG]: Config Data 4: name=FSUIPC_lvalues1, size=8192, type=2
3-7-2022 14:47:46 -  [DEBUG]: Config Data 5: name=FSUIPC_lvalues2, size=8192, type=2
3-7-2022 14:47:47 -  [DEBUG]: CDA name FSUIPC_VNAME7 mapped to ID 4 [requestId=16]
3-7-2022 14:47:47 -  [DEBUG]: Client data area created with id=4 (size=8176) [requestID=17]
3-7-2022 14:47:47 -  [DEBUG]: Client data definition added with id=4 (size=8176)
3-7-2022 14:47:47 -  [DEBUG]: CDA 'FSUIPC_VNAME7 with id=4 and definitionId=4 requested
3-7-2022 14:47:47 -  [DEBUG]: CDA name FSUIPC_VNAME8 mapped to ID 5 [requestId=20]
3-7-2022 14:47:47 -  [DEBUG]: Client data area created with id=5 (size=8176) [requestID=21]
3-7-2022 14:47:47 -  [DEBUG]: Client data definition added with id=5 (size=8176)
3-7-2022 14:47:47 -  [DEBUG]: CDA 'FSUIPC_VNAME8 with id=5 and definitionId=5 requested
3-7-2022 14:47:47 -  [DEBUG]: CDA name FSUIPC_VNAME9 mapped to ID 6 [requestId=24]
3-7-2022 14:47:47 -  [DEBUG]: Client data area created with id=6 (size=3976) [requestID=25]
3-7-2022 14:47:47 -  [DEBUG]: Client data definition added with id=6 (size=3976)
3-7-2022 14:47:47 -  [DEBUG]: CDA 'FSUIPC_VNAME9 with id=6 and definitionId=6 requested
3-7-2022 14:47:47 -  [DEBUG]: CDA name FSUIPC_lvalues0 mapped to ID 7 [requestId=28]
3-7-2022 14:47:47 -  [DEBUG]: Client data area created with id=7 (size=8192) [requestID=29]
3-7-2022 14:47:47 -  [DEBUG]: Client data definition added with id=7 (size=8192)
3-7-2022 14:47:47 -  [DEBUG]: CDA 'FSUIPC_lvalues0 with id=7 and definitionId=7 requested
3-7-2022 14:47:47 -  [DEBUG]: CDA name FSUIPC_lvalues1 mapped to ID 8 [requestId=32]
3-7-2022 14:47:47 -  [DEBUG]: Client data area created with id=8 (size=8192) [requestID=33]
3-7-2022 14:47:47 -  [DEBUG]: Client data definition added with id=8 (size=8192)
3-7-2022 14:47:47 -  [DEBUG]: CDA 'FSUIPC_lvalues1 with id=8 and definitionId=8 requested
3-7-2022 14:47:47 -  [DEBUG]: CDA name FSUIPC_lvalues2 mapped to ID 9 [requestId=36]
3-7-2022 14:47:47 -  [DEBUG]: Client data area created with id=9 (size=8192) [requestID=37]
3-7-2022 14:47:47 -  [DEBUG]: Client data definition added with id=9 (size=8192)
3-7-2022 14:47:47 -  [DEBUG]: CDA 'FSUIPC_lvalues2 with id=9 and definitionId=9 requested
3-7-2022 14:47:47 -  [DEBUG]: EVENT_LVARS_RECEIVED: dwObjectID=0, dwDefineID=4, dwDefineCount=1, dwentrynumber=1, dwoutof=1
3-7-2022 14:47:47 -  [DEBUG]: EVENT_LVARS_RECEIVED: dwObjectID=0, dwDefineID=5, dwDefineCount=1, dwentrynumber=1, dwoutof=1
3-7-2022 14:47:47 -  [DEBUG]: EVENT_LVARS_RECEIVED: dwObjectID=0, dwDefineID=6, dwDefineCount=1, dwentrynumber=1, dwoutof=1

3-7-2022 14:47:47 -  [DEBUG]: Flagging lvar for callback: id=26
3-7-2022 14:47:47 -  [DEBUG]: Flagging lvar for callback: id=30
3-7-2022 14:47:47 -  [DEBUG]: Flagging lvar for callback: id=32
3-7-2022 14:47:47 -  [DEBUG]: Flagging lvar for callback: id=33
3-7-2022 14:47:47 -  [DEBUG]: Flagging lvar for callback: id=34
3-7-2022 14:47:47 -  [DEBUG]: Flagging lvar for callback: id=35
3-7-2022 14:47:47 -  [DEBUG]: Flagging lvar for callback: id=36
3-7-2022 14:47:47 -  [DEBUG]: Flagging lvar for callback: id=37
3-7-2022 14:47:47 -  [DEBUG]: Flagging lvar for callback: id=38
3-7-2022 14:47:47 -  [DEBUG]: Flagging lvar for callback: id=39
3-7-2022 14:47:47 -  [DEBUG]: Flagging lvar for callback: id=40
3-7-2022 14:47:47 -  [DEBUG]: Flagging lvar for callback: id=41

 

 

The wasm had loaded fine according to the log:

Sun Jul  3 13:00:39 2022  [ALWAYS]: <=============================== START OF PROGRAM ===============================>
Sun Jul  3 13:00:39 2022  [ALWAYS]: **** WASM version is 0.5.9 ****
Sun Jul  3 13:00:39 2022    [INFO]: Ini file loaded from add-on package
Sun Jul  3 13:00:39 2022    [INFO]: No ini file found in persistant storage at '\work\FSUIPC_WASM.ini'
Sun Jul  3 13:00:39 2022  [ALWAYS]: useAirLocForHvars is: 0
Sun Jul  3 13:00:39 2022  [ALWAYS]: Maximum number of lvars/hvars per Client Data Area is 146
Sun Jul  3 13:00:39 2022    [INFO]: Config Client Data Area mapped to ID 1
Sun Jul  3 13:00:39 2022    [INFO]: Data Definition 1 added for Config Client Data Area definition
Sun Jul  3 13:00:39 2022    [INFO]: Config Client Data Area created.
Sun Jul  3 13:00:39 2022    [INFO]: Lvar Value Client Data Area mapped to ID 2
Sun Jul  3 13:00:39 2022    [INFO]: Data Definition 2 added for Lvar Set Request Client Data Area definition
Sun Jul  3 13:00:39 2022    [INFO]: Lvar Value Client Data Area created.
Sun Jul  3 13:00:39 2022    [INFO]: Calculator Code Client Data Area mapped to ID 3
Sun Jul  3 13:00:39 2022    [INFO]: Data Definition 3 added for Lvar Set Request Client Data Area definition
Sun Jul  3 13:00:39 2022    [INFO]: Exec Calculator Code Client Data Area created.
Sun Jul  3 13:00:39 2022    [INFO]: Lvar values CDA with id=4 mapped to name FSUIPC_lvalues0 [requestId=19]
Sun Jul  3 13:00:39 2022    [INFO]: Lvar values Client data definition 4 added [requestID=20]
Sun Jul  3 13:00:39 2022    [INFO]: Lvar values CDA created with id=4, (size=8192 for 1024 values), mapped to name FSUIPC_lvalues0 [requestId=21]
Sun Jul  3 13:00:39 2022    [INFO]: Lvar values CDA with id=5 mapped to name FSUIPC_lvalues1 [requestId=22]
Sun Jul  3 13:00:39 2022    [INFO]: Lvar values Client data definition 5 added [requestID=23]
Sun Jul  3 13:00:39 2022    [INFO]: Lvar values CDA created with id=5, (size=8192 for 1024 values), mapped to name FSUIPC_lvalues1 [requestId=24]
Sun Jul  3 13:00:39 2022    [INFO]: Lvar values CDA with id=6 mapped to name FSUIPC_lvalues2 [requestId=25]
Sun Jul  3 13:00:39 2022    [INFO]: Lvar values Client data definition 6 added [requestID=26]
Sun Jul  3 13:00:39 2022    [INFO]: Lvar values CDA created with id=6, (size=8192 for 1024 values), mapped to name FSUIPC_lvalues2 [requestId=27]
Sun Jul  3 13:01:46 2022    [INFO]: Aircraft loaded: 'C:\MSFS\Community\flysimware-cessna-414a\SimObjects\Airplanes\flysimware_Cessna_414A\aircraft.CFG'
Sun Jul  3 13:01:46 2022    [INFO]: Flight loaded: 'flights\other\MainMenu.FLT'

Link to comment
Share on other sites

22 hours ago, FlyingDutchman77 said:

Do you see anything abnormal in the log lines below? There are 3 EVENT_LVARS lines which I cannot make sense of. See the bold lines.

That log is normal - those bold lines indicate the lvar names have been received in the client, and they should be available to use once received.

Note that when using the WAPI, you should register for a callback using the function registerUpdateCallback(void (*callbackFunction)(void)) and then only start using the WAPI to access lvars/hvars etc once the callback has been called.

22 hours ago, FlyingDutchman77 said:

I have my own program in C#, that uses the WAPI and FSUIPC WASM module to control switches etc. 90% of the time it works fine, but in 10% of the cases, the FSUIPC events do not trigger in the sim. If I then reload the sim, it works fine again.

This sounds like the lvars are not available when the lvar scan is performed. The scan is performed after LvarScanDelay seconds after the aircraft has loaded. This is a WASM ini file parameter that defaults to 5 (seconds). You can increase this by setting this parameter in your FSUIPC_WASM.ini file - see the Advanced User guide for details.

If writing your own WAPI client, you could also check for the existence of all the lvars you are using before you start, and if the lvars are not available you can wait and then reload the WASM, which will re-scan for lvars. The best way of doing this would be first to determine the last lvar that is loaded that you are using - this will be the one with the highest id. You can then check that this lvar has been loaded, by retrieving the id of this lvar using getLvarIdFromName(). If the id is -1, the lvar isn't available, and you should wait/sleep for a short period (e.g. 5s) and then call reload() and check again. Repeat until the lvar id retrieved is not -1 and then continue, or until a certain number of retries have passed without the lvar being found and then exit with an appropriate message.

John

  • Thanks 1
Link to comment
Share on other sites

  • 1 month later...

I have a similar question.

I made a lua plugin that I also shared with a limited number of users from the community. It needs the WAPI to run, because there is interaction with LVARs of the add-on aircraft it was made for. On my computer, everything is running fine. In the log file, I can see the WAPI loading and connecting on startup.

There are users, where the loading of WAPI is apparently not happening (not in the log), altough they tell me it is installed and presumably running, if they go to the FSUIPC "Add-ons" tab -> "WASM".

What can prevent the WAPI from loading? If it is listed as running in the "Add-ons" tab -> "WASM", why it doesn't show in the log? Is there more to it?

Thanks for helping.

Link to comment
Share on other sites

1 hour ago, NovemberUniform said:

There are users, where the loading of WAPI is apparently not happening (not in the log), altough they tell me it is installed and presumably running, if they go to the FSUIPC "Add-ons" tab -> "WASM".

If the Add-ons->WASM menu contains a Disable menu item, the WAPI is enabled, and if it contains an Enable menu item, it isn't. You only need to Enable once. If the other items in that menu are disabled, it means that the config data (lvar and hvar lists) has not yet been received from the WASM. Once the config data gas been received, the remaining WASM menu items are enabled - and also lua autos will then be started 9i.e. lua autos are started only once the WASM/WAPI config data has been received if the WASM/WAPI is enabled.

1 hour ago, NovemberUniform said:

What can prevent the WAPI from loading? If it is listed as running in the "Add-ons" tab -> "WASM", why it doesn't show in the log? Is there more to it?

Nothing should prevent the WAPI from loading, although it can take a while for the config data to be received, depending on the value of the WASM ini parameter LvarScanDelay. And sone WAPI messages should always be seen in the log, when the WASM is enabled:

Quote

...
    16016 Starting WAPI...
    16016 [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 0.5.10 (WASM version 0.5.9)
    16016 [INFO]: Connected to MSFS
...
    16141 Lvars/Hvars received - checking aircraft autos....
 

Everything should be ready once that message in bold has been logged. This will only happen once an aircraft is loaded and ready-to-fly, and not if/when in the MSFS menu system. Any issues, then you should activate Debug logging, initially in the WAPI by adding the following line to the [WAPI] section of your FSUIPC7.ini file:
    LogLevel=Debug
With this added, additional messages such as the following will be logged once the WAPI config data gas been received:

Quote

    16063 51916  [DEBUG]: Config Data 0: name=FSUIPC_VNAME10, size=8176, type=0
    16063 51916  [DEBUG]: Config Data 1: name=FSUIPC_VNAME11, size=8176, type=0
    16063 51916  [DEBUG]: Config Data 2: name=FSUIPC_VNAME12, size=8176, type=0
    16063 51916  [DEBUG]: Config Data 3: name=FSUIPC_VNAME13, size=8176, type=0
    16063 51916  [DEBUG]: Config Data 4: name=FSUIPC_VNAME14, size=8176, type=0
    16063 51916  [DEBUG]: Config Data 5: name=FSUIPC_VNAME15, size=8176, type=0
    16063 51916  [DEBUG]: Config Data 6: name=FSUIPC_VNAME16, size=8176, type=0
    16063 51916  [DEBUG]: Config Data 7: name=FSUIPC_VNAME17, size=8176, type=0
    16063 51916  [DEBUG]: Config Data 8: name=FSUIPC_VNAME18, size=8176, type=0
    16063 51916  [DEBUG]: Config Data 9: name=FSUIPC_VNAME19, size=8176, type=0
    16063 51916  [DEBUG]: Config Data 10: name=FSUIPC_VNAME8, size=8176, type=0
    16063 51916  [DEBUG]: Config Data 11: name=FSUIPC_VNAME9, size=8176, type=0
    16063 51916  [DEBUG]: Config Data 12: name=FSUIPC_VNAME21, size=8176, type=0
    16063 51916  [DEBUG]: Config Data 13: name=FSUIPC_VNAME22, size=8176, type=0
    16063 51916  [DEBUG]: Config Data 14: name=FSUIPC_VNAME23, size=1680, type=0
    16063 51916  [DEBUG]: Config Data 15: name=FSUIPC_lvalues0, size=8192, type=2
    16063 51916  [DEBUG]: Config Data 16: name=FSUIPC_lvalues1, size=8192, type=2
    16063 51916  [DEBUG]: Config Data 17: name=FSUIPC_lvalues2, size=8192, type=2
    16063 51916  [DEBUG]: CDA name FSUIPC_VNAME10 mapped to ID 4 [requestId=16]
    16063 51916  [DEBUG]: Client data area created with id=4 (size=8176) [requestID=17]
    16063 51916  [DEBUG]: Client data definition added with id=4 (size=8176)
    16063 51916  [DEBUG]: CDA 'FSUIPC_VNAME10 with id=4 and definitionId=4 requested
    16063 51916  [DEBUG]: CDA name FSUIPC_VNAME11 mapped to ID 5 [requestId=20]
    16063 51916  [DEBUG]: Client data area created with id=5 (size=8176) [requestID=21]
    16063 51916  [DEBUG]: Client data definition added with id=5 (size=8176)
    16063 51916  [DEBUG]: CDA 'FSUIPC_VNAME11 with id=5 and definitionId=5 requested
    16063 51916  [DEBUG]: CDA name FSUIPC_VNAME12 mapped to ID 6 [requestId=24]
    16063 51916  [DEBUG]: Client data area created with id=6 (size=8176) [requestID=25]
    16063 51916  [DEBUG]: Client data definition added with id=6 (size=8176)
    16079 51916  [DEBUG]: CDA 'FSUIPC_VNAME12 with id=6 and definitionId=6 requested
    16079 51916  [DEBUG]: CDA name FSUIPC_VNAME13 mapped to ID 7 [requestId=28]
    16079 51916  [DEBUG]: Client data area created with id=7 (size=8176) [requestID=29]
    16079 51916  [DEBUG]: Client data definition added with id=7 (size=8176)
    16079 51916  [DEBUG]: CDA 'FSUIPC_VNAME13 with id=7 and definitionId=7 requested
    16079 51916  [DEBUG]: CDA name FSUIPC_VNAME14 mapped to ID 8 [requestId=32]
    16079 51916  [DEBUG]: Client data area created with id=8 (size=8176) [requestID=33]
    16079 51916  [DEBUG]: Client data definition added with id=8 (size=8176)
    16079 51916  [DEBUG]: CDA 'FSUIPC_VNAME14 with id=8 and definitionId=8 requested
    16079 51916  [DEBUG]: CDA name FSUIPC_VNAME15 mapped to ID 9 [requestId=36]
    16079 51916  [DEBUG]: Client data area created with id=9 (size=8176) [requestID=37]
    16079 51916  [DEBUG]: Client data definition added with id=9 (size=8176)
    16094 51916  [DEBUG]: CDA 'FSUIPC_VNAME15 with id=9 and definitionId=9 requested
    16094 51916  [DEBUG]: CDA name FSUIPC_VNAME16 mapped to ID 10 [requestId=40]
    16094 51916  [DEBUG]: Client data area created with id=10 (size=8176) [requestID=41]
    16094 51916  [DEBUG]: Client data definition added with id=10 (size=8176)
    16094 51916  [DEBUG]: CDA 'FSUIPC_VNAME16 with id=10 and definitionId=10 requested
    16094 51916  [DEBUG]: CDA name FSUIPC_VNAME17 mapped to ID 11 [requestId=44]
    16094 51916  [DEBUG]: Client data area created with id=11 (size=8176) [requestID=45]
    16094 51916  [DEBUG]: Client data definition added with id=11 (size=8176)
    16094 51916  [DEBUG]: CDA 'FSUIPC_VNAME17 with id=11 and definitionId=11 requested
    16094 51916  [DEBUG]: CDA name FSUIPC_VNAME18 mapped to ID 12 [requestId=48]
    16094 51916  [DEBUG]: Client data area created with id=12 (size=8176) [requestID=49]
    16094 51916  [DEBUG]: Client data definition added with id=12 (size=8176)
    16094 51916  [DEBUG]: CDA 'FSUIPC_VNAME18 with id=12 and definitionId=12 requested
    16094 51916  [DEBUG]: CDA name FSUIPC_VNAME19 mapped to ID 13 [requestId=52]
    16094 51916  [DEBUG]: Client data area created with id=13 (size=8176) [requestID=53]
    16094 51916  [DEBUG]: Client data definition added with id=13 (size=8176)
    16094 51916  [DEBUG]: CDA 'FSUIPC_VNAME19 with id=13 and definitionId=13 requested
    16094 51916  [DEBUG]: CDA name FSUIPC_VNAME8 mapped to ID 14 [requestId=56]
    16094 51916  [DEBUG]: Client data area created with id=14 (size=8176) [requestID=57]
    16094 51916  [DEBUG]: Client data definition added with id=14 (size=8176)
    16094 51916  [DEBUG]: CDA 'FSUIPC_VNAME8 with id=14 and definitionId=14 requested
    16094 51916  [DEBUG]: CDA name FSUIPC_VNAME9 mapped to ID 15 [requestId=60]
    16094 51916  [DEBUG]: Client data area created with id=15 (size=8176) [requestID=61]
    16110 51916  [DEBUG]: Client data definition added with id=15 (size=8176)
    16110 51916  [DEBUG]: CDA 'FSUIPC_VNAME9 with id=15 and definitionId=15 requested
    16110 51916  [DEBUG]: CDA name FSUIPC_VNAME21 mapped to ID 16 [requestId=64]
    16110 51916  [DEBUG]: Client data area created with id=16 (size=8176) [requestID=65]
    16110 51916  [DEBUG]: Client data definition added with id=16 (size=8176)
    16110 51916  [DEBUG]: CDA 'FSUIPC_VNAME21 with id=16 and definitionId=16 requested
    16110 51916  [DEBUG]: CDA name FSUIPC_VNAME22 mapped to ID 17 [requestId=68]
    16110 51916  [DEBUG]: Client data area created with id=17 (size=8176) [requestID=69]
    16110 51916  [DEBUG]: Client data definition added with id=17 (size=8176)
    16110 51916  [DEBUG]: CDA 'FSUIPC_VNAME22 with id=17 and definitionId=17 requested
    16110 51916  [DEBUG]: CDA name FSUIPC_VNAME23 mapped to ID 18 [requestId=72]
    16110 51916  [DEBUG]: Client data area created with id=18 (size=1680) [requestID=73]
    16110 51916  [DEBUG]: Client data definition added with id=18 (size=1680)
    16110 51916  [DEBUG]: CDA 'FSUIPC_VNAME23 with id=18 and definitionId=18 requested
    16110 51916  [DEBUG]: CDA name FSUIPC_lvalues0 mapped to ID 19 [requestId=76]
    16110 51916  [DEBUG]: Client data area created with id=19 (size=8192) [requestID=77]
    16110 51916  [DEBUG]: Client data definition added with id=19 (size=8192)
    16110 51916  [DEBUG]: CDA 'FSUIPC_lvalues0 with id=19 and definitionId=19 requested
    16110 51916  [DEBUG]: CDA name FSUIPC_lvalues1 mapped to ID 20 [requestId=80]
    16110 51916  [DEBUG]: Client data area created with id=20 (size=8192) [requestID=81]
    16125 51916  [DEBUG]: Client data definition added with id=20 (size=8192)
    16125 51916  [DEBUG]: CDA 'FSUIPC_lvalues1 with id=20 and definitionId=20 requested
    16125 51916  [DEBUG]: CDA name FSUIPC_lvalues2 mapped to ID 21 [requestId=84]
    16125 51916  [DEBUG]: Client data area created with id=21 (size=8192) [requestID=85]
    16125 51916  [DEBUG]: Client data definition added with id=21 (size=8192)
    16125 51916  [DEBUG]: CDA 'FSUIPC_lvalues2 with id=21 and definitionId=21 requested
    16125 51916  [DEBUG]: EVENT_LVARS_RECEIVED: dwObjectID=0, dwDefineID=4, dwDefineCount=1, dwentrynumber=1, dwoutof=1
    16125 51916  [DEBUG]: EVENT_LVARS_RECEIVED: dwObjectID=0, dwDefineID=5, dwDefineCount=1, dwentrynumber=1, dwoutof=1
    16125 51916  [DEBUG]: EVENT_LVARS_RECEIVED: dwObjectID=0, dwDefineID=6, dwDefineCount=1, dwentrynumber=1, dwoutof=1
    16125 51916  [DEBUG]: EVENT_LVARS_RECEIVED: dwObjectID=0, dwDefineID=7, dwDefineCount=1, dwentrynumber=1, dwoutof=1
    16125 51916  [DEBUG]: EVENT_LVARS_RECEIVED: dwObjectID=0, dwDefineID=8, dwDefineCount=1, dwentrynumber=1, dwoutof=1
    16125 51916  [DEBUG]: EVENT_LVARS_RECEIVED: dwObjectID=0, dwDefineID=9, dwDefineCount=1, dwentrynumber=1, dwoutof=1
    16125 51916  [DEBUG]: EVENT_LVARS_RECEIVED: dwObjectID=0, dwDefineID=10, dwDefineCount=1, dwentrynumber=1, dwoutof=1
    16125 51916  [DEBUG]: EVENT_LVARS_RECEIVED: dwObjectID=0, dwDefineID=11, dwDefineCount=1, dwentrynumber=1, dwoutof=1
    16125 51916  [DEBUG]: EVENT_LVARS_RECEIVED: dwObjectID=0, dwDefineID=12, dwDefineCount=1, dwentrynumber=1, dwoutof=1
    16125 51916  [DEBUG]: EVENT_LVARS_RECEIVED: dwObjectID=0, dwDefineID=13, dwDefineCount=1, dwentrynumber=1, dwoutof=1
    16125 51916  [DEBUG]: EVENT_LVARS_RECEIVED: dwObjectID=0, dwDefineID=14, dwDefineCount=1, dwentrynumber=1, dwoutof=1
    16125 51916  [DEBUG]: EVENT_LVARS_RECEIVED: dwObjectID=0, dwDefineID=15, dwDefineCount=1, dwentrynumber=1, dwoutof=1
    16125 51916  [DEBUG]: EVENT_LVARS_RECEIVED: dwObjectID=0, dwDefineID=16, dwDefineCount=1, dwentrynumber=1, dwoutof=1
    16125 51916  [DEBUG]: EVENT_LVARS_RECEIVED: dwObjectID=0, dwDefineID=17, dwDefineCount=1, dwentrynumber=1, dwoutof=1
    16125 51916  [DEBUG]: EVENT_LVARS_RECEIVED: dwObjectID=0, dwDefineID=18, dwDefineCount=1, dwentrynumber=1, dwoutof=1
    16141 51916 Lvars/Hvars received - checking aircraft autos....
 

Debug level logging can also be set for the WASM (see Advanced User guide for details on how to do this), and you can/should also check the FSUIPC_WASM.log file.
This is how it should look if functioning correctly (and with Debug level logging set) - lines in bold indicate when everything is ready:

Quote

Wed Aug 17 09:02:22 2022  [ALWAYS]: <=============================== START OF PROGRAM ===============================>
Wed Aug 17 09:02:22 2022  [ALWAYS]: **** WASM version is 0.5.9 ****
Wed Aug 17 09:02:22 2022    [INFO]: Ini file loaded from add-on package
Wed Aug 17 09:02:22 2022    [INFO]: Ini file loaded from persistant storage
Wed Aug 17 09:02:22 2022  [ALWAYS]: useAirLocForHvars is: 0
Wed Aug 17 09:02:22 2022   [DEBUG]: SimConnect connection opened ok
Wed Aug 17 09:02:22 2022  [ALWAYS]: Maximum number of lvars/hvars per Client Data Area is 146
Wed Aug 17 09:02:22 2022    [INFO]: Config Client Data Area mapped to ID 1
Wed Aug 17 09:02:22 2022    [INFO]: Data Definition 1 added for Config Client Data Area definition
Wed Aug 17 09:02:22 2022    [INFO]: Config Client Data Area created.
Wed Aug 17 09:02:22 2022    [INFO]: Lvar Value Client Data Area mapped to ID 2
Wed Aug 17 09:02:22 2022    [INFO]: Data Definition 2 added for Lvar Set Request Client Data Area definition
Wed Aug 17 09:02:22 2022    [INFO]: Lvar Value Client Data Area created.
Wed Aug 17 09:02:22 2022    [INFO]: Calculator Code Client Data Area mapped to ID 3
Wed Aug 17 09:02:22 2022    [INFO]: Data Definition 3 added for Lvar Set Request Client Data Area definition
Wed Aug 17 09:02:22 2022    [INFO]: Exec Calculator Code Client Data Area created.
Wed Aug 17 09:02:22 2022    [INFO]: Lvar values CDA with id=4 mapped to name FSUIPC_lvalues0 [requestId=19]
Wed Aug 17 09:02:22 2022    [INFO]: Lvar values Client data definition 4 added [requestID=20]
Wed Aug 17 09:02:22 2022    [INFO]: Lvar values CDA created with id=4, (size=8192 for 1024 values), mapped to name FSUIPC_lvalues0 [requestId=21]
Wed Aug 17 09:02:22 2022    [INFO]: Lvar values CDA with id=5 mapped to name FSUIPC_lvalues1 [requestId=22]
Wed Aug 17 09:02:22 2022    [INFO]: Lvar values Client data definition 5 added [requestID=23]
Wed Aug 17 09:02:22 2022    [INFO]: Lvar values CDA created with id=5, (size=8192 for 1024 values), mapped to name FSUIPC_lvalues1 [requestId=24]
Wed Aug 17 09:02:22 2022    [INFO]: Lvar values CDA with id=6 mapped to name FSUIPC_lvalues2 [requestId=25]
Wed Aug 17 09:02:22 2022    [INFO]: Lvar values Client data definition 6 added [requestID=26]
Wed Aug 17 09:02:22 2022    [INFO]: Lvar values CDA created with id=6, (size=8192 for 1024 values), mapped to name FSUIPC_lvalues2 [requestId=27]
Wed Aug 17 09:03:19 2022    [INFO]: Aircraft loaded: 'D:\MSFS2020\Community\pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700\aircraft.CFG'
Wed Aug 17 09:03:19 2022    [INFO]: Flight loaded: 'flights\other\MainMenu.FLT'
Wed Aug 17 09:03:19 2022   [DEBUG]: In main menu - de-activated and config data area cleared
Wed Aug 17 09:03:20 2022   [DEBUG]: Sim data received: aircraft='PMDG 737-700 PMDG House (N737BW | 2021)' [loadCDAsFlag=0]
Wed Aug 17 09:03:20 2022   [DEBUG]: Sim data received: parkingState=0
Wed Aug 17 09:04:32 2022   [DEBUG]: Sim data received: parkingState=1
Wed Aug 17 09:18:57 2022    [INFO]: Aircraft loaded: 'D:\MSFS2020\Official\Steam\asobo-aircraft-c172sp-as1000\SimObjects\Airplanes\Asobo_C172sp_AS1000\aircraft.CFG'
Wed Aug 17 09:18:58 2022    [INFO]: Aircraft loaded: 'D:\MSFS2020\Official\Steam\asobo-aircraft-c172sp-as1000\SimObjects\Airplanes\Asobo_C172sp_AS1000\aircraft.CFG'
Wed Aug 17 09:18:59 2022   [DEBUG]: Sim data received: aircraft='Cessna Skyhawk G1000 Asobo' [loadCDAsFlag=0]
Wed Aug 17 09:19:03 2022    [INFO]: Aircraft loaded: 'D:\MSFS2020\Official\Steam\asobo-aircraft-c172sp-as1000\SimObjects\Airplanes\Asobo_C172sp_AS1000\aircraft.CFG'
Wed Aug 17 09:19:03 2022    [INFO]: Flight loaded: 'C:\Users\jldow\AppData\Roaming\Microsoft Flight Simulator\MISSIONS\Custom\CustomFlight\CustomFlight.FLT'
Wed Aug 17 09:19:06 2022   [DEBUG]: Sim data received: parkingState=0
Wed Aug 17 09:20:19 2022   [DEBUG]: Scan delay passed - loading hvars/lvars: timePassed=46, lvarScanDelay=45
Wed Aug 17 09:20:19 2022   [DEBUG]: Loading hvars for aircraft 'Cessna Skyhawk G1000 Asobo'
Wed Aug 17 09:20:19 2022   [DEBUG]: Modules folder opened
Wed Aug 17 09:20:19 2022   [DEBUG]: Found 3 *.hvar files under work folder
Wed Aug 17 09:20:19 2022   [DEBUG]: Modules folder opened
Wed Aug 17 09:20:19 2022   [DEBUG]: Found 7 *.hvar files under .modules folder
Wed Aug 17 09:20:19 2022   [DEBUG]: Checking hvar file A320 for aircraft 'Cessna Skyhawk G1000 Asobo'
Wed Aug 17 09:20:19 2022   [DEBUG]: No match on aircraft name to hvar filename
Wed Aug 17 09:20:19 2022   [DEBUG]: Checking hvar file Asobo_C152 for aircraft 'Cessna Skyhawk G1000 Asobo'
Wed Aug 17 09:20:19 2022   [DEBUG]: No match on aircraft name to hvar filename
Wed Aug 17 09:20:19 2022   [DEBUG]: Checking hvar file DA40 TDI for aircraft 'Cessna Skyhawk G1000 Asobo'
Wed Aug 17 09:20:19 2022   [DEBUG]: No match on aircraft name to hvar filename
Wed Aug 17 09:20:19 2022   [DEBUG]: Checking hvar file DA40-NG for aircraft 'Cessna Skyhawk G1000 Asobo'
Wed Aug 17 09:20:19 2022   [DEBUG]: No match on aircraft name to hvar filename
Wed Aug 17 09:20:19 2022   [DEBUG]: Checking hvar file DA62 for aircraft 'Cessna Skyhawk G1000 Asobo'
Wed Aug 17 09:20:19 2022   [DEBUG]: No match on aircraft name to hvar filename
Wed Aug 17 09:20:19 2022   [DEBUG]: Checking hvar file Skyhawk for aircraft 'Cessna Skyhawk G1000 Asobo'
Wed Aug 17 09:20:19 2022   [DEBUG]: Loading aircraft hvar file: .\modules\Skyhawk.hvar
Wed Aug 17 09:20:19 2022   [DEBUG]: Found 47 hvars in file '.\modules\Skyhawk.hvar'
Wed Aug 17 09:20:19 2022   [DEBUG]: CDA name FSUIPC_HSkyhawk0 mapped to ID 7 [requestId=31]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area created with id=7 (size=2632) [requestID=32]
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=7, name=FSUIPC_HSkyhawk0
Wed Aug 17 09:20:19 2022   [DEBUG]: Checking hvar file TBM for aircraft 'Cessna Skyhawk G1000 Asobo'
Wed Aug 17 09:20:19 2022   [DEBUG]: No match on aircraft name to hvar filename
Wed Aug 17 09:20:19 2022   [DEBUG]: 1 HVAR CDAs loaded from 1 files (max client data size=8192)
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data definition added with id=7 (size=2632) [requestID=33]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area set with id=7 and definitionId=7 with size=2632 [requestID=34]
Wed Aug 17 09:20:19 2022   [DEBUG]: Hvars loaded
Wed Aug 17 09:20:19 2022    [INFO]: 47 hvars loaded for aircraft 'Cessna Skyhawk G1000 Asobo'
Wed Aug 17 09:20:19 2022   [DEBUG]: Loading lvars for aircraft 'Cessna Skyhawk G1000 Asobo'
Wed Aug 17 09:20:19 2022   [DEBUG]: CDA name FSUIPC_VNAME8 mapped to ID 8 [requestId=35]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area created with id=8 (size=8176) [requestID=36]
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=8, name=FSUIPC_VNAME8
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=8, name=FSUIPC_VNAME8 (on size only)
Wed Aug 17 09:20:19 2022   [DEBUG]: CDA name FSUIPC_VNAME9 mapped to ID 9 [requestId=37]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area created with id=9 (size=8176) [requestID=38]
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=9, name=FSUIPC_VNAME9
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=9, name=FSUIPC_VNAME9 (on size only)
Wed Aug 17 09:20:19 2022   [DEBUG]: CDA name FSUIPC_VNAME10 mapped to ID 10 [requestId=39]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area created with id=10 (size=8176) [requestID=40]
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=10, name=FSUIPC_VNAME10
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=10, name=FSUIPC_VNAME10 (on size only)
Wed Aug 17 09:20:19 2022   [DEBUG]: CDA name FSUIPC_VNAME11 mapped to ID 11 [requestId=41]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area created with id=11 (size=8176) [requestID=42]
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=11, name=FSUIPC_VNAME11
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=11, name=FSUIPC_VNAME11 (on size only)
Wed Aug 17 09:20:19 2022   [DEBUG]: CDA name FSUIPC_VNAME12 mapped to ID 12 [requestId=43]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area created with id=12 (size=8176) [requestID=44]
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=12, name=FSUIPC_VNAME12
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=12, name=FSUIPC_VNAME12 (on size only)
Wed Aug 17 09:20:19 2022   [DEBUG]: CDA name FSUIPC_VNAME13 mapped to ID 13 [requestId=45]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area created with id=13 (size=8176) [requestID=46]
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=13, name=FSUIPC_VNAME13
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=13, name=FSUIPC_VNAME13 (on size only)
Wed Aug 17 09:20:19 2022   [DEBUG]: CDA name FSUIPC_VNAME14 mapped to ID 14 [requestId=47]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area created with id=14 (size=8176) [requestID=48]
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=14, name=FSUIPC_VNAME14
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=14, name=FSUIPC_VNAME14 (on size only)
Wed Aug 17 09:20:19 2022   [DEBUG]: CDA name FSUIPC_VNAME15 mapped to ID 15 [requestId=49]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area created with id=15 (size=8176) [requestID=50]
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=15, name=FSUIPC_VNAME15
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=15, name=FSUIPC_VNAME15 (on size only)
Wed Aug 17 09:20:19 2022   [DEBUG]: CDA name FSUIPC_VNAME16 mapped to ID 16 [requestId=51]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area created with id=16 (size=8176) [requestID=52]
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=16, name=FSUIPC_VNAME16
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=16, name=FSUIPC_VNAME16 (on size only)
Wed Aug 17 09:20:19 2022   [DEBUG]: CDA name FSUIPC_VNAME17 mapped to ID 17 [requestId=53]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area created with id=17 (size=8176) [requestID=54]
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=17, name=FSUIPC_VNAME17
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=17, name=FSUIPC_VNAME17 (on size only)
Wed Aug 17 09:20:19 2022   [DEBUG]: CDA name FSUIPC_VNAME18 mapped to ID 18 [requestId=55]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area created with id=18 (size=8176) [requestID=56]
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=18, name=FSUIPC_VNAME18
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=18, name=FSUIPC_VNAME18 (on size only)
Wed Aug 17 09:20:19 2022   [DEBUG]: CDA name FSUIPC_VNAME19 mapped to ID 19 [requestId=57]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area created with id=19 (size=8176) [requestID=58]
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=19, name=FSUIPC_VNAME19
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=19, name=FSUIPC_VNAME19 (on size only)
Wed Aug 17 09:20:19 2022   [DEBUG]: CDA name FSUIPC_VNAME20 mapped to ID 20 [requestId=59]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area created with id=20 (size=448) [requestID=60]
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=20, name=FSUIPC_VNAME20
Wed Aug 17 09:20:19 2022   [DEBUG]: CDAIdBank: allocating new id=20, name=FSUIPC_VNAME20 (on size only)
Wed Aug 17 09:20:19 2022    [INFO]: 1760 LVARS found, created 13 Client Data Areas
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data definition added with id=8 (size=8176) [requestID=61]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area set with id=8 and definitionId=8 with size=8176 [requestID=62]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data definition added with id=9 (size=8176) [requestID=63]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area set with id=9 and definitionId=9 with size=8176 [requestID=64]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data definition added with id=10 (size=8176) [requestID=65]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area set with id=10 and definitionId=10 with size=8176 [requestID=66]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data definition added with id=11 (size=8176) [requestID=67]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area set with id=11 and definitionId=11 with size=8176 [requestID=68]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data definition added with id=12 (size=8176) [requestID=69]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area set with id=12 and definitionId=12 with size=8176 [requestID=70]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data definition added with id=13 (size=8176) [requestID=71]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area set with id=13 and definitionId=13 with size=8176 [requestID=72]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data definition added with id=14 (size=8176) [requestID=73]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area set with id=14 and definitionId=14 with size=8176 [requestID=74]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data definition added with id=15 (size=8176) [requestID=75]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area set with id=15 and definitionId=15 with size=8176 [requestID=76]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data definition added with id=16 (size=8176) [requestID=77]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area set with id=16 and definitionId=16 with size=8176 [requestID=78]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data definition added with id=17 (size=8176) [requestID=79]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area set with id=17 and definitionId=17 with size=8176 [requestID=80]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data definition added with id=18 (size=8176) [requestID=81]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area set with id=18 and definitionId=18 with size=8176 [requestID=82]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data definition added with id=19 (size=8176) [requestID=83]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area set with id=19 and definitionId=19 with size=8176 [requestID=84]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data definition added with id=20 (size=448) [requestID=85]
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data area set with id=20 and definitionId=20 with size=448 [requestID=86]
Wed Aug 17 09:20:19 2022   [DEBUG]: Lvar name CDAs created
Wed Aug 17 09:20:19 2022    [INFO]: 1760 lvars loaded for aircraft 'Cessna Skyhawk G1000 Asobo'
Wed Aug 17 09:20:19 2022   [DEBUG]: Client data config area set with 17 CDAs (1 hvar, 13 lvar, 3 lvar values) [requestID=87]

Wed Aug 17 09:20:19 2022   [DEBUG]:    HVAR CDA 'FSUIPC_HSkyhawk0' with size=2632
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME8' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME9' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME10' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME11' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME12' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME13' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME14' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME15' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME16' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME17' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME18' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME19' with size=8176
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR CDA 'FSUIPC_VNAME20' with size=448
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR Values CDA 'FSUIPC_lvalues0' with size=8192
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR Values CDA 'FSUIPC_lvalues1' with size=8192
Wed Aug 17 09:20:19 2022   [DEBUG]:    LVAR Values CDA 'FSUIPC_lvalues2' with size=8192
 

 

John

Link to comment
Share on other sites

  • 3 weeks later...

I am having the same issues of FSUIPC not loading on initial startup in MSFS.. Only works when reloading the sim again. I've noticed this since installing GSXPro.... I am not sure how to find the disconnect/reconnect in the MSFS menu. Where is it located?

 

V/r

Tom

Link to comment
Share on other sites

6 minutes ago, tdenbrock said:

I am having the same issues of FSUIPC not loading on initial startup in MSFS

What do you mean by "FSUIPC not loading"? If you mean that FSUIPC7 is not auto-starting, please see 

 

Or do you mean that FSUIPC7 is not loading/receiving the lvars/hvars from the WASM? If that is the case, follow the instructions in this thread and show me your log (with appropriate logging enabled) and ini files if you want me to take a look.

11 minutes ago, tdenbrock said:

I am not sure how to find the disconnect/reconnect in the MSFS menu. Where is it located?

Strange question...The MSFS drop-down menu is in the FSUIPC7 main window menu bar. Please see the FSUIPC7 User guide.

John

Link to comment
Share on other sites

Just now, tdenbrock said:

What I mean is FSUIPC7 is not autoloading on initial startup of MSFS

Again, what do you mean by autoloading? If you mean FSUIPC7 is not loading/receiving the lvars/hvars from the WASM then I have told you what you need to do. If you mean FSUIPC7 is not auto-starting, I have provided you with a link on how to resolve this. I have explained where the MSFS menu is so that you can disconnect/reconnect.
If none of this helps, then please explain what your issues is.

Link to comment
Share on other sites

John, I'm sorry for all this confusion. What I am trying to say is the when I start MSFS.. FSUIPC 7 does not load/Auto start.   I have to restart MSFS for it to load.  I have also tried manually starting FSUIPC 7 after MSFS has loaded and still it will not load.  It doesn't show in my system tray until  I restart it. The only way (on my computer) for it to load is restart MSFS and then it loads. I read your response on this issue with another person in not having to restart MSFS but to disconnect/reconnect in the Menu for MSFS in FSUIPC 7 but if it doesn't load how can I disconnect/reconnect it if there is no way to access the menu.  I also am not sure where to find all this information that you have posted in how to fix it.

 

Tom

Link to comment
Share on other sites

5 minutes ago, tdenbrock said:

What I am trying to say is the when I start MSFS.. FSUIPC 7 does not load/Auto start. 

So, FSUIPC7 does not auto-start? If that is the issue, see the post I reference in my first comment on your issue.

6 minutes ago, tdenbrock said:

I have to restart MSFS for it to load. 

This I don't understand...why would FSUIPC7 auto-run the 2nd time but not the first? Each time you start should be the same as the last...and why restart MSFS and not just run FSUIPC7?

10 minutes ago, tdenbrock said:

I have also tried manually starting FSUIPC 7 after MSFS has loaded and still it will not load.  It doesn't show in my system tray until  I restart it.

Your use of the word load is what is confusing...and when you say 'restart it' do you mean MSFS or FSUIPC7?.

And what happens the third or on subsequent attempts to run MSFS? 

13 minutes ago, tdenbrock said:

I read your response on this issue with another person in not having to restart MSFS but to disconnect/reconnect in the Menu for MSFS in FSUIPC 7 but if it doesn't load how can I disconnect/reconnect it if there is no way to access the menu.

The MSFS menu is only (obviously...) available if FSUIPC7 is actually running...

13 minutes ago, tdenbrock said:

I also am not sure where to find all this information that you have posted in how to fix it.

All the information is in the User manuals or in the posts I have referenced...

But I still don't understand your issue... Could you tell me EXACTLY what happens when you run MSFS - do you see an FSUIPC7 splash screen? If not, it is not auto-starting, and if this is the case you should try to start manually by double-clicking the FSUIPC7.exe.  What happens when you do that? If it runs ok then, then your issue is with auto-start and you should refer to the link I posted on this issue. Otherwise, it could be a problem running FSUIPC7 - which is documented in the README.

But please explain your issue, without using load. A program either runs when you start it or not - do you have FSUIPC7 running? If it is in your system tray, it is running.

Link to comment
Share on other sites

OK, When I first initially start MSFS for the  day, There is No FSUPIC 7 Splash screen showing. .  MSFS pauses for about 70-90 seconds then continues.   There is no FSUIPC in the system tray. I shut it down and restart the game again and  then it pauses for 45-60 seconds then continues "ONLY" then will FSUIPC 7  show a splash screen FSUIPC7 and it shows running in the system tray.    Now if I try to start it  using the FSUIPC.exe file,  MSFS will run along with FSUIPC  showing "Getting cabin ready" splash screen, but it will not  show a FSUIPC 7 splash screen or show in the system tray.  It will not run using the FSUIPC .exe file at all.   Again I have to shut it down and restart the game using the MSFS .exe file  every time for it to run and for it to show  running in the system tray.   It only happens when I first run MSFS  or if I reboot my computer...... Not sure how else to explain it....

 

Tom

Edited by tdenbrock
Link to comment
Share on other sites

6 minutes ago, tdenbrock said:

OK, When I first initially start MSFS for the  day, There is No FSUPIC 7 Splash screen showing. .

Then FSUIPC7 is not auto-starting... How are you starting MSFS?

6 minutes ago, tdenbrock said:

MSFS pauses for about 20-30 secs then continues. 

This is normal...

7 minutes ago, tdenbrock said:

I shut it down and restart the game again and  then and "ONLY" then will FSUIPC 7  show a splash screen FSUIPC7 and it shows running in the system tray.   

So you are saying that FSUIPC7 auto-starts the 2nd and subsequent times you run MSFS, but not the first (after a reboot)...I don't understand this - there is no count on the number of times you start MSFS. 

9 minutes ago, tdenbrock said:

Now if I try to start it for the first time of the day  just using the FSUIPC.exe file,  MSFS will run along with FSUIPC  showing "Getting cabin ready" splash screen, but it will not  show a FSUIPC 7 splash screen or show in the system tray. 

This I don't understand either... Running the FSUIPC7.exe ONLY runs FSUIPC7, not MSFS. If you see the 'Preparing the cabin'  splash screen, you are using the MSFS desktop icon (created by the FSUIPC7 installer) or the MSFS.bat file, and not the FSUIPC7.exe. Please try and start using the FSUIPC7.exe, i.e. go to your FSUIPC7 installation folder and double click the FSUIPC7.exe file, NOT the MSFS desktop icon created by FSUIPC7 installer as that starts MSFS and not FSUIPC7, as the name suggests...

But if FSUIPC7 is just not starting the first time you run MSFS after a reboot, but works on subsequent attempts, then I have no idea what could cause thus. It is an MSFS issue, not an FSUIPC7 one, and I do not know why or how it could be doing this. It is not obeying the MSFS EXE.xml, so you should report this to Asobo.
When this occurs, just manually start FSUIPC7 by double clicking the FSUIPC7.exe, and NOT the FSUIPC7 MSFS icon or MSFS.bat file.

 John

Link to comment
Share on other sites

 

Then FSUIPC7 is not auto-starting... How are you starting MSFS?    JOHN said:

I use the desktop  MSFS  icon  MSFS created when the game was installed to start the game. 

 

So you are saying that FSUIPC7 auto-starts the 2nd and subsequent times you run MSFS, but not the first (after a reboot)...I don't understand this - there is no count on the number of times you start MSFS.   JOHN said:

 

Yes, if I do not reboot the computer FSUIPC7 auto-starts the 2nd and subsequent times I run MSFS, but not the first

 

John said:

Please try and start using the FSUIPC7.exe, i.e. go to your FSUIPC7 installation folder and double click the FSUIPC7.exe file, NOT the MSFS desktop icon created by FSUIPC7 installer 

 

Thanks John.  Yes I just realized that it is MSFS FSUIPC7 Icon. 🙄 I thought it was the FSUIPC exe file.  My Mistake. Having said that, I never use that MSFS FSUIPC icon to start MSFS.   

 I will try the latter and see if that works  Thanks

Tom

 

MSFS.lnk

Link to comment
Share on other sites

Hi John...  So,... I rebooted my computer and started MSFS. Again, FSUIPC7 didn't auto start so  I used the FSUIPC .exe file after MSFS loaded and it worked just fine. I am happy to say by doing as you suggested using the FSUIPC .exe file, FSUIPC started  just fine even when MSFS didn't load it on initial start-up. I greatly appreciate all your help in this matter... I consider this matter closed  (except that Asobo MSFS  FSUIPC 7 auto/start has an issue on initial startup)

 

Tom

Link to comment
Share on other sites

10 hours ago, tdenbrock said:

except that Asobo MSFS  FSUIPC 7 auto/start has an issue on initial startup

Yes, this is very strange, I do not know what could cause this, as the auto-start does work on subsequent runs of MSFS You will just have to manually start GSUIPC7 on the first run of MSFS I'm afraid.

Note the desktop MSFS icon created by the installer is just a shortcut to the MSFS.bat file, which shows a splash screen while MSFS is starting. It does not start FSUIPC7 - that is performed by MSFS itself using the EXE.xml file,

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.