1 Background

This document describes the configuration and usage of the Microsoft Flight Simulator BGL scenery file ‘plug-in’ for Gndmaker. Plug-ins extend the basic functionality of Gndmaker without making changes to the base Gndmaker code. Plug-ins exist as separate code modules and are released as Dynamic Link Libraries (DLL’s).

Currently supported version of Flight Simulator:

FS2000

FS2002, FS2002 Professional

BGL files make up not only the visual aspects of Flight Simulator (runways, etc), but also all the of the ‘hard’ navigation aids (VOR’s, Airports, etc.), but non-physical objects like airways, fixes, etc.

For obvious reasons, BGL data is extremely useful for the virtual Flight Simulator community in the creation of sector files.

**** DUE TO CHANGES TO THE NEWEST MICROSOFT FLIGHT SIMULATOR 2004, AKA ‘CENTURY OF FLIGHT’, BGL IMPORTS ARE NOT CURRENTLY SUPPORTED. THIS WILL BE FIXED IN THE NEAR FUTURE.

Only BGL files from Flight Simulator 2002 or 2002 will work. ****

2 Preparing Data Set

In order to use the BGL plug-in, the user must be aware of where Flight Simulator stores it’s BGL files:

FS2000:

SCENEDB\AFDFILES	Contains facility data (essentially anything you can see it the cockpit GPS window).
SCENEDB\JEPP	Airways and waypoints/fixes.
SCENERY	Main scenery location (do not use)

FS2002:

SCENEDB\AFDFILES	Contains facility data (essentially anything you can see it the cockpit GPS window).
SCENEDB\ATC	Airways and waypoints/fixes.
SCENERY	Main scenery location (do not use)

The type of data that is useful to Gndmaker can be found in the AFDFILES and JEPP/ATC directories mentioned above. It is not recommended to search the generic SCENERY directory since the processing a lot more intensive and does not provide anything that is not already in AFDFILES or JEPP/ATC.

Because relevant BGL data is split into two different locations, the BGL plug-in must perform searches into both locations separately. It is not recommended to simply search for BGL data starting (see the next section) at the FS2000/FS2002 install directory because the search would scan every file in this location (and would take a lot of time).

3 Property Page

Like any Gndmaker plug-in, the configuration of the External Source is done when an individual Search Profile is added to an Import Profile. In the Import Profile Management dialog (Import->Import Profiles), when the ‘Edit’ button is clicked, the External Source Property Page dialog appears:

When ‘BGL is selected from the External Source Type dropdown list and the ‘Options’ button is clicked, the BGL-specific property page is displayed.

The list box describes all the BGL objects that can be imported. The user can select one or more objects to import, or by checking the ‘Select All’ checkbox – select all object types. (Note: currently the user has no choice in configuring specific objects that can be imported – this will be selectable in a later release).

Pre-scan: allows the user pre-search the selected directory looking for BGL files which have the requested objects – discarding those that do not. Pre-scanning significantly speeds up the import process since only applicable files are then loaded.

BGL File drive: pointer this to the root BGL search directory.

Search AFD: Select this for FS2000 when AFD files are to be searched (always select this).

Search Sub-Dirs: Recursively search sub-directories under the specified root BGL directory.

4 Implementation Details

This section discusses some of the implementation details made for this Plug-in.

None at this time.

5 Troubleshooting

To be filled in as needed.

6 Technical Support

6.1 Contacting the Author

Like anything else, I will be happy to help with any questions you may have with Gndmaker, time permitting. I HIGHLY suggest, that you first look at the Gndmaker Forums to see if someone else posted a similar message. If you do not find an answer, post the question there.

And as a last resort, send me an e-mail. I cannot guarantee a quick response, but I will try. Also, note that if you register your copy of Gndmaker, you are much more likely to get a fast response (see Section 7L Contribute to Gndmaker).

6.2 Crashes/Bugs

Like they say, crap happens. If it happens to you, please give me as much information as you can:

If the problem occurs while reading a sector file, be prepared to send me the file.
Any error dialogs that appear. In the case of a crash, the meaningless hexadecimal numbers in a crash dialog are actually of great use to me.
What were you doing at the time? A sequence of documented mouse clicks is helpful for me to duplicate the problem.
What Plug-In were you using? If the error occurs in a Data Import, I will need to know the Bounding Box parameters, the dataset version, if applicable, and how far the import progress completed.

7 Contribute to Gndmaker

As you may have guessed, I do not charge any money for Gndmaker even though I have spent literally THOUSANDS of hours developing it. I consider this a small contribution of my own to the online hobby we all love so much.

But, in reality, Gndmaker is 'POSTWARE' or 'CHARTWARE':

In order to keep me enthusiastic about continuing support for Gndmaker and to provide new, exciting features, I would ask one small favor. If you find Gndmaker useful, PLEASE send me a postcard, or even better, a real-life (paper) navigation chart from your area. Refer to the ‘Contribute!’ link on the Gndmaker website:

http://wirun.homelinux.net/gndmaker

Of course, any monetary, or otherwise, gifts or trinkets will cheerfully be accepted as well. This being a worldwide community, I'm sure people could send me all sorts of cool, inexpensive, stuff from their part of the world ;)

This way I get an indication that my efforts are appreciated and will ensure that Gndmaker has a future.

Those that do 'register' with me will get advance notice of new releases, priority technical support, and a much higher likelihood that I will help out creating sector files for you (if asked)!

Corey MJ Wirun