Milan van den Muyzenberg

Nvm; looks like something else changed. Setting HVARs on the default A320neo works. Sorry.

Quite recently, setting HVARs stopped working for me. More specific, I use HVARs to set the ECAM on FBW A32NX in MSFS2020, e.g. H:A320_Neo_EICAS_2_ECAM_CHANGE_PAGE_HYD Is there any known issue with HVARs? Am using FSUIPC 7.3.16 on latest MSFS. Setting this HVAR from FSUIPC seems to have no effect.

Thanks, with this update I was able to get my application up and running again!

There's a new beta of FSUIPC: 7.3.9h. After installation, when I start MSFSVariableServices, I get an AccesViolationException, so I guess MSFSVariableServices needs an update as well.

Hi, After updating to SU10 and the latest SDK, a large part of the interface appears to be broken: Not all LVARs are visible (also not in FSUIP's WASMClient), e.g. in FBW A32NX Callbacks on LVARs that I can write to, are not called when values are updated in the sim @Paul Henty: just to be sure...can this be caused by issues that require fixing by John?

Thank you so much for putting us on the right track. Things did not work in John's client. I decided to first reinstall FSUIPC and amazingly that did the trick...

Dear Paul, Your work is great and I am progressing with supporting my HW modules for MSFS. On my system, everything connects just fine to MSFS, all LVARS get loaded, etc. Another user of my SW has an issue: no LVARs are shown when he starts my application. To determine the root cause, we updated everything to latest greatest (FSUIPC 7.3.6. and FSUIPCClientDLL 3.2.20), compiled and ran MSFSVariableServices_CSharp application, but the same issue appears. The "Monitor Changing LVars in Real Time box just stays empty. See attached image. I checked, and in FSUIPC (Add-ons->WASM->List Lvars) the full list of Lvars is available. Do you have any idea as to what might cause this?

Whow, that's fast. Will migrate asap. Migrated and working fine. Thanks

Thanks Paul; looking forward to this release

Problem seems to be solved. For anyone reading this topic dealing with the same issue: don't dispose the MSFSVariableServices or set its reference to null. Timing of subscribing delegates to change of an LVar somehow seems to matter...

Debug/trace does not reveal any issue. Your example code works. In fact, my code is very much the same and partly taken from the example. Hopefully, you find anything by briefly looking at the code (see DM). It's not much and not complex. Thanks.

Following your suggestion to not dispose object of type MSFSVariableServices, I ran into another issue. After first start of MSFSVariableServices, everything runs fine, i.e. am getting LVAR change updates. After stopping and restarting, I do no longer get LVAR updates. I trimmed down my entire application to a bare minimum, which I am obviously willing to share if you are interested.

Hi Paul, Thanks for your quick response. Your DLL, FSUIPC and the FSUIPC_WAPID.DLL all have the version numbers you refer to. When I disconnect, I first remove the "generic" callbacksm (OnLogEntryReceivedOnValuesChangedOnVariableListChanged) followed by a call to Stop() on the MSFSVariableServices object. After that, I set the reference to null. I do not explicitly call Dispose() on the object. Even though I can (and will for now) implement your suggestion (i.e. do not dispose of the object), I wonder how I can get rid of it without running the risk of getting this exception. Can you explain how to get rid of it in a controlled way? Edit: the suggested fix somehow does not work. After calling Stop() and Start(), the IsRunning getter returns false consistently...

First of I'd like to express my appreciation for the client DLL for .Net. Works great. There's one thing that's bugging me at this moment. It's this exception: Managed Debugging Assistant 'CallbackOnCollectedDelegate' Message=Managed Debugging Assistant 'CallbackOnCollectedDelegate' : 'A callback was made on a garbage collected delegate of type 'fsuipcClient!FSUIPC.WAPI+LogCallback::Invoke'. This may cause application crashes, corruption and data loss. When passing delegates to unmanaged code, they must be kept alive by the managed application until it is guaranteed that they will never be called.' I get this when disconnecting from MSFSVariableServices. When disconnecting, I first remove all generic and lvar callbacks. Subsequently, I stop the services. Nevertheless, this exception occurs. What am I doing wrong?