-
Notifications
You must be signed in to change notification settings - Fork 21
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
Reconnect button #15
Comments
likely the MSFS crash to desktop is not sending a connection termination to the simconnect client, and therefore the app still sees it as connected and doesn't reconnect later. I believe that this is an issue for this library: https://github.com/c-true/FsConnect, or maybe even a level below (MSFS base simconnect dll, which is not open source) Cannot do anything from the app besides hacking the connection termination (listening if the values don't change or something) which is not something I'd do, as this would bring other bugs. |
How STKP work with simconnect and know about disconnection? Pushback Express? |
I don't know. The underlying library I use is one abstraction layer above the simconnect.dll which is handling the connections and similar things. For what I see it uses ConnectionChanged event from the underlying library (simconnect base) to detect the change in the connection. |
Can you contact with author of library to resolve issue? |
May be you add disconnect button. Or reconnect. Or something. It's annoying restart application every time after CTD |
dude, how often your game crashes? :) |
It's every day 1-2 time always. This is microsoft style. When you fly alot - you have gamecrash a lot. |
If MSFS going to CTD - gees keep connected state. Next run of MSFS cause not working gees. It's staying connected, but no any report.
Every time after CTD i need to restart gees.
The text was updated successfully, but these errors were encountered: