Flex45

I was on VS2022, MSVC v143 and tried SDK 10.0.19041,0 but was failing in the same way. I did a complete VS2022 update and that fixed the issue, so I don't know what it was exactly but at least the issue is now resolved! Not sure either, just trying to set an Lvar with v1.0.0 libraries, Lvar was set and then an exception was thrown. I didn't investigate further though as with v1.0.1 libraries there was no issue. fsuipc-lvar-module version in community folder, was in both cases v1.0.0. Thanks for the help once more Regards,

Hi again, Disregard the above post, it was totally my bad. I used the new WAPI versions but didn't update the libraries from the new package. I am however facing a different issue now. Using the new version libraries I can only build in debug mode with the debug library but not in release mode. In release mode with release library I get the following error during build: Any ideas John? I get the same behavior using library from WAPI package v 1.0.0 and 1.0.1. Also I confirm as well what another user reported, (at least in debug mode that I can build) v1.0.0 is causing exceptions and crashes, v1.0.1 looks more stable. Regards,

Hi John, Using FSUIPC_WAPI v1.0.0 and 1.0.1, I am unable to use getLvar() as it used to work with v0.9.1. I guess that's caused by the delay introduced in the recent versions and the requirement to get the callback before but, the getLvar/setLvar etc, since they are called on demand and not using callbacks, can't they be excluded from these changes in loading of variables and work like they used to work? Regards,

Great! Many Thanks! Regards,

Not sure either, but it happens every time and can be reproduced very easily. Initialize with park brake set and then release parking brake. You will see that one side gives the callback and drops pressure to 0 the other one remains to the old value without callback. Yes for the moment and for my project the getLvar method works more optimally I think. Regards,

Hi John, A quick update on how it worked out. I had some issues as well with the callback method. 1) Even though I was waiting for a call that Lvars are loaded and available before using them, they never initialized properly. However when an Lvar was changing I was getting a callback with the proper value - not for all of them at init though. I even increased LvarScanDelay from 5 to 50 but still with no luck. I didn't investigate further though as it wasn't the only issue. 2) A few variables, never called back even when their value was changed. Out of my head, to name a few: - A32NX_HYD_BRAKE_ALTN_RIGHT_PRESS (A32NX_HYD_BRAKE_ALTN_LEFT_PRESS updates normally or vice versa 🙂) Eg. Parking brake on->off....One gives the callback with the updated value the other one doesn't. - A32NX_FMA_VERTICAL_MODE Also I didn't investigate too much on this, there might be more. (Doing a getLvar Call though returns the correct value). 3) Even though this is not a bug, I think callback method works for my project less optimally compared to the getLvar individual call method. (Explained below) If throughout the flight I use for example 50 Lvars, those 50 are not used all the time and for the whole flight. At a given flight phase a few are only used and might not be used again for the rest of the flight. The getLvar method allows me to call only the few I need and don't bother with the rest that won't be used anymore. The register for callback method, unless there is a way I am missing, will keep monitoring all the Lvars all the time. Regards,

Yes, now there are no getLvar calls, just a few setLvar calls on demand along with the 3 instances with execcalclatorCode. Let's see how it goes, I will test it for a couple of days and let you know the results either case. Regards,

Hi John, Many thanks for the help, it works perfectly now using the callback. I keep simconnect logging and once the issue with execcalclatorCode occurs again (if it does), I will send you the logs. Many thanks

That was because simconnect.ini logging was at Error level....I increased to Verbose and now it's logging all the data however I need to reproduce the issue again and send you the log. I did check those simconnect connections throwing the exceptions though and are mostly other aircrafts/applications exe when autoloading with MSFS start. After that simconnect runs without any exceptions. (I will send you the log once I reproduce the issue to have a look as well). Meanwhile I am trying to register the callbacks however as easy as it should be, I must be doing something wrong and get some build errors. My workflow up to the errors point is the following: In the initialization I do: WasmPtr = WASMIF::GetInstance(); WasmPtr->setLvarUpdateFrequency(6); WasmPtr->Start(); and then I add the following function (which I expect to be called when loading is completed, as described here https://github.com/jldowson/FSUIPC_WAPI) void WASMIF::registerUpdateCallback(void(*callbackFunction)(void)) { } When I build the code I get an error that registerUpdateCallback function is already defined. Is there an example/workflow somewhere I can follow to do the callback registers correctly? Thanks

Not yet I will implement this tonight/tomorrow and let you know. Attached it's the simconnect log..... simconnect000.log

[DEBUG] never logged successful execcalcCode calls, only [ERROR] ones were logged. In [TRACE] level unfortunately, file size becomes excessive very fast, which makes it impossible to log in that level for too long. (I have to start the flight from cold and dark and then hope the issue occurs in flight to be logged otherwise it never occured up to now). I tried this as well but error logged by simconnect isn't of much help I think. 3821.27980 [336] I/O Error! (2, 80004004) As a temporary workaround for now (since execcalclatorCode calls in my code are in only 3 instances and called on demand/not frequently) I tried, after those calls to stop and start connection again to the module (using end() and start() functions). After the restart everything is back to normal, also execcalclatorCode calls. I know it's not the best solution/fix but at least it protects things from breaking after the error, for now. (reload() call didn't help) Thanks

Hi John, Issue occured again and got the debug log: Wed Jan 25 2023 10:44:08.348 [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 0.9.1 (WASM version 0.9.1) Wed Jan 25 2023 10:44:08.349 [INFO]: Connected to MSFS Wed Jan 25 2023 10:44:08.349 [DEBUG]: Starting config request timer... Wed Jan 25 2023 10:44:08.384 [DEBUG]: Config Data 0: name=FSUIPC_VNAME7, size=8176, type=0 Wed Jan 25 2023 10:44:08.384 [DEBUG]: Config Data 1: name=FSUIPC_VNAME8, size=8176, type=0 Wed Jan 25 2023 10:44:08.384 [DEBUG]: Config Data 2: name=FSUIPC_VNAME9, size=8176, type=0 Wed Jan 25 2023 10:44:08.384 [DEBUG]: Config Data 3: name=FSUIPC_VNAME10, size=8176, type=0 Wed Jan 25 2023 10:44:08.384 [DEBUG]: Config Data 4: name=FSUIPC_VNAME11, size=8176, type=0 Wed Jan 25 2023 10:44:08.384 [DEBUG]: Config Data 5: name=FSUIPC_VNAME12, size=8176, type=0 Wed Jan 25 2023 10:44:08.384 [DEBUG]: Config Data 6: name=FSUIPC_VNAME13, size=8176, type=0 Wed Jan 25 2023 10:44:08.384 [DEBUG]: Config Data 7: name=FSUIPC_VNAME14, size=8176, type=0 Wed Jan 25 2023 10:44:08.384 [DEBUG]: Config Data 8: name=FSUIPC_VNAME15, size=8176, type=0 Wed Jan 25 2023 10:44:08.384 [DEBUG]: Config Data 9: name=FSUIPC_VNAME16, size=8176, type=0 Wed Jan 25 2023 10:44:08.384 [DEBUG]: Config Data 10: name=FSUIPC_VNAME17, size=8176, type=0 Wed Jan 25 2023 10:44:08.384 [DEBUG]: Config Data 11: name=FSUIPC_VNAME18, size=6216, type=0 Wed Jan 25 2023 10:44:08.384 [DEBUG]: Config Data 12: name=FSUIPC_lvalues0, size=8192, type=2 Wed Jan 25 2023 10:44:08.384 [DEBUG]: Config Data 13: name=FSUIPC_lvalues1, size=8192, type=2 Wed Jan 25 2023 10:44:08.384 [DEBUG]: Config Data 14: name=FSUIPC_lvalues2, size=8192, type=2 Wed Jan 25 2023 10:44:08.384 [DEBUG]: SIMCONNECT_RECV_ID_CLIENT_DATA received: EVENT_CONFIG_RECEIVED Wed Jan 25 2023 10:44:08.384 [DEBUG]: CDA name FSUIPC_VNAME7 mapped to ID 4 [requestId=16] Wed Jan 25 2023 10:44:08.384 [DEBUG]: Client data area created with id=4 (size=8176) [requestID=17] Wed Jan 25 2023 10:44:08.384 [DEBUG]: Client data definition added with id=4 (size=8176) Wed Jan 25 2023 10:44:08.384 [DEBUG]: CDA 'FSUIPC_VNAME7 with id=4 and definitionId=4 requested Wed Jan 25 2023 10:44:08.384 [DEBUG]: CDA name FSUIPC_VNAME8 mapped to ID 5 [requestId=20] Wed Jan 25 2023 10:44:08.384 [DEBUG]: Client data area created with id=5 (size=8176) [requestID=21] Wed Jan 25 2023 10:44:08.384 [DEBUG]: Client data definition added with id=5 (size=8176) Wed Jan 25 2023 10:44:08.384 [DEBUG]: CDA 'FSUIPC_VNAME8 with id=5 and definitionId=5 requested Wed Jan 25 2023 10:44:08.384 [DEBUG]: CDA name FSUIPC_VNAME9 mapped to ID 6 [requestId=24] Wed Jan 25 2023 10:44:08.384 [DEBUG]: Client data area created with id=6 (size=8176) [requestID=25] Wed Jan 25 2023 10:44:08.384 [DEBUG]: Client data definition added with id=6 (size=8176) Wed Jan 25 2023 10:44:08.384 [DEBUG]: CDA 'FSUIPC_VNAME9 with id=6 and definitionId=6 requested Wed Jan 25 2023 10:44:08.384 [DEBUG]: CDA name FSUIPC_VNAME10 mapped to ID 7 [requestId=28] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data area created with id=7 (size=8176) [requestID=29] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data definition added with id=7 (size=8176) Wed Jan 25 2023 10:44:08.385 [DEBUG]: CDA 'FSUIPC_VNAME10 with id=7 and definitionId=7 requested Wed Jan 25 2023 10:44:08.385 [DEBUG]: CDA name FSUIPC_VNAME11 mapped to ID 8 [requestId=32] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data area created with id=8 (size=8176) [requestID=33] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data definition added with id=8 (size=8176) Wed Jan 25 2023 10:44:08.385 [DEBUG]: CDA 'FSUIPC_VNAME11 with id=8 and definitionId=8 requested Wed Jan 25 2023 10:44:08.385 [DEBUG]: CDA name FSUIPC_VNAME12 mapped to ID 9 [requestId=36] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data area created with id=9 (size=8176) [requestID=37] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data definition added with id=9 (size=8176) Wed Jan 25 2023 10:44:08.385 [DEBUG]: CDA 'FSUIPC_VNAME12 with id=9 and definitionId=9 requested Wed Jan 25 2023 10:44:08.385 [DEBUG]: CDA name FSUIPC_VNAME13 mapped to ID 10 [requestId=40] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data area created with id=10 (size=8176) [requestID=41] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data definition added with id=10 (size=8176) Wed Jan 25 2023 10:44:08.385 [DEBUG]: CDA 'FSUIPC_VNAME13 with id=10 and definitionId=10 requested Wed Jan 25 2023 10:44:08.385 [DEBUG]: CDA name FSUIPC_VNAME14 mapped to ID 11 [requestId=44] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data area created with id=11 (size=8176) [requestID=45] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data definition added with id=11 (size=8176) Wed Jan 25 2023 10:44:08.385 [DEBUG]: CDA 'FSUIPC_VNAME14 with id=11 and definitionId=11 requested Wed Jan 25 2023 10:44:08.385 [DEBUG]: CDA name FSUIPC_VNAME15 mapped to ID 12 [requestId=48] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data area created with id=12 (size=8176) [requestID=49] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data definition added with id=12 (size=8176) Wed Jan 25 2023 10:44:08.385 [DEBUG]: CDA 'FSUIPC_VNAME15 with id=12 and definitionId=12 requested Wed Jan 25 2023 10:44:08.385 [DEBUG]: CDA name FSUIPC_VNAME16 mapped to ID 13 [requestId=52] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data area created with id=13 (size=8176) [requestID=53] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data definition added with id=13 (size=8176) Wed Jan 25 2023 10:44:08.385 [DEBUG]: CDA 'FSUIPC_VNAME16 with id=13 and definitionId=13 requested Wed Jan 25 2023 10:44:08.385 [DEBUG]: CDA name FSUIPC_VNAME17 mapped to ID 14 [requestId=56] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data area created with id=14 (size=8176) [requestID=57] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data definition added with id=14 (size=8176) Wed Jan 25 2023 10:44:08.385 [DEBUG]: CDA 'FSUIPC_VNAME17 with id=14 and definitionId=14 requested Wed Jan 25 2023 10:44:08.385 [DEBUG]: CDA name FSUIPC_VNAME18 mapped to ID 15 [requestId=60] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data area created with id=15 (size=6216) [requestID=61] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data definition added with id=15 (size=6216) Wed Jan 25 2023 10:44:08.385 [DEBUG]: CDA 'FSUIPC_VNAME18 with id=15 and definitionId=15 requested Wed Jan 25 2023 10:44:08.385 [DEBUG]: CDA name FSUIPC_lvalues0 mapped to ID 16 [requestId=64] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data area created with id=16 (size=8192) [requestID=65] Wed Jan 25 2023 10:44:08.385 [DEBUG]: Client data definition added with id=16 (size=8192) Wed Jan 25 2023 10:44:08.386 [DEBUG]: CDA 'FSUIPC_lvalues0 with id=16 and definitionId=16 requested Wed Jan 25 2023 10:44:08.386 [DEBUG]: CDA name FSUIPC_lvalues1 mapped to ID 17 [requestId=68] Wed Jan 25 2023 10:44:08.386 [DEBUG]: Client data area created with id=17 (size=8192) [requestID=69] Wed Jan 25 2023 10:44:08.386 [DEBUG]: Client data definition added with id=17 (size=8192) Wed Jan 25 2023 10:44:08.386 [DEBUG]: CDA 'FSUIPC_lvalues1 with id=17 and definitionId=17 requested Wed Jan 25 2023 10:44:08.386 [DEBUG]: CDA name FSUIPC_lvalues2 mapped to ID 18 [requestId=72] Wed Jan 25 2023 10:44:08.386 [DEBUG]: Client data area created with id=18 (size=8192) [requestID=73] Wed Jan 25 2023 10:44:08.386 [DEBUG]: Client data definition added with id=18 (size=8192) Wed Jan 25 2023 10:44:08.386 [DEBUG]: CDA 'FSUIPC_lvalues2 with id=18 and definitionId=18 requested Wed Jan 25 2023 10:44:08.386 [DEBUG]: EVENT_LVARS_RECEIVED:1 of 12: dwObjectID=0, dwDefineID=4, dwDefineCount=1, dwentrynumber=1, dwoutof=1 Wed Jan 25 2023 10:44:08.386 [DEBUG]: EVENT_LVARS_RECEIVED:2 of 12: dwObjectID=0, dwDefineID=5, dwDefineCount=1, dwentrynumber=1, dwoutof=1 Wed Jan 25 2023 10:44:08.386 [DEBUG]: EVENT_LVARS_RECEIVED:3 of 12: dwObjectID=0, dwDefineID=6, dwDefineCount=1, dwentrynumber=1, dwoutof=1 Wed Jan 25 2023 10:44:08.386 [DEBUG]: EVENT_LVARS_RECEIVED:4 of 12: dwObjectID=0, dwDefineID=7, dwDefineCount=1, dwentrynumber=1, dwoutof=1 Wed Jan 25 2023 10:44:08.386 [DEBUG]: EVENT_LVARS_RECEIVED:5 of 12: dwObjectID=0, dwDefineID=8, dwDefineCount=1, dwentrynumber=1, dwoutof=1 Wed Jan 25 2023 10:44:08.386 [DEBUG]: EVENT_LVARS_RECEIVED:6 of 12: dwObjectID=0, dwDefineID=9, dwDefineCount=1, dwentrynumber=1, dwoutof=1 Wed Jan 25 2023 10:44:08.386 [DEBUG]: EVENT_LVARS_RECEIVED:7 of 12: dwObjectID=0, dwDefineID=10, dwDefineCount=1, dwentrynumber=1, dwoutof=1 Wed Jan 25 2023 10:44:08.386 [DEBUG]: EVENT_LVARS_RECEIVED:8 of 12: dwObjectID=0, dwDefineID=11, dwDefineCount=1, dwentrynumber=1, dwoutof=1 Wed Jan 25 2023 10:44:08.386 [DEBUG]: EVENT_LVARS_RECEIVED:9 of 12: dwObjectID=0, dwDefineID=12, dwDefineCount=1, dwentrynumber=1, dwoutof=1 Wed Jan 25 2023 10:44:08.386 [DEBUG]: EVENT_LVARS_RECEIVED:10 of 12: dwObjectID=0, dwDefineID=13, dwDefineCount=1, dwentrynumber=1, dwoutof=1 Wed Jan 25 2023 10:44:08.387 [DEBUG]: EVENT_LVARS_RECEIVED:11 of 12: dwObjectID=0, dwDefineID=14, dwDefineCount=1, dwentrynumber=1, dwoutof=1 Wed Jan 25 2023 10:44:08.387 [DEBUG]: EVENT_LVARS_RECEIVED:12 of 12: dwObjectID=0, dwDefineID=15, dwDefineCount=1, dwentrynumber=1, dwoutof=1 Wed Jan 25 2023 11:27:03.557 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:03.728 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:03.882 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:04.052 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:04.224 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:04.379 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:04.549 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:04.720 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:04.875 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:05.043 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:05.213 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:05.383 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:05.552 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:05.709 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:05.878 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:06.049 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:06.204 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:06.374 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:06.545 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:06.715 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:06.869 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:07.040 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:07.209 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:07.379 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:07.533 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:07.703 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:07.873 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:08.043 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:08.198 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:08.368 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:08.538 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:08.693 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:08.864 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:09.032 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:09.200 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:09.370 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:09.525 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:09.696 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:09.866 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:10.035 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:10.191 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:10.361 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:10.531 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:10.686 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:10.855 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:10.903 [ERROR]: Error setting Client Data Calculator Code: '(>H:A320_Neo_CDU_2_BTN_L6)' Wed Jan 25 2023 11:27:11.027 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:11.197 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:11.353 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:11.523 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:11.693 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:11.847 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:12.018 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:12.187 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Wed Jan 25 2023 11:27:12.358 [ERROR]: SimConnect_RequestClientData for lvars failed!!!! Note: Before the execcalclatorCode call that failed (BTN_L6) there was another executecalclatorCode call for another mcdu button which worked ok and the fault triggered between the two calls, thus the first error is not a calc code. Any ideas? Thanks

I already debugged my code when the issue is active and all seems ok (executecalclatorCode lines still running). I am not sure how to debug WAPI though.

I enabled the debug level logging and waiting for the issue to occur again as I can't reproduce on demand. I will let you know once I have the data you need. Thanks once more

It's an external application so just a restart of the application restores everything.... No need for a simulator restart. I don't use anything else, just the fsuipc wapi to get and set the variables through my code. In my code I have some setLvar and executecalclatorCode calls on demand and a general getLvar function which is called every 1 or 2 seconds.... Also if it helps you further, when the issue occurs, trying the same executecalclatorCode command through your Wasm Client application works perfectly and then retrying from my code still does nothing (execute CalculatorCode line still hit in my code but the command never reaches the aircraft). Is there a chance the connection to the module terminates when this occurs? I will enable the debug as you suggested and I will let you know. Thanks

Hi John, I notice a weird issue when using executecalccode to set an Hvar (using FSUIPC_WAPI module) and looking in the forum I can only find related topics but not the same. Specifically I try to set a simple Hvar for the A32NX using executecalclatorcode and everything is working perfectly except is some random cases which I cannot figure out when they occur. The call in my code is similar to this: WasmPtr->executecalclatorCode("(>H:A320_Neo_CDU_2_BTN_CLR)"); As said above everything works ok most of the time but there are some random cases where it fails and the main issue is that everything else breaks as well. eg. getLvar() (which I call from anothier function in my code) also stops working etc (see log data below). Looking in the FSUIPC_WASMIF debug log, in normal conditions I have the following: [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 0.9.1 (WASM version 0.9.1) [INFO]: Connected to MSFS but when executecalclatorCode fails I have the following: [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 0.9.1 (WASM version 0.9.1) [INFO]: Connected to MSFS [ERROR]: Error setting Client Data Calculator Code: '(>H:A320_Neo_CDU_2_BTN_CLR)' [ERROR]: SimConnect_RequestClientData for lvars failed!!!! [ERROR]: SimConnect_RequestClientData for lvars failed!!!! [ERROR]: SimConnect_RequestClientData for lvars failed!!!! [ERROR]: SimConnect_RequestClientData for lvars failed!!!! [ERROR]: SimConnect_RequestClientData for lvars failed!!!! [ERROR]: SimConnect_RequestClientData for lvars failed!!!! [ERROR]: SimConnect_RequestClientData for lvars failed!!!! [ERROR]: SimConnect_RequestClientData for lvars failed!!!! [ERROR]: Error setting Client Data Calculator Code: '(>H:A320_Neo_CDU_2_BTN_CLR)' [ERROR]: SimConnect_RequestClientData for lvars failed!!!! [ERROR]: SimConnect_RequestClientData for lvars failed!!!! [ERROR]: SimConnect_RequestClientData for lvars failed!!!! [ERROR]: SimConnect_RequestClientData for lvars failed!!!! [ERROR]: SimConnect_RequestClientData for lvars failed!!!! [ERROR]: SimConnect_RequestClientData for lvars failed!!!! and log goes on like this...... Any ideas as to why this might happening? Also is there a way I can protect it from breaking completely in case the Hvar call fails? Thanks in advance, Regards,

Hi John, This debug library worked perfectly right away! (Without even the setSimConfigConnection line). Many thanks for the help! Regards,

Hi John, Many thanks for the info and the files! I will give it a try and let you know of the results. Thanks

To be honest I am not quite sure how to do this 🙂 Will it be possible to provide also the debug library when you can? Thanks

Hi John, Sorry if this is known but I couldn't find anything in the forum. In my code, I am able to perfectly read and write Lvars from/to the sim (using FSUIPC_WAPI getLvar and setLvar calls) but in release mode only! (using FSUIPC_WAPI.lib) In debug mode (using FSUIPC_WAPI_debug.lib) is causing a crash when calling the module start() function. Trying also to build and run WASMClient found on git (https://github.com/jldowson/WASMClient), in release mode it is able to run and connect to simconnect but in debug it also fails saying: "failed opening a simconnect connection." So, since the issue is not only in my code and since release mode is functioning perfectly, is there a chance there is something wrong with the debug library or am I doing something wrong/missing a VS setting etc? I am using latest FSUIPC_WAPI libraries (v0.9.1 - 20Oct2022). Thanks in advance, Regards,