Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Strange error at FOOL (Leon M'Ba)

Featured Replies

I have posted the following on the DreamTeam forum, but thought it might get more exposure here.

 

When I try to locate an aircraft at FOOL, the Leon M'Ba airport in Libreville, Gabon, I get the following error message:

 

"The addon <unknown. is causing the Couatl Scripting Engine to restart. Details can be found in C:\Users/Roger\AppData\Roaming\Virtuali\Couatl.err. Please download and install the latest Stand-Alone Addon Manager from http://www.fsdreamteam.com/sa-addon-manger."

 

When I try to access the link for the referenced latest addon manager as instructed, I get an "Internet Explorer cannot display the webpage."

 

The details say: "Windows can't open this file. File: Cousatl.err. To open this file, Windows needs to know what program you want to use to open it. Windows can go online to look it automatically, or you can manually select from a list of programs that are related on your computer." A search gets no results.

 

I have DreamTeam KDFW, KFLL, KJFK, KLAS, KORD, LSGG, LSZH, PHLI, PHTO, and PHNL Airports in FS9 and FSX with no problems. They all load fine and none are anywhere near FOOL.

 

This problem only shows up in FSX. Loading FOOL is no problem in FS9 and it looks as expected.

 

My origin to fly to FOOL is FPST. No problem there. My destination from FOOL was to be FCBB. No problem there either. I can locate my aircraft at either FBST or FCBB with no error. The problem seems to be unique to the FOOL location,and it appears that my addon manager thinks this is a corrupt DreamTeam location for some reason.

 

If anyone has a similar DreamTeam installation, please try locating an aircraft at FOOL in FSX and let me know if you have any problem.

 

This is no biggie as I have never seen this error anywhere else, but I am curious. Now a bit of trivia as to how I got into this scenario. If you are not a glutton for punishment, you may want to ignore the following:

 

I made a spreadsheet and have made flights to all of the USA Capital cities. I then made spreadsheets for all of the Continent Country Capitals. I have completed Europe and Asia. As a hedge against boredom, I go to Wikpedia and read the information about each city before each flight. In my ignorance, I have never heard of many of these places and often have no idea how to pronounce the text. I never realized how many countries are in each Continent, particularly North America which is home territory. I am presently in the middle of the African Continent doing the same thing and ran into this error.

 

For what it is worth, I just tried flying from FPST to FOOL hoping I could sneak into my destination. All went well until I arrived in the area of FOOL and began my ILS approach. About 5 miles DME, I again got my error popup.

 

Also, I cannot close the popup. If I click on close my plane advances for a split second and then the popup continues to reappear indefinitely. I kept clicking on close and my plane advanced each time until I finally reached the ground. There is also no normal way to get rid of the popup totally, or to shut down FSX. The only way to completely close the popup and FSX is to shut down FWX with the task manager.

 

Seems that the problem is unique to a five mile radius of FOOL for some reason.

 

Respectfully: RTH

 

 

I've got the same airports as you (as well as GSX) and I have seen that message once before (though not at FOOL, can't remember where). I don't get any errors at all when loading FSX at FOOL.

 

Hope that helps!

 

James

  • Author

Thanks for the reply James.

 

Glad to know it exists for someone else, but still a mystery.

 

Regards:

RTH

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.