• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Flightsim Definitions 101

n4gix

Resource contributor
Messages
11,674
Country
unitedstates
Flightsim Definitions 101:

AFD files: Airport Facilities Data files - this is the file that defines all of the Airport Facilities for a specific airport. In the default sim, these are typically "bundled" into a single .BGL file by Region. Single airport AFD files may be created and placed in the sim's ..\Addon Scenery\scenery folder and will override the default AFD files.

AFCAD: Airport Facilities Computer Asssisted Design - this is the name of a design program used to develop AFD files. This program was designed to be used for FS2002/2004. Many people mistakenly refer to the AFD files as "AFCADs," much the same way "Kleenex" is used to refer to any brand of tissue.

ADE: Airport Design Editor - This is one of the programs developed to create FSX AFD files. As is the case with AFCAD, AFD files placed in the sim's ..\Addon Scenery\scenery folder will override the default AFD files.

Maybe the sim world ought to adopt the name "AFDADEs" to identify the FSX version of the AFD files produced by ADE... :laughing:

EDIT: Updated to reflect the correct nomenclature as "AFD" instead of just "AF".
 
Last edited:
This is always a nice source of confusion indeed :). Maybe we should make some entries in the Wiki for this kind of terms.
 
This is always a nice source of confusion indeed :). Maybe we should make some entries in the Wiki for this kind of terms.

I actually copied this over from another forum where I was attempting to "unconfuse" some few individuals regarding AFCAD and ADE, and the fact that they both produce AF files...

I know that it's like tilting at windmills, but I truly wish AF files weren't referred to as "AFCADs..." :duck:

Which is -of course- why I somewhat tongue-in-cheek suggested that for the sake of clarity, perhaps FSX AF files produced by ADE should henceforth be called "AFADEs" :rotfl:
 
You could call the AF files AFADE's, but what about the people that use AFX or FSX Planner for their AF creations?

David
 
Last edited:
You could call the AF files AFADES, but what about the people that use AFX or FSX Planner for their AF creations?

David


Another reason to just go with a generic "AF" "AirFac" or something similar.

For example, for me, an AFX file is a model's source file produced with FlightShop/Aircraft Factory 99 (AF99), so I end up doing a quick double take and rereading the post so "it makes sense".
 
The ADE beta team spent some happy time discussing this back in the early days and concluded that AFCAD has become like 'Hoover' or 'Kleenex' and that those with an interest would know more or less what such a thing contained. As pointed out there are several tools for FSX to do this work and something is needed that does not use the name, initials or other associations with any of them so AFCAD stuck with us :)

It is also a recognition for Lee that what came after is influenced to a greater or lesser extent by the great work that he did.
 
Which is precisely why I drew the analogy with "Kleenex" in the commentary...

Part of the problem is that too many seem to assume and all "AFCADs" are the same, and wind up confusing FS9 AF files amongst their FSX AF files...

...then wonder why they sometimes have very strange results... :stirthepo
 
Yes, it remains tricky. I made a blog post about this a few years ago already, to make it clear that a AFCAD BGL file was not something magic, but could also just be made with BGLComp. Some people don't seem to know that. And that was even before the release of FSX, which made things even more tricky :).

When I am writing here in the forum I tend to write "BGLComp Airport file" or something similar, but maybe AF BGL file is easier to use.

But I guess we can never change it that some people keep calling all of them AFCADs, then we just have to make sure they know the differences and that they are not magic BGL files :).
 
Generically they are AFD (airport Facilities Data) files :)

So, an AFD file, once compiled, stands independent of the program used to create it?

If so, for years I've been hesitant to download and add "AFCAD" files because I didn't have AFCAD, and having read that AFCAD (the Program) didn't "work" for FS-X, couldn't see downloading a file to be used with a program that didn't work for FS-X.

Hereinafter, I shall call an FS-X Airport Facilities Data file a "scruffy" ... well, maybe not in public.

:D
 
So, an AFD file, once compiled, stands independent of the program used to create it?

If so, for years I've been hesitant to download and add "AFCAD" files because I didn't have AFCAD, and having read that AFCAD (the Program) didn't "work" for FS-X, couldn't see downloading a file to be used with a program that didn't work for FS-X.

Hereinafter, I shall call an FS-X Airport Facilities Data file a "scruffy" ... well, maybe not in public.

:D

Thanks Felix I will remember that ;)

To answer your question you are correct that a well mannered AFD bgl file will be independent of the program that created it.

However in FS9 there was really only AFCAD 2.21 to do this work although SceneGenX also creates airport files and they should be the same once compiled.

In FSX there are two editors (FSX Planner and ADE) that us the Microsoft Bgl compiler to create the files. you can be sure that these are compliant. AFX uses its own compiler (as did AFCAD) and while the bgl files they produce are absolutely fine and work perfectly in FSX they may have elements that do not comply with the SDK. AFCAD is a good example where limitations of the Micrsoft FS9 compiler related some factors are by-passed. AFX is likely to be the same I think. And to be absolutely correct ADE does bypass the compiler in relation to apron edge lighting, color, spacing and intensity.

But generally you are safe to use a bgl file created by any of the utilities.
 
Thanks, Bill, from time to time I try to teach people at the Aerosoft forums that it's actually not called an "AFCAD" but an "AFD" file, but with almost no effect... :rolleyes:
 
Back
Top