Hi,

i have a serious problem with GSX/couatl. Of course I know this belongs first of all in the FSDT forum and I started a topic there to get help, but after some initial troubleshooting commmunication has ceased and my further questions have just been ignored. May be you can help me here with some ideas.

Here is my problem:

GSX is sometimes every buggy (especially in conenction with the FSLABS A32X) and I need to restart the couatl service through the top menu, the same is done automatically when you change the settings in the GSX menu itself. The service used to restart with no issue rebuilding cache etc. But for the last year or so, the serice just disappears and only the Addon manager entry in the top menu is left. No way to restart couatl manually.

I have already done quite some troubleshooting:

- reinstalling P3Dv5.3 completelly from scratch and GSX as the only addon present in P3D

- deactivating all firewalls/antivirus services (I'm on WIn11 using only the default security/antivirus features), the complete Addon manager folder is excluded from the antivirus-program

- uninstall and reinstall of many VC++ libraries

Unfortunately, the issue persists. I even bought FSX Steam version and tried GSX there as well - the same problem happens there as well. So it seems it is not a P3D internal problem, but more some system wise problem. A complete Win re-installation is unfortunately not an option right now.

Can anybody of you think of a way to solve the problem or at least give me a hint what might be causing this issue? Maybe a problem with simconnect?

Here you can see the content of the log file:

"Python 2.7.13 Stackless 3.1b3 060516 (default, May 22 2017, 13:45:26) [MSC v.1900 32 bit (Intel)] wxPython 3.0.2.0
couatl v3.2 (build 4641)
log started on Sat Feb 26 13:40:09 2022

connecting to SimConnect...
connected to SimConnect
connected to bglmanx
disconnected from SimConnect."

I really like the program itself and would love to use it, but this couatl service drives me crazy, many bug reports around the net and the customer service, at least in my case, is really not helping!

Thanks for your help!
Kind regards

chris

Please don't post here questions that are best answered on FSDT support forum.

DO NOT reply here. Post this on FSDT forum, and the problem will be fixed so, don't say "customer service is not helping", because we obviously are, if you provide a proper report on the proper place, and Avsim is not.

Edited March 1, 20224 yr by virtuali

Sorry to say this, but this is exactly what i did on the FSDT forum. I reported an update on my problem on February 13th and again on Febrauary 26th and got no response.

But I'm more than glad to continue to solve the problem over on the FSDT if I get a response there.

2 hours ago, Chrjs said:

Sorry to say this, but this is exactly what i did on the FSDT forum. I reported an update on my problem on February 13th and again on Febrauary 26th and got no response.

But I'm more than glad to continue to solve the problem over on the FSDT if I get a response there.

This not true:

http://www.fsdreamteam.com/forum/index.php/topic,25596.0.html

You have been replied multiple times since last October, where you said you were using P3D 5.2 and your problem, which was clearly caused by an issue with your P3D install ( the API.DLL error doesn't have anything to with GSX, it came from Prepar3d.exe itself ).

Of course, this was absolutely correct and, after you disappeared for months, on February you said the API.DLL error stopped after reinstalling the sim, proving the problem never had anything to do with GSX to begin with.

I must have missed your last post but now I think I found the cause, after checking your log better:

- YOU ARE USING the 32 bit version of Couatl in P3D V5, that's likely because you modified by hand the add-on.xml to do so, since our installer surely configures it to use the 64 bit version, which is the one to use with P3D 4 and 5.

Or, perhaps another add-on that manages the add-on.xml files might have replaced the correct add-on.xml with a very old version, maybe coming from years ago, when we used a single 32 bit executable for FSX and P3D.

So yes, of course it's to be expected having issues when using the 32 bit version of the program in P3D V5 since, after we released the 64 bit version, years ago, we don't test the 32 bit version in P3D anymore, it's remarkable it even starts once...