Author Topic: couatl crash **SOLVED**  (Read 3887 times)

rv08

  • Newbie
  • *
  • Posts: 5
couatl crash **SOLVED**
« on: November 21, 2019, 08:02:32 pm »
Hi,

After updating GSX, couatl stops with this message :

couatl v3.2 (build 4278)
panic log started on Thu Nov 21 19:45:32 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'
{}
Airplane major/minor version: 737 800
[KCLT] P3D V3 Mode objects enabled
[KIAH] jetway in use  FSDT_SODE_JW2
[KMEM] P3D V3 Mode objects enabled
aircraftDb.py provides aircraft data with priority 2
Using aircraft data from aircraftDb.py
Loading airport LCLK from E:\Prepar3D v4 Add-ons\SimMarket\JustSim-LCLK v2.0 P3Dv4\data\scenery\AFX_LCLK.bgl"

I click "YES" to restart couatl and have always the same problem.

Yesterday, everything was running smoothly.

Regards
« Last Edit: November 23, 2019, 02:38:19 am by virtuali »

rv08

  • Newbie
  • *
  • Posts: 5
Re: couatl crash
« Reply #1 on: November 21, 2019, 09:50:23 pm »
I uninstall et reinstall GSX and now I need to reactivate GSX again and again and again !!!

Regards

Yellmmet

  • Newbie
  • *
  • Posts: 1
Re: couatl crash
« Reply #2 on: November 21, 2019, 10:15:29 pm »
I have similar problem - activation is not stored. GSX stays in trial mode. Quite annoying. GSX v 2.8, P3D v 4.5.13.32097 - new install with PMDG 737 & 747 only, EDDF Pro Aerosoft
« Last Edit: November 21, 2019, 10:32:48 pm by Yellmmet »

rv08

  • Newbie
  • *
  • Posts: 5
Re: couatl crash
« Reply #3 on: November 21, 2019, 10:26:52 pm »
And the problem is with ALL the FSDT Airports !! Activation not stored !!

rv08

  • Newbie
  • *
  • Posts: 5
Re: couatl crash
« Reply #4 on: November 21, 2019, 11:30:35 pm »
Hi,

I restarted my computer then run the updater and everything is good to go.

Regards

jlaporte

  • Newbie
  • *
  • Posts: 12
Re: couatl crash
« Reply #5 on: November 22, 2019, 05:00:35 am »
Restarted my computer per the message above and still have the same issue.

I have GSX and GSX2 since the beginning. Never had really any issues. But the update crashed it.

couatl v3.2 (build 4278)
panic log started on Thu Nov 21 20:56:40 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'
{'User Pos': (40.774831254478045, -111.97313411574605, 1290.87 m, 2.48034 m, 354.9700077046147)}
[KCLT] P3D V3 Mode objects enabled
[KSDF] P3D V3 Mode objects enabled
[KCLT] P3D V3 Mode objects enabled
[KIAH] jetway in use  FSDT_SODE_JW2
[KMEM] P3D V3 Mode objects enabled
Loading airport KSLC from D:\Prepar3D v4\PacSim\Salt Lake City Intl P3Dv4\data\scenery\KSLC_ADEX_gm.bgl
Added Menu SubItem "Customize airport positions..." (parentId 82, id 100)
onEnteredAirport KSLC

Dallen1919

  • Newbie
  • *
  • Posts: 22
Re: couatl crash
« Reply #6 on: November 22, 2019, 05:19:44 am »
Same error message after update. No issues yesterday prior to updating today.

krouner

  • Jr. Member
  • **
  • Posts: 64
Re: couatl crash
« Reply #7 on: November 22, 2019, 07:03:05 pm »
I, too, am having the same issue. I uninstalled/reinstalled then restarted computer and ran the updater, still have the same issue.

couatl v3.2 (build 4278)
panic log started on Fri Nov 22 12:00:47 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': 'KSFO', 'User Pos': (37.611785860032896, -122.35844530519647, 5.19839 m, 1.23639 m, 297.8683745196993)}
Using aircraft data from SimConnect

KRouner

rv08

  • Newbie
  • *
  • Posts: 5
Re: couatl crash
« Reply #8 on: November 22, 2019, 09:22:03 pm »
Hi,

Look at the thread in FSDreamTeam forum in General

Quote
   
Re: coualt error log after fsdt update
« Reply #2 on: November 21, 2019, 01:50:29 PM »
   Reply with quoteQuote
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.

I delete this folder before running the updater and it works for me



virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51400
    • VIRTUALI Sagl
Re: couatl crash **SOLVED**
« Reply #9 on: November 23, 2019, 02:41:28 am »
The problem should be solved as explained in this thread:

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

The latest Live Update will now check if it wasn't able to clear that folder automatically by itself, which is usually caused by the antivirus, or having run the Updater when the sim was still running, or was still in the act of closing itself and all its open files, and if this happens, it will give a warning message, prompting to remove the folder manually,