Products Support > GSX Support FSX/P3D
GSX Couatl scripting engine hasn't started **SOLVED**
golfkung05:
Hi,
I also faced the issue as well, i understand that there might be an issue with the simmconnection somehow because I cannot call the GSX as usual a couple days ago and then I decided to reinstall the GSX1,2 again. Before I decided to uninstall the gsx, I found that my gsx had been downgraded to trial mode without any reason.
After installing again, I activated via the FSDT Universal Installer which shows that I'm already fully activated but after validation on my P3D, it is still in the trail mode.
I have attached the log file for your clarification. Regards
virtuali:
--- Quote from: golfkung05 on August 14, 2022, 09:25:57 pm ---After installing again, I activated via the FSDT Universal Installer which shows that I'm already fully activated but after validation on my P3D, it is still in the trail mode.
--- End quote ---
Your problem doesn't have anything to do with activation: if the FSDT Installer says a product is active, than IT IS active. The issue is, according to your log, the Couatl program started, but disconnected immediately, as if the simulator quit, or there was another similar problem with Simconnect.
It's important to note, when you see that kind of log, it shows no error happened, just the program received a "Quit" order from Simconnect, which usually should only come when you exit the sim.
And the puzzling thing is, it's a *clean* quit, as if you really exited the sim normally. When it's an abrupt disconnection, the log will be different, saying something like "has the sim crashed ?" because this is what we detected and log when the connections stops without receiving a proper "quit" command.
Which wasn't your case or, if it was, it wasn't logged (that might be a possibility), it really looks like a straight quit. Could be you have other add-ons running the FSX version of Simconnect ? Some add-ons do this, to make it "easier" for them, so they only distribute a single client for all simulators, because FSX clients *usually* can connect to P3D. We are a proper P3D native client but, it's possible another add-on is using the FSX Simconnect and if THAT one is missing/corrupted or has other issues, it might even affect a proper P3D client like ours.
The only way to know this for sure, would be disabling all add-ons from the Options->Add-ons menu, except of course for FSDT Addon manager, and see if it runs alone. If it does, re-enable one add-on at a time, to eventually find a conflict.
Beaufort:
Could that also be my problem? As you might see from my log, in my case simconnect connects. Might an fsx Simconnect give some kind of exit command after couatl already has connected?
Might it help to let Windows search all simconnect.dll files and exchange them wit the one from the latest SDK?
virtuali:
--- Quote from: Beaufort on August 14, 2022, 11:14:48 pm ---Might an fsx Simconnect give some kind of exit command after couatl already has connected?
--- End quote ---
Normally, when all works, no. It looks more like a conflict of some kind.
--- Quote ---Might it help to let Windows search all simconnect.dll files and exchange them wit the one from the latest SDK?
--- End quote ---
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.
gevan:
Hi Umberto,
I had all this year without using P3Dv4+ because I replaced the hard disk due to failures and now that I have used the simulator again, I have the problem that GSX 1 and 2 don't work, it gives me an error that couatl is not executed and it's due to the antivirus, which I have always excluded the folders and files of the FSDreamTeam programs (I have used time ago and I haven't had that problem with antivirus, I have always used Avira)
I have already uninstalled all the FSDT programs including sceneries and gsx, reinstalled with the new installers available on your website and then ran the "FSDT Installer" program to update everything. I did this with the antivirus disabled, just in case.
I attach the log file and a screenshot of my antivirus to confirm what I say.
I appreciate a little help on what else I can do to solve this problem..
Regards
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version