FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: cbd80 on August 26, 2012, 09:08:17 pm
-
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
-
Any update on this issue please?
-
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.
-
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?
-
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)
-
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.
-
Details can be found in....
That was the most important information: what the Couatl.ERR file that message is referring to contains now ?
-
Hi Virtuali. Please find attached the latest log.
-
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.
-
Both the addon manager and GSX have been updated since August, are you using fresh downloads to reinstall?
-
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
-
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?
-
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.
-
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?
-
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.
-
I've been playing around with Stansted, and I can't get Couatl to crash at all. Unless you have Gary's service fleet active and its messing with Couatl in some way...
-
It's done it at FranceVFR's LFSB, and Taxi2Gates MHTG. So I don't think it is a UK2000 Scenery problem.
I can't figure anything specific that triggers it. I've tried with different aircraft and I get the same result.
-
Afraid I can't help you there, I don't have either of those sceneries to test.
-
Thanks anyway for looking at EGSS.
-
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...
On the GSX settings menu, there's a Troubleshooting page that allows you to create a Log file. Use that, and post the content of it, after going on an airport that generates the error.
-
Hi Virtuali. I have run the Troubleshooting Log, please find it attached.
I loaded UK2000 EGSS and when the scenery loaded the green text came up saying that GSX was re-generating scenery cache. It got to about 46% and I got the message that Couatl.exe had stopped responding. I let the message appear 3 times before exiting FSX.
The log doesn't say much, but hopefully it will be of some help to you.
Thanks.
-
This should be a better log. What seems to happen is that when Couatl.exe crashes and then restarts the log is erased. I managed to capture this between 2 crashes.
-
Here is another log when I try to load Taxi2Gate MHTG.
The only difference I can see is that it states it has failed to enumerate audio devices.
I have also included a screenshot of what I get on screen. Plus this time I also got a C++ Runtime Library error.
-
Here is another log when I try to load Taxi2Gate MHTG.
The only difference I can see is that it states it has failed to enumerate audio devices.
I have also included a screenshot of what I get on screen. Plus this time I also got a C++ Runtime Library error.
The audio driver is probably the only problem. You think there are different problems at the same time, but only because the audio problem happened at different steps.
As discussed many times on the forum, if the runtime error is caused by your audio driver, you should try the following:
- Restart Windows first.
- Update your audio driver. Try first updating it with the version of your audio card (or mainboard) manufacturer. If that doesn't work, try instead to use the default audio driver for your card (or mainboard) supplied with Windows.
- If that doesn't work, try this OpenAl download from Creative:
http://connect.creativelabs.com/openal/Downloads/oalinst.zip
Which installs an updated Open sound driver
- If that doesn't work, try to run FSX As Administrator.
-
Thank you for your detailed reply. Unfortunately none of the steps suggested have resolved the issue.
I have 2 audio devices:
1. Creative Xtreme Gamer PCI Card
2. Realtek (on-board sound card)
I have the requirement to use both cards.
With reference to your recommendations:
1. Restarting windows has no effect.
2. I updated the audio drivers of both devices with OEM drivers and this did not resolve the issue. In turn I disabled each device in Device Manager, and the problem still persisted i.e. I have not been able to determine which driver causes the issue.
3. I removed both hardware devices and rebooted and let Windows install the driver. This made no difference to the problem.
4. The Open Sound Driver did not resolve the issue either.
5. I always run FSX as administrator and I don't use UAC and I have cascaded Full Permissions through all of my FSX folders.
I have attached the log of loading FranceVFR LFSB (which only sometimes results in a Couatl crash). This time the scenery loaded fine and GSX worked.
From the log you can see that audio has been disabled. So, this wouldn't appear to be a factor with Couatl crashing and GSX subsequently not working. Also, at the bottom of the log it can be seen that GSX has loaded and it has loaded the scenery.bgl.
The Couatl crash happens 100% of the time at EGSS. The log for EGSS only ever gets as far as reading the scenery library and no further, understandably due to the Couatl crash.
If the audio drivers are the issue, why doesn't Couatl crash for all airports? What makes loading LFSB different from EGSS?
Furthermore, after Couatl crashing at EGSS, I can change location and load LFSB and it will then work fine.
I can't help but feel there is something more than sound drivers at play here. Is there anything we can do to investigate this issue further?
I appreciate your assistance.
-
Virtuali,
Please see the attached log. I was loading LFSB again and I managed to get this log before Couatl crashed.
What is the significance of this warning:
Warning: airport F6723 described in multiple BGL files without proper DeleteAirport record
-
Virtuali,
Please also see this log. I loaded LFSB again and this time it didn't crash. The log details further warnings.
When Couatl crashes the log is wiped as soon as the error message appears on screen. Is there anyway to prevent this from happening?
-
Virtuali,
It appears that Couatl/GSX can't handle more than 1 active AFCAD file at a time.
With my install of UK2000 EGSS I have the their AFCAD plus an AFCAD generated by VoxATC (a voice recognition AI ATC program) that informs VoxATC of the latest runway number changes from the current AIRAC.
When I disable the VoxATC generated AFCAD the scenery and GSX load without issue.
How can this be resolved?
-
It appears that Couatl/GSX can't handle more than 1 active AFCAD file at a time.
We'll check this. In general, GSX doesn't work with partial AFCADs, that are not self-contained, it assumes the AFAD in use will contain all the information needed. This is by design and won't likely be changed but, we surely must prevent the program from crashing in these cases.
-
Thank you Virtuali.
I have attached the AFCAD that VoxATC generated in the hope it can be of assistance to you.
Please let me know if there is anything further I can do to assist in this matter.
-
We found the problem, it's caused by a bit non-standard way the VoxATC program creates its AFCAD, which confuses GSX. Standby for a fix in the next days.
-
Good news, thank you.
-
Guys does anyone know if this has been fix or update made, still have this problem with various airports.
-
Guys does anyone know if this has been fix or update made, still have this problem with various airports.
If you are really having the *same* error (VoxATC creating AFCAD files with a non-standard layout), this has already been fixed in the current updated. If it's not, maybe you don't have the same error.
In this case, open a different thread, and clearly indicate:
- The airport used. If it's not default, clearly indicate which airport is and possibly the AFCAD in use.
- The gate used
- The airplane used.
- The GSX operation that should be called to replicate the error.
- The content of the COUATL.ERR that comes out when you have an error. The file is located under %APPDATA%\Virtuali