Learn why MSFS scenery add-ons do not work in FSX: Steam Edition, how to spot the correct download, and whether conversion is practical.
No. Scenery built for Microsoft Flight Simulator 2020 or 2024 is not compatible with FSX: Steam Edition. The simulators use different scenery engines, package structures, materials and SDK standards. Copying an MSFS package into FSX folders, or adding it to the FSX Scenery Library, will not convert or load it.
Why doesn't MSFS scenery work in FSX: Steam Edition?
MSFS scenery fails in FSX: Steam Edition because FSX cannot interpret the newer simulator's package and asset formats. This applies to airports, landmarks, city enhancements, aerial imagery and object libraries.
| Component | MSFS 2020 and 2024 | FSX: Steam Edition |
|---|---|---|
| Package structure | Uses MSFS package metadata, commonly including manifest.json and layout.json | Uses the legacy FSX scenery system and scenery.cfg |
| Loading method | Community packages or simulator-managed content | Scenery folders registered through the FSX Scenery Library |
| Models and materials | Modern MSFS model, material and rendering formats | Legacy FSX model and material formats |
| Aerial and terrain data | May use MSFS-specific compiled imagery and terrain data | Requires data compiled for the FSX terrain engine |
Both platforms use files with a .BGL extension, but that extension does not make the files interchangeable. The data compiled inside an MSFS BGL is not automatically readable by FSX.
FSX: Steam Edition retains the core scenery framework of boxed FSX, although installers and folder detection can differ. Our explanation of which legacy FSX add-ons work in Steam Edition covers those compatibility caveats.
How can I identify the correct scenery download?
Check the named simulator version on the download page and inside the archive before installing anything.
- Read the compatibility label. Look for
FSX,FSX: Steam EditionorFSX-SE. A package labelled only for MSFS 2020 or MSFS 2024 will not work. - Inspect the archive. An MSFS Community-ready package commonly contains
manifest.jsonandlayout.json. FSX scenery commonly has separateSceneryandTexturefolders or an FSX-specific installer. - Check dual-platform releases carefully. If a developer supports MSFS and FSX, the download should provide separate builds. Select the FSX build rather than copying files from the MSFS folder.
- Confirm dependencies. Some FSX airports require separate FSX object libraries, terrain mesh or other scenery packages. MSFS versions of those dependencies cannot substitute for them.
Older listings sometimes use “Microsoft Flight Simulator” as a broad product name. Because FSX itself belongs to that series, rely on an explicit version label rather than the words “Microsoft Flight Simulator” alone.
Can MSFS scenery be converted to FSX?
There is no reliable one-click method for converting finished MSFS scenery into FSX scenery. A proper conversion is a rebuild using the original source assets and the FSX SDK, not a renamed folder or a change to the file extension.
Airport layouts, models, materials, effects, terrain polygons and aerial imagery may all need to be exported or compiled again for FSX. A compiled MSFS package often lacks the editable project data required to do that cleanly, and any reused assets must have suitable licence permission.
The technical direction differs, but the same limitations described in our guide to rebuilding FSX or Prepar3D scenery for MSFS apply in reverse: scenery must be reconstructed for the destination simulator's SDK.
What scenery should I install in FSX: Steam Edition?
Install only scenery explicitly built for FSX or confirmed to support FSX: Steam Edition. Our FSX add-on library keeps FSX downloads separate from modern MSFS packages, reducing the risk of choosing the wrong platform.
A common mistake we see is placing an MSFS Community package inside FSX's Addon Scenery directory. FSX will not recognise it there, and registering that folder in the Scenery Library does not change the package format.
Why might compatible FSX scenery still not appear?
If an FSX-labelled package does not show, the usual causes are an extra nested folder, an unregistered scenery area, incorrect library priority or a missing object library. Restart FSX after activating scenery and verify that the selected folder directly contains the expected scenery subfolders.
For activation and ordering problems, follow our instructions for registering and prioritising scenery in the FSX Scenery Library. Those fixes apply to genuine FSX scenery; they cannot make an MSFS package compatible.