Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SimConnect.cfg in My Documents - conflict with other mods #6

Closed
thealx-eech opened this issue Jan 29, 2021 · 2 comments · Fixed by #7
Closed

SimConnect.cfg in My Documents - conflict with other mods #6

thealx-eech opened this issue Jan 29, 2021 · 2 comments · Fixed by #7
Assignees

Comments

@thealx-eech
Copy link

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;

@dga711
Copy link

dga711 commented Feb 2, 2021

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

@TimianHeber
Copy link
Contributor

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!

@TimianHeber TimianHeber self-assigned this Feb 5, 2021
TimianHeber added a commit that referenced this issue Feb 27, 2021
* 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants