Author Topic: GSX making new config files even if one there  (Read 1230 times)

Blu_ee

  • Newbie
  • *
  • Posts: 6
GSX making new config files even if one there
« on: October 12, 2021, 06:55:03 pm »
Hello, GSX keeps on making new config files (AppData\Roaming\Virtuali\GSX folder) even if a current one is there. For example, I download a config file but GSX does not even look over it and makes a new one. it's quite annoying as then jetways won't show and all the data within the ini is not there. Could it be a possibility that I have to add the exact AFCAD file location, pointing it in the directory? Thanks for the help

Blu_ee

  • Newbie
  • *
  • Posts: 6
Re: GSX making new config files even if one there
« Reply #1 on: October 12, 2021, 06:56:31 pm »
Sorry, for context this is P3D V5.2 HF1 and it happens at a lot of airports, I believe at some it works, not 100% sure though

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51237
    • VIRTUALI Sagl
Re: GSX making new config files even if one there
« Reply #2 on: October 12, 2021, 10:07:50 pm »
That's not a bug but, instead, it's a new feature, which is explained at Page 70 of the GSX Manual but briefly, it's done for TWO reasons:

1) Since P3D V5 doesn't support custom textures, if you download a GSX profile made for P3D V4 that uses custom textures and load it in P3D V5, instead of giving you an error (the first release with the new multi-livery support did that ), it will scan the file, and remove all references to custom textures, reverting to default operators at those gates. And, as soon as you EDIT the file, it will save it to a new file, but flagged as being for P3D V5 only. This way, it won't touch your original profile, in case you also use P3D V4, which will load its version instead.

2) Since the default database has changed quite a bit from P3D V4 to V5, in order to prevent malfunctioning profiles due to different gate assignments, if the name of the .BGL starts with APX* ( all default airports have such names ), GSX assumes it's a default airport so, it also set itself in a way that, as soon as you try to edit it, it will save it back as being V5 only, so P3D V4 won't load it, something that in previous versions would have ( the name of the .BGL is the same ), causing problems because of the changing gate assignements.