Learn what FSX scenery can be reused in Microsoft Flight Simulator, what must be rebuilt with the SDK, and why direct BGL copies fail.
Yes, but FSX scenery cannot normally be copied straight into Microsoft Flight Simulator 2020 or 2024. A usable conversion means returning to the original source assets where possible, converting models and textures, then rebuilding airport, terrain, placement, lighting and package data with the MSFS SDK. Complex products often need substantial rework.
Is there a one-click FSX scenery converter?
No converter can reliably turn every FSX scenery package into finished MSFS scenery. An FSX .bgl may contain airport records, object placements, terrain data or references to separate model libraries. Modern Microsoft Flight Simulator uses a different package system, rendering pipeline and scenery engine.
Conversion utilities may recover coordinates or provide a starting point for simple custom models. They cannot automatically correct materials, exclusions, ground surfaces, terrain alignment, effects, animations, level-of-detail models or dependencies on FSX stock objects. A mistake we see constantly is assuming that a package which compiles without an error is therefore converted correctly.
Copying an FSX BGL into the MSFS Community folder does not convert it. Our broader explanation of why legacy FSX add-ons cannot simply be copied into MSFS covers the same compatibility boundary for aircraft and other add-on types.
Which parts of FSX scenery can be reused?
| FSX scenery element | Reuse potential | Work normally required |
|---|---|---|
| Coordinates and object placements | Often useful as reference data | Recreate or import placements, then correct elevation and orientation |
| Original 3D source models | Usually the best candidates | Export through an MSFS-compatible glTF workflow; rebuild materials, collision and LODs |
| Compiled FSX MDL models | Limited | Recovery can be lossy and may not be permitted by the licence |
| Texture source files | Often reusable with permission | Convert the material setup and create suitable normal, roughness, metallic and emissive maps where needed |
| Airport layout or AFCAD data | Useful as a reference | Rebuild runways, aprons, taxiways, parking, markings and exclusions in the MSFS Scenery Editor |
| Legacy ground polygons | Rarely suitable unchanged | Rebuild as MSFS airport surfaces, polygons or properly prepared projected imagery |
| FSX effects, animations and stock library objects | Usually incompatible | Replace them with MSFS-native effects, animation definitions and objects |
The cleanest conversion starts with the creator's original model, texture and geographic source files. If only compiled BGL and MDL files remain, rebuilding may be faster and produce a better result than trying to recover every asset.
How do you convert FSX scenery to MSFS?
- Confirm ownership and permissions. Check that the licence allows modification and use in Microsoft Flight Simulator. Personal access to an FSX add-on does not automatically grant permission to extract and redistribute its assets.
- Inventory the original package. Identify airport BGLs, custom model libraries, placement data, textures, aerial imagery, elevation data and dependencies. Separate custom assets from FSX stock content, which must not be bundled into a new package.
- Create an MSFS scenery project. Enable Developer Mode on the PC version, create a scenery package and establish the airport or project location. Our practical MSFS scenery-building process explains the editor and package workflow.
- Prepare the models and materials. Export from the original modelling source into the supported glTF-based workflow. Check scale, axes, model origin, transparency, collision, bounding information and LODs. Legacy FSX materials need to be recreated rather than merely renamed.
- Rebuild the airport and terrain work. Recreate runways, taxiways, aprons, parking positions, polygons, exclusions and terraforming. Use the FSX data as a reference, but align the result against the terrain and imagery used by the target MSFS version.
- Replace unsupported features. Rebuild night lighting, windsocks, animated objects, smoke or particle effects, seasonal behaviour and custom scripts with features supported by the MSFS SDK.
- Build and test the package. Compile it with the target simulator's SDK, install the built package rather than the source project, and inspect Developer Mode warnings. Test approach paths, ground operations, day and night lighting, multiple weather conditions and different scenery-detail settings.
Microsoft Flight Simulator 2020 packages may work in MSFS 2024, but compatibility should not be assumed. Build and test for the intended version because default airports, terrain, vegetation, streamed scenery and SDK behaviour can differ.
Why does converted FSX scenery look wrong?
Most conversion faults come from features that survived only partially or were positioned against a different terrain base.
- Nothing appears: the raw FSX BGL was copied rather than rebuilt, the package structure is invalid, the package was not compiled, or the wrong Community folder is being used.
- Duplicate runways or buildings: the replacement scenery lacks correct airport records or exclusion polygons, allowing the default airport and converted objects to appear together.
- Objects float or sink: FSX altitude assumptions no longer match the MSFS terrain. Check whether each object uses altitude above ground or an absolute elevation, then add suitable terraforming.
- Aprons flicker: an old ground polygon is competing with the default surface. Rebuild the surface instead of stacking nearly coplanar polygons.
- Textures are missing or look plastic: texture references, transparency or legacy material properties did not translate. Recreate the material and verify every referenced texture is included in the package.
- Performance is poor: recovered models often lack sensible LODs and may use excessive material assignments, draw calls or texture resolution. Optimise these before adding more scenery detail.
- Lights, effects or animations do nothing: FSX animation tags and effect files do not map directly to the modern engine and must be rebuilt.
Package order can also produce missing objects, overlapping airports or exclusions that affect another add-on. See our explanation of MSFS package priority and Community-folder management before changing the scenery itself.
Is it better to convert or rebuild FSX scenery?
A hybrid rebuild is usually the best choice: retain lawful, high-quality source models and reference data, but recreate the airport and scenery definitions natively in MSFS.
- Convert and reuse assets when you have the editable source files, clear permission, accurate custom models and straightforward object placement.
- Rebuild from scratch when only compiled files survive, the scenery depends heavily on FSX ground polygons or stock libraries, or its imagery and geometry no longer match the modern simulator.
- Abandon the conversion when ownership is unclear or the recovered result requires more repair than a clean native project.
Can converted scenery be installed on Xbox or PlayStation?
Custom scenery development and Community-folder installation are PC workflows. Xbox Series X|S and PlayStation 5 do not provide users with an equivalent folder for sideloading arbitrary converted packages. Console availability requires distribution through the simulator's supported in-sim channels and compliance with the relevant platform restrictions.