General Category > General Discussion

Couatl.exe issue

(1/3) > >>

flynryan692:
I posted this in a different thread earlier, but I think it probably needs its own thread.

I did a flight on the 9th from KLAX to KDFW to see the new GSX stuff, everything worked great. Didn't turn my computer on yesterday, and today I went to fly out of KDFW and it wouldn't load the terminals etc, couatl.exe didn't start with the sim (addon manager was working though). This happens from time to time, no big deal, just tried to restart the sim. That didn't work, so I downloaded the addon manager and installed it, now both addon manager and couatl will not start with the sim at all.

I searched around the forums and have tried the numerous suggestions for people who can't get couatl to start like the anti virus etc, that hasn't worked either. It's just dead and won't work. I decided to uninstall ALL of my FSDT and Flightbeam products, restarted, and then reinstalled the FSDT products. I tested it and couatl.exe was working again and the sceneries were loading right. I then installed my FlightBeam products and once again the couatl.exe stopped loading up with the sim and my scenery won't load.

I'm really not sure what it is doing or why. I do know that I get a warning telling me that SFO is out of date and to visit FlightBeam to update, but I don't know if that is causing the issue or not. The exe.xml and dll.xml are both fine as well...

I'm on Windows 10 and P3D v2.5

manfredc3:
Haveing a similar issue here in FSX.

After the latest Cautl update the add-on sceneries are missing te termnal buildings.

All was working fine on Wednesday. Did not fly yesterday, but today, it asked to updaate cautl, and after that KLAS and KDEN are missing te terminal buildings. All default sceneries seem to be unaffected.

manfredc3:
I may have fixed the issue in FSX. After re-installing GSX I was still missin terminals on add-on airports.

So I finally decided to uninstall GSX and the add-on manager one more time and rename the scenery.cfg file. That way FSX would create a new one at startup.

Loaded up FSX, and....... EURECA!! The terminals are back.

So I closed fsx, and re-installed GSX from a fresh download. Rebooted the computer, and fired up FSX.

It did not come with a message that Cautl needed to be updated, and all terminals are still there. The fact that untill I uninstalled GSX for the first time today, the update message popped up with every start of a flight makes me asume that somehow Cautl did not finish the update.

No idea why I didn't think about renewing the scenery file earlier. I wasted several hours trying to figure out what the issue was without having to go to the extreme of doing a complete clean re-install of FSX.

RudiJG1:
I'm having the exact same issue as the OP. Running FSX-SE on Win 7 64 and have enjoyed FSDT products for years with no issues until now.

I am very leery of following advice to rename the scenery.cfg file...if you're going to try the advice in this thread - BACK UP that file first and foremost. I did try this (after backing up the file!) but had no success with any of the issues noted in the first post of this thread.

flynryan692:
I tried the scenery.cfg mentioned and it didn't work for me either.

Navigation

[0] Message Index

[#] Next page