FSX repaints not showing? Fix texture folders, aircraft.cfg numbering, model references, hidden variations, white textures and Steam paths.
Default aircraft repaints fail to appear in FSX or FSX: Steam Edition when the texture folder is in the wrong aircraft, the repaint has no valid sequential [fltsim.n] entry in the active aircraft.cfg file, its model references are incompatible, or selection filters hide variations. Correct those points, save the file, and restart FSX.
How do I make FSX repaints appear?
Install the texture folder inside the correct default aircraft, register it in that aircraft's configuration file, and enable all variations in the aircraft selector.
- Find the installation you actually use. Open the active FSX installation and go to
SimObjects\Airplanes. For FSX: Steam Edition, use Steam's installed-files option rather than assuming where the library is located. If boxed FSX and Steam Edition are both installed, editing the wrong copy is a common reason a repaint does not appear. - Back up aircraft.cfg. Copy the relevant aircraft's
aircraft.cfgoutside the simulator directory before editing it. File verification, repairs and replacement configuration files can remove custom repaint entries. - Confirm that the repaint matches the exact model. A repaint for the default FSX Boeing 737-800 belongs in the default
B737_800folder. It will not automatically work on an add-on 737, another 737 variant or an FS2004 model, even if the aircraft name looks similar. Repaints for expansion aircraft also require the corresponding aircraft to be installed. - Place the texture folder at the correct level. A folder such as
texture.MyLiverymust sit beside the aircraft'saircraft.cfg,model,panelandsoundfolders. Open it and check that the DDS or bitmap files are directly inside; extraction tools sometimes create an unwanted secondtexture.MyLiveryfolder. - Add the supplied configuration block. Paste the repaint's
[fltsim.X]section below the existing variations inaircraft.cfg. ReplaceXwith the next number in the sequence. If the final section is[fltsim.5], use[fltsim.6]. - Check the repaint-specific values. Give the entry a unique
title=, settexture=to the texture-folder suffix, and add a usefului_variation=name. Copysim=,model=,panel=,sound=and the menu classification fields from a working variation of the same aircraft unless the repaint documentation explicitly requires another installed model variant. - Save the real CFG file. Protected installation directories may require administrator approval. Reopen the file after saving and confirm that the new block remains present. Also verify that Windows has not created
aircraft.cfg.txtinstead ofaircraft.cfg. - Restart FSX and reveal every variation. Configuration changes made while FSX is open are not reliably reflected until it restarts. In the aircraft-selection screen, enable Show all variations and clear manufacturer, publisher and aircraft-type filters.
For a worked example of the folder suffix and sequential numbering, use our step-by-step FSX livery installation instructions. Merge the supplied block into your existing file; do not overwrite the whole aircraft.cfg, as that can remove other installed repaints.
Which aircraft.cfg entries can stop a repaint from showing?
FSX can omit or misfile a repaint when its section number, title, resource references or aircraft-selection labels are invalid.
| Entry | What FSX expects | Typical mistake |
|---|---|---|
[fltsim.n] | An unbroken sequence beginning with [fltsim.0] | A duplicate number, a gap, or leaving X in the heading |
title= | A unique title for the installed variation | Reusing the title of another aircraft or repaint |
sim= | The base aircraft's .air filename without the extension | Copying the value from a different aircraft package |
model= | The suffix of the required model.suffix folder, or blank for the plain model folder | Referring to a model variant that is not installed |
texture= | The part after texture.; for texture.MyLivery, enter texture=MyLivery | Entering the full folder name or naming a different suffix |
ui_manufacturer=, ui_type= and ui_variation= | Menu labels consistent with the base aircraft | Filing the repaint under an unexpected manufacturer, type or variation name |
The safest repair for an incomplete or outdated repaint entry is to duplicate a working [fltsim.n] section from the same default aircraft. Change only its section number, title=, texture=, ui_variation= and any repaint-specific identification values.
Why is the livery still not showing after installation?
If no new variation appears after restarting FSX, determine whether the configuration was ignored, the aircraft was filed elsewhere, or the entire default aircraft is missing.
- No new variation appears: reopen the active
aircraft.cfg. Check that the entry was saved, its number immediately follows the previous section, itstitle=is unique, and the section heading still has both square brackets. - The repaint appears under the wrong name: correct
ui_manufacturer=,ui_type=andui_variation=. The texture folder's name does not automatically become the name shown in the selector. - The entry disappears after a repair or file verification: the original default
aircraft.cfgmay have been restored. Confirm that the texture folder remains installed, then reinsert your backed-up[fltsim.n]section using the next available number. - Only one paint scheme is visible: enable Show all variations. This option can conceal correctly installed liveries while leaving the main aircraft visible.
- Every default aircraft is absent: that is a simulator-wide problem rather than a single repaint fault. Follow our checks for restoring default aircraft missing from the FSX selector.
Why is the repaint listed but white, blank or incomplete?
A repaint that is listed but renders incorrectly has passed the aircraft-selection stage; the fault is now in its texture files, fallback paths or model compatibility.
- No preview picture: place a valid
thumbnail.jpgdirectly inside the repaint's texture folder. A missing thumbnail does not prevent the aircraft from being selected or flown. - White or grey surfaces: confirm that every downloaded texture was extracted and that any
texture.cfgfallback points to the correct shared texture folder. Many repaints contain only the files changed by the artist and depend on default textures for the remaining surfaces. - The default paint appears instead: check that
texture=names the intended folder suffix and that the files are not nested one folder too deep. - Markings are distorted or misplaced: the repaint was made for another model or texture mapping layout. Changes to
aircraft.cfgcannot adapt it to different geometry. - The fault occurs only in DirectX 10 Preview: test with that preview option disabled. Older texture sets can expose rendering compatibility problems there, although missing files and broken fallback paths should still be checked.
Our missing-texture and fallback-path troubleshooting guide covers the white-aircraft problem in more detail.
Can a default-aircraft repaint use its own Airplanes folder?
A texture-only repaint cannot normally work as a separate aircraft because it lacks its own model, flight model and complete configuration.
Install it inside the existing default aircraft folder and register it as another [fltsim.n] variation. Use a separate folder under SimObjects\Airplanes only when the download is a complete aircraft package containing its own aircraft.cfg, compatible .air file, model folder and supporting files.