coualt error log after fsdt update **SOLVED**

[dexter21]

Hi

I ran the updater today, and receive this message when I first load into an airport in P3D (this is from loading into KORD, but it happens at other airports):

couatl v3.2 (build 4278)
panic log started on Thu Nov 21 00:09:35 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': 'KORD', 'User Pos': (41.96907766141874, -87.8838659378971, 205.417 m, 1.81136 m, 269.85980938505475)}

Any help would be much appreciated.  Thanks!

[david roch]

Welcome to the club!
Same here.


couatl v3.2 (build 4278)
panic log started on Thu Nov 21 09:42:51 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': 'LPPT', 'User Pos': (38.770277777743644, -9.130933333334967, 116.499 m, 2.50575 m, 77.32519546594517)}
Added Menu SubItem "Customize airport positions..." (parentId 82, id 99)
onEnteredAirport LPPT

[virtuali]

I cannot reproduce the problem and, it seems to be caused by the updater not being able to clear the airport cache, which is supposed to do automatically ( and it surely does it here... ) after an update.

The most likely cause is antivirus interference, which is preventing the program from removing the folder.

Try to remove it manually, when the simulator is not running, by removing this folder:

C:\ProgramData\Virtuali

And see if the error goes away.

[david roch]

Yes, grazie mille Umberto, it did fix the issue for me and Couatl is back online.
Super support, as usual.

[dexter21]

Thank you very much for the assistance Umberto, things are back to working order.  Do you think I'll have to do this in the future or is this kinda of a fluke?

[contractpilot]

Had a similar problem as detailed in the original message.  Followed Umberto's suggestion and it fixed the problem.  Don't know if it's an antivirus or application problem? As a point of interest I've used Windows Defender on this computer for 2 plus years and this is the first problem.

Paul K
KGYR

[DrJ1]

I too had this same error.   Haven't had a chance to test the fix yet.  Just an FYI. Never had interference from AV before.   Anyway thanks for a quick fix.  Edit:. Fix worked of course

[Claude]

I experienced similar issues Wednesday. P3Dv4 at first loaded correctly and then simply closed without warning if I switched to a FSDT airport. On Thursday (after a computer re-boot), P3D began loading and then switched to a warning screen stating "The addon <unknown> is causing the Couatl Scripting Engine to restart. Please download and install the latest Stand-Alone Addon Manager..." The log offered no obvious clue (and it was not a "panic log" either).

After a bit of research on the forum, I decided to downloaded the current GSX installer, uninstall my existing GSX (Ver 2.6.0) and re install GSX (Ver 2.8.0). So far everything seems okay, however I wish I had a better sense of why the problem occurred (assuming it doesn't return). FYI I'm running P3DV4.5 with Win10 PRO!

[MELKOR]

This happened to me too, and deleting the c:\ProgramData\Virtuali folder solved the issue. This happened right after I ran Live Update, which updated some files.

I'm using Win10 Pro 1909, stock Antivirus. So, I think there's some issue with Live Update, maybe related to 1909 update?

Thanks.

- Bill