Author Topic: Not using correct .bgl files after update **SOLVED**  (Read 2185 times)

Aviara

  • Newbie
  • *
  • Posts: 2
Not using correct .bgl files after update **SOLVED**
« on: November 11, 2019, 08:19:55 pm »
Hi there,

Yesterday had no issues with GSX, now all of a sudden pretty much every airport (except FlyTampa EHAM for one) is using the P3D default bgl file for the airport (the one that can't be deactivated). And I think I have found the problem. The files according to the log cannot be found, because it's searching one "scenery" folder too much. Is there anyway I can force GSX to not go "too far"?

................
  IGNORING "E:\Simulator\FlyTampa\Libraries\Scenery\scenery" (layer 186): directory not found
  using "E:\Simulator\FlyTampa\Toronto\scenery_LC\scenery" (layer 187)
  IGNORING "E:\Simulator\FlyTampa\Toronto\scenery\scenery" (layer 188): directory not found
  IGNORING "E:\Simulator\FlyTampa\StBartholomew\scenery\scenery" (layer 189): directory not found
  IGNORING "E:\Simulator\FlyTampa\Saba\scenery\scenery" (layer 190): directory not found
  IGNORING "E:\Simulator\FlyTampa\StMaarten\scenery\scenery" (layer 191): directory not found
  IGNORING "E:\Simulator\FlyTampa\Montreal\scenery\scenery" (layer 192): directory not found
  using "E:\Simulator\FlyTampa\KaiTak\scenery_LC\scenery" (layer 193)
  IGNORING "E:\Simulator\FlyTampa\KaiTak\scenery\scenery" (layer 194): directory not found
  IGNORING "E:\Simulator\FlyTampa\Boston\scenery\scenery" (layer 195): directory not found
  IGNORING "E:\Simulator\FlyTampa\Vienna\scenery\scenery" (layer 196): directory not found
  IGNORING "E:\Simulator\FlyTampa\LasVegas\scenery\scenery" (layer 197): directory not found
  IGNORING "E:\Simulator\Flightbeam\Flightbeam - KPDX\scenery\scenery" (layer 198): directory not found
  IGNORING "E:\Simulator\Flightbeam\Flightbeam - KSFOHD\scenery\scenery" (layer 199): directory not found
  IGNORING "E:\Simulator\Flightbeam\Flightbeam - KDEN\scenery\scenery" (layer 200): directory not found
  IGNORING "E:\Simulator\Flightbeam\Flightbeam - KMSP\scenery\scenery" (layer 201): directory not found
  IGNORING "E:\Simulator\Flightbeam\Flightbeam - KIAD\scenery\scenery" (layer 202): directory not found
  IGNORING "E:\Simulator\Flightbeam\Flightbeam - NZWN\scenery\scenery" (layer 203): directory not found
  IGNORING "E:\Simulator\Flightbeam\Flightbeam - SEQM\scenery\scenery" (layer 204): directory not found
  IGNORING "E:\Simulator\Flightbeam\Flightbeam - KPHX\scenery\scenery" (layer 205): directory not found
.................

Obviously e.g. Flightbeam - KPHX\scenery is where the AFCAD it located not scenery\scenery.

Best Regards,

Amadeo
« Last Edit: November 12, 2019, 01:58:25 am by virtuali »

Bill721

  • Newbie
  • *
  • Posts: 44
Re: Not using correct .bgl files after update
« Reply #1 on: November 11, 2019, 08:56:01 pm »
This sounds similar to the issue I'm having.  After updating GSX I've lost all of the FSDT KMEM Memphis scenery.  Where did you go to see the error log?

skyrat77

  • Newbie
  • *
  • Posts: 17
Re: Not using correct .bgl files after update
« Reply #2 on: November 11, 2019, 09:55:48 pm »
I can report the same problem at all my add-on airports (FlightBeam/FlyTampa).
IGNORING "P:\P3Dv4.2\FlyTampa\Libraries\Scenery\scenery" (layer 141): directory not found
  IGNORING "P:\P3Dv4.2\FlyTampa\Montreal\scenery\scenery" (layer 142): directory not found
  IGNORING "P:\P3Dv4.2\FlyTampa\StMaarten\scenery\scenery" (layer 143): directory not found
  using "P:\P3Dv4.2\FlyTampa\Toronto\scenery_LC\scenery" (layer 144)
  IGNORING "P:\P3Dv4.2\FlyTampa\Toronto\scenery\scenery" (layer 145): directory not found
  IGNORING "P:\P3Dv4.2\FlyTampa\Boston\scenery\scenery" (layer 146): directory not found
  IGNORING "P:\P3Dv4.2\FlyTampa\LasVegas\scenery\scenery" (layer 147): directory not found
  IGNORING "P:\P3Dv4.2\Flightbeam\Flightbeam - KSFOHD\scenery\scenery" (layer 148): directory not found
  IGNORING "P:\P3Dv4.2\Flightbeam\Flightbeam - KDEN\scenery\scenery" (layer 149): directory not found
  IGNORING "P:\P3Dv4.2\Flightbeam\Flightbeam - KMSP\scenery\scenery" (layer 150): directory not found
  using "P:\P3Dv4.2\LatinVFR\Miami_KMIAv4\scenery" (layer 151)
  using "P:\P3Dv4.2\LatinVFR\San Juan_TJSJ\scenery" (layer 152)
  using "P:\P3Dv4.2\LatinVFR\Key West_KEYW\scenery" (layer 153)
  IGNORING "P:\P3Dv4.2\Flightbeam\Flightbeam - KIAD\scenery\scenery" (layer 154): directory not found
  IGNORING "P:\P3Dv4.2\Flightbeam\Flightbeam - KPHX\scenery\scenery" (layer 155): directory not found
  IGNORING "C:\Addon Manager\FsDreamTeam\Exclude\Scenery\scenery" (layer 156): directory not found
  IGNORING "C:\Addon Manager\FsDreamTeam\KFLL\Scenery\scenery" (layer 157): directory not found
  IGNORING "C:\Addon Manager\FsDreamTeam\PHNL\Scenery\scenery" (layer 158): directory not found
  IGNORING "C:\Addon Manager\FsDreamTeam\KSDF\Scenery\scenery" (layer 159): directory not found
  IGNORING "C:\Addon Manager\FsDreamTeam\KMEM\Scenery\scenery" (layer 160): directory not found
  IGNORING "C:\Addon Manager\FsDreamTeam\KIAH\Scenery\scenery" (layer 161): directory not found
  IGNORING "C:\Addon Manager\FsDreamTeam\KCLT\Scenery\scenery" (layer 162): directory not found
  IGNORING "P:\P3Dv4.2\29Palms\29Palms - Libraries\scenery\scenery" (layer 163): directory not found
  IGNORING "P:\P3Dv4.2\Flightbeam\Flightbeam - KPDX\scenery\scenery" (layer 164): directory not found
  IGNORING "P:\P3Dv4.2\Flightbeam\Flightbeam - SEQM\scenery\scenery" (layer 165): directory not found
« Last Edit: November 11, 2019, 10:08:44 pm by skyrat77 »

Emi

  • Newbie
  • *
  • Posts: 35
Re: Not using correct .bgl files after update
« Reply #3 on: November 11, 2019, 11:24:31 pm »
Same problem here. Any way to revert to an older version?
Best regards,
Emanuel

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51238
    • VIRTUALI Sagl
Re: Not using correct .bgl files after update
« Reply #4 on: November 12, 2019, 01:58:12 am »
Fixed in the current Live Update.

Aviara

  • Newbie
  • *
  • Posts: 2
Re: Not using correct .bgl files after update **SOLVED**
« Reply #5 on: November 12, 2019, 01:18:20 pm »
Works perfectly again. Thanks, much appreciated.