Author Topic: the addon unknown is causing couatl scripting engine to restart  (Read 4307 times)

ramoucho

  • Newbie
  • *
  • Posts: 24
the addon unknown is causing couatl scripting engine to restart
« on: January 05, 2024, 03:45:41 pm »
Hello to all,
New to GSX on MSFS.

I just noticed that on parking where push-back is not needed I have this error poping when I click on Prepare for push-back and departure, after the question if push-back is nedded.
Anyone has a clue of what is causing the problem?
Thanks.

guoliao

  • Newbie
  • *
  • Posts: 2
    • pay for assignment
Re: the addon unknown is causing couatl scripting engine to restart
« Reply #1 on: January 08, 2024, 02:23:36 pm »
The error you're experiencing in GSX on MSFS when you click "Prepare for push-back and departure" in a situation where push-back is not needed may be due to a configuration issue or a glitch in the add-on. To resolve it, try updating GSX to the latest version and double-check your aircraft's configuration for push-back.
Make sure to pay for assignment and reads smoothly.

ramoucho

  • Newbie
  • *
  • Posts: 24
Re: the addon unknown is causing couatl scripting engine to restart
« Reply #2 on: January 08, 2024, 05:54:58 pm »
Thanks for Guoliao,
I did update to the latest again.

Also I ran a cople of test. During push-back and departure procedure, I request clearance for departure, system asks me if I need puschback, I say no, and then ask me if I need deicing, if I click no, I get the error. If I click yes, deicing process begin. At the end of the process, I get the error.
I tested it with defaukt A310, Ini A300, and Defautl A320neo.

Do other user departing on a stand where no push-back is needed have this error?


Here is the log:

couatl v4.8 (build 5341)
panic log started on Mon Jan  8 17:36:52 2024

problem raised by addon <unknown>
Traceback (most recent call last):
  File ".\GSX\assistanceServices\__init__.py", line 3426, in pushBackRequested
  File ".\common\fsm.py", line 67, in switchToState
  File ".\GSX\assistanceServices\__init__.py", line 3658, in enter
AttributeError: 'Departure' object has no attribute 'pushBackVehicle'
{'Airport': 'EDDF', 'Requested assistance services at': 'Gate V 175', 'User Pos': (50.03632820685071, 8.538701054281852, 111.545 m, 4.60068 m, 159.4759394556032, -0.000499448855407536, 0.003490658476948738, -0.0012404396713198516, 4.572, 1.0)}
« Last Edit: January 08, 2024, 05:58:13 pm by ramoucho »

paulanders

  • Newbie
  • *
  • Posts: 12
Re: the addon unknown is causing couatl scripting engine to restart
« Reply #3 on: January 09, 2024, 04:06:31 pm »
Yes, I am getting the same issue, when no pushback is needed. Just tried it at LIML where pushback is disabled in the Profile.

  File ".\GSX\assistanceServices\__init__.py", line 3426, in pushBackRequested
  File ".\common\fsm.py", line 67, in switchToState
  File ".\GSX\assistanceServices\__init__.py", line 3658, in enter
AttributeError: 'Departure' object has no attribute 'pushBackVehicle'
{'Airport': 'LIML', 'Requested assistance services at': 'Parking 9', 'User Pos': (45.45674444441704, 9.280683126921824, 109.419 m, 2.46361 m, 90.10037202914329, 0.01839163899421692, 0.024434609338641167, -0.0002704175807281792, 2.553919111633301, 1.0)}

Got the same message from non-pushback stands at LEIB and LEZL too.

I am on the latest version 2.9 and to make sure also used the offline installer.

ramoucho

  • Newbie
  • *
  • Posts: 24
Re: the addon unknown is causing couatl scripting engine to restart
« Reply #4 on: January 10, 2024, 09:24:57 am »
So can we assume this is a kind of a bug?
How can we report it?

paulanders

  • Newbie
  • *
  • Posts: 12
Re: the addon unknown is causing couatl scripting engine to restart
« Reply #5 on: January 11, 2024, 02:25:00 pm »
I have reported and it has been acknowledged and will be fixed in the next update.

ramoucho

  • Newbie
  • *
  • Posts: 24
Re: the addon unknown is causing couatl scripting engine to restart
« Reply #6 on: January 12, 2024, 09:21:34 am »
great, for my culture how do you report?

paulanders

  • Newbie
  • *
  • Posts: 12
Re: the addon unknown is causing couatl scripting engine to restart
« Reply #7 on: January 12, 2024, 06:01:54 pm »
great, for my culture how do you report?

This forum is the usual place. I just encountered the same issue when creating a GSX profile so asked in a creators Discord server. However it seems the issue is now fixed with the latest update released today.  :)
« Last Edit: January 12, 2024, 06:07:51 pm by paulanders »

ramoucho

  • Newbie
  • *
  • Posts: 24
Re: the addon unknown is causing couatl scripting engine to restart
« Reply #8 on: January 16, 2024, 01:58:33 pm »
Thanks m8

gvert

  • Newbie
  • *
  • Posts: 39
Re: the addon unknown is causing couatl scripting engine to restart
« Reply #9 on: January 18, 2024, 08:05:02 am »
great, for my culture how do you report?

This forum is the usual place. I just encountered the same issue when creating a GSX profile so asked in a creators Discord server. However it seems the issue is now fixed with the latest update released today.  :)

Doesn't look like it's fixed... :/

Couatl is constantly crashing on every start now, on version 2.9.1. It's even crashing in the main menu already.

Code: [Select]
couatl v4.8 (build 5341)
panic log started on Thu Jan 18 08:03:20 2024

problem raised by addon __init__.py
Traceback (most recent call last):
  File ".\common\modelCustomization.py", line 1076, in setJetwayAirlineCode
  File ".\common\modelCustomization.py", line 1120, in getModelForCouatlType
  File ".\common\modelCustomization.py", line 1089, in getModelsForCouatlType
  File ".\common\criticalsection.py", line 23, in _synchronized
  File ".\common\modelCustomization.py", line 756, in _cache
  File ".\common\modelCustomization.py", line 729, in fetchDependentPackages
  File ".\python27\json\__init__.py", line 291, in load
  File ".\python27\json\__init__.py", line 339, in loads
  File ".\python27\json\decoder.py", line 364, in decode
  File ".\python27\json\decoder.py", line 380, in raw_decode
UnicodeDecodeError: 'utf8' codec can't decode byte 0xc0 in position 1: invalid start byte
{'User Pos': (48.35694166670856, 11.79705816169235, 452.793 m, 2.83055 m, 83.40062706792669, -1.8359651221544482e-05, 0.004014257341623306, 0.0, 2.7096721046447754, 1.0)}

gvert

  • Newbie
  • *
  • Posts: 39
Re: the addon unknown is causing couatl scripting engine to restart
« Reply #10 on: January 18, 2024, 08:24:03 am »
And now an even more extensive log.

Can't use GSX at all right now unfortunately. Couatl is crashing everytime and instant, without doing anything.

theersink

  • Newbie
  • *
  • Posts: 2
Re: the addon unknown is causing couatl scripting engine to restart
« Reply #11 on: January 18, 2024, 09:21:06 am »
And now an even more extensive log.

Can't use GSX at all right now unfortunately. Couatl is crashing everytime and instant, without doing anything.

I am getting the same issue. Thought it was an addon but it is the one loaded with FSDT KORD so...

balfie_ryr

  • Newbie
  • *
  • Posts: 2
Re: the addon unknown is causing couatl scripting engine to restart
« Reply #12 on: January 18, 2024, 09:30:17 am »
I am having exactly the same issue since yesterday,
I thought it was to do with recent install of Flightbeam KPDX, but just realised it's happening at all airports I had before, watching this thread for any suggestions or updates, COUATL crashing after 30secs 100% of the time at multiple gates at multiple airports in US, Europe and APJ.

Presume something in recent update is the culprit ;-)

Jayteauk

  • Newbie
  • *
  • Posts: 1
Re: the addon unknown is causing couatl scripting engine to restart
« Reply #13 on: January 18, 2024, 09:52:36 am »
I'm also having same issue after update to 2.9.1 last night - every airport, payware, Asobo, etc - Couatl crashes every time  - "unkown addon" error.

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51443
    • VIRTUALI Sagl
Re: the addon unknown is causing couatl scripting engine to restart
« Reply #14 on: January 18, 2024, 09:55:27 am »
Doesn't look like it's fixed...

Because what you are reporting doesn't have anything to do with the error discussed here, which HAS been fixed, of course.

This is something new that has introduced with a new feature we are testing, and yes, of course, it has been fixed as well, you need to run the updater again now, no version change, but it should be fixed.