Learn what MSFS scenery can be converted to X-Plane, what cannot, the legal limits, required formats and a reliable airport conversion workflow.
Microsoft Flight Simulator scenery cannot be installed directly in X-Plane. Conversion is possible only when you have usable source assets and the licence permits it; models, textures, airport data and terrain must be rebuilt or exported into X-Plane formats. Streamed Microsoft world scenery is not a convertible add-on.
This applies particularly to Microsoft Flight Simulator 2020 and 2024, whose scenery packages are built for Microsoft's engine. Older FSX scenery can sometimes be translated more easily, but its BGL and MDL content is not native to X-Plane either.
What MSFS scenery can be converted?
Original scenery projects with reusable source files are the best candidates; compiled, encrypted or streamed scenery usually cannot be converted completely.
| Scenery source | Conversion prospects | Main limitation |
|---|---|---|
| Your own original MSFS project | Good | Models, materials, placement and airport data still require X-Plane exports. |
| Third-party add-on with source files and permission | Good to partial | MSFS-specific materials, effects and behaviours must be replaced. |
| Unencrypted compiled add-on | Partial at best | The licence may prohibit extraction, and compiled placement or airport data may not translate cleanly. |
| Encrypted or DRM-protected package | Not practical | The usable source assets are unavailable and bypassing protection may breach the licence. |
| Default streamed scenery, aerial imagery or photogrammetry | No | It is a licensed online service rather than a distributable scenery project. |
| Legacy FSX BGL or MDL scenery | Sometimes partial | Geometry may be recoverable, but airports, terrain, animations and effects normally need rebuilding. |
The MSFS rolling cache does not turn streamed scenery into reusable source material. Aerial imagery also has separate copyright and distribution terms; our explanation of how licensed source imagery becomes photoreal scenery covers that distinction.
Visual models are only one layer. MSFS placement data, airport definitions, XML behaviours, custom shaders, animated jetways and effects do not automatically become X-Plane DSF, apt.dat or OBJ8 content.
How do you convert an MSFS airport to X-Plane?
Convert each component separately and assemble the result as a new X-Plane scenery package; there is no dependable one-click converter for an entire MSFS airport.
- Check the licence first. Confirm that extraction and conversion are permitted. For a public release, obtain permission covering conversion and redistribution of every model, texture and image you intend to include.
- Gather the original assets. Source Blender or glTF models, texture masters, geographic coordinates and the original airport project are preferable to files recovered from a compiled package.
- Prepare the models for OBJ8. Import the authorised models into Blender, apply scale and rotation, correct normals, simplify excessive geometry and rebuild materials for X-Plane. The OBJ8 model-export process, including scale and texture preparation, explains this stage.
- Rebuild the airport in WorldEditor. Create or verify runways, taxiways, aprons, ramp starts, lighting, ATC routes, facades, object placements and exclusion zones. Follow our practical WED package-building workflow rather than trying to reuse MSFS airport definitions directly.
- Handle terrain and imagery separately. Orthophotos require properly licensed, georeferenced source images. Custom mesh is a separate job again and can conflict with other mesh packages.
- Export and test a clean package. Validate for the intended X-Plane version, test without unrelated scenery libraries, and check the result by day and night. The X-Plane 12 installation and scenery-ordering procedure shows where the package belongs and how
scenery_packs.iniaffects loading.
Why does converted scenery fail in X-Plane?
Converted scenery usually fails because coordinate systems, materials, elevations or simulator-specific behaviours were carried across without being adapted.
- Missing or pink textures: check relative texture paths, filename case and supported formats. Case mismatches are especially easy to miss when moving a project between operating systems.
- Black, glossy or flat-looking surfaces: MSFS glTF material channels do not map directly to X-Plane's normal-map and reflectivity conventions. Rebuild the material rather than merely renaming texture files.
- Wrong scale or orientation: apply object transforms, work in metres and verify the model origin before export.
- Floating or buried buildings: compare airport elevation with the active X-Plane mesh. Hard-coded MSFS elevations often produce bad results on a different terrain model.
- Duplicate terminals, trees or roads: add carefully targeted exclusion zones. An airport identifier alone will not suppress every underlying scenery element.
- Static jetways or missing effects: MSFS animation logic, lights and XML behaviours need X-Plane-native replacements.
- Poor frame rate: reduce unnecessary draw calls, oversized textures and distant detail, then define sensible levels of detail for complex objects.
Test against the exact X-Plane release you intend to support. A package exported with X-Plane 12-specific assets or features should not be assumed to work unchanged in X-Plane 11.
Can you distribute converted MSFS scenery?
You may distribute converted scenery only when the licences or rights holders explicitly allow conversion and redistribution.
Buying an add-on gives you a licence to use it, not ownership of its models, textures or aerial imagery. Do not assume that a private conversion is permitted either; the package terms and applicable law still apply. Microsoft-supplied world scenery and imagery should not be extracted and repackaged.
For a public project, rebuilding the airport around authorised source assets is usually cleaner than reverse-engineering a compiled package. Conversion makes sense when you own the project or have the creator's cooperation; otherwise, create new models and layouts from legitimate references rather than copying simulator files.