Are Prepar3D aircraft compatible with FSX? See which models, gauges and add-ons work, what fails, and how to check safely before installing.
Prepar3D aircraft are not automatically compatible with FSX. An aircraft may work only if it includes an FSX-built model, FSX-compatible gauges and no Prepar3D-only dependencies. Native Prepar3D v4, v5 or v6 add-ons generally will not work in 32-bit FSX, even when their folders look familiar.
Which Prepar3D aircraft can work in FSX?
The best candidates are aircraft packages whose developer explicitly supplies a separate FSX or FSX: Steam Edition build. Prepar3D and FSX share architectural roots, so both use familiar components such as aircraft.cfg, panel.cfg, model folders and texture folders. That similarity does not guarantee binary compatibility.
| Aircraft package | Likely FSX compatibility | Reason |
|---|---|---|
| Package officially supporting FSX and Prepar3D | Yes, using the FSX build | The installer should provide models, gauges and dependencies compiled for FSX. |
| FSX aircraft later made compatible with Prepar3D | Often | Use the original FSX release rather than copying the installed P3D version back. |
| Prepar3D v1-v3-only aircraft | Uncertain | These versions are 32-bit, but P3D-specific models, gauges and APIs can still prevent FSX compatibility. |
| Prepar3D v4-v6-only aircraft | Usually no | Prepar3D became 64-bit from v4, while FSX is 32-bit. Native DLL gauges and modules cannot cross that boundary. |
| Prepar3D repaint or livery | Only in limited cases | It must target the exact same FSX model and texture mapping; a repaint does not include the aircraft itself. |
That shared history causes confusion in both directions. Our breakdown of how Prepar3D generations handle legacy FSX add-ons explains why model format, bitness and simulator-specific modules matter.
How do I check a P3D aircraft before installing it in FSX?
Check the supported simulator list, model build and gauge dependencies before copying any files into FSX.
- Confirm explicit FSX support. Look in the product description, manual or readme for FSX or FSX: Steam Edition. A label saying only “Prepar3D compatible” is not enough.
- Use the dedicated FSX installer. If the package offers separate simulator choices, select FSX. Do not install the Prepar3D edition and assume its aircraft folder is identical.
- Check gauges and external modules. XML gauges may be portable when they use variables supported by FSX, but DLL gauges compiled for 64-bit Prepar3D cannot load. P3D-specific SimConnect clients, avionics modules and activation components also need an FSX edition.
- Check how the package is registered. Prepar3D can load add-ons through
add-on.xml; FSX does not read that file. Aircraft intended for FSX normally place or register their files under a recognised SimObjects path such asSimObjects\Airplanes. - Test one aircraft at a time. If the licence permits manual installation, keep a backup and avoid merging entire Gauges, Effects or root folders blindly. Check the exterior model, virtual cockpit, instruments, controls, engine start, lights, animations and sounds.
A mistake we see constantly is treating matching folder names as proof of compatibility. Configuration text can be readable by both simulators while the underlying .mdl model or DLL gauge remains completely incompatible.
Why does a Prepar3D aircraft fail in FSX?
Most failures come from an unsupported model, an incompatible gauge or a missing P3D-only dependency.
- The aircraft does not appear: FSX may not be scanning its location, or the package may depend on Prepar3D's
add-on.xmlsystem. A brokenaircraft.cfgentry or missing model reference can cause the same symptom. - The aircraft is invisible or missing parts: the model may have been compiled for Prepar3D, or required model and texture files may be absent. Use our checks for invisible and incomplete aircraft models to separate installation faults from true incompatibility.
- The cockpit is black or gauges are blank: the panel probably uses incompatible DLL gauges or an external avionics module. Editing
panel.cfgcannot convert a 64-bit gauge into an FSX gauge. - FSX crashes while loading the aircraft: remove the aircraft and any modules installed with it. Repeatedly approving an incompatible gauge or running FSX as administrator will not fix a model or binary compiled for another simulator.
- Systems, sounds or animations are missing: the package may reference P3D-specific effects, variables, modules or shared files. Install the official FSX dependencies if they exist; otherwise the aircraft is not fully compatible.
Can a P3D-only aircraft be converted to FSX?
A P3D-only aircraft cannot usually be converted to FSX by an end user. A proper conversion may require the original source model to be exported with the FSX SDK, native gauges to be rebuilt as 32-bit FSX modules, unsupported materials and animations to be replaced, and the complete aircraft to be retested.
Renaming model files, changing folder paths or editing aircraft.cfg does not perform that conversion. Source files and the author's permission are also required, particularly for commercial or copyrighted aircraft.
For a dependable result, choose an aircraft explicitly packaged for FSX or FSX: Steam Edition. Our FSX aircraft and add-on library provides packages intended for that simulator, though each download's readme should still be checked for edition-specific instructions.