Are FS2004 add-ons compatible with FSX? Learn what works, what breaks, and how to test aircraft, scenery, gauges and AI traffic safely.
FS2004 add-ons are not universally compatible with FSX or FSX: Steam Edition. Some aircraft, scenery and textures work after manual installation, but older gauges, modules, effects and installers often fail. Use a package explicitly marked for FSX whenever possible; otherwise, back up FSX and treat each add-on as a conversion test, not a guaranteed installation.
FSX retained partial support for Flight Simulator 2004, also called FS9, but the two simulators do not use identical rendering, scenery, gauge and module systems. Our breakdown of the FS2004-to-FSX format changes explains why copying an add-on is sometimes successful and sometimes produces only a partly working result.
Which FS2004 add-ons work in FSX?
| Add-on type | Typical compatibility | Main limitation |
|---|---|---|
| Aircraft | Mixed | FSX can display many FS2004 aircraft models, but panels, gauges, animations, lighting and propeller effects may fail. |
| Scenery | Often partial | Legacy scenery files may load, while airport elevations, exclusions, coastlines, autogen and object libraries can conflict with FSX. |
| Repaints | Only with the correct base model | An FS2004 repaint cannot be applied to a different FSX model merely because it represents the same aircraft. |
| Sounds and effects | Sometimes | The files may be usable, but aliases, folder paths and configuration references must point to resources available in FSX. |
| Gauges and panels | Mixed to poor | XML gauges are generally more portable than older compiled gauges. Missing libraries or simulator-specific code can leave instruments blank. |
| AI aircraft and traffic | Mixed | Aircraft may display, but FS2004-format traffic schedules can interfere with FSX-native traffic files. |
| Utilities and modules | Low | Programs that connect to the simulator or load through configuration files normally require a dedicated FSX build. |
How can I check compatibility before installing?
The package description and readme are more reliable than the folder structure. Look for an explicit statement such as FSX compatible, FS2004 and FSX or converted for FSX. A package containing aircraft.cfg, scenery BGL files or familiar texture folders is not automatically compatible.
- Prefer an FSX-specific release. A genuine conversion may include rebuilt models, corrected materials, replacement gauges and revised configuration files.
- Check required dependencies. Missing base aircraft, object libraries, gauges or effects can make a compatible add-on appear broken.
- Do not trust the installer alone. An old installer may recognise only the Flight Simulator 9 registry entry or install into the wrong directory.
- Check the repaint model. Texture names, model geometry and texture mapping must match the exact aircraft package for which the repaint was made.
Aircraft need several checks beyond copying their folder into SimObjects\Airplanes. We cover those separately in our aircraft-specific installation and compatibility instructions.
How should I test an FS2004 add-on safely in FSX?
- Back up affected files. Preserve any configuration file the package intends to replace, especially scenery, traffic and simulator-start configuration files.
- Extract into a temporary folder. Inspect the archive before moving anything. Do not merge its complete Flight Simulator 9 folder tree into FSX.
- Install one package at a time. Keep a record of every file copied outside the add-on's main folder, including gauges, effects and texture libraries.
- Test in a simple flight. For an aircraft, inspect the exterior, virtual cockpit, instruments, lights, animations and sound. For scenery, check the airport from several directions and at different times of day.
- Remove the package if errors begin. Delete only its recorded files and restore the backups rather than reinstalling FSX.
Scenery should normally be kept in its own folder and added through the FSX scenery library. Our FSX scenery installation procedure covers folder layout, activation and scenery-library priority.
Why does an FS2004 add-on appear in FSX but not work correctly?
Partial compatibility is common because FSX may recognise the add-on's main file while failing to load one of its supporting components.
- Blank or frozen cockpit instruments: the panel references a missing or incompatible gauge. Copying unrelated gauges into the FSX Gauges folder will not repair simulator-specific code.
- White textures or an opaque propeller disc: legacy texture formats, alpha channels and material settings may render incorrectly, particularly with the optional DirectX 10 preview enabled.
- Missing sounds: the aircraft may alias a default FS2004 aircraft or sound folder that does not exist in FSX.
- Terrain spikes, plateaus or duplicate runways: an older airport may conflict with FSX elevation, flatten or exclusion data.
- Default AI traffic disappears: an active FS2004-format traffic BGL can suppress FSX-format traffic. Convert or remove the old schedule rather than increasing the traffic sliders.
- FSX crashes while loading the add-on: suspect an incompatible model, gauge, module or damaged BGL. Remove components methodically instead of continuing to load the same flight.
Is FSX: Steam Edition compatibility different?
FSX: Steam Edition has broadly the same content compatibility as boxed FSX, but old installers and executable modules are more troublesome. They may search for a boxed-FSX registry entry, write to the wrong path or expect configuration entries that Steam Edition stores differently.
Ordinary aircraft and scenery can often be installed manually. Utilities, weather engines, DLL modules and other programs that connect directly to FSX should have explicit Steam Edition support; our guide to boxed FSX and Steam Edition add-on differences explains the extra checks.
Can an incompatible FS2004 add-on be converted?
Some problems can be corrected, but editing configuration files is not a complete conversion. Paths, sound aliases, panel references and aircraft contact points can be adjusted; an incompatible binary aircraft model, compiled gauge or DLL generally needs source files and an FSX-specific rebuild.
Scenery and traffic files are sometimes convertible with suitable tools, while a complex aircraft may require replacement gauges, new materials and model work. Choose a documented FSX conversion when one exists, and do not redistribute a modified package unless its licence permits it.