FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: chubaka on January 10, 2024, 01:27:02 pm
-
Hi!
Just flew from EDDM to LEAL with FSL A320SL and everything worked as it should. All jetways worked properly, I could see the fuel truck and pople boarding, deboarding and boarding again in LEAL.
Some minutes after t/o from LEAL I received a message, that couatl shut down and if I want to restart it (what never ever worked yet). Had this problem for a few weeks now, before everything was good.
The problem occurs sometime on 1st flight, sometimes on 2nd, but normally inflight...
Updated yesterday with FSDT Update as couatl upater 1 and 2 seemed to not work well.
See the attached panic log (after t/o LEAL somewhere between ALC and BCN):
couatl v4.8 (build 5335)
panic log started on Wed Jan 10 12:27:43 2024
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\common\aircraftData.py", line 82, in update
ImportError: No module named Couatl
{'Airport': 'LEAL', 'Requested assistance services at': 'Gate A 217', 'Requested parking services to': 'Gate 31', 'User Pos': (38.26599885249904, -0.7047455931717083, 1712.52 m, 1629.52 m, 183.9217276617675, -0.21739576756954193, -0.0, 0.43640158577849014, 4.572, 0.0)}
GSX SimStop
Specs:
i9-14900k
RTX4090 24GB
32GB DDR5-5600
P3Dv5.4
Pilot's LEAL
FSLABS
a lot of ORBX
AS P3D
-
Next error. DUS-PMI-DUS. Happend when pushing back in PMI, Gate 52 with FSL A320. Pushing back in DUS@B09.
couatl v4.8 (build 5335)
panic log started on Thu Jan 11 13:29:02 2024
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\common\fsm.py", line 73, in executeDoFuncToCompletion
File ".\GSX\assistanceServices\pushBack.py", line 1095, in do
UnboundLocalError: local variable 'pushBackContact' referenced before assignment
{'Airport': 'LEPA', 'Requested assistance services at': 'Gate B 9', 'Requested parking services to': 'Gate 52', 'User Pos': (39.54999041378625, 2.737235049241403, 11.6804 m, 4.36735 m, 238.5792254317268, 0.001962527632713318, -0.0, -0.0, 4.572, 1.0)}
GSX SimStop
-
So, reinstalled from the scratch and updated via FSDT Installer.
This time FRA-MXP and still in FRA this error occurs
couatl v4.8 (build 5335)
panic log started on Thu Jan 11 19:52:40 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 153', 'User Pos': (50.04147141324214, 8.559624658097347, 115.344 m, 4.39436 m, 159.9900047955173, 0.000930014590267092, -0.0, -0.0, 4.572, 1.0)}
GSX SimStop
FSL A320
Nobody able to give a hint??? Does FSDT have a ticket system?
-
Wow! No feedback yet....
Good work :o :-\
-
Trying again...
GSX still give me the error - more or less the same. Today out off EDDM for EDDH. Again FSLabs, and ORBX etc. Whether I have an a/c profile or let GSX build one. I am frustrated now...
couatl v4.8 (build 5335)
panic log started on Tue Feb 20 12:52:48 2024
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\common\aircraftData.py", line 82, in update
ImportError: No module named Couatl
{'Airport': 'EDDM', 'Requested assistance services at': 'Gate 181', 'User Pos': (48.4658710897538, 11.604309210364956, 2710.1 m, 2233.44 m, 338.75419796451405, -0.08088916540145874, -0.0, -0.0022882535404049062, 4.572, 0.0)}
GSX SimStop
The error "Coautl stopped.." came about 5min after leaving EDDM/26R
What's meant with "no module named Couatl"? I have no Antivirus software despite of Windows own one...
Any help please :(
-
I am really frustrated! GSX is absolutely unusable :(
Thank you for not even viewing this thread...
It is always the "aircraftData.pye" and "No module named Couatl" that crashes GSX (and sometimes P3D). Yes, there must be a relationship: No crashes when GSX is disabled, some crashges when couatl quits mid-flight
-
Thank you for not even viewing this thread...
To be clear, I've read the posts, but as I'm not tech support and don't know what would cause the issue, I haven't responded as it would be pointless. Umberto is usually the one who handles support here, but no clue where he's been the last few weeks.
-
couatl v4.8 (build 5335)
panic log started on Tue Mar 5 08:53:33 2024
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\GSX\assistanceServices\__init__.py", line 2480, in passengersOnBoard
File ".\GSX\assistanceServices\__init__.py", line 1335, in stopEmitters
AttributeError: 'Boarding' object has no attribute 'checkCameraRequest'
{'Airport': 'EDDB', 'Requested assistance services at': 'Gate B 12', 'User Pos': (52.36210506898234, 13.507027700392273, 49.4049 m, 4.38488 m, 68.79999626308208, 0.0004232221399433911, -0.0, -0.00024351921422235756, 4.572, 1.0)}
GSX SimStop
....
-
Could do this all time... :)
couatl v4.8 (build 5335)
panic log started on Tue Mar 5 11:05:58 2024
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\GSX\assistanceServices\__init__.py", line 2480, in passengersOnBoard
File ".\GSX\assistanceServices\__init__.py", line 1335, in stopEmitters
AttributeError: 'Boarding' object has no attribute 'checkCameraRequest'
{'Airport': 'LSZH', 'Requested assistance services at': 'Gate A 11', 'User Pos': (47.45424050881122, 8.557966264375045, 435.985 m, 4.38884 m, 185.91501549370867, 0.002410613000392914, -0.0, -0.00017379025328073477, 4.572, 1.0)}
GSX SimStop
-
couatl v4.8 (build 5335)
panic log started on Tue Mar 5 13:53:41 2024
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\GSX\assistanceServices\__init__.py", line 2480, in passengersOnBoard
File ".\GSX\assistanceServices\__init__.py", line 1335, in stopEmitters
AttributeError: 'Boarding' object has no attribute 'checkCameraRequest'
{'Airport': 'EDDM', 'Requested assistance services at': 'Gate A 213', 'User Pos': (48.354557651006544, 11.792938067144929, 454.393 m, 4.39299 m, 263.36000584359374, 0.0022563417442142963, -0.0, -0.00018687865783467304, 4.572, 1.0)}
GSX SimStop
P3dv5, FSLabs A320
-
See the attached...
-
@virtuali
Here is the log-file from start to crash after boarding passengers. Installed the newest update and reinstalled completely before.
It is quite sad, that not even an info or a feedback comes over :(
Every flight is quite a mess....
-
It has surely to to do with the passengers. When using refueling through the ATSU by GSX and boarding with instant function nothing happens and everythings works out well.
Would be nice to have at least an idea or comment regarding this problem....
-
Would be nice to have at least an idea or comment regarding this problem....
And I still have no idea where Umberto has been.
-
Getting the same error when using FSL A320 at EFHK
Python 2.7.16 Stackless 3.1b3 060516 (default, Mar 9 2019, 21:32:11) [MSC v.1500 64 bit (AMD64)] wxPython 3.0.2.0
couatl v4.8 (build 5335)
Traceback (most recent call last):
File ".\GSX\assistanceServices\__init__.py", line 2480, in passengersOnBoard
File ".\GSX\assistanceServices\__init__.py", line 1335, in stopEmitters
AttributeError: 'Boarding' object has no attribute 'checkCameraRequest'
{'Airport': 'EFHK', 'Requested assistance services at': 'Gate 29', 'Requested parking services to': 'Gate 29', 'User Pos': (60.31842389583445, 24.964599546719796, 58.9629 m, 4.40588 m, 137.46450149426914, 0.0012249659048393369, -0.0, -0.00022176456182090642, 4.572, 1.0)}
GSX SimStop
-
You will get this message on every airport. I found a workaround for now.
Load the fuel via ATSU and GSX, but do not load the passengers via GSX but "instant". After pushback I disable GSX till taxi on the destination airport.
I logged the report file from sim start to GSX crash. The crash occured when the last passenger boarded. Couatl then wants to be restarted...
No answer or idea from Umberto yet :(
But nice to know, that I'm not the only one though...
-
When you posted first, in February, you had an impossible error that seems to indicate a partial install, something nobody ever reported before. Then you stopped posting for several days, and it seems you fixed it.
Because now, from March 5th, after you stopped posting for a while, you have posted a completely different NEW error, and that is of course fixed, as we always fix everything that is reported and can be reproduced.
So, just run the Live Update now.
-
Tried to fix it myself first. And had something to do in the meantime :)
Nevertheless, thank you very much for your quick upload and correction, now!!