Author Topic: Update Nov 29 - FATAL ERROR **SOLVED**  (Read 3057 times)

Rickinferno

  • Newbie
  • *
  • Posts: 2
Update Nov 29 - FATAL ERROR **SOLVED**
« on: November 27, 2019, 01:07:56 pm »
Hey there,

I have been getting this error when loading my aircraft at any airports within P3dV4.5!  Trying to figure what would be causing this?

couatl v3.2 (build 4278)
panic log started on Wed Nov 27 06:54:15 2019

problem raised by addon <unknown>
Traceback (most recent call last):
  File ".\common\modelCustomization.py", line 618, in setJetwayAirlineCode
  File ".\common\modelCustomization.py", line 662, in getModelForCouatlType
  File ".\common\modelCustomization.py", line 631, in getModelsForCouatlType
  File ".\common\criticalsection.py", line 23, in _synchronized
  File ".\common\modelCustomization.py", line 448, in _cache
  File ".\python27\shelve.py", line 121, in __getitem__
  File ".\python27\dumbdbm.py", line 122, in __getitem__
KeyError: 'baseColors'
{'Airport': 'CYUL', 'User Pos': (45.47412324198063, -73.71470684329306, 37.7774 m, 1.81138 m, 41.77146901348828)}
onEnteredAirport CYUL

Thanks for your help
« Last Edit: November 29, 2019, 12:14:10 pm by virtuali »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51400
    • VIRTUALI Sagl
Re: Update Nov 29 - FATAL ERROR **SOLVED**
« Reply #1 on: November 27, 2019, 05:28:45 pm »
Already discussed here:

http://www.fsdreamteam.com/forum/index.php/topic,22447.msg151597.html#msg151597

and here:

http://www.fsdreamteam.com/forum/index.php/topic,22492.msg151897.html#msg151897

Have you ran the latest Live Updater ? It's supposed to give you a warning, in case it cannot clear the airport cache (which is supposed to do it automatically), suggesting to remove it manually.

Rickinferno

  • Newbie
  • *
  • Posts: 2
Re: Update Nov 29 - FATAL ERROR **SOLVED**
« Reply #2 on: November 28, 2019, 12:57:44 am »
Thanks for the links and it worked on my side also :)

MELKOR

  • Newbie
  • *
  • Posts: 49
Re: Update Nov 29 - FATAL ERROR **SOLVED**
« Reply #3 on: November 29, 2019, 07:17:39 am »
See the attached screenshot. When I look in couatl.log, I see the following:

Traceback (most recent call last):
  File ".\GSX\assistanceServices\__init__.py", line 3166, in willMaterialize
  File ".\common\criticalsection.py", line 23, in _synchronized
  File ".\GSX\assistanceServices\baggageTrain.py", line 246, in materialize
  File ".\common\criticalsection.py", line 23, in _synchronized
  File ".\GSX\assistanceServices\baggageTrain.py", line 72, in materialize
  File ".\GSX\assistanceServices\baggageTrain.py", line 532, in makeTrain
TypeError: unsupported operand type(s) for //: 'NoneType' and 'int'
{'Airport': 'KLAX', 'Requested assistance services at': 'Terminal 1|Gate 13  (FSX Name=Gate 13)', 'User Pos': (33.9471814420962, -118.40080926965149, 40.9867 m, 2.50273 m, 263.0000051302268)}

This is after a recent update using Live Update. I've also tried clearing c:\ProgramData\Virtuali, but this did not help.

Thanks.

- Bill


bpcw001

  • Newbie
  • *
  • Posts: 17
Re: Update Nov 29 - FATAL ERROR **SOLVED**
« Reply #4 on: November 29, 2019, 10:40:34 am »
Hi, I did a live update this morning (Nov. 29). Since that, I get on every airport:


couatl v3.2 (build 4278)
panic log started on Fri Nov 29 10:30:47 2019

problem raised by addon <unknown>
Traceback (most recent call last):
  File ".\GSX\assistanceServices\__init__.py", line 3166, in willMaterialize
  File ".\common\criticalsection.py", line 23, in _synchronized
  File ".\GSX\assistanceServices\baggageTrain.py", line 246, in materialize
  File ".\common\criticalsection.py", line 23, in _synchronized
  File ".\GSX\assistanceServices\baggageTrain.py", line 72, in materialize
  File ".\GSX\assistanceServices\baggageTrain.py", line 557, in makeTrain
TypeError: unsupported operand type(s) for //: 'NoneType' and 'int'
{'Airport': 'EIDW', 'Requested assistance services at': 'Gate 314', 'User Pos': (53.42570226224483, -6.246795709247921, 78.2154 m, 4.45445 m, 70.7672632170029)}
Number of passengers provided by airplane addon =  20

What I tried, so far with no success:

- remove C:\ProgramData\Virtuali
- competely de-install GSX and re-install with the latest installer downloaded from FSDT website

Diagnostic log is attached.

« Last Edit: November 29, 2019, 10:43:39 am by bpcw001 »

mpanis

  • Newbie
  • *
  • Posts: 5
Re: Update Nov 29 - FATAL ERROR **SOLVED**
« Reply #5 on: November 29, 2019, 11:30:45 am »
Hello

I have just encountered the following error in Aerosoft Zurich Professional airport along with Aerosoft Airbus Professional v1.2.5 which never occurred before until i run the FSDT updater today. I double checked with other aircraft and in other airports too and the same error occurs, therefore it has to do something with the latest GSX update. Below you will find the error and also attached the relevant file and error print screen.

couatl v3.2 (build 4278)
panic log started on Fri Nov 29 12:10:38 2019

problem raised by addon <unknown>
Traceback (most recent call last):
  File ".\GSX\assistanceServices\__init__.py", line 3166, in willMaterialize
  File ".\common\criticalsection.py", line 23, in _synchronized
  File ".\GSX\assistanceServices\baggageTrain.py", line 246, in materialize
  File ".\common\criticalsection.py", line 23, in _synchronized
  File ".\GSX\assistanceServices\baggageTrain.py", line 72, in materialize
  File ".\GSX\assistanceServices\baggageTrain.py", line 532, in makeTrain
TypeError: unsupported operand type(s) for //: 'NoneType' and 'int'
{'Airport': 'LSZH', 'Requested assistance services at': 'Gate A 5', 'User Pos': (47.45411725603557, 8.56064188311913, 436.134 m, 4.53749 m, 186.18401611644404)}

I already deleted the Virtuali folder in ProgramData as seen in other posts and still the same happens.

I would appreciate some assistance with this issue

Thank you in advance
George
« Last Edit: November 29, 2019, 12:12:29 pm by virtuali »

Julz8585

  • Newbie
  • *
  • Posts: 3
Re: Update Nov 29 - FATAL ERROR **SOLVED**
« Reply #6 on: November 29, 2019, 11:36:56 am »
Hi, I have the same problem since the latest update.

Aersoft Heathrow, GSX actions triggered by FSLabs.



Code: [Select]
couatl v3.2 (build 4278)
panic log started on Fri Nov 29 11:28:58 2019
problem raised by addon <unknown>
Traceback (most recent call last):
  File ".\GSX\assistanceServices\__init__.py", line 3166, in willMaterialize
  File ".\common\criticalsection.py", line 23, in _synchronized
  File ".\GSX\assistanceServices\baggageTrain.py", line 246, in materialize
  File ".\common\criticalsection.py", line 23, in _synchronized
  File ".\GSX\assistanceServices\baggageTrain.py", line 72, in materialize
  File ".\GSX\assistanceServices\baggageTrain.py", line 532, in makeTrain
TypeError: unsupported operand type(s) for //: 'NoneType' and 'int'
{'Airport': 'EGLL', 'Requested assistance services at': 'Gate 505', 'User Pos': (51.47405280217546, -0.48758459436553714, 29.7524 m, 4.45438 m, 179.5796132851515)}
Number of passengers provided by airplane addon =  20

Kind Regards...

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51400
    • VIRTUALI Sagl
Re: Update Nov 29 - FATAL ERROR **SOLVED**
« Reply #7 on: November 29, 2019, 12:12:22 pm »
Fixed by running the Live Update now. We made a change to fix a bug reported by another user in the passenger count, but if you go straight to departure, it didn't work.

We reverted to the previous version in the update, to have more time to test the other fix.

SN737

  • Full Member
  • ***
  • Posts: 134
Re: Update Nov 29 - FATAL ERROR **SOLVED**
« Reply #8 on: November 29, 2019, 11:04:22 pm »
what a disaster of an update man, never had so many errors with a version, flew 2 legs and couldn't use gsx at all.
Yes i know "run the live update", but all immersion thrown away by those nasty error windows

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51400
    • VIRTUALI Sagl
Re: Update Nov 29 - FATAL ERROR **SOLVED**
« Reply #9 on: November 29, 2019, 11:59:45 pm »
what a disaster of an update man, never had so many errors with a version, flew 2 legs and couldn't
 se gsx at all. Yes i know "run the live update", but all immersion thrown away by those nasty error windows

"So many errors" ? There was just ONE error, which happened only in ONE case (when you went straight to pushback without calling any other services first), and it has been obviously fixed immediately, as usual.

Sorry for trying to make improvements suggested by other users as soon as possible.