Author Topic: Problem with GSX Airport Cache  (Read 6533 times)

pierre789

  • Newbie
  • *
  • Posts: 8
Problem with GSX Airport Cache
« on: April 28, 2014, 02:14:40 pm »
Hi
Every time I load or delete an airport, or any AFCAD file, in FSX, I have the GSX message : "regenerating airport cache", during more than 5'...
I saw in the forum that it wasn't normal, so I suppose there are some corrupted in my installation.
So, here is my last coatl log file :

couatl v2.0 (build 2358)
log started on Mon Apr 28 12:35:39 2014

connecting to SimConnect...
connected to FSX
bglmanx non ready yet, waiting.
connected to bglmanx
Loading addons
requesting AddOn list to bglmanx
bglmanx list contains 20 AddOn(s)
Loading addon OHareX
Addon OHareX not installed or missing one or more files, skipping
Loading addon KDFW
Addon KDFW not installed or missing one or more files, skipping
Loading addon LSGG
Addon LSGG not installed or missing one or more files, skipping
Loading addon GSX
Initializing audio...
Available devices:
  Generic Software on Haut-parleurs (SoundMAX Integrated Digital HD Audio) (47656e6572696320536f667477617265206f6e20486175742d7061726c657572732028536f756e644d415820496e7465677261746564204469676974616c20484420417564696f29)
  Generic Software on Interface SPDIF (SoundMAX Integrated Digital HD Audio) (47656e6572696320536f667477617265206f6e20496e746572666163652053504449462028536f756e644d415820496e7465677261746564204469676974616c20484420417564696f29)
  Generic Software on Sortie numérique (SoundMAX Integrated Digital HD Audio) (47656e6572696320536f667477617265206f6e20536f72746965206e756de972697175652028536f756e644d415820496e7465677261746564204469676974616c20484420417564696f29)
  Haut-parleurs (SoundMAX Integrated Digital HD Audio) (486175742d7061726c657572732028536f756e644d415820496e7465677261746564204469676974616c20484420417564696f29)
  Interface SPDIF (SoundMAX Integrated Digital HD Audio) (496e746572666163652053504449462028536f756e644d415820496e7465677261746564204469676974616c20484420417564696f29)
  Sortie numérique (SoundMAX Integrated Digital HD Audio) (536f72746965206e756de972697175652028536f756e644d415820496e7465677261746564204469676974616c20484420417564696f29)
Detected failed previous attempt to use device 'Haut-parleurs (SoundMAX Integrated Digital HD Audio)', device will be ignored
Created OpenAL device: Generic Software on Haut-parleurs (SoundMAX Integrated Digital HD Audio)

Device info:
   Major version: 1
   Minor version: 1
   Frequency: 44100
   Refresh: 40
   Sync: 0
   Mono sources: 255
   Stereo sources: 1
   Extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_EFX

Context info:
   Vendor: Creative Labs Inc.
   Version: 1.1
   Renderer: Software
   Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX3.0EMULATED EAX4.0EMULATED AL_EXT_OFFSET AL_EXT_LINEAR_DISTANCE AL_EXT_EXPONENT_DISTANCE

Using EFX 1.0 extension, with 1 auxiliary send(s)
Using EAX reverb
Current sim directory is C:/Program Files (x86)/Microsoft Games/Microsoft Flight Simulator X
Looking for scenery.cfg in C:/ProgramData/Microsoft/FSX/scenery.cfg
  using Scenery/World/scenery (layer 1)
  using Scenery/BASE/scenery (layer 2)
  using Scenery/0000/scenery (layer 3)
  using Scenery/0001/scenery (layer 4)
  using Scenery/0002/scenery (layer 5)
  using Scenery/0003/scenery (layer 6)
  using Scenery/0004/scenery (layer 7)
  using Scenery/0005/scenery (layer 8)
  using Scenery/0006/scenery (layer 9)
  using Scenery/0007/scenery (layer 10)
  using Scenery/0100/scenery (layer 11)
  using Scenery/0101/scenery (layer 12)
  using Scenery/0102/scenery (layer 13)
  using Scenery/0103/scenery (layer 14)
  using Scenery/0104/scenery (layer 15)
  using Scenery/0105/scenery (layer 16)
  using Scenery/0106/scenery (layer 17)
  using Scenery/0107/scenery (layer 18)
  using Scenery/0200/scenery (layer 19)
  using Scenery/0201/scenery (layer 20)
  using Scenery/0202/scenery (layer 21)
  using Scenery/0203/scenery (layer 22)
  using Scenery/0204/scenery (layer 23)
  using Scenery/0205/scenery (layer 24)
  using Scenery/0206/scenery (layer 25)
  using Scenery/0207/scenery (layer 26)
  using Scenery/0300/scenery (layer 27)
  using Scenery/0301/scenery (layer 28)
  using Scenery/0302/scenery (layer 29)
  using Scenery/0303/scenery (layer 30)
  using Scenery/0304/scenery (layer 31)
  using Scenery/0305/scenery (layer 32)
  using Scenery/0306/scenery (layer 33)
  using Scenery/0307/scenery (layer 34)
  using Scenery/0400/scenery (layer 35)
  using Scenery/0401/scenery (layer 36)
  using Scenery/0402/scenery (layer 37)
  using Scenery/0403/scenery (layer 38)
  using Scenery/0404/scenery (layer 39)
  using Scenery/0405/scenery (layer 40)
  using Scenery/0406/scenery (layer 41)
  using Scenery/0407/scenery (layer 42)
  using Scenery/0500/scenery (layer 43)
  using Scenery/0501/scenery (layer 44)
  using Scenery/0502/scenery (layer 45)
  using Scenery/0503/scenery (layer 46)
  using Scenery/0504/scenery (layer 47)
  using Scenery/0505/scenery (layer 48)
  using Scenery/0506/scenery (layer 49)
  using Scenery/0507/scenery (layer 50)
  using Scenery/0600/scenery (layer 51)
  using Scenery/0601/scenery (layer 52)
  using Scenery/0602/scenery (layer 53)
  using Scenery/0603/scenery (layer 54)
  using Scenery/0604/scenery (layer 55)
  using Scenery/0605/scenery (layer 56)
  using Scenery/0606/scenery (layer 57)
  using Scenery/0607/scenery (layer 58)
  using Scenery/0700/scenery (layer 59)
  using Scenery/0701/scenery (layer 60)
  using Scenery/0702/scenery (layer 61)
  using Scenery/0703/scenery (layer 62)
  using Scenery/0704/scenery (layer 63)
  using Scenery/0705/scenery (layer 64)
  using Scenery/0706/scenery (layer 65)
  using Scenery/0707/scenery (layer 66)
  using Scenery/0800/scenery (layer 67)
  using Scenery/0801/scenery (layer 68)
  using Scenery/0802/scenery (layer 69)
  using Scenery/0803/scenery (layer 70)
  using Scenery/0804/scenery (layer 71)
  using Scenery/0805/scenery (layer 72)
  using Scenery/0806/scenery (layer 73)
  using Scenery/0807/scenery (layer 74)
  using Scenery/0900/scenery (layer 75)
  using Scenery/0901/scenery (layer 76)
  using Scenery/0902/scenery (layer 77)
  using Scenery/0903/scenery (layer 78)
  using Scenery/0904/scenery (layer 79)
  using Scenery/0905/scenery (layer 80)
  using Scenery/0906/scenery (layer 81)
  using Scenery/0907/scenery (layer 82)
  using Scenery/1000/scenery (layer 83)
  using Scenery/1001/scenery (layer 84)
  using Scenery/1002/scenery (layer 85)
  using Scenery/1003/scenery (layer 86)
  using Scenery/1004/scenery (layer 87)
  using Scenery/1005/scenery (layer 88)
  using Scenery/1006/scenery (layer 89)
  using Scenery/1007/scenery (layer 90)
  using Scenery/1100/scenery (layer 91)
  using Scenery/1101/scenery (layer 92)
  using Scenery/1102/scenery (layer 93)
  using Scenery/1103/scenery (layer 94)
  using Scenery/1104/scenery (layer 95)
  using Scenery/1105/scenery (layer 96)
  using Scenery/1106/scenery (layer 97)
  using Scenery/1107/scenery (layer 98)
  using Scenery/AFRI/scenery (layer 157)
  using Scenery/AUST/scenery (layer 155)
  using Scenery/OCEN/scenery (layer 183)
  using Scenery/Global/scenery (layer 154)
  using Scenery/Props/scenery (layer 101)
  using Addon Scenery/scenery (layer 102)
  using Scenery/SAME/scenery (layer 156)
  using Scenery/NAME/scenery (layer 163)
  using Scenery/ASIA/scenery (layer 158)
  using Scenery/EURE/scenery (layer 159)
  using Scenery/NAMC/scenery (layer 161)
  using Scenery/NAMW/scenery (layer 162)
  using Scenery/UtExcl/scenery (layer 164)
  using Scenery/UtUsaLights/scenery (layer 172)
  using Scenery/UtUsaRoad/scenery (layer 173)
  using Scenery/UtUsaRail/scenery (layer 174)
  using Scenery/UtUsaWater/scenery (layer 175)
  using Scenery/UtUsaGP/scenery (layer 176)
  using Scenery/UtObjRepo/scenery (layer 177)
  using Scenery/UtWc/scenery (layer 178)
  using Scenery/UtLcVeg/scenery (layer 179)
  using Scenery/UtLcCity/scenery (layer 180)
  using Scenery/UtLcCust/scenery (layer 181)
  using Scenery/EURW/scenery (layer 160)
  using ORBX/FTX_NA/FTX_NA_PNW08_CUSTOM/scenery (layer 184)
  using ORBX/FTX_NA/FTX_NA_PNW07_MESH/scenery (layer 185)
  using ORBX/FTX_NA/FTX_NA_PNW06_CVX/scenery (layer 186)
  using ORBX/FTX_NA/FTX_NA_PNW05_SCENERY/scenery (layer 187)
  using MyTraffic/scenery (layer 191)
  using Addon Scenery/Asia mesh/scenery (layer 182)
  using Addon Scenery/N_Zealand_mesh_30m/scenery (layer 194)
  using Addon Scenery/Fiji mesh/scenery (layer 192)
  using Addon Scenery/Australia_Brisb_Sydn_mesh/scenery (layer 193)
  using Addon Scenery/Marshalls_Islands_mesh/scenery (layer 188)
  using Addon Scenery/Micronesia_islands/scenery (layer 189)
  using Addon Scenery/PKMJ Majuro island/scenery (layer 190)
Airport cache not valid: scenery.cfg has changed since last time
Regenerating airport cache, looking for scenery files under C:/Program Files (x86)/Microsoft Games/Microsoft Flight Simulator X/
Worker thread started
Addon GSX loaded
Loading addon HAWAII1
Addon HAWAII1 not installed or missing one or more files, skipping
Loading addon HAWAII2
Addon HAWAII2 not installed or missing one or more files, skipping
Loading addon PHNL
Addon PHNL not installed or missing one or more files, skipping
Loading addon JFK
Addon JFK not installed or missing one or more files, skipping
Loading addon JFK2
Addon JFK2 loaded
Loading addon KFLL
Addon KFLL not installed or missing one or more files, skipping
Loading addon KLAS
Addon KLAS not installed or missing one or more files, skipping
Loading addon KLAX
Addon KLAX loaded
Loading addon ParkMe
Addon ParkMe loaded
Loading addon CYVR
Addon CYVR not installed or missing one or more files, skipping
Loading addon XPOI
Addon XPOI not installed or missing one or more files, skipping
Loading addon ZurichX
Addon ZurichX not installed or missing one or more files, skipping
Loading addon ENBR
Addon ENBR not installed or missing one or more files, skipping
Loading addon KSFO
Addon KSFO not installed or missing one or more files, skipping
Loading addon KPHX
Addon KPHX not installed or missing one or more files, skipping
Loading addon KIAD
Addon KIAD not installed or missing one or more files, skipping
Starting system monitors
Current locale is French_France.1252
SharedMemInterface connected
Loading aircraft data from Airplanes\C172
aircraftDb.py provides aircraft data with priority 2
Using aircraft data from aircraftDb.py
Section [contact_points] contains invalid data at entry point.4
Airport cache regeneration warnings:
Warning: airport LOAN described in multiple BGL files without proper DeleteAirport record
Warning: airport F45 described in multiple BGL files without proper DeleteAirport record
Warning: airport NRC described in multiple BGL files without proper DeleteAirport record
Airport cache regeneration completed with success in 91 seconds
Loading airport KSEA from C:/Program Files (x86)/Microsoft Games/Microsoft Flight Simulator X/MyTraffic/scenery/BR2_KSEA.BGL
Customization file C:\Users\Pierre\AppData\Roaming\Virtuali\GSX\ksea-ealgkw.ini ignored: AFCAD file doesn't match afcad_path entry

There are some warnings, but I don't know where these files are.
Could you help me ?

Thank you

Pierre

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51462
    • VIRTUALI Sagl
Re: Problem with GSX Airport Cache
« Reply #1 on: April 28, 2014, 03:13:07 pm »
Every time I load or delete an airport, or any AFCAD file, in FSX, I have the GSX message : "regenerating airport cache", during more than 5'.. I saw in the forum that it wasn't normal, so I suppose there are some corrupted in my installation So, here is my last coatl log file :

There's nothing corrupted in your installation, if you mean your GSX installation. The problems seems to be caused by some external add-ons:

Quote
Airport cache not valid: scenery.cfg has changed since last time

This might be or not a problem, depending if you REALLY changed your scenery.cfg or not since the last time you ran FSX. If you haven't changed anything ( you haven't installed a new scenery and you haven't changed the Scenery Library in FSX ), and you keep seeing this message in the log file at every startup, it's possible the problem is caused by another add-on product that is constantly changing the scenery.cfg. We heard of some external ATC utilities that do that, because the create modified AFCADs on the fly.

If another add-on is keep changing the scenery.cfg, you WILL have GSX regenerating its cache but, it SHOULD be a very fast process, unless that external add-on is changing LOTS of files.

Quote
Airport cache regeneration warnings:
Warning: airport LOAN described in multiple BGL files without proper DeleteAirport record
Warning: airport F45 described in multiple BGL files without proper DeleteAirport record
Warning: airport NRC described in multiple BGL files without proper DeleteAirport record

These are not serious problems, but are not the cause of the cache regeneration themselves, they only indicate that you have some AFCADs that only "add" to an existing airport, without replacing it. They won't really affect GSX, but if you have GSX not working well at one of those airports, you would have an indication where to look for ( it might be an error by the scenery designer, or it might be made on purpose ), that's why they are labeled as warnings, NOT errors.

Quote
Airport cache regeneration completed with success in 91 seconds

That's a bit too much, so it seems the other add-on that is changing your scenery.cfg, is affecting many files.

Quote
Loading airport KSEA from C:/Program Files (x86)/Microsoft Games/Microsoft Flight Simulator X/MyTraffic/scenery/BR2_KSEA.BGL
Customization file C:\Users\Pierre\AppData\Roaming\Virtuali\GSX\ksea-ealgkw.ini ignored: AFCAD file doesn't match afcad_path entry

This is an entirely different warning, which doesn't have any relationship to your issue. It's simply telling you that the GSX airport customization file you made for KSEA will not be used, because you are now using a different AFCAD compared to the one you used when you made that customization.

This is an indication that you should do one of the following:

1) Restore the original AFCAD you were using when you made that customization, so your customization will work again. This can be done by removing the MyTraffic AFCAD.

OR

2) Create a new customization file for KSEA now, with the AFCAD coming from MyTraffic as the active one

OR

3) Change the pathname in the afcad_path line in your %APPDATA%\Virtuali\GSX\ksea-ealgkw.ini file, to match the MyTraffic AFCAD name. This MIGHT work well or not, depending if the MyTraffic BGL has the same parking names as the original one. Impossible to say without trying, but if it works, it will save you from having to redo your customization from scratch.

OR

4) Do nothing, and just use GSX without any customization at KSEA.

pierre789

  • Newbie
  • *
  • Posts: 8
Re: Problem with GSX Airport Cache
« Reply #2 on: April 28, 2014, 04:20:41 pm »
.. the regenerating doesn't occur every time I load FSX, but only if I have changed an airport.bgl file, or a scenery with some airports.
The problem being that I use to manage the airports sceneries or landscapes, to facilitate the processor work during the flights, and to prevent files of becoming too large, so I frequently add or delete some airports or scenaries when I arrive or leave an area.
When I change a lot of things, I understand that GSX has to regenerate the cache, the problem is that this process is always very long, 4 to 5', even if the change concerns a very small bgl file !
Concerning the KSEA problem, I will look for the best of your solutions.
Many thanks
Pierre

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51462
    • VIRTUALI Sagl
Re: Problem with GSX Airport Cache
« Reply #3 on: April 28, 2014, 06:37:13 pm »
... the regenerating doesn't occur every time I load FSX, but only if I have changed an airport.bgl file, or a scenery with some airports.

That's entirely normal, then.

Quote
The problem being that I use to manage the airports sceneries or landscapes, to facilitate the processor work during the flights, and to prevent files of becoming too large, so I frequently add or delete some airports or scenaries when I arrive or leave an area.

Ok, so it wasn't an external product, it was just you editing the Scenery Library.

Quote
When I change a lot of things, I understand that GSX has to regenerate the cache, the problem is that this process is always very long, 4 to 5', even if the change concerns a very small bgl file !

It's not just GSX that has to regenerate its cache, it's FSX too! You would have had exactly the same problem even if you didn't had GSX. But GSX must first wait for FSX to end regenerating its cache, before it can *start* regenerating its own.

According to your own log, the GSX cache regeneration took exactly 91 seconds so, if it's really 4-5 minutes, then the rest is taken by FSX so, the problem would have been there exactly the same ( minus the 90 seconds taken by GSX ), if there wasn't any GSX to begin with.

Martyjr

  • Full Member
  • ***
  • Posts: 181
Re: Problem with GSX Airport Cache
« Reply #4 on: December 14, 2014, 05:14:47 pm »
I had this also:

Warning: airport LOAN described in multiple BGL files without proper DeleteAirport record
Warning: airport F45 described in multiple BGL files without proper DeleteAirport record
Warning: airport NRC described in multiple BGL files without proper DeleteAirport record

I posted on MyTraffic forum:

MT ver 54c FSX multiple BGL files
 http://forum.simflight.com/topic/78186-mt-ver-54c-fsx-multiple-bgl-files/#entry474208


And it was fixed and there is a zip file to download with the fixed files.
Best Regards,
Vaughan Martell

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51462
    • VIRTUALI Sagl
Re: Problem with GSX Airport Cache
« Reply #5 on: December 14, 2014, 10:11:14 pm »
Warning: airport LOAN described in multiple BGL files without proper DeleteAirport record
Warning: airport F45 described in multiple BGL files without proper DeleteAirport record
Warning: airport NRC described in multiple BGL files without proper DeleteAirport record

And I already replied to you about this message too, see by above reply, it's not a serious error, and it might (or not) be done on purpose by the scenery designer, for example to provide just an enhancement to a default AFCAD.

While this is supported by FSX, GSX requires an AFCAD to be entirely self contained, but since it cannot obviously know if the DeleteAirport records are missing on purpose or are just a bug, it gives you that warning, which won't cause any problems as such, it's just to letting you know that, if you have a problem on an airport, it MIGHT be related to that.

In this case, it seems they were missing because of a bug.

Martyjr

  • Full Member
  • ***
  • Posts: 181
Re: Problem with GSX Airport Cache
« Reply #6 on: December 14, 2014, 10:14:03 pm »
Ok,

Thanks for the additional information.

Have a good day.
Best Regards,
Vaughan Martell