What is the Flight Simulator 2004 SDK, and how do I use it?

The Flight Simulator 2004 SDK is Microsoft’s collection of documentation, compilers and authoring tools for creating FS2004 aircraft, scenery, terrain, panels, effects and AI traffic. It is not one program: install the kit for your project, prepare its source files, compile or export them where required, then test the output in FS2004 (FS9).

SDK means Software Development Kit. You do not need it to install an ordinary add-on; it is intended for creating, compiling and debugging add-on content. Some projects use a compiler, while panels, effects and aircraft configuration work may consist mainly of documented text files and assets.

Which FS2004 SDK kit should I use?

Choose the SDK component according to the file you need FS2004 to load; installing every kit does not create a project automatically.

BGLComp turns correctly structured XML source into scenery BGL files. MakeMDL exports models from the supported gmax toolchain. The traffic and terrain kits have their own inputs and build procedures, so a command copied from one kit rarely applies to another.

How do I use the FS2004 SDK?

The safest workflow is to compile an unchanged SDK sample first, then alter one part at a time.

1. Define the output. Decide whether FS2004 needs a BGL, an MDL, a traffic database or a set of configuration files. This identifies the relevant kit and avoids installing unrelated tools.
2. Install the appropriate kit. Our complete FS2004 SDK bundle and documentation provides the individual development components in one package. Extract tools to a short, writable path such as C:\FS9SDK, keeping each compiler with its supporting files and examples.
3. Create a separate working folder. Use folders such as Source, Build and Package outside the FS2004 installation. This prevents a failed build or clean-up operation from damaging the simulator.
4. Build the supplied sample. Copy the example closest to your project and compile it without changes. If that fails, fix the toolchain before editing coordinates, model references or schedules.
5. Edit and compile the source. BGLComp is normally run from a command prompt or batch file so its XML errors remain visible. A gmax model must be opened with the FS2004 gamepack and exported through the MakeMDL toolchain. Read the kit’s own documentation for terrain and traffic command formats.
6. Package the output correctly. Scenery BGL files normally go in an active folder such as Addon Scenery\ProjectName\scenery, with textures in the adjacent texture folder. A complete aircraft belongs under Aircraft\ProjectName and needs its configuration, model, panel, sound and texture structure—not just an MDL. Our FS2004 add-on installation and folder guide explains the package layouts.
7. Activate and test it. Add a new scenery area through the FS2004 Scenery Library when necessary, restart the simulator, and test near the project’s coordinates. Change one item per build so an error can be traced to a specific edit.
8. Keep the source and package separate. Distribute the compiled output and the assets you have permission to share. Do not bundle Microsoft’s SDK tools with an add-on, and do not assume a compiled BGL or MDL can later be converted back into editable source.

Why does my SDK project not appear in FS2004?

Most missing projects are caused by a failed compile, an incorrect package structure or an output file that FS2004 has not loaded.

• The compiler window closes immediately: many SDK utilities are command-line programs. Run the tool from a command prompt or batch file so you can read the error rather than double-clicking its executable.
• No BGL is produced: check the compiler’s first XML or schema error, confirm the file is not accidentally named project.xml.txt, and make sure the output folder is writable. One malformed entry can stop the entire build.
• The BGL exists but nothing appears: confirm the scenery area is active, check latitude and longitude signs, verify referenced library objects are installed, and restart FS2004. Reloading only the flight may not reload changed scenery.
• The model is white or partly missing: check texture names, supported FS2004 texture formats, material assignments and the package’s texture folder. Models exported for FSX, Prepar3D or newer Microsoft Flight Simulator versions are not automatically FS2004-compatible.
• An MDL does not appear in the aircraft menu: an MDL alone is not an aircraft. FS2004 also needs a valid aircraft.cfg, the correct model.cfg reference and the expected aircraft folder structure.
• The gmax exporter is absent: confirm that the FS2004 gamepack and MakeMDL components are installed where their documentation expects them. Starting a generic gmax configuration may not load the FS2004 exporter.
• AI traffic is missing: verify that schedule entries use the exact aircraft title defined in aircraft.cfg, that the traffic database compiled successfully, and that the simulator’s AI traffic setting is above zero.

Can the FS2004 SDK run on modern Windows?

Many FS2004 SDK command-line tools can run on modern Windows, but the older modelling and exporter components are more sensitive to paths, permissions and legacy dependencies.

• Work outside protected locations such as Program Files; use administrator or compatibility settings only when a specific permission or launch error requires them.
• Keep paths short and avoid unusual characters. Older tools do not always handle long or complex paths reliably.
• If downloaded SDK documentation opens as a blank help window, use the Windows file properties to unblock the archive or help file, then extract it to a local folder.
• Do not replace missing components with similarly named FSX or Prepar3D SDK files. Their schemas, exporters and compiled formats are not a dependable substitute for the FS2004 versions.
• Retain a known-good sample build and your editable source files. They provide a quick way to distinguish a broken tool installation from an error introduced by the project.