Learn which FS2004 aircraft run in FSX, why native FSX aircraft fail in FS2004, and how to identify port-overs before installing.
Many FS2004 aircraft can work in FSX as port-overs, though gauges, animations, transparency and effects may need fixes. Native FSX aircraft generally cannot work in FS2004 because the older simulator cannot read the newer FSX model format. A package containing separate files for both simulators is the main exception.
Why does compatibility mostly work in one direction?
FSX retained support for many aircraft models compiled for FS2004, but FS2004 was never designed to read native FSX models. That makes compatibility backwards-looking: the newer simulator can often load older content, while the older simulator cannot interpret content built with the newer SDK.
The compiled .mdl visual model is the decisive part. Editing aircraft.cfg, replacing the .air file or moving textures cannot turn a native FSX model into an FS2004 model. Our comparison of the underlying FS2004 and FSX differences explains why other add-on components also behave differently.
| Aircraft package | In FSX | In FS2004 |
|---|---|---|
| Native FS2004 aircraft | Often loads as a port-over, sometimes with faults | Supported |
| Native FSX aircraft | Supported | Not compatible |
| Separate FS2004 and FSX versions | Use the FSX files | Use the FS2004 files |
| FSX-labelled FS2004 port-over | Usually works as documented | Use the original FS2004 release rather than copying it back |
What can break when an FS2004 aircraft is used in FSX?
An aircraft appearing in the FSX selection menu does not prove that every part of it is compatible. Common port-over faults include:
- Missing instruments: older compiled gauges or gauge dependencies may not load, leaving blank areas in the 2D panel or virtual cockpit.
- Black or opaque windows: texture alpha channels and material transparency can render differently in FSX.
- Propeller and rotor artefacts: prop discs may appear behind clouds, turn opaque or display incorrectly, particularly with DX10 Preview enabled.
- Broken animations: doors, control surfaces, landing gear or cockpit controls may not operate as intended.
- Silent panels or engines: panel and sound aliases can point to default FS2004 aircraft that do not exist in FSX.
- Missing effects: smoke, lighting or afterburner entries may depend on effect files that were not copied into the FSX
Effectsfolder. - Different handling: FS2004 flight-dynamics files can load, but the aircraft may not perform identically under FSX.
These faults do not always have a practical fix. A native FSX edition is preferable when both versions are available because it can use FSX materials, animations, virtual-cockpit features and gauge behaviour directly.
How can I identify an FS2004 port-over before installing it?
The package description and included documentation are more reliable than the folder or file names. Look for wording such as FS2004/FSX compatible, FS9 port-over, native FSX or separate downloads for each simulator.
Do not assume that an aircraft is native merely because its archive says “FSX”. Many older releases were repackaged for FSX without rebuilding the visual model. Likewise, the presence of aircraft.cfg, model.cfg or a thumbnail does not identify the format in which the model was compiled.
How should I install and test an FS2004 aircraft in FSX?
Install it as a port-over rather than copying the complete FS2004 folder structure into FSX. FS2004 normally stores aircraft beneath its Aircraft directory, whereas FSX uses SimObjects\Airplanes.
- Read the package instructions. Check whether an FSX update, replacement panel or revised model is included.
- Keep the aircraft folder intact. Its top level should contain
aircraft.cfg, with the model, panel, sound and texture subfolders beneath it. - Place supporting files carefully. Gauges and effects may need their corresponding FSX folders, but do not overwrite newer shared files with older copies.
- Test from a simple ground position. Check the external model, virtual cockpit, 2D panel, engines, lights, landing gear and control animations before using the aircraft in a saved flight.
- Remove it if FSX becomes unstable. A failed gauge or module can cause a crash even when the aircraft model itself is readable.
Our detailed FS2004 aircraft installation procedure for FSX covers the folder layout and common nesting mistakes.
Does FSX: Steam Edition change the answer?
FSX: Steam Edition uses the same basic FSX aircraft formats, so its model compatibility with FS2004 aircraft is broadly the same. Installation paths can differ, and old gauge modules or installers may expect the boxed FSX location rather than the Steam library.
If the model loads but a panel module fails, treat that as a gauge or installer compatibility problem rather than proof that every FS2004 aircraft is unusable. See our guidance on add-ons in FSX: Steam Edition for those version-specific concerns.
Can a native FSX aircraft be converted to FS2004?
A native FSX aircraft cannot be converted to FS2004 by changing configuration files. Rebuilding it requires suitable source assets, an FS2004-compatible export process and permission from the original developer; the compiled FSX model alone is not enough for an ordinary installation conversion.
If a download advertises both simulators, use the dedicated FS2004 model, gauges and configuration supplied in the package. Otherwise, assume a native FSX aircraft is FSX-only.