FlyingDutchman77

So far so good (using new .exe and ini setting)! Flying the 737 now; will test as well with the hondajet that I used initially.

What John is saying, that although those messages are there, this is not the cause of the current FPS drop. MS/Asobo has changed something in SU12 beta that is causing the FPS drop. Let's just wait until he has investigated. His support has been great so far, so I trust this will be sorted as well.

With wasm loaded: Without wasm loaded: So it is not the wasm. However, it takes a while for this to occur (let say 1-2 minutes after loading the flight for me). I will also update everything to the latest version and report the results. EDIT: Updated and issue is still present. So in version 7.3.17 and wasm 1.0.0.

Not sure if this is related, but there are a lot of messages being caused by FSUIPC (reported on the MSFS forum: https://forums.flightsimulator.com/t/fsuipc-introduces-microstutters-every-second-su12beta/578005/15

I will test without the wasm module. All other simconnect clients are fine. Mobiflight wasm is also not giving these stutters. Thx for having a look!

Actually the same happened to me today. Not having this issue ever before. Seems to be related to the SU12beta. Will report any further experiences!

Hi John, although I understand your suggestion, this is becoming increasingly more difficult with the increasing amount of Marketplace aircraft that cannot be used with Addon Manager very easily.... The limit is really becoming an issue now. Just for understanding, could you explain maybe a bit with this limit is there?

Thx! I struggled initially until I discovered in the FSUIPC console that the WAPI version was not matching. Now it is working again! Thanks again!

Great news. Could you share some code how you managed to do this? I'm using the MSFSVariableServices at the moment, but not sure how to use the FSUIPCConnection.WriteLVAR() function.

Hi, It seems the write function of FSUIPC LVARs is broken with MSFS SU10 beta. This is not happening with e.g. Mobiflight or SPAD.next. I know beta's are difficult to support, but it might be worth checking what makes FSUIPC different in this case. NB Reporting it here after experiencing it myself with the dotnet module, and seeing multiple posts on the MSFS forums on this issue.

Hi, It seems that with SU10 Beta, I can't get the LVARs set anymore. Using the MSFSVariableServices v1.3. Tried reload, stop, start, etc, but still not working anymore. Reading works fine btw. The LVAR is in the list for Writing to an LVar but it seems the write event does not arrive?! Interested to know if others experience the same issue.

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'

Hi John, 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. Btw: I will also update to the latest version. Many thx, Erik

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?

So in the end I think I found the issue. It has to do with exactly this that John posted: When I did that, the issue was solved. If I select 10 for the VS.LVARUpdateFrequency in my C# app (and still having 6Hz in the WASM .ini file) it will crash after a while when in release mode (not in debug mode). I haven't tested the other way around, but can do if you are interested in that. I might experience this issue where others do not, because I have various SimConnect tools talking to the sim simultanuously, and thereby reaching the stresspoint earlier. But it would be good to highlight this advice from John in the tutorial or example code for the MSFSVarService example. Again, both @Paul Henty and @John Dowson many thanks for (1) the great tools you are providing, and (2) the willingness to assist in issues like this.