Couatl Error at EGSS (UK2000 Stansted)

[cbd80]

Hi.

Everytime I try and load UK2000's Stansted, no matter what aircraft I get an error message saying the Couatl engine has been forced to restart. I have attached the error log.

The error message keeps popping up every 10 seconds and my memory usage spikes up to maximum.

I have uninstalled/reinstalled EGSS and I have the latest version of Addon Manager.

Any suggestions to resolve the issue please?

Thanks,

Chris

[cbd80]

Any update on this issue please?

[virtuali]

That error doesn't happen here. Try to download and install the full GSX installer, instead of just the Addon Manager.

If that doesn't work, try to remove the following folder:

C:\ProgramData\Microsoft\FSX\SceneryIndexes

(note that C:\ProgramData is hidden, so you'll have to enable hidden folders view in Explorer)

This will force both FSX and GSX to rebuild their caches. When GSX it's done, exit from FSX and enter it again, and see if the problem gets fixed.

[cbd80]

Thanks for the response Virtuali.

I have tried both options and unfortunately I have had no success.

I have found that the memory usage increase I am experiencing is caused by couatl.exe being continuously restarted.

Any further suggestions?

[virtuali]

I have found that the memory usage increase I am experiencing is caused by couatl.exe being continuously restarted.

None of this can be replicated, and nobody every reported it so far. Your error log doesn't show anything meaningful. The usual suggestion is to trying uninstalling GSX and reinstall it using the full installer, downloaded now (not a previous installer you might have)

[cbd80]

Hi. I did re-download the latest GSX installer.

The message that appears states:

The addon <unknown> is causing the Couatl Scripting Engine to restart. Details can be found in....

Perhaps it is not GSX put Couatl then. I have not had issues at other airports.

[virtuali]

Details can be found in....

That was the most important information: what the Couatl.ERR file that message is referring to contains now ?

[cbd80]

Hi Virtuali. Please find attached the latest log.

[cbd80]

I've done another fresh install of both the Addon Manager and GSX. I still keep getting errors at different airports. This one was with France VFR Bale Mulhouse.

[Bruce Hamilton]

Both the addon manager and GSX have been updated since August, are you using fresh downloads to reinstall?

[cbd80]

Hi Bruce,

Yes both latest installers. If I uninstall the Addon Manager and then install it GSX doesn't appear in the 'Addon' menu in FSX, so then I have to re-install GSX at which point the problems continue.

Chris

[Bruce Hamilton]

GSX isn't under the add-ons menu... what you should see is Addon Manager, which is pretty self explanatory, and Couatl Powered Products, which is where you'll find GSX.  If you have a proper install, you'll see both of those entries under add-ons.  Are either of those missing?

[cbd80]

Sorry Bruce, I should have been more specific. I was referring to the GSX Setting disappearing from the Couatl Powered Products Menu under Addon-Ons if I uninstall and re-install the Addon Manager.

I currently have both the Addon Manager and Couatl Powered Products listed under Add-ons.

[Bruce Hamilton]

The GSX setting will disappear if you remove the addon manager, GSX needs it to run.  You can't just reinstall the addon manager and expect GSX to return, you need to reinstall it as well.  Presuming you have both menu items under add-ons and GSX under Couatl powered products, start a flight with your aircraft on the active runway and press control-F12... what happens?

[cbd80]

That's fair enough about having to re-install GSX after a re-install of Addon Manager.

Ctrl-F12 opens the GSX dialogue box, that is not an issue.

What happens with some airports is that I get a message box that pops up saying an 'Addon (unknown) has caused Couatl.exe to stop responding'. Couatl restarts, and shortly afterwards the message pops back up and Couatl restarts again, and so on...

In the end I end up with several Couatl.exe running in Task Manager and my memory usage goes through the roof.