The addon unknown is causing...

[xaevo]

Bought GSX today. Installed, updated, and get the message that "The addon <unknown> is causing the Couatl Scripting Engine to restart".
GSX uninstalled, all folders removed, and reinstalled. Tried downloading the offline update and running that. Still getting that error.

Error log when prompted:


couatl v4.8 (build 4834)
panic log started on Wed Aug 31 20:58:36 2022

problem raised by addon <unknown>
Traceback (most recent call last):
  File ".\GSX\__init__.py", line 525, in <lambda>
  File ".\common\youcontrol.py", line 243, in showMenusWithSameTag
  File ".\common\youcontrol.py", line 84, in showContainer
  File ".\GSX\__init__.py", line 1012, in checkOnGroundState
  File ".\GSX\assistanceServices\__init__.py", line 4058, in aircraftEngaged
  File ".\GSX\__init__.py", line 1548, in checkSimBrief
  File ".\common\simBrief.py", line 112, in __init__
UnboundLocalError: local variable 'icao_airline' referenced before assignment
{'Airport': 'TUPJ', 'User Pos': (18.44558918945787, -64.53794172901037, 5.21213 m, 2.46143 m, 88.8834212301932, 0.021888865157961845, 0.024434609338641167, 0.013089923135709778, 2.553919111633301, 1.0)}




Aircraft: PMDG B738, airport is default, no installed scenery for the airport used. Any advise?

[xaevo]

Full log when trying the GSX button right after sim load attached.

[flybysky]

Same here, after Live Update

Now I'm trying this from another topic http://www.fsdreamteam.com/forum/index.php/topic,26933.0.html

Perhaps this is of interest I tried it with the CRJ 700

Couatl.err.txt attached.

[virtuali]

Run the Update again, please, it's should work now.

[xaevo]

Still getting the same error after running live update.

[virtuali]

The problem is surely fixed, as confirmed here:

https://www.fsdreamteam.com/forum/index.php/topic,27266.msg178671.html#msg178671

Try it again now.

[flybysky]

Yes its fixed...wow this was verry fast thank you verry much...

[MrMarcelA380]

I ran the Updater a few minutes ago.

The instant crash when opening gsx is fixed but the crash still appears if there is no connection to SimBrief and you push "Reload SimBrief".

And, before the update the connection to SimBrief worked perfectly, after the update it says "Can*t connected to SimBrief". Username is entered correctly in the settings.

The last few flights before the update, it worked perfectly. I like the new SimBrief Button to update Passengers during Turnaround, but something is going wrong at the moment

[virtuali]

It seems the flightplan was missing the airline, which we added in this update, I added an extra check to prevent this error in the Live Update now.

[MrMarcelA380]

It seems the flightplan was missing the airline, which we added in this update, I added an extra check to prevent this error in the Live Update now.

ohh I see thank you!, yeah i did not have a airline in for the test flightplan. Now it works, also without updating again.
One thing i noticed while checking this right now: I know from the manual how gsx checks the departure time and ignores the date. This creates a problem:

The departure time is set to 0100 UTC (so at the next day). The current sim time is 1150 UTC. GSX now thinks the Departure time is before the sim time and does not load the flightplan.
(This case is not so likely, atleast not in my time zone, but i wanted to mention it in case it's unknown )

And another question because i could not test it yet: Does gsx save the pax numbers from the SimBrief Flight to use for deboarding. Or does it reload simbrief on arrival at the stand and so can't use the simbrief pax numbers because the current airport (destination) does not match the departure airport in the current SimBriefPlan for the Flight (because it searches for plan with the current airport as departure)?

[virtuali]

The departure time is set to 0100 UTC (so at the next day). The current sim time is 1150 UTC. GSX now thinks the Departure time is before the sim time and does not load the flightplan.

good question, I'll have to look into it.

And another question because i could not test it yet: Does gsx save the pax numbers from the SimBrief Flight to use for deboarding.

Yes, they are saved, because SimBrief is treated as if a 3rd party airplane set the pax number and, if a 3rd party airplane already set the pax number, SimBrief won't be used. Which means, the SimBrief on departure, by acting like a a 3rd party airplane to set the pax number, is preventing the SimBrief on arrival to reset it.

[MrMarcelA380]

ok thank you very much.
I had no major problems in my flights the last few days with the PMDG 738 since the post release updates. The SimBriefRefresh is a great addition for flying more than one leg! That was one of the few things i was missing. So thanks for your work!

[trisho0]

GSX Pro updated a few minutes ago. I have the same problem after requesting Boarding with AA. Reporting this issue with Logs.

Patricio Valdes

[Keirtt]

Having the same issue. Log attached. I've updated multiple times in the last few minutes.

[theersink]

Same issue here. Using Skywest and CRJ-900. Log attached.

Updated multiple times and always same error.

Reloaded old full installer and issue is gone.