Hi, I got a constant error when try to open gsx menu in all airports and with all aircrafts (payware too).

The issue is with gsx jetways only that generates crash for coautl and ask me to restart it. But the problem is cycled. I try to update, reinstall from scratch but nothing.

Only happens with gsx jetways, no with default. I have installed SODE 1.8.0

Normally use NGX but with default aircraft is the same.

Thanks in advance

Remove SODE 1.80 and use this link to download and install SODE 1.7.1. SODE 1.8.0 doesn't play well with GSX.

https://www.avsim.com/forums/topic/691040-sode-v171-available-here/

Hi Jerry, first of all thanks so muc.

I've tryed to remove and install 1.7.1 but doesn't solve the matter, even the same error, this is the log:

couatl v5.0 (build 6840)

panic log started on Tue Jul 14 08:35:25 2026

problem raised by addon <unknown>

[00:00:16.968] Traceback (most recent call last):

[00:00:16.968] File ".\common\aircraftData.py", line 6156, in clearCharger_LCD

[00:00:16.968] AttributeError: 'NoneType' object has no attribute 'writeText'

{'Airport': 'LIEE', 'User Pos': (39.25345954850869, 9.057128612049766, 6.36809 m, 2.40609 m, 48.13000796738392, 0.011561084538698196, 0.011344640515744686, 0.0, 2.5511759651184085, 1.0)}

[00:00:16.968] Traceback (most recent call last):

[00:00:16.968] File "<string>", line 49, in OnIdle

[00:00:16.968] File ".\common\aircraftData.py", line 6156, in clearCharger_LCD

[00:00:16.968] AttributeError: 'NoneType' object has no attribute 'writeText'

[00:00:19.203] GSX SimStop

20 hours ago, FXDWG said:

SODE 1.8.0 doesn't play well with GSX.

SODE 1.8.0 works fine with GSX on P3D.

Ok, but what can solve the matter? I have reinstalled and updated 2/3 times without success.

I have gsx base, I ser on my sistem is installed also Level 2 but not activated (ai don't own it), could be this the problem?

1 hour ago, Luke said:

SODE 1.8.0 works fine with GSX on P3D.

It may for you Luke but it never did for me. v1.7.1 does.

@riccardo74 , probably best posting on the FSDT GSX forum.

https://www.fsdreamteam.com/forum/index.php?board=50.0

Hi Ray, sure! I did it and am waiting for a replay. Another user has the same error. I try to ask AI to solve the problem but the unique conclusion is that maybe is necessary an update in python script that cause the conflict. I'm waiting for a response from support team.

@riccardo74 , Umberto hasn’t been present on the forum since 28 June. Probably on holiday. He is the only person providing support.

Hi Riccardo, GSX is updated frequently and some of them break GSX.  I usually like to review what each update fixes or adds before deciding whether to preform the update.  If an update breaks GSX in P3D, the next update usually resolves the problem.  I always back up GSX before updating.

The last time this happened I opened SODE Platform Manager, went to Settings, and set Enable Aircraft State Triggered Auto Docking and Enable AI Traffic Detection to false..  This helped until the issue was fixed.  This may or may not work, but it’s worth the try.

Can you guys tell me how do you back up your GSX installation? , I have not updated mine for about 6 months and everything is working ok but I do see new features still being added for both FSX and P3D which is awesome.

@Dazkent , this is the instruction given to me by @virtuali

robocopy "C:\Source\Folder_Path" "D:\Destination\Backup_Path" /E /MIR

Source folder is C:\Program Files(x86)\AddonManager.

3 hours ago, FXDWG said:

Hi Riccardo, GSX is updated frequently and some of them break GSX.  I usually like to review what each update fixes or adds before deciding whether to preform the update.  If an update breaks GSX in P3D, the next update usually resolves the problem.  I always back up GSX before updating.

The last time this happened I opened SODE Platform Manager, went to Settings, and set Enable Aircraft State Triggered Auto Docking and Enable AI Traffic Detection to false..  This helped until the issue was fixed.  This may or may not work, but it’s worth the try.

Thanks so much, I'll give it a try. If not working I'll waiting for next update and then will backup the working installation.

I meet this problem as soon as I updated my GSX + GSX Lv2 yesterday. However, I solved it at a cost of some compromise.

At the beginning, check the lines in your Couatl.err to make sure we have met the exact same problem as shown below:

File ".\common\aircraftData.py", line 6156, in clearCharger_LCD

Somewhere before and after this line, I found the Coualt addon was trying to load the following items, as shown below in Coualt.err:

[00:00:15.594] Jetway status None, power = (True,2), air = (True,0)

[00:00:15.594] endChargeAircraftBattery()

[00:00:15.594] Requested parking services to (Wherever a gate with jetways)

From my test between default airports and addon airports, this error always occur when my aircraft was within the range of a GSX Lv2 jetway with an External Power Pod, or trying to parking my aircraft into such a gate using GSX guidance.

And my test also showed that any parkings without GSX Lv2 replacement jetways (like a thirdparty scenery with SODE jetways but without specific GSX Lv2 files, default Ctrl J jetways, static jetways) or a ramp won't trigger that error.

When further testing GSX Lv2 replacement jetways, I found that when the external power units were removed, this error won't be triggered either

Thus, I concluded two solutions, both tested by myself and proven successful:

Solution A, Universal solution: find your GSX Control Panel which was automatically generated on your desktop when you installed GSX + GSX LV2, and restore the default jetways, which disabled the GSX LV2 SODE jetways on all default airports.

Solution B, Precision solution: When you load into an airport for the first time, respawn on the runway, navigate to addons→GSX→Airport Customization, click "select all parkings with jetways" on the top left area, click jetway1, uncheck the box of External Power, which would prevent the Couatl Error on the airport you have configured. But you need to repeat the process each time you get into a new airport which you haven't configured yet.

Attached to both solutions, if you have any GSX lv2 configuration files(.ini) by any third party developers for their sceneried, check if there is a line of the following entry inside:

jetway_linkedsimobjectsmask = 14 (or 15)

replace "xx" into:

"13" if you want to keep Air Conditioner Pod.

"12" if you want to remove both pods.

"xx"=14 or 15 would trigger that error.

@DouglasMcCormick

New version now available.

https://fsdreamteam.com/couatl_liveupdate_notes.html

They don't fix all the problems. If anything, they've made them worse. Now FSDT LAX is completely unusable, instead of just ground services not being functional.

What a mess.