Why are textures missing in FSX, and how do I fix them?

Missing textures in FSX or FSX: Steam Edition mean the simulator cannot find, map or render the required image files. Identify whether one livery, an entire aircraft, one scenery area or all default content is affected; then correct the folder path, configuration reference, shared-texture fallback or DX10 Preview setting.

Match the missing texture symptom to its cause

The smallest consistently affected item usually identifies where the fault lies.

Blurry textures are not genuinely missing. Use our guide to diagnosing soft and slowly loading FSX textures instead of reinstalling files that are already present.

What does a grey surface or @TexturesMissing mean?

A flat grey surface accompanied by @TexturesMissing usually indicates that FSX loaded the model or scenery geometry but could not resolve the material’s intended texture.

@TexturesMissing is associated with the missing-texture placeholder; it is not normally the artwork the add-on was meant to supply. Do not rename that placeholder or copy it over other files. Find the required filename in the add-on’s documentation or error information, then search the aircraft, scenery and shared texture folders for the real file.

If the named image exists but the surface is still grey, check its folder mapping and test with DX10 Preview disabled. A present file can still be inaccessible because the configuration points elsewhere, the archive created an extra nested directory, or the material is incompatible with the selected renderer.

I didn’t see the Steam\steamapps\common\FSX folder — where is it?

The correct Steam common folder is the library containing the active FSX installation, and it may be on a different drive from Windows or the Steam application itself.

A common location is C:\Program Files (x86)\Steam\steamapps\common\FSX, but another Steam library might use a path such as D:\SteamLibrary\steamapps\common\FSX. In Steam, open FSX’s installed-file options and use the command to browse its local files. The folder that opens should contain fsx.exe, SimObjects, Scenery and Texture.

steamapps\common is only the parent folder for installed Steam games. Aircraft files belong below FSX\SimObjects\Airplanes, not directly inside common. Do not create a second FSX directory merely because an installer proposed the wrong location.

Boxed FSX uses a separate Microsoft Flight Simulator X installation folder. When boxed FSX and Steam Edition have both been installed, older add-on installers can follow a stale path. Always verify the destination against the folder containing the fsx.exe you actually run.

How do I fix missing aircraft textures in FSX?

Missing aircraft textures are usually repaired by correcting the aircraft’s folder structure, repaint registration or shared-texture fallback.

1. Open the active installation. For Steam Edition, use Steam’s browse-local-files command rather than assuming the drive. For boxed FSX, locate the folder containing its active fsx.exe.
2. Check the aircraft folder depth. The aircraft’s main directory should sit directly under SimObjects\Airplanes and contain aircraft.cfg alongside its model, panel, sound and texture folders. A structure such as AircraftName\AircraftName\aircraft.cfg is one level too deep.
3. Match the repaint suffix. Back up aircraft.cfg, then inspect the affected [fltsim.x] section. A line reading texture=BA selects the folder texture.BA; an empty texture= value selects the plain texture folder. Do not write texture=texture.BA.
4. Inspect the repaint files. Confirm that the expected .dds or .bmp files are inside the selected texture folder rather than another nested directory. Texture filenames are defined by the aircraft model, so renaming images to something that looks more logical will not fix them.
5. Check texture.cfg fallbacks. An incomplete repaint may intentionally contain only its unique paint files and obtain common cockpit, wing or detail textures from a base folder. Verify that every fallback. path leads to an existing directory. The paths are relative, and a repaint made for a separate base aircraft will not work without that aircraft.
6. Restore the original package. Re-extract a complete archive or reinstall the required base aircraft. Do not convert textures at random: an unsuitable conversion can remove alpha channels, mipmaps or night lighting while leaving the filename unchanged.
7. Restart FSX and load the exact affected livery. FSX should be closed while configuration files and folders are changed. Testing another paint scheme does not prove that the repaired [fltsim.x] entry works.

A repaint does not require texture.cfg when it already contains every needed image. Conversely, copying a fallback file from an unrelated aircraft can direct FSX to plausible-looking but incorrect textures. If the whole aircraft remains white, follow our repaint-specific checks for completely white add-on aircraft.

Should I use Ctrl+F or Cmd+F to find the texture entry?

On the Windows PC running FSX, use Ctrl+F in Notepad to find texture= in aircraft.cfg or fallback. in texture.cfg.

Cmd+F is the macOS equivalent and is relevant only if you are reading a copied file on a Mac. If the search finds no texture.cfg, that is not automatically an error: a complete texture folder may not need one. If there is no matching texture= line in the affected repaint section, repair that entry rather than adding an arbitrary fallback.

Why do textures disappear with DirectX 10 Preview?

DX10 Preview can make older FSX aircraft materials appear white, black, transparent or incomplete even though all required files are installed.

1. Turn off DX10 Preview in FSX’s display settings.
2. Close FSX completely so the renderer is restarted.
3. Reload the same aircraft, livery, location and time of day.

If the textures return, the folder installation is intact and the add-on has a DX10 compatibility problem. Reinstalling the same package or deleting FSX.cfg will not make an older material compatible. Keep DX10 Preview disabled for that content unless the package supplies an appropriate update.

How do I restore missing scenery textures?

Missing scenery textures are fixed by restoring the scenery package’s texture directory, registering its parent folder correctly and installing any required object libraries.

1. Check the directory structure. A conventional scenery package has sibling folders such as MyScenery\scenery and MyScenery\texture. The Scenery Library entry points to MyScenery, not directly to either child folder.
2. Re-extract the complete archive. Make sure the texture folder was not omitted, left empty or placed one level too deep. Extracting only the BGL files from the scenery folder leaves the geometry present but its surfaces untextured.
3. Check required dependencies. If only certain terminals, vehicles, trees or signs are grey, the airport may be calling objects from a separate library. Install the dependency named by the package rather than searching for unrelated replacement bitmaps.
4. Confirm the scenery is active. If its entry disappeared or points to an old folder, use our steps for rebuilding missing FSX Scenery Library entries. Restart FSX after changing the library.
5. Test for a package conflict. Temporarily disable the affected add-on and restart FSX. If the default airport or ground returns normally, the fault is inside that scenery package, its registration or one of its dependencies.

Scenery priority decides which overlapping BGL content takes precedence, but changing priority cannot restore image files that are physically absent. Missing water everywhere is also a different core or rendering fault from one airport’s absent texture folder.

When should I verify the FSX Steam Edition files?

Verify Steam files when default FSX aircraft or scenery are missing across several locations, not when a single third-party repaint is broken.

1. Back up modified default files and custom configuration. Verification can replace altered files that belong to the standard installation.
2. Open FSX’s properties in Steam. Under the installed-files options, run the integrity verification command.
3. Let Steam restore damaged core files. This repairs files supplied with FSX: Steam Edition; it does not reconstruct an incomplete third-party add-on or correct its aircraft.cfg.
4. Recheck security software if files vanish again. Review quarantine records for the known package rather than disabling protection globally.

For boxed FSX, use the original installer or media’s repair facility after backing up add-ons. Reinstalling the whole simulator should be a last resort because a wrong repaint suffix, absent dependency or bad scenery registration will remain wrong afterwards.

Should I delete FSX.cfg to fix missing textures?

No. Rebuilding FSX.cfg does not restore missing image files, repair an incorrect texture= line or fix a broken fallback path.

Rename the file as a late diagnostic test only when default content is affected and the evidence points to a damaged display configuration. FSX will create a fresh configuration at the next start, so expect to restore graphics, control and other customised settings. Keep the renamed original as a backup.

Still not working after every step?

If none of the fixes worked, isolate the fault by testing default and add-on content separately with DX10 Preview disabled.

Change one item at a time and reload the same test situation. Moving the aircraft, changing the livery, enabling DX10 Preview and reinstalling files simultaneously makes it impossible to tell which change solved or concealed the original missing-texture problem.