Why are my FSX add-on aircraft textures all white?

In FSX and FSX: Steam Edition, an add-on aircraft appears all white when its model loads but required textures do not. The usual causes are a mismatched aircraft.cfg texture entry, misplaced files, a broken texture.cfg fallback, a repaint installed without its base aircraft, or incompatibility with DirectX 10 Preview.

What do all-white aircraft textures mean in FSX?

An all-white aircraft usually means FSX found the model but could not find, read or correctly render one or more texture files assigned to it. It is a texture-loading fault, not normally a problem with the flight model.

This differs from an aircraft that is absent from the selection menu, completely invisible, replaced by the wrong model or briefly blurry while higher-detail textures load.

• Wrong texture= value — the selected [fltsim.x] block points to a texture folder that does not exist.
• Incorrect or incomplete extraction — texture files are missing, installed under an extra nested folder or copied into another aircraft.
• Wrong base model — the repaint was made for a different developer's model or a different variant of the same aircraft type.
• Missing base aircraft — the download contains only a repaint and expects common textures and model files from a separate aircraft package.
• Broken texture.cfg fallback — the repaint relies on shared textures, but the path to them is wrong or the shared folder is absent.
• DirectX 10 Preview incompatibility — older FSX models and materials may appear white, partly white or lose transparency under this renderer.
• Wrong FSX installation — files were added to boxed FSX while FSX: Steam Edition is running, or the reverse.
• Damaged or incompatible files — a corrupt archive, failed copy or unsuitable texture format can prevent an otherwise correct repaint from loading.

How should aircraft.cfg and texture.cfg match?

FSX must be able to trace the selected [fltsim.x] entry to a real texture folder and then to any shared texture folders used by that repaint. A break anywhere in that chain can leave the model white.

What should the FSX aircraft folder look like?

A normal fixed-wing add-on sits under SimObjects\Airplanes\AircraftName\. Its main folder should contain aircraft.cfg and usually folders named model, panel, sound and texture, possibly with variant suffixes such as model.1 or texture.BA.

The texture files must be directly inside their texture folder. A common extraction mistake is creating texture.BA\texture.BA\; FSX will not search that extra level. Our guide to placing FSX model, panel, sound and texture folders correctly shows the complete aircraft structure.

How does the texture= entry work?

The value after texture= must match everything after texture. in the folder name. For example, texture.BA requires texture=BA. The unsuffixed folder texture normally uses an empty texture= value.

Spaces and punctuation are part of the suffix and must match; letter case is not normally significant on Windows. Also confirm that the repaint's model= value selects the model variant for which it was painted. Back up aircraft.cfg before editing it, keep each [fltsim.x] number unique and do not add the folder name or a file extension to texture=.

For a worked explanation of this relationship, see our guide to adding repaint folders and matching [fltsim.x] entries.

What does texture.cfg do?

A sparse repaint folder is not necessarily incomplete. Many liveries contain only the painted exterior files and use texture.cfg to borrow cockpit, propeller, glass and detail textures from a shared folder.

Fallback entries are relative paths. For example, fallback.1=..\texture points from the repaint folder back to a sibling folder named texture. The folder containing the required shared files must actually exist, and the number of ..\ levels must be correct.

Do not copy fallback lines from an unrelated aircraft: its folder names and required texture files may differ. If texture.cfg was created manually, enable file-name extensions in Windows and confirm that it has not been saved as texture.cfg.txt.

How to fix white FSX add-on aircraft textures

The quickest reliable fix is to test the repaint, folder mapping and shared textures in that order before changing broader FSX settings.

1. Establish the scope. Load a default FSX aircraft, a known-working add-on and another repaint of the affected aircraft. One white repaint points to its folder or configuration; every repaint of one aircraft points to missing shared files; many older add-ons failing together suggests DirectX 10 Preview or an installation-wide problem.
2. Confirm the exact base model. Match the repaint to the named add-on aircraft and model variant, not merely the real-world aircraft type. A livery for one model cannot be transferred to another model of the same aeroplane. If the download is repaint-only, install its required base aircraft first.
3. Inspect the extracted files. Open the affected texture... folder and remove any accidental extra folder level. Check that the archive was fully extracted rather than opened and copied piecemeal, and make sure the files were not placed in a similarly named backup or variant folder.
4. Correct the configuration. With FSX closed, compare the folder suffix with texture=, verify the supplied model= value and inspect any fallback paths in texture.cfg. Compare a broken livery with a working repaint of the same aircraft; one missing file or changed path often reveals the fault.
5. Test without DirectX 10 Preview. Untick Preview DirectX 10 in the FSX display settings, exit the simulator completely and reopen it. If the textures return, use the standard renderer or a version of the aircraft and textures explicitly made for the DX10 path.
6. Verify the active simulator folder. Find the folder containing the fsx.exe that is actually running and confirm the aircraft is under that installation's SimObjects\Airplanes folder. Boxed FSX, FSX: Steam Edition and custom Steam libraries can all use different roots. Our explanation of FSX add-ons under Steam Edition covers the compatibility and path traps.
7. Check whether Windows accepted the copy. Installations under protected folders may block a manual copy or redirect an edit to the Windows VirtualStore. Reopen the active aircraft folder and verify that the expected files and changes are physically present; do not rely only on an installer reporting success.
8. Reinstall cleanly if necessary. Back up any custom changes, remove the broken repaint folder and its matching [fltsim.x] entry, then extract a fresh copy. If common textures are missing, restore the complete base aircraft before adding the repaint again rather than repeatedly pasting files over a damaged installation.

Is the repaint, DX10 Preview or the whole installation at fault?

The pattern of affected aircraft usually identifies where to start looking.

If every add-on aircraft is white, what should I do first?

When every add-on is affected, disable DirectX 10 Preview, restart FSX and verify that the files are installed beside the active copy of fsx.exe. Reinstalling individual liveries before making those checks wastes time.

If default aircraft are white as well, stop editing repaint configuration files. That broader symptom points to the simulator's renderer or installation rather than an individual texture= entry.

What if only the cockpit, windows or propeller are white?

Partially white components usually identify the missing texture group more precisely than an entirely white exterior.

• White exterior with a normal cockpit usually means the livery files are missing, misnamed or assigned to the wrong model.
• White virtual cockpit across several repaints usually points to shared cockpit textures missing from the base aircraft or an incorrect fallback path.
• White windows, propeller discs or reflective layers often indicate a missing texture with transparency information, a damaged alpha channel or a material that does not behave correctly under DirectX 10 Preview.
• One white wing, engine or tail section usually means the model calls a separate texture file that the repaint does not contain and cannot find through its fallback.

Compare the failed repaint with a working livery for the exact same model. Do not copy random files from a different aircraft, even when their names look similar.

Why do the textures turn white only after a long session?

Textures that load correctly at first but fail later are more likely to reflect resource pressure than a permanent repaint error. FSX is a 32-bit application with finite address space, and complex scenery, heavy AI traffic and numerous high-resolution textures can exhaust the resources available during a long session.

Restart FSX and load the same aircraft at a simple default airport. If it appears normally, reduce texture resolution, scenery complexity or AI load one variable at a time. A true resource-related failure tends to affect several textures or aircraft and clears after a restart; a repaint that is white on the first clean load still needs its files and configuration corrected.