Can you convert FSX scenery to FS2004? Learn what must be rebuilt, which assets can survive, and how to avoid missing objects, crashes and texture errors.
FSX scenery can sometimes be converted for Microsoft Flight Simulator 2004 (FS9), but it cannot normally be copied straight across. Native FSX BGL files, models, materials and terrain output are not backward-compatible. A usable conversion usually requires original source assets, FS2004-compatible recompilation, texture and model changes, and careful testing.
Why can't FSX BGL files be used directly in FS2004?
FS2004 cannot read most scenery compiled in native FSX formats. The .bgl extension is only a container name; airport data, object libraries, placement data, terrain and imagery can each contain simulator-specific records.
FSX also introduced a newer model format, different material features and widespread use of DDS textures. Putting those files into an FS9 scenery folder may produce invisible objects, missing textures or loading failures. Renaming a file does not change its internal format.
There is one useful exception: FSX can load some older FS2004-format scenery, so an add-on advertised for FSX may actually contain legacy FS9 assets. If it began as an FS2004 product and was merely repackaged, locate the original FS9 release rather than converting the FSX package.
Which scenery components can be converted?
The reusable part is usually the source material, not the compiled FSX scenery files.
| Component | FS2004 conversion route | Likely limitations |
|---|---|---|
| Airport layout | Edit or recreate the airport data and compile it for FS9 | FSX-only records must be removed; elevations, aprons and exclusions need checking |
| Custom 3D models | Recompile original models as FS9-compatible MDL and object-library files | Materials, animations, bump maps and specular effects may be lost or simplified |
| Textures | Convert suitable artwork to FS9-compatible extended BMP textures | Alpha channels, mipmaps, transparency and night textures require manual checking |
| Photoreal, mesh or landclass | Recompile the original imagery, elevation or landclass source for FS2004 | Compiled FSX terrain BGLs cannot simply be reused |
| Ground polygons and effects | Rebuild using techniques supported by FS9 | Draw order, blending and FSX-specific effects may not translate |
How do I convert FSX scenery to FS2004?
A reliable conversion rebuilds the package one component at a time and produces native FS9 output.
- Check the licence and obtain the source files. Secure the author's permission before modifying or distributing the scenery. Original airport XML, model source, textures and terrain imagery are far more useful than decompiled BGL files.
- Inventory the package. Separate airport facility data, object libraries, object-placement BGLs, terrain files, effects and textures. This reveals which parts need rebuilding and prevents an incompatible file from being hidden inside the finished package.
- Recompile the airport and placements. Use an airport editor or compiler that explicitly targets FS2004. Remove unsupported FSX records, replace references to FSX default-library objects, and recreate exclusions or flattens where required. Our explanation of the FS2004 SDK toolchain covers the native compilers and what each one produces.
- Convert custom models and textures. Compile models for FS9 rather than retaining their FSX MDL format. Simplify unsupported materials, verify animations, and convert DDS artwork to suitable FS9 texture files while preserving any required alpha channel and night variant.
- Rebuild terrain and aerial imagery. Return to the original source imagery or elevation data and compile it with FS2004-compatible tools. The FS9-specific photoreal scenery process explains why source data must be compiled for the target simulator.
- Package and test the FS9 scenery. Place BGL files in a
scenerysubfolder and textures in the neighbouringtexturesubfolder, then activate the parent folder through the Scenery Library. Follow our FS2004 folder structure and Scenery Library steps if the rebuilt package is not appearing.
What causes converted scenery to fail?
Most failed conversions contain one incompatible component or an unresolved reference rather than a completely unusable package.
- FS9 crashes or stops loading: remove the scenery layer, then restore one BGL at a time. A native FSX BGL or invalid object library is a common cause.
- Objects are missing: the placement file may reference FSX library-object GUIDs that do not exist in FS2004. Replace those objects with FS9 equivalents or compile a compatible custom library.
- Objects appear white, black or transparent: check texture names, folder placement, file format and alpha channels. FSX material settings do not automatically survive recompilation.
- The airport floats or sits underground: airport elevation, flatten and mesh data disagree. Set a consistent FS9 airport elevation and remove duplicate or conflicting elevation files.
- Runways or aprons flicker: both the default airport surface and a converted ground polygon may be drawing in the same place. Correct the exclusion, flatten or polygon layering rather than stacking another copy over it.
- Night or seasonal textures are absent: the required texture variants were not converted, named correctly or referenced by the rebuilt model.
Is there a one-click FSX-to-FS2004 converter?
No single converter reliably translates an entire FSX scenery package into FS2004 format. Specialist utilities can assist with individual airport records, models or textures, but they cannot automatically resolve unsupported materials, missing libraries, terrain compilation, elevations and licensing.
If the source files are unavailable or the scenery relies heavily on native FSX features, using scenery built specifically for FS2004 is usually faster and more reliable than reverse-engineering the FSX release.
Can converted scenery be shared?
A conversion should only be redistributed when the original licence and author permit modification and sharing. Texture artwork, custom models, aerial imagery and elevation data may have separate usage terms, so permission for the airport package alone may not cover every included asset.