Are FS2004 add-ons compatible with FSX?

FS2004 (FS9) add-ons are only partly compatible with Microsoft Flight Simulator X (FSX) and FSX: Steam Edition. Many simple aircraft, repaints, sounds and scenery files can work, but gauges, executable modules, installers, AI traffic and complex scenery often need correction or an FSX-specific build. Compatibility is package-by-package, never automatic.

FS2004 means Microsoft Flight Simulator 2004: A Century of Flight, commonly called FS9 after its executable. Here, FSX means Microsoft Flight Simulator X, including FSX: Steam Edition; this advice does not apply to Microsoft Flight Simulator 2020 or 2024.

FSX vs FS2004: why is compatibility only partial?

FSX can read several FS2004 formats, but it does not reproduce every FS9 rendering, gauge, scenery and module system. Identical folder names or file extensions therefore do not prove compatibility.

An aircraft model might load while its cockpit remains blank, or an airport BGL might appear while producing duplicate runways and terrain plateaus. Our explanation of the format and simulator differences behind these failures covers the broader FSX vs FS2004 comparison.

Which FS2004 add-ons work in FSX?

Standalone content has the best chance of working; add-ons tied to FS2004 code, default assets or configuration tools have the worst.

How can I check compatibility before installing?

The package description and readme are better evidence than its folder structure. Look for an explicit statement such as FSX compatible, FS2004 and FSX or converted for FSX.

• Prefer a genuine FSX release. A proper conversion may contain rebuilt models, corrected materials, replacement gauges and new configuration files rather than the unchanged FS2004 package.
• Check every dependency. Missing base aircraft, object libraries, effects and gauges can make compatible content look broken.
• Match repaints exactly. The aircraft name is not enough; the repaint must be made for that package and model variation.
• Treat installers separately from content. An old installer can fail to recognise FSX even when the files inside could work after a lawful manual installation.
• Read the licence. Compatibility testing does not automatically grant permission to modify or redistribute somebody else’s work.

Aircraft require checks beyond copying a folder. Our FS2004 aircraft installation and troubleshooting guidance explains the required folder structure, panel references and common selection-menu failures.

Will Orbx FS2004 scenery work in FSX?

An Orbx FS2004 product should be treated as FS2004-only unless its documentation explicitly includes FSX. These products can depend on simulator-specific terrain definitions, object libraries, configuration components and installers; the presence of ordinary BGL files does not make the complete package transferable.

Use the release made for FSX where one exists. Do not copy an entire Orbx FS2004 installation or mix library versions in the hope that FSX will sort out the dependencies, because that can affect other scenery as well as the product being tested.

How should I test an FS2004 add-on safely in FSX?

Test legacy content in isolation and keep a record of every file placed outside its own folder.

1. Extract it into a temporary folder. Inspect the archive and readme before moving anything. Do not merge a complete Flight Simulator 9 directory tree into FSX.
2. Back up files that may be changed. This includes configuration files such as scenery.cfg, module-start files and any default aircraft, traffic or scenery files the package proposes to replace.
3. Install only the required components. A correctly formed aircraft folder belongs under SimObjects\Airplanes; shared gauges and effects belong in Gauges and Effects only when the package specifically requires them.
4. Keep scenery self-contained. Use a separate folder with its own scenery and texture subfolders, then activate it in the Scenery Library. Follow our safe FSX scenery folder and library procedure rather than overwriting default scenery.
5. Test one package at a time. For aircraft, check the exterior, virtual cockpit, 2D panel, controls, lights, animations and sound. For scenery, inspect approaches, runway elevation, ground textures and night lighting.
6. Remove it methodically if problems begin. Delete only the files recorded during installation and restore changed configuration files from backup.

What should an old installer point to?

If an installer asks for the simulator location, its destination must point to the folder containing fsx.exe, not directly to SimObjects or the aircraft folder. For FSX: Steam Edition this is normally an FSX folder inside the chosen Steam library’s steamapps\common directory, although Steam libraries can be placed elsewhere.

An installer that recognises only Flight Simulator 9 may write to the wrong directory or refuse to continue. Very old installers may also be unable to run on 64-bit Windows even though some of their content is usable. Prefer a documented manual method where the package and licence permit one; avoid registry tricks as a first fix.

Why does an FS2004 add-on appear in FSX but not work correctly?

Partial operation usually means FSX recognised the main aircraft or scenery file but could not load one of its supporting components.

• The aircraft is not listed: check for an extra nested folder and confirm that aircraft.cfg, the model folder and the texture folders sit at the expected level.
• The aircraft is listed but invisible or crashes: suspect an incompatible or damaged model rather than repeatedly changing the aircraft configuration.
• Cockpit instruments are blank: the panel is calling a missing or incompatible gauge. Copying unrelated gauges into FSX will not repair FS9-specific compiled code.
• Textures are white or the propeller is opaque: legacy alpha channels and material settings may render incorrectly. Disable the FSX setting labelled Preview DirectX 10 as a diagnostic test; if that fixes the symptom, the add-on still needs corrected FSX materials or textures for reliable use in that mode.
• There is no sound: inspect the sound alias. It may name a default FS2004 aircraft or folder absent from FSX.
• Runways are duplicated or sit in a hole or plateau: disable the scenery and check for conflicting airport, elevation, flatten and exclusion files. Library priority alone cannot repair every FS2004 airport.
• Default AI traffic disappears: search the installed package for an FS2004-format traffic BGL and remove or convert it. Raising the traffic sliders will not solve the format conflict.
• FSX fails during startup or flight loading: remove newly installed gauges, DLL modules, models and BGL files one group at a time. Do not keep accepting an unknown module merely to suppress a warning.

Is FSX: Steam Edition different, and is there a Flight Simulator 2004 Steam edition?

There is no official Flight Simulator 2004 Steam edition; the Microsoft simulator released through Steam is FSX: Steam Edition. Searches for “Flight Simulator 2004 Steam” usually concern running an FS2004 add-on in FSX: Steam Edition.

Ordinary aircraft, textures and scenery have broadly the same compatibility limitations in boxed FSX and Steam Edition. The extra problems are installation paths, registry detection, side-by-side boxed and Steam installations, and executable modules expecting a different FSX setup.

Utilities, weather programs and DLL-based add-ons should explicitly support Steam Edition. Our Steam Edition installer, path and module checks cover those edition-specific problems.

Can a forum fix it, or is new model work required?

Forum instructions can repair a configuration mistake, but they cannot turn incompatible compiled FS2004 code into an FSX-native model, gauge or DLL. Sound aliases, panel references, contact points, texture entries and some scenery placement errors are editable; the underlying binary format is not.

True model work normally requires the author’s source files, suitable development tools and an FSX-specific rebuild. Without those sources, replacing the model or gauge with an authorised FSX component is usually more practical than attempting a conversion. A patch should not be redistributed unless the original licence allows modified files to be shared.

Should I use the FS2004 version or find an FSX version?

Use the FSX-native release whenever one is available, especially for complex aircraft, regional scenery, compiled gauges, utilities and anything that modifies simulator-wide files.

• Test the FS2004 package when it is simple, self-contained, has no FSX alternative and can be removed cleanly.
• Choose the FSX release when you need working virtual cockpits, reliable materials, active support, Steam-aware installation or external modules.
• Keep the add-on in FS2004 when it depends heavily on FS9 gauges, models or scenery libraries and no authorised conversion exists.