Might an fsx Simconnect give some kind of exit command after couatl already has connected?
Normally, when all works, no. It looks more like a conflict of some kind.
Might it help to let Windows search all simconnect.dll files and exchange them wit the one from the latest SDK?
You should never do that, because FSX's Simconnect used the dreaded SideBySide system, which in theory should allow multiple versions of the same .DLL running all at the same time. However, it was so complex and cumbersome that, when it didn't work for any reason, disasters happens and it required a very high level of knowledge to fix, like booting Windows
in safe mode and manually removing folder, then going through the registry to remove the problematic versions.
It was so complex and so fragile that:
- Microsoft themselves stopped using it for their VC++ redistributables
- Lockheed Martin got rid of it, when they switched for 64 bit, to a more traditional static library system.
However, this would only help the modern applications, those made using the new system. But since P3D server can still accept connections from ancient clients, dating back to the first FSX, those would STILL use the SideBySide method, so they might still confuse the newer application using static libraries because, while this approach is simpler, is NOT designed to allow multiple version of the same libraries running together.
So, the only real way to fix this, would be pester the developers of those applications still using the FSX Simconnect to switch to the P3D version, and make a proper native P3D version of their app. If you try to fix it yourself, it might work or not. Yes, there's a system (one of the many that can fail) in SideBySide in which you can "upgrade" an application made for an older version of the library to use a newer one, which must still be Side-by-side, but at least it might be the latest version. Because, there's only thing worse than using P3D with mixed FSX Simconnect apps, and is using P3D with *multiple* mixed version of *different* FSX Simconnect apps, like RTM, SP1 and SP2 clients, all connecting at the same time (hoping SideBySide works ), together with proper P3D apps using the native P3D Simconnect. When it works, it works, but its a miracle it even works...
That's why I said to disable all other add-ons first. To at least KNOW, for sure, if this is a Simconnect conflict, and identify the source. Because maybe it's not, and you risk completely screwing up your whole P3D installation if try to fix that yourself without knowing exactly what you are doing.