Author Topic: Fatal Error B4278 at KMIA with Panic Log  (Read 2075 times)

downscc

  • Full Member
  • ***
  • Posts: 168
Fatal Error B4278 at KMIA with Panic Log
« on: November 25, 2019, 06:48:06 pm »
Ran FSDT Update today 25Nov, launched P3Dv4.5 with aircraft parked at KMIA H14 and after couatl cache reload I get this:

couatl v3.2 (build 4278)
panic log started on Mon Nov 25 11:44:25 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': 'KMIA', 'User Pos': (25.790247222246887, -80.27603888889193, 4.96186 m, 2.52386 m, 266.86059505047035)}
Added Menu SubItem "Customize airport positions..." (parentId 82, id 102)
onEnteredAirport KMIA


EDIT:  I closed P3D and a few  minutes later launched P3D and selected PMDG NGXu B739ER at LatinVFR KMIA gate H14 and got an error before it even loaded the scenario:


couatl v3.2 (build 4278)
panic log started on Mon Nov 25 12:04:17 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 KMIA from D:\Addon\LatinVFR\KMIA\scenery\KMIA_ADEP4_RGM.bgl
Loading user customizations from C:\Users\I7-6700K\AppData\Roaming\Virtuali/GSX\kmia-y6ih4z.ini

I am unable to use P3D since today's live update.  This is very unusual, I haven't had a problem like this with FSDT for several years.

FINAL EDIT:  Issue resolved.  I found an earlier post (http://www.fsdreamteam.com/forum/index.php/topic,22447.msg151597.html#msg151597) and deleted programdata\virtuali and that resolved the issue.  I've been using the same Windows Defender for years and never had this problem.

I'll know what to look for next time.
« Last Edit: November 25, 2019, 07:18:20 pm by downscc »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51452
    • VIRTUALI Sagl
Re: Fatal Error B4278 at KMIA with Panic Log
« Reply #1 on: November 25, 2019, 11:09:58 pm »
deleted programdata\virtuali and that resolved the issue.  I've been using the same Windows Defender for years and never had this problem.

In addition to the antivirus, another possible reason is that you started the Live Update too quickly after exiting from the sim. If you have many add-ons, this could take a while, even well long after the simulator icon has disappeared from the Task Bar.

If you want to have a feel how much you should wait on your system, open the GSX Control Panel when the simulator is running, and note how much it takes for the "Compile" button to become available. That's when it's really safe to start the Live Update, or restart the sim.

Quote
I'll know what to look for next time.

Following that thread, we already updated the updater that, after it deletes the airport cache, it will check if the folder is still there, and will give a warning, suggesting to remove it manually.

downscc

  • Full Member
  • ***
  • Posts: 168
Re: Fatal Error B4278 at KMIA with Panic Log
« Reply #2 on: November 26, 2019, 05:28:30 pm »
I ran FSDT Live Update after booting up before launching P3D.  I use Process Explorer to note when P3D has left the room and even that isn't a safe bet since I have another application I'm testing that gives a green light when P3D is gone and that takes about 30 sec longer than what is indicated with Process Explorer.  I'm well aware of this delay time.  Regardless, P3D had not been launched yet.

I appreciate the function that verifies the deletion and warning.  Don't trust the environment.