Learn what Prepar3D scenery can be reused in MSFS, X-Plane and FSX, what must be rebuilt, and why direct copying usually fails.
Yes, but Prepar3D scenery cannot normally be copied straight into MSFS or X-Plane. A lawful conversion usually requires the original source models, textures and placement data, then rebuilding with the destination simulator’s SDK. FSX is the easiest target for older, content-only P3D scenery, though newer Prepar3D features may still fail.
Which destination simulator is easiest to convert for?
FSX is usually the easiest target because it shares Prepar3D’s technical ancestry, while MSFS and X-Plane use substantially different scenery systems. Even with FSX, compatibility depends on which SDK compiled the scenery and which Prepar3D-specific features it uses.
| Target | Can files be copied directly? | What can usually be reused? | What normally needs rebuilding? |
|---|---|---|---|
| MSFS | No | Authorised source models, texture artwork, coordinates and imagery | Package structure, model exports, materials, airport data, ground surfaces, exclusions, lighting and effects |
| X-Plane | No | Source models, textures, coordinates and some georeferenced source data | OBJ assets, apt.dat airport data, DSF placement or terrain, materials and exclusions |
| FSX | Sometimes | Legacy FSX-format BGLs and textures already being used by Prepar3D | Anything compiled with P3D-only SDK features, materials, effects or code |
MSFS may use the .bgl extension for compiled scenery, but that does not make its files interchangeable with Prepar3D BGLs. Our detailed explanation of rebuilding legacy scenery for MSFS covers the target package and asset requirements.
X-Plane requires its own airport, object and terrain formats rather than Prepar3D’s Scenery Library structure. See our technical breakdown of moving FSX or P3D scenery into X-Plane for the platform-specific limitations.
For FSX, first establish whether the add-on was originally an FSX product that was merely installed in Prepar3D. If so, use the original FSX package instead of reverse-converting the P3D installation. Our guide to how FSX-era scenery behaves across Prepar3D versions explains why content-only scenery is generally more portable than modules and other compiled code.
What Prepar3D scenery files can actually be reused?
Original project assets are far more useful than compiled scenery. Source 3D models, texture artwork, airport coordinates, placement XML, elevation data and licensed aerial imagery can often be adapted for another simulator.
- Models and textures: The source model can be exported for the destination simulator, but materials, transparency, reflections, emissive lighting and texture channels usually need reworking.
- Airport layouts: Runway coordinates, parking positions and taxiway plans provide a useful reference, but the airport must be rebuilt in the target format.
- Object placement: Coordinates may be reusable. Library references are not useful unless the referenced models are also available and licensed for conversion.
- Photo scenery: Original georeferenced imagery may be reusable if its licence permits it. Compiled photo BGLs are not direct inputs for MSFS or X-Plane.
- Terrain mesh and landclass: The underlying source data may be valuable, but each simulator needs its own terrain processing and compilation.
- Effects and dynamic features: P3D-specific effects, shaders, dynamic lighting, animations and scripts generally require replacement rather than conversion.
The add-on.xml file only tells Prepar3D how to discover an add-on. It does not translate the scenery into another simulator’s package format. Likewise, copying a Scenery and Texture folder into an MSFS Community folder or an X-Plane custom-scenery folder does not convert its contents.
Freeware does not automatically grant conversion rights. You need ownership of the source assets or explicit permission to modify and redistribute them. Payware extraction and redistribution are normally prohibited, and private conversion remains subject to the product’s licence.
How do you convert Prepar3D scenery reliably?
A dependable conversion is a controlled rebuild using the destination simulator’s SDK, not a one-click file translation.
- Inventory the add-on. Separate airport data, object libraries, textures, ground polygons, imagery, mesh, effects, traffic files and compiled modules. Record external library dependencies.
- Obtain authorised source files. Work from the original models, texture masters, placement data and project files wherever possible. Decompiling a BGL is lossy and may breach the licence.
- Create a native target project. Use an MSFS package project, an X-Plane scenery package or an FSX SDK project as appropriate. The overview of SDKs and asset-development tools explains which parts of the toolchain differ by simulator.
- Re-export the visual assets. Rebuild material definitions, texture channels, transparency, night lighting, animations and levels of detail for the target renderer.
- Recreate placement and airport data. Add runways, taxiways, parking, exclusions, terrain adjustments and object placements in the destination format rather than relying on P3D metadata.
- Compile and test in isolation. Test without unrelated add-ons first, then check runway alignment, elevations, missing objects, night appearance, frame rate and conflicts with default scenery.
Do not use 32-bit versus 64-bit as the sole compatibility test. Architecture matters greatly for DLLs and other compiled code, but ordinary scenery compatibility depends more on the compiler, model format and features used.
Why does converted scenery fail or display incorrectly?
Most failed conversions come from incompatible compiled assets, missing dependencies or assumptions carried over from Prepar3D’s renderer and terrain system.
- Nothing appears: The P3D folder or BGL was copied without being rebuilt and registered as a valid target package.
- Buildings are missing: The scenery references an external object library that was not converted, installed or licensed for reuse.
- Textures are black, opaque or reflective: Material channels, alpha handling or texture conventions were not remapped for the target renderer.
- The airport floats or sits underground: Elevation, flatten and terrain rules differ between simulators. Rebuild the airport elevation treatment against the target simulator’s terrain.
- Runways or buildings are duplicated: The converted airport lacks suitable exclusions for default or streamed scenery.
- Ground markings flicker: Legacy ground polygons are competing with the target surface. Recreate them using native ground materials and layering.
- Performance is poor: Extracted or automatically translated models often lack sensible levels of detail, efficient materials or suitable texture sizes.
If the original source project is unavailable, rebuilding the airport from reference data is often quicker and cleaner than trying to rescue a compiled P3D package. It also avoids carrying obsolete material settings, hidden dependencies and elevation fixes into the new simulator.