Learn which FSX repaint downloads match your add-on aircraft, how to verify the developer and model variant, and why compatible liveries fail.
FSX and FSX: Steam Edition repaint downloads are compatible only when they were made for the exact base aircraft, developer and model variant you own. Match the repaint’s stated requirement, not merely the aircraft type; a livery for one developer’s Boeing 737, for example, will not fit another developer’s 737.
How do I check whether an FSX repaint is compatible?
The download description or included readme should name the required base aircraft explicitly. Before installing anything, check these four details:
- Required base package: Look for the aircraft developer, product name and any required expansion or update. A ZIP containing a
texture.namefolder and an[fltsim.x]entry is normally a texture-only repaint, not a flyable aircraft by itself. - Aircraft developer: The real-world aircraft name is not enough. Models of the same aeroplane made by different developers usually have different texture layouts, file names and surface mapping.
- Model variant: Match details such as passenger or freighter, wheel or float, long or short fuselage, engine type and virtual-cockpit version. A repaint can display misplaced markings or white sections when applied to the wrong variant from the same product.
- Supported simulator: Prefer a package that explicitly lists FSX. FS2004, Prepar3D and MSFS texture sets should not be treated as FSX-compatible unless the author says they support the same FSX base model.
| What the repaint listing says | Likely result in FSX |
|---|---|
| Exact developer, aircraft package and variant match | Compatible |
| Same aircraft type but a different developer | Not compatible |
| Exact FSX base model used in FSX: Steam Edition | Usually compatible; installation paths may differ |
| FS2004 or Prepar3D repaint with no FSX support stated | Do not assume compatibility |
| Texture-only download with no base aircraft installed | Will not work until the required aircraft is installed |
What does a correctly labelled repaint look like?
A good listing identifies the dependency rather than describing the download as simply an “A-7 repaint” or “C-117 livery”. For example, this CAG-colour A-7 texture package states that it requires the payware RAZBAM LTV A-7 Corsair II.
The same rule applies to freeware aircraft. This RAF C-117D repaint requires Manfred Jahn’s specific freeware C-117D package. Whether the base aircraft is free or payware has no bearing on compatibility; its 3D model and texture mapping do.
Do FSX repaints work in FSX: Steam Edition?
Repaints made for an FSX aircraft normally work in FSX: Steam Edition when the same base aircraft is compatible and installed there. The texture and aircraft.cfg structure is fundamentally the same.
The usual obstacle is an old automatic installer searching for the boxed FSX directory. For a manual installation, place the repaint inside the actual aircraft folder under Steam Edition’s SimObjects\Airplanes directory and add the supplied configuration entry. Our FSX livery installation instructions cover that process without duplicating it here.
Can I rename a repaint to make it fit another aircraft?
No; renaming the texture folder or its files does not make a repaint compatible with a different model. The artwork is positioned against the original model’s UV mapping, so another developer’s model may place a fuselage texture on the wings, show blank surfaces or ignore the files entirely.
Compatibility across several variants is possible when their developer deliberately reused the same mapping. The repaint documentation should list those supported variants. Otherwise, adapting it requires a new repaint made from the correct paint kit, not a folder-name change.
Why does a compatible repaint not appear in FSX?
A repaint that matches the aircraft can still remain hidden because of an installation or aircraft.cfg error. Check the following before deciding that the download is incompatible:
- The
texture.namefolder sits directly inside the correct aircraft folder, not inside an extra nested directory. - The supplied
texture=value matches the suffix of that texture folder. - The
[fltsim.x]sections are numbered sequentially without gaps. - Every
title=value is unique. - The
model=value points to the intended model variant. - FSX’s aircraft selection screen is set to show all available variations.
If the livery appears in the menu but the aircraft is completely or partly white, the likely causes are missing shared textures, an incorrect fallback path or a genuine model mismatch. Use our white add-on aircraft texture checks to separate those faults from basic repaint compatibility.