FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: piperpilot99 on April 17, 2025, 12:07:17 am
-
GSX is currently unusable in MSFS2020.
Whenever I try to initiate a pax load or pushback, the Couatl restart message appears asking me to restart Couatl. I then get stuck in a loop of attempting to restart Couatl.
So far, this has happened on the Ini A350, FBW A380, Ini A320NEO and Fenix A320 irrespective of the airport.
GSX version 3.4.6 and latest versions of all the airlines mentioned above.
-
Same here. Hello, Umberto, Virtualli!!! Resolve!
-
As explained so many times, sending a screenshot of the dialog that says there has been an error, it's completely useless, because we KNOW how that window looks like. The reason why the error window suggest to open the error log to see what's the error is about, is precisely so you can post the actual error, not the window!
-
Same issue.
couatl v5.0 (build 5622)
panic log started on Thu Apr 17 15:15:49 2025
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\GSX\assistanceServices\__init__.py", line 4081, in willMaterialize
File ".\common\criticalsection.py", line 23, in _synchronized
File ".\GSX\assistanceServices\baggageLoader.py", line 138, in materialize
File ".\common\criticalsection.py", line 23, in _synchronized
File ".\GSX\assistanceServices\cargoLoader.py", line 80, in materialize
AssertionError
{'Airport': 'LFPG', 'User Pos': (48.999200319671935, 2.5660033819836845, 109.44 m, 4.22542 m, 84.75142276533687, 0.007809159380676672, 0.007853982038795948, -4.508144566986266e-05, 4.129735134887696, 1.0)}
-
Please don't post the same identical message in two places, I already replied to you in another thread. This line clearly indicates you don't have the latest version, because this bug has been fixed several updates ago. Run the FSDT Installer and, if the problem doesn't go away because your local cloudflare node is outdated, download and install the OFFLINE Installer linked in the Sticky thread of this forum.
-
Hello:
I have followed your instructions. I have run both the on-line and off-line updater and GSX still crashes.
couatl v5.0 (build 5622)
panic log started on Fri Apr 25 08:57:36 2025
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\GSX\assistanceServices\__init__.py", line 4081, in willMaterialize
File ".\common\criticalsection.py", line 23, in _synchronized
File ".\GSX\assistanceServices\baggageLoader.py", line 138, in materialize
File ".\common\criticalsection.py", line 23, in _synchronized
File ".\GSX\assistanceServices\cargoLoader.py", line 80, in materialize
AssertionError
{'Airport': 'RKSI', 'User Pos': (37.44998578128913, 126.44298339872786, 11.3629 m, 4.22783 m, 82.02259065394831, 0.007634722379717159, 0.007853982038795948, 4.682934991867867e-05, 4.129735134887696, 1.0)}
-
Hi, I'm having the same issue as the others. My log looks the exact same as what Dreamflight posted, with an AssertionError following the materialising of the cargo loader in line 80. I can provide a copy if needed. Conditions for causing the crash are the same too, it happens no matter what aircraft or airport I'm in, nor whether I have a profile for either installed or not. Selecting the service in the air or on the ground also makes no difference.
I followed the recommendations provided (running the FSDT Installer first, then the offline installer) with no luck.
-
Any information on this? GSX Pro is currentle unusabl with the A350 and PMDG 777.
-
Same issue
Updated FSDT as well
-
this bug has been fixed several updates ago. Run the FSDT Installer and, if the problem doesn't go away because your local cloudflare node is outdated, download and install the OFFLINE Installer linked in the Sticky thread of this forum.
-
I have run both the installer and the offline installer multiple times and am still encountering this error. I have noticed that on initial load all is fine however if I restart GSX/ Couatl then try to load services is when I get the error.
-
I have run both the installer and the offline installer multiple times and am still encountering this error.
I'm sorry but, if you mean exactly THIS error (the one in the only log somebody posted in this thread), I can only repeat and confirm it has been fixed several updates ago and it's not possible you'll have it if you used the Offline installer AFTER a Live Update (assuming your problem was a network issue).
If you still have an error, post your log, because it might be something else.