FSDreamTeam forum

Products Support => GSX Support FSX/P3D => Topic started by: Ray Proudfoot on November 26, 2015, 05:11:19 pm

Title: Rare Couatl Error inbound to KSFO
Post by: Ray Proudfoot on November 26, 2015, 05:11:19 pm
Hi Umberto,

Around 6 miles out from KSFO 19L (older FlightBeam package) Couatl crashed on me and generated the following report...


couatl v3.0 (build 3187)
panic log started on Thu Nov 26 15:52:30 2015

problem raised by engine or unspecified addon
{'User Pos': (37.75566731260887, -122.280166655116, 960.413 m, 960.413 m, 210.86017975700324)}
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FlightBeam_KSFO_gen_mid'
{'User Pos': (37.75566731260887, -122.280166655116, 960.413 m, 960.413 m, 210.86017975700324)}
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FlightBeam_KSFO_gen_term'
{'User Pos': (37.75566731260887, -122.280166655116, 960.413 m, 960.413 m, 210.86017975700324)}
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FlightBeam_KSFO_gen_south'
{'User Pos': (37.75566731260887, -122.280166655116, 960.413 m, 960.413 m, 210.86017975700324)}
Restarting persistent timer 'KSFO', timer adjusted'

Any idea what the problem might be? These crashes are pretty rare for me.
Title: Re: Rare Couatl Error inbound to KSFO
Post by: virtuali on November 26, 2015, 06:38:00 pm
Around 6 miles out from KSFO 19L (older FlightBeam package) Couatl crashed on me and generated the following report...

Any idea what the problem might be? These crashes are pretty rare for me.

It seems you simply haven't installed the scenery. Or, some of its files has been corrupted/missing. Reinstalling the scenery should fix this.

I suggest to also reinstall the Stand-Alone Addon Manager (or the full GSX) after KSFO, because the installer of old version hasn't been updated to all the latest updates, so there's a risk that reinstalling it now might downgrade something.
Title: Re: Rare Couatl Error inbound to KSFO
Post by: Ray Proudfoot on November 26, 2015, 06:42:22 pm
Thanks Umberto. I'll do as you suggest.

Might be a coincidence but I did uninstall and reinstall GSX a couple of days ago on separate and unrelated matter.
Title: Re: Rare Couatl Error inbound to KSFO
Post by: tosco92 on March 10, 2016, 12:07:30 pm
This is happening to me, I did what you said but nothing stays the same problem, how do I?
Title: Re: Rare Couatl Error inbound to KSFO
Post by: virtuali on March 10, 2016, 01:46:28 pm
This is happening to me, I did what you said but nothing stays the same problem, how do I?

I can only repeat and confirm what I already said in reply to this: it seems you simply haven't installed the scenery. Or, some of its files has been corrupted/missing. Reinstalling the scenery should fix this.

I suggest to also reinstall the Stand-Alone Addon Manager (or the full GSX) after KSFO, because the installer of old version hasn't been updated to all the latest updates, so there's a risk that reinstalling it now might downgrade something.
Title: Re: Rare Couatl Error inbound to KSFO
Post by: tosco92 on March 10, 2016, 01:47:56 pm
in this way you told me not working
Title: Re: Rare Couatl Error inbound to KSFO
Post by: tosco92 on March 10, 2016, 05:28:23 pm
now it goes to me, but it makes me so:
Scenery.Cfg file error. local scenery directory (flightbeam/KSFO/Scenery) in scenery Area. 211 not found.
Title: Re: Rare Couatl Error inbound to KSFO
Post by: virtuali on March 11, 2016, 09:29:36 am
Scenery.Cfg file error. local scenery directory (flightbeam/KSFO/Scenery) in scenery Area. 211 not found.

That's an FSX message, which of course doesn't have anything to do with GSX or any of our software or Flightbeam, and it simply means you removed the folder without removing the scenery from the Scenery Library, which is something you should *always* do when removing a scenery.

Of course, the proper way to uninstall a scenery, is to run the UNINSTALLER, that (as with any other Windows program out there) can be found in the Windows Control Panel. If you ran the uninstaller, it would have removed *both* the scenery files AND the area entry in the scenery.cfg, so you wouldn't see the error.

Never remove files manually. Uninstaller are there for a reason...