Jim Young

Then you will have to go to their website forums and ask for assistance. There is no other solution to this problem. Software developers must have a security system to protect their investments. FSDT and FlightBeam use couatl. Evidently your product was not properly registered.

Most likely not. I've had two or three updates this week alone. In any case, if you do not want to download and install the latest, go to the Menu in P3D and select Addon Manager and then click on Couatl. Once Couatl is open, click on Restart Couatl. If it is not there, then you will have to reinstall the Addon Manager.

There's a possible fix in the AVSIM CTD Guide, page 26 (see link in my signature) where you can download a dotnet repair tool. The tool will try to fix the problem the next time the error occurs. Best regards,

I use the settings in the AVSIM FSX Configuration Guide (see link in my signature). They work great for FSX w/DX 10 Preview enabled. I believe the author of the guide you are referring to went to another website. His guide will not be updated by AVSIM in any case. Best regards,

This error was caused by the security software 'couatl.exe' for FSDT and FlightBeam products. Download the latest Addon Manager from FSDT (download is shown whenever you click on any product) and install. There are changes/updates to their products and most of the time the product is upgraded while you are running your simulator but sometimes, this causes an error and the sim crashes. Best regards,

This error does not pertain to FSX but here is a possible solution - http://www.winhelponline.com/blog/event-id-414-task-misconfiguration-event-log/

Beta testers, posting in the AVSIM Forums, should make everyone aware of your affiliation(s) in your signature so our membership can see where you are coming from when posting. In the past we asked developers to let us know if they are developers so members can see the individuals affiliation when posting. We never did this for beta testers but, ethically and morally, letting our membership know who you represent or work for should be included in your signature. Beta testers should be proud to show they are beta testing products! I have seen a lot of outstanding banners in signatures showing the product with the words "Beta Tester" inside. That's a good idea but I am not asking for everyone to post a banner with the words "beta tester" inscribed, just asking everyone to indicate they are a beta tester for (name of company). That way our members will know, just like we know many members are developers, they are beta testing. Thanks to everyone for your cooperation.

Beta testers, posting in the AVSIM Forums, should make everyone aware of your affiliation(s) in your signature so our membership can see where you are coming from when posting. In the past we asked developers to let us know if they are developers so members can see the individuals affiliation when posting. We never did this for beta testers but, ethically and morally, letting our membership know who you represent or work for should be included in your signature. Beta testers should be proud to show they are beta testing products! I have seen a lot of outstanding banners in signatures showing the product with the words "Beta Tester" inside. That's a good idea but I am not asking for everyone to post a banner with the words "beta tester" inscribed, just asking everyone to indicate they are a beta tester for (name of company). That way our members will know, just like we know many members are developers, they are beta testing. Thanks to everyone for your cooperation.

Digging up old topics is necroposting and not considered appropriate on the Internet (not just this website). I split the topic from the old posts and edited the topic to show a link to "post #3". Also moved the topic to the FS9 Forum.

You'll have to ask Navigraph this question. I do not think that has any affect on the installation as you map it to the location where P3D Navigraph is located. The data is the same for FSX and P3D. Here is the header for my latest Navigraph update: No. If there was then this would have been reported a long time ago. You just have to map your location of the NavData to the proper location on your computer. I recall I had to do this as the NavData was being installed in the same location as yours. Just go into Navigraph and map it properly.

Topic closed. The topic is getting way off topic from the OP.

Welcome! AVSIM has two guides to help you set up FSX. The AVSIM FSX Config Guide and the AVSIM CTD Guide if you have crashes or things go wrong. See the links to the guides in my signature.

I removed my copy of ASN before installing AS16 and have had no problems.

Thanks for your cooperation.

Please post any crashes or errors you are getting in the CTD Forum. The AVSIM CTD Guide provides instructions on properly reporting crashes, errors, and/or freezes. Topic locked.

It is difficult around here is being a volunteer moderator with comments like this. Whatever a moderator does to communicate something they like or dislike, members get upset depending on which way they agree or disagree with a moderator. Please keep your rude comments about any of our moderators to yourself.

Couatl is the security module for FSDT or FlightBeam airports (KSFO HD belongs to FlightBeam). Unfortunately there was a problem with the airport and it was not registered properly (check under Addons>FlightBeam>KSFO HD). Sometimes Couatl loses focus and cannot activate the airport. I have been successful in clicking on the Menu>Addons>Couatl>Restart Couatl to get KSFO reactivated but it appears you were running low on VAS during your landing into KSFO and Couatl did not have the resources to check to see if KSFO HD was registered properly or not. You can go to FSDT Forums and see if there is a solution. Best regards,

I think this topic has been discussed enough here. We need to wait to see what the OP will actually do when released. When it is released, then we will have more information and we can start a new topic. Best regards,

See the AVSIM CTD Guide for some possible solutions. I had this crash once where it would always crash at the same spot. I ran Process Monitor and wrote down the time of the crash. I then looked at the Process Monitor and looked at everything loading at the minute. It was only MyTrafficX. I had loaded an incompatible schedule (believe the 2013 schedule). The AI were trying to fly the routes/flight plans in that schedule and evidently an AI aircraft was not available for the flightplan or the flight plan was corrupt. I downgraded to a previous version and got rid of the 2013 schedule and the problem was fixed.

According to the AVSIM CTD Guide, page 36: Terrain.dll - Usually indicates high scenery/terrain settings, especially Autogen. Restart sim to see if the error reoccurs. Most of the time, the error occurs on a whim.

Most likely you are getting the ai_player.dll or ntdll.dll like I get when I try to shutdown P3D sometimes. Just think something did not shutdown properly when I quit. For me, it is mostly gone and seems to have fixed itself. Best regards,

Esellerate is required software for FSDT. It must remain enabled or your scenery will not work properly - https://fsdreamteam.com/faq.html Best regards,

That was a great video Stephen! All very true!

I suspect the link to the sale is here - http://www.justflight.com/ ?

There have been thousands who have installed this client update without problems or having Windows Defender "whitelisting" the program. You must have your settings in Windows Defender set very high. I have disabled Windows Defender on my system as I use Anti-MalwareBytes to screen for malware. It works very well except it quarantined an iFly dll but at least it told me it had done this and I was able to make sure the program never ever scanned by FSX or P3D Folders as I know exactly everything that is installed in those folders is safe.