Author Topic: No AFCAD Path in my Profiles  (Read 1255 times)


  • Newbie
  • *
  • Posts: 1
No AFCAD Path in my Profiles
« on: February 20, 2023, 04:08:36 pm »
Whenever I download profiles, there ist a first line afcad_path = \\?\D:\MSFS\......\.....\xyz.bgl followed by the name of the creator.

If I create Profiles, there is no afcad_path-line. Just my creator-name. The Profile works fine for me - even without the afcad_path-line. But what, if I want to publish such a profile without this line? Will it work for other users?


  • Full Member
  • ***
  • Posts: 186
Re: No AFCAD Path in my Profiles
« Reply #1 on: April 06, 2023, 05:20:49 pm »
I'm pretty sure this all changed with SU 12. But you could post this question in the main forum and maybe get an answer.


  • Full Member
  • ***
  • Posts: 186
Re: No AFCAD Path in my Profiles
« Reply #2 on: April 06, 2023, 09:23:24 pm »
From the Manual

Customization files Priority
GSX follows a general priority rule, which is also valid for all Airplane customization
options that user-made content will always take precedence over internal data or
developer-supplied data. Airport customization are loaded according to the following
priority rules:

• A possible GSX internal customization for a scenery. They usually come with
FSDT airports, but not always, since GSX might come with some specific adjustment
for popular 3rd party sceneries as well. These settings are loaded first, so
they have the lowest priority.

• If an airport scenery comes with its own GSX .INI profile placed in the scenery
own folder, together with the other .BGLs that makes the airport, this file will
take precedence over any GSX internal data, adding to it.

• When users start to modify settings, the GSX .INI profile automatically created
in %APPDATA%\Virtuali\GSX\MSFS will get the highest possible priority, allowing
users to further customize a scenery which was already customized by the
original developer.

The name of the .BGL used to customize the scenery is listed in the [GENERAL]
section of the GSX .INI profile. It will include the complete path valid for your syste
mbut, don’t worry, there’s no need to edit it out before sharing your work, since
GSX will only use the .BGL filename, and will ignore the full path altogether, it
has been designed like this exactly to facilitate sharing of GSX .INI profiles without
worrying about different paths. As long the currently active .BGL matches the
name referenced in the .INI file, the .INI will be loaded by GSX, no matter the path