Problem raised by engine or unspecified addon

[Bombero18]

I was flying with no problems all these last days with my new 787 and the next day after I started my computer again, and loaded FSX this is what happened to me every time I spawn in any FSDT or FlightBeam Airports.


So this is the problem it prompts into my FSX when I spawn in any FSDT airport, or FlightBeam as well.

1-The airport wont load because of this fault
2- Will ask me to restart Couatl engine again
3- If I said yes it goes back to the same "Show me the log of this problem"  and then to the step N°2 again.

If I said no to restart Couatl it wont load the airport at all of course so I got sick of keep trying and its been 2 days like that so I decided to  come here.


For the record, my PC has not make any updates, I have not installed nothing to my FSX after the Quality Wings 787 and I had no problem flying with the 787 every day since the 787 came out.

This is the error log it gives every time I go to an airport that uses Couatl engine.

couatl v3.2 (build 3829)
panic log started on Sat Oct  7 05:06:14 2017

problem raised by engine or unspecified addon
{'Airport': 'KDFW', 'User Pos': (32.879499796493874, -97.03000855631734, 187.037 m, 1.90545 m, 0.25987743721510803)}



Thanks in advance for any kind of support.


Regards,

Mauricio D.R

[Bombero18]

I never understood the problem but I found the fast solution to this...

https://i.imgur.com/ghpMmUY.png

[virtuali]

The problem didn't had anything to do with GSX. It was caused by the missing entry in the FSX.CFG file for the Simobjects paths that are added by our installer to let GSX find its objects.

The line is normally added by our installer but, it might not be there because one of these reasons:

1) Your FSX.CFG had a problem when you originally installed GSX, so the installer couldn't change it.

OR

2)  Another product has corrupted/changed the required lines

OR

3) You reset the FSX.CFG to the defaults, losing the line which was added by our installer.

Running any one of the current FSDT installers (assuming your FSX.CFG was now clean), fixed the problem. There was no need to install more than one of them.

[Bombero18]

Thanks once again for your time Umberto.