General Category > General Discussion

Couatl.exe issue

<< < (2/3) > >>

virtuali:
If your scenery.cfg is corrupted, because of having hand-edited, it's very likely that Couatl.exe will not start (it's probably crashing).

However, that doesn't mean it's a common cause or a solution that should be tried by everybody. The most common cause it's the antivirus, mistakenly blocking it.

This thread here indicates all known causes for the missing menus (Couatl, Addon Manager, or both)

http://www.fsdreamteam.com/forum/index.php/topic,8428.msg68872.html#msg68872

RudiJG1:
Thanks, Umberto...in my case, the first option in your referenced post worked. Oddly enough, I've never had to be that concerned about my anti-virus program (NOD32 by Eset) interfering with a FSDT installation until now.

All's well here and am enjoying the GSX updates, not to mention the airports. Please bring on KMEM... ;)

flynryan692:
Seems like it has to do with the scenery config, but I am not sure how to fix it.

Earlier when I tried the scenery.cfg I simply renamed the one in the root directory of P3D and nothing changed. However, after some digging around I discovered the scenery.cfg is in C:\ProgramData\Lockheed Martin\Prepar3D v2 and I moved both it and the one in the root directory to my desktop, then started the sim. It rebuilt the scenery config and when I loaded up both addon manager and couatl were running and options in the menu. GSX was working. I didn't have the scenery so I decided to manually add them to the scenery library. After doing so the scenery loaded up but not the terminals and both coutal and addon manager were still options. I restarted the sim thinking that was maybe the last step, but nope back to square one, no addon manager and no coutal.

Suggestions?

I'll tinker with it some more while I wait. I'm not sure what is causing this.

virtuali:

--- Quote from: flynryan692 on September 12, 2015, 11:50:06 pm ---I didn't have the scenery so I decided to manually add them to the scenery library.
--- End quote ---

Which scenery ? Scenery or sceneries ? Have you added just a single area, or you copied a whole block from a previous scenery.cfg ? In this case, you might have simply reintroduced the same problem you had before.

flynryan692:
What I meant was, I loaded up at Las Vegas and did not see the Vegas scenery, it was default, so I readded all of the sceneries in the scenery library.

However, I just redeleted the scenery.cfg and then ran each of my FSDT and Flightbeam installers. Everything seems to be working now. I guess the solution was to delete the scenery.cfg AND reinstall each scenery.

Navigation

[0] Message Index

[#] Next page

[*] Previous page