You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CJ4 mod team contacted me about conflict with my Kinetic Assistant, which uses your fsConnect.DLL, that SimConnect.cfg in My Documents cause their WASM module functionality problems. I have fixed it on my end, but you should consider to set local CFG placement as default:
public SimConnectFileLocation SimConnectFileLocation { get; set; } = SimConnectFileLocation.Local;
The text was updated successfully, but these errors were encountered:
Got confirmation the SimConnect client that drives the WASM modules in MSFS looks for simconnect.cfg in documents etc. first. For some reason.
Asobo will fix this in the future.
But it would still be good to apply the changes @thealx-eech suggested. Thank you
Thanks for the feedback. I will change the default location as you suggested and push an update.
Any other suggestions and feature requests are always welcome!
* Fixes#6, setting Local as default location for writing SimConnect.cfg
* Added all simulation variables and units as documented by the SimVarWatcher example in the MSFS SDK
* Verified that bundled SimConnect binaries in SDK 0.10.0 is the same as in this release.
CJ4 mod team contacted me about conflict with my Kinetic Assistant, which uses your fsConnect.DLL, that SimConnect.cfg in My Documents cause their WASM module functionality problems. I have fixed it on my end, but you should consider to set local CFG placement as default:
public SimConnectFileLocation SimConnectFileLocation { get; set; } = SimConnectFileLocation.Local;
The text was updated successfully, but these errors were encountered: