Why are my add-on aircraft textures all white in Microsoft Flight Simulator X (FSX)?

Add-on aircraft textures turn all white in FSX when the simulator cannot load the repaint files properly. The usual causes are a bad livery install, a broken texture.cfg fallback, an aircraft.cfg mismatch, DirectX 10 Preview incompatibility, or missing permissions/corrupted texture files.

What causes white aircraft textures in FSX?

In FSX and FSX: Steam Edition, a fully white aircraft usually means the model has loaded but the texture set has not. That is different from a black aircraft, a missing aircraft, or a low-resolution blurry aircraft. White textures nearly always point to a texture lookup problem rather than a flight model problem.

The most common causes are:

• Incorrect repaint installation — the texture folder was copied to the wrong aircraft, or not all files were extracted.
• Wrong texture= entry in aircraft.cfg — FSX is looking for a folder name that does not exist.
• Broken texture.cfg fallback — the repaint relies on shared textures from another folder, but the fallback path is wrong.
• DX10 Preview issues — some older aircraft and repaints do not display properly with the DirectX 10 Preview option enabled.
• Missing base package files — you installed a repaint that needs the original aircraft model and common texture files, but only the repaint was installed.
• Permissions or archive issues — files were blocked, partially extracted, or placed in a protected folder incorrectly.
• Corrupt or unsupported texture files — less common, but possible with badly packaged older add-ons.

How do I fix white add-on aircraft textures in FSX?

1. Work out whether the problem affects one repaint or every add-on aircraft. Load a default FSX aircraft first, then another add-on aircraft, then the specific repaint showing white. If only one repaint is white, the issue is usually inside that aircraft's texture installation. If every add-on aircraft is white, look harder at DX10 Preview, permissions, or a broader installation problem.

2. Check the repaint folder name against aircraft.cfg. Open the aircraft's aircraft.cfg file and find the relevant [fltsim.x] entry. The line texture= must match the suffix of the texture folder exactly.

   For example, if the folder is texture.BA, the entry should be texture=BA. If the folder is named slightly differently, or has an extra space, FSX will often show a white aircraft.

3. Make sure the repaint files are actually inside the texture folder. A correct repaint folder should contain the texture files themselves, not another folder nested inside it. A common mistake is ending up with something like texture.BA\texture.BA\ after extracting a ZIP archive. FSX will not look that deep.

4. Inspect texture.cfg if the repaint uses shared textures. Many aircraft repaints do not include every texture file. Instead, they use a texture.cfg file that tells FSX to fall back to a common texture folder. If that fallback path is wrong, the model loads but the surfaces appear white.

   Open texture.cfg and check the fallback entries. They must point to real folders that exist in that aircraft package. If the repaint was meant for a different variant or a different developer's base model, the fallback often breaks.

5. Disable DirectX 10 Preview and test again. This is one of the biggest causes with older FSX aircraft. In the FSX display settings, turn off the DirectX 10 Preview option, restart the sim, and reload the aircraft.

   If the textures appear normally with DX10 Preview off, the aircraft or repaint is not fully compatible with that rendering mode. In that case, either keep DX10 Preview disabled for that aircraft or use a version of the aircraft known to work properly in standard DX9 mode.

6. Confirm you installed the full base aircraft, not just a repaint. Many repaints are upload packages that contain only livery files. They assume you already have the original aircraft installed. If the aircraft model, shared texture folder, or model-specific files are missing, the repaint can appear white even though it shows in the menu.

   This catches people often with freeware repaints for older airliners, military aircraft, and packages with several model variants.

7. Reinstall the aircraft and repaint cleanly. Remove the broken repaint entry from aircraft.cfg, delete the suspect texture folder, then reinstall using a fresh archive. If needed, start from a clean base aircraft installation before adding the repaint again.

   If you need a fresh package, use a clean copy from our FSX downloads library at https://flyawaysimulation.com/downloads/.

8. Check Windows permissions if FSX is installed in a protected location. Older FSX installs under Program Files can behave awkwardly with manual file copying. Files may appear to copy but end up redirected or blocked. Make sure the repaint folders and edited configuration files are really inside the active simulator folder.

   If changes do not stick, edit and copy files with administrator rights and verify you are not accidentally changing a backup copy or a virtualised location.

9. Test with lower texture load and fewer heavy add-ons. FSX is a 32-bit simulator, and very heavy aircraft, large AI packages, or high-resolution textures can trigger texture loading problems. White textures are not the most common memory symptom, but they can appear when the sim is under strain.

   If the problem only happens at dense add-on airports or after a long session, reduce texture resolution, AI traffic, and other memory-hungry scenery, then test again.

Is this a repaint problem or an FSX graphics problem?

What should the aircraft folder look like?

For a normal FSX aircraft installation, we expect to see the aircraft's main folder containing the model, panel, sound and texture folders, plus the aircraft.cfg file. Each repaint should be in its own texture folder, and the folder suffix should match the corresponding [fltsim.x] entry.

If the repaint relies on shared textures, the repaint folder may contain only a few files plus texture.cfg. That is normal. What matters is that the fallback lines point to folders that are actually present.

Why does DX10 Preview make aircraft go white in FSX?

FSX's DirectX 10 Preview mode was never fully trouble-free with older content. A lot of aircraft were built for the standard rendering path, and some materials, alpha channels, bump maps or texture formats do not behave properly in DX10 Preview. The result can be white fuselages, missing cockpit textures, transparent parts showing wrongly, or flashing surfaces.

If turning DX10 Preview off fixes the issue immediately, you have found the cause. That does not mean the aircraft is broken; it usually means the aircraft was not designed for that display mode.

What if only the cockpit or only parts of the aircraft are white?

That usually narrows things down further:

• White exterior only often means the repaint texture folder or fallback is wrong.
• White virtual cockpit only points more towards missing panel textures, shared cockpit textures, or a DX10 material issue.
• White propeller disc, windows or shine layer often suggests an alpha or material compatibility problem rather than a completely missing repaint.

In those cases, compare the broken aircraft folder against a working repaint of the same aircraft. Differences in a few texture files or one texture.cfg line are often the giveaway.

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

1. Disable DX10 Preview. Then restart FSX fully.

2. Test a known-good add-on aircraft. If it is still white, the issue is broader than one repaint.

3. Check the simulator folder you are editing is the real active one. This matters especially if you have both boxed FSX and FSX: Steam Edition installed, or old backup copies.

4. Reinstall one aircraft from scratch. Choose a simple add-on with a complete package, not just a repaint-only download.

Quick checklist for white textures in FSX

• texture= matches the texture folder name
• No extra nested folders after extraction
• texture.cfg fallback paths are valid
• The base aircraft package is installed, not just the repaint
• DX10 Preview is disabled for testing
• Files were copied into the active FSX installation
• Permissions are not blocking edits
• Heavy memory use is not overwhelming texture loading

If we had to pick the most likely fix, it would be this: check the repaint's folder name, the matching aircraft.cfg entry, and any texture.cfg fallback file. In plain terms, white aircraft in FSX nearly always mean the sim cannot find the textures it expects to load.