FSL A320 COUATL error when turning off seatbelt sign

[AirBorne]

Which triggers GSX for disembarking. A black screen with a message appears.
This error started happening recently, after the latest update, most probably.
If I close the message by selecting to not close COUATL then I have the possibility of disembark my PAX, but I have to select it manually.

[virtuali]

You should post your error details.

[Moritz1992]

Hi,

i have the same issue.

ErrorLoG:
AttributeError: 'Terminate' object has no attribute 'updateAttributeError: 'Terminate' object has no attribute 'update

Any idea?

Cheers
Moritz

[virtuali]

You should post your log without editing it, because it contains meaningful information for us.

[federicoangelino]

Buonasera Umberto,

same error here with FSLabs A321. Having selected the gate as usual upon arrival (already on ground), then when arrived at the selected gate after the message to cut engines, I, as usual, turn off beacon and then seatbelts and GSX instead start deboarding process crashes with the couatl error reported above.
I attach the couatl.err file that probably contains useful informations for you.

Grazie,
Federico

[virtuali]

Your log shows you don't have the latest update installed. Not that this ensure that error will surely go away, but we need to be sure you use the current version to make the log meaningful to us.

[federicoangelino]

I’ve update GSX via the Live Update this morning. Actually it asked me for an update. I think is the 7th June update. This evening when started P3D (v 4.5 HF3) it didn’t asked me for another update. Could it be that the updater didn’t work well for any reason?
Currently flying, will try to update again tomorrow morning and when completed a flight report back.

Grazie,
Federico

[federicoangelino]

Your log shows you don't have the latest update installed. Not that this ensure that error will surely go away, but we need to be sure you use the current version to make the log meaningful to us.

Buongiorno Umberto,

as you suggested yesterday, this morning I did the update, but the error with FSlabs is still there. Actually this morning happened both in LIML at stand 6 (no sode jetway involved in case could it be an issue with sode 1.7.1) and at EGLL at gate 515.

Please find attached pics of the crash together with the log, so you'll be able to check if I actually have the latest version. Again, as other users reported, this happened after the latest update, before everything was working fine.

Sure you'll find a solution

Grazie,
Federico

[virtuali]

We are looking into this. I assume it doesn't happen with another airplane ?

[federicoangelino]

We are looking into this. I assume it doesn't happen with another airplane ?

Unfortunately on my side I can't tell since I only fly FSlabs.
The thing I can tell you, maybe useful for your investigation, is that arriving at the gate without selecting it before arrival, it works without error. Just tried.

[virtuali]

maybe useful for your investigation, is that arriving at the gate without selecting it before arrival, it works without error. Just tried.

Yes, this is very useful to know.

[federicoangelino]

Buongiorno Umberto,

Issue seems to be solved. This morning ran Live updater and it downloaded a marshaller.py file (which was probably the cause of the error, looking at the err log file), and then did a couple of flights one arriving with a VDGS and one with a marshaller. No error on both and everything normal as before.

Will do another couple of flights to test again and then report back.

Grazie,
Federico