Learn how to convert FS2004 scenery to FSX, rebuild airports and objects, and fix missing textures, exclusions, elevation and DX10 issues.
To convert FS2004 scenery for FSX, first test it unchanged in a separate add-on folder; many legacy BGL files still load. Rebuild any broken airport data, object libraries, placements, exclusions and terrain with FSX-targeted tools, then retain only the working or FSX-compiled files. Renaming or copying BGLs alone is not a true conversion.
This applies to boxed FSX and FSX: Steam Edition. We recommend treating each scenery component separately because an airport BGL may work while its buildings, ground polygons or elevation data do not.
Can FS2004 scenery work in FSX without conversion?
Some FS2004 scenery works directly in FSX, especially simple airport layouts, object placements, mesh and landclass. Compatibility depends on how each BGL was compiled, which object libraries it references and whether it uses legacy ASM or SCASM rendering commands.
| Component | Try it unchanged when | Rebuild it when |
|---|---|---|
| Airport or AFCAD | Runways, taxiways, parking and frequencies display correctly | There are duplicate runways, elevation faults, broken approaches or missing exclusions |
| Object library and placements | All buildings appear with their correct textures | Objects are missing, black, transparent, untextured or unstable |
| Mesh, landclass or photo scenery | The BGL displays in the correct position without terrain faults | It does not load, uses the wrong seasons or produces corrupt terrain |
| Custom ground polygons | Aprons and markings render without flickering | They disappear in DX10 Preview, bleed through other surfaces or suppress autogen incorrectly |
Direct compatibility is not the same as native FSX scenery. A legacy package that behaves in the default DX9 renderer may still lose models, transparency or ground layers under DX10 Preview.
How do I convert FS2004 scenery to FSX format?
- Back up and stage the package. Work on a copy outside the simulator. Keep the converted scenery in its own folder, normally with sibling
sceneryandtexturedirectories, rather than placing files directly into FSX's global scenery folders. - Test the unmodified files first. Add the package through the FSX Scenery Library and place it above the corresponding default area. Check the airport by day and night, in different seasons, and with DX10 Preview both disabled and enabled if you intend to use it. Record which parts fail before changing anything.
- Recover the best available source. Original XML, airport projects, models, imagery and terrain source files are preferable to decompiling finished BGLs. Our BGLXML 2.1 utility download can disassemble many scenery BGLs into XML and extract embedded MDL objects, but it cannot reconstruct every project losslessly. Protected scenery should not be bypassed.
- Rebuild the airport data. Import or recreate the FS2004 airport in an FSX-targeted airport editor, then review the airport reference point, runway elevation, taxi links, parking codes, navaids, approaches, flattens and exclusion rectangles. Our airport-rebuilding workflow for Airport Design Editor covers the layout and compilation process. Disable the old AFCAD after compiling the replacement; running both produces duplicate facilities and conflicting data.
- Convert object models and placements. Import recoverable FS2004 MDLs into an FSX-capable model tool such as ModelConverterX, correct their materials and animation tags, and export them as FSX MDLs. Compile a new object-library BGL and placement BGL with the FSX SDK tools. Preserve the original library GUIDs when practical; if they change, every placement referencing them must also change. Our guide to setting up the FSX SDK scenery compilers explains the native toolchain.
- Rebuild terrain from source data. Finished mesh, vector and photo BGLs generally cannot be turned back into complete source projects. If a terrain BGL fails in FSX, obtain the original raster, elevation or vector data and compile it with the FSX Resample or terrain tools. For imagery, follow the process for building native FSX photo scenery from source files.
- Handle ground polygons separately. FS2004 custom ground layers often rely on legacy drawing methods. Replace them with native airport aprons, photo imagery or an FSX-compatible ground-polygon build. Check layer order, flickering, shadows, autogen suppression and DX10 Preview rather than assuming an apparently correct daytime view is sufficient.
- Verify textures, effects and dependencies. Preserve texture basenames, alpha channels, light maps and mipmaps. Do not batch-convert every BMP to DDS: unnecessary conversion can alter transparency or orientation. Replace references to missing FS2004 default-library objects with FSX equivalents instead of copying stock FS2004 libraries.
- Remove superseded legacy files. Once the rebuilt component works, take its old FS2004 BGL out of the active package. Keep an inventory showing which files remain legacy-compatible and which have been compiled for FSX.
Why is converted FS2004 scenery broken in FSX?
Most conversion failures come from a missing library, an incompatible model, duplicated airport data or mismatched elevation rather than the scenery folder itself.
| Symptom | Likely cause | Fix |
|---|---|---|
| Runways appear but buildings do not | Missing object library, unsupported FS2004 MDLs or absent textures | Activate the required library, rebuild the models and verify the package's texture folder |
| Default buildings or trees cover the airport | Legacy exclusions were not understood or the package has insufficient priority | Create FSX exclusion rectangles and check Scenery Library order |
| Airport sits on a plateau or in a hole | Airport elevation, flatten and altitude-adjustment files disagree | Use one consistent elevation and remove competing elevation BGLs |
| Duplicate runways, navaids or parking | The FS2004 airport and rebuilt FSX airport are both active | Disable the old airport BGL and search for other AFCAD files using the same ICAO code |
| Black, opaque or invisible surfaces | Legacy material settings, damaged alpha channels or DX10 incompatibility | Correct the material, preserve texture alpha and re-export the model for FSX |
| FSX crashes near the scenery | A malformed legacy model, effect or BGL is being loaded | Disable files in small groups until the offending component is isolated, then rebuild or remove it |
A mistake we see constantly is changing the airport, models and textures together. Isolate one class of BGL at a time; otherwise a working airport file can be blamed for a failing object library.
Can I share converted FS2004 scenery?
A file being extractable does not make it redistributable. Conversion for a personal installation may be allowed by the original licence, but publishing rebuilt BGLs, models, textures or modified source requires the author's permission unless the licence explicitly grants redistribution and modification rights.
Do not package Microsoft stock FS2004 libraries or textures with the conversion. Replace those dependencies with suitable FSX assets, and document any separate libraries the user must already be licensed to use.