Couatl keeps Crashing **SOLVED**

[Aang72]

This only started after updating to the latest version.  At first I thought it was only for baggage loading as that would be the only time it was doing it...til today when I skipped the boarding process and just did the JetWay..

This has happened in multiple airports such as KRDM, KBOS, KEWR (Standard) and KSFO (Addon), KJFK (FS Dream Team V2).

I have completely uninstalled and reinstalled GSX and ran the updater several time. During these times, the Anti Virus program I have was compelely disabled.  I am still unsure if I did something somehow.

Meant to mention as well I am using FSX Accleration (gold) version

[Julean]

Me to...After latest update, I ask for the catering truck in SCEL and they and GSX freeze ...
Rest of the sim ok.

All the best

Jens

https://i.imgur.com/wiJdqWJ.jpg

[virtuali]

Me to...After latest update, I ask for the catering truck in SCEL and they and GSX freeze ...

Please clarify exactly what do you mean with "Freeze" and provide with your precise, exact, configuration, the sim used, the airport, if you ust a custom profile or not, etc.

[DjBricheta]

Me to...After latest update, I ask for the catering truck in SCEL and they and GSX freeze ...

Please clarify exactly what do you mean with "Freeze" and provide with your precise, exact, configuration, the sim used, the airport, if you ust a custom profile or not, etc.

Hi there guys, while testing GSX yesterday I also encountered this problem. I assumed it might have been something related to the trial, but since I have bought GSX and the problem is still there.

Simulator: FSX Steam Edition
Airport: Munich(EDDM)
Scenery: not sure if it was default or not
Gate: 121
Aircraft: Default Boeing 737-800
Livery: Custom (Walker Air Transport)

I did some modifications in GSX related to the aircraft, by setting the service doors as 'Doors with no open/close checks' and same with some cargo doors.

I encountered the issue while doing a test of the departure scenario, I had boarding fueling and catering active.

After that I tested an arrival scenario, using a follow me car, and de-boarding, and there were no issues there. The gate for arrival was also different but I can't remember the number. (Not sure if it makes any difference, though)
I also tested a departure scenario on a Cessna Citation X(Alrot) and I didn't have any issues there.

I don't have my log file, but the error log was exactly the same as the one seen in Aang72's attachment. By the name of the file that causes the issue and my tests, it seems that there might be an issue with one of the trucks that are used for the bigger planes, so to say.

Please let me know if you need any information.

[virtuali]

I don't have my log file, but the error log was exactly the same as the one seen in Aang72's attachment.

Please post your log file because, Aang72's log shows he didn't had the latest version of the code, because the error references to a line number that has changed in the version currently online so, please post your log too, to be sure that (assuming you have updated with the FSDT Live Updater), the error still happens, likely with a different line number.

[DjBricheta]

I don't have my log file, but the error log was exactly the same as the one seen in Aang72's attachment.

Please post your log file because, Aang72's log shows he didn't had the latest version of the code, because the error references to a line number that has changed in the version currently online so, please post your log too, to be sure that (assuming you have updated with the FSDT Live Updater), the error still happens, likely with a different line number.

I tried remotely connecting to my PC and testing it, but now it seems that it doesn't reproduce.
I will try again in 2 hours when I can access my PC, and let you know about any updates.

[DjBricheta]

So I got home and booted my PC and before retesting I decided to run Couatl_Updater.exe and Couatl_Updater2.exe, just to be sure I have all the latest data.

Unfortunately, it looks like something went wrong, as now I get an instant error when trying to use any of the services. The error is regarding __init__.py.
I ran both the updaters again after seeing this error, but with no luck.

I have attached the log file here.

Later edit: I tried uninstalling and reinstalling everything, but I still get the same error for now.

Second edit: I posted about the problem above in its dedicated thread. I'll continue testing for this one once the one mentioned above will be resolved.

[SG38]

I have a similar problem.  Any use of GSX at any location terminates Coatll with the _init_py issue.  I use the FLSLab A320.  I hope this can be resolved soon.
Thanks

[virtuali]

You don't have the same problem, your error is different, and it's fixed by running the FSDT Live Update now.

[virtuali]

Second edit: I posted about the problem above in its dedicated thread. I'll continue testing for this one once the one mentioned above will be resolved.

The problem is fixed now, so the thread has been removed, since it might confuse users.

[CraigDubya]

The problem is fixed now, so the thread has been removed, since it might confuse users.

I'm not at my computer right now so can't re-check if Live Updater will fix my issue, but are you saying that you found something wrong with the updater and have now fixed it? Because I was fine until I randomly ran the Live Updater yesterday, and started having the same problem.

[virtuali]

are you saying that you found something wrong with the updater and have now fixed it?

That's exactly what I said, see my previous post:

The problem is fixed now

[CraigDubya]

Not exactly what you said at all really....

It is fixed now (referring to someone's problem dating back to 31st October) is not the same as it has been fixed in the last 24 hours.

In any case, despite the abrupt reply, I have now confirmed that the updater has fixed my problem.

Thank you for a pleasant first contact customer engagement.

[virtuali]

It is fixed now (referring to someone's problem dating back to 31st October) is not the same as it has been fixed in the last 24 hours.

My reply wasn't related to the OP but, instead, I was replying to a post dated Nov 9th, which reported a DIFFERENT error than the one which started this thread which, incidentally, was the same of your error so yes, my reply "it's fixed now" was accurate for THAT specific problem, which was your problem as well.

The OP problem was already fixed before that, but it wasn't your problem.

In any case, despite the abrupt reply, I have now confirmed that the updater has fixed my problem.

Of course it has.

[SG38]

After the update, this time Coatl works again.  Thanks Umberto for the quick response.