Can FSX or Prepar3D scenery add-ons be used in X-Plane?

No—FSX and Prepar3D scenery add-ons cannot normally be installed directly in X-Plane. They use different terrain, airport, object and configuration formats. A package must be rebuilt or lawfully converted for X-Plane, and many commercial licences forbid conversion. The original scenery installer will not make it compatible.

Why are FSX and Prepar3D scenery incompatible with X-Plane?

X-Plane cannot read the compiled scenery system used by FSX, FSX: Steam Edition and Prepar3D. FSX and Prepar3D are related platforms, but X-Plane uses a separate scenery engine and package structure. Our explanation of the FSX heritage behind Prepar3D provides more context for why compatibility between those two does not extend to X-Plane.

Some texture files may happen to use an extension that X-Plane also recognises, such as .dds. That does not make the scenery compatible: object materials, texture references, coordinates, animations and placement data still belong to the original simulator.

Can any part of the scenery be converted?

Some source assets can be rebuilt for X-Plane, but a compiled add-on rarely converts cleanly as a complete package.

• Photo imagery: Original georeferenced images can sometimes be processed into native X-Plane scenery if their licence permits it. A compiled photoreal BGL cannot simply be copied; our guide to how FSX photoreal scenery is packaged shows why it remains tied to the FSX scenery system.
• 3D models: Models are best exported from the creator's original source files. Extracting compiled models can breach the licence and often loses materials, animations or effects.
• Airport layouts: Runways, taxiways and parking positions can be recreated in an X-Plane scenery editor. Imported data still needs checking for airport identifiers, elevations, exclusions and alignment.
• Terrain mesh: This normally requires an X-Plane-specific build. The process is more involved than converting airport objects because the DSF contains the terrain geometry for an entire tile.
• Animations and dynamic features: Jetways, road traffic, platform-specific effects and scripted objects usually need replacements written for X-Plane.

Freeware does not automatically grant permission to convert or redistribute an add-on. Check the included licence or obtain the copyright owner's permission before extracting assets. Commercial packages may prohibit even private conversion, while redistribution nearly always requires explicit authorisation.

How can I tell whether a download has an X-Plane version?

A genuine X-Plane edition will identify X-Plane explicitly and contain native package files rather than only an FSX or Prepar3D installer.

• An FSX or Prepar3D package commonly contains Scenery and Texture directories, .bgl files, or an installer that searches for those simulators.
• An X-Plane package typically contains Earth nav data, .dsf, apt.dat, .obj or library.txt files and is placed under Custom Scenery.
• If a developer supplies separate FSX, Prepar3D and X-Plane downloads, use the edition made for your exact simulator. Renaming folders or changing the installer destination does not convert the files.

A package labelled for X-Plane may still depend on separate object libraries. If objects are missing, follow our instructions for installing X-Plane scenery libraries rather than copying libraries from FSX or Prepar3D.

Why does converted scenery look broken in X-Plane?

Partly converted scenery fails when placement, elevation, materials or dependencies have not been rebuilt for X-Plane.

• The airport does not appear: X-Plane has no native DSF or airport data to load; a folder containing only BGL files will be ignored.
• Buildings are missing: The objects were not converted, their texture paths are wrong, or required X-Plane libraries are absent.
• Textures are white or magenta: Material conversion failed, file references are broken, or filename capitalisation does not match on a case-sensitive file system.
• Two airports overlap: The converted package uses the wrong airport identifier or lacks suitable exclusions for default scenery.
• Runways float or sit in trenches: The airport elevation does not match the active terrain mesh. Two complete base meshes cannot simply be blended by changing scenery priority; one normally controls the tile.
• Jetways or animations remain static: The original feature relies on simulator-specific scripting, effects or modules that X-Plane cannot execute.

Should I convert the scenery or find an X-Plane replacement?

Use a native X-Plane package whenever one exists; attempt a rebuild only when you have permission, suitable source assets and the time to correct the result manually.

• Choose the native edition when the same airport or region is offered for X-Plane. This preserves supported materials, exclusions, lighting and animations.
• Rebuild from source when you created the original scenery or have written permission and editable models, imagery and placement data.
• Replace the package when all you possess is an installer or compiled BGL files. There is no dependable drag-and-drop conversion.

Terrain deserves particular care because it affects every airport and overlay in its tile. The process for installing native X-Plane mesh scenery also explains the package structure and ordering that an FSX or Prepar3D terrain BGL lacks. Check the stated X-Plane version as well, since mesh, vegetation, lighting and plugin-driven features may be version-specific.