Why are static aircraft completely black in FSX?

Static aircraft turn completely black in FSX or FSX: Steam Edition when the model loads but its materials cannot use the intended textures. The usual causes are missing or misplaced texture files, mismatched object-library versions, or an FS2004-era model that is incompatible with DirectX 10 Preview. Restore the complete package, then test DirectX 9.

How can I tell what is making static aircraft black?

The scope and timing of the fault usually reveal whether the problem is an installation error, an AI livery issue or an incompatible model.

If the aircraft is solid black but its shape, reflections or windows remain visible, FSX has loaded the geometry and failed at the material or texture stage. A dark silhouette seen only at night is a different problem.

How do I fix completely black static aircraft in FSX?

Fix the package structure and texture references first; graphics drivers and shader files are not the starting point when only one airport or aircraft library is affected.

1. Test in daylight. Set the flight to noon with clear weather, reload it and inspect the aircraft from several directions. If the proper colours return, the main daytime texture works and the problem is confined to night lighting or materials.
2. Determine whether it is scenery or AI traffic. Set both airline and general-aviation traffic density to zero, then reload the flight. A scenery object remains fixed at the airport; normal AI disappears. An external traffic injector may need to be paused separately. For AI, use our guide to finding the active FSX aircraft folder in boxed and Steam installations.
3. Check the active scenery folder structure. A conventional package contains files such as Addon Scenery\<package>\Scenery\*.bgl and Addon Scenery\<package>\Texture\*.bmp or *.dds. The Scenery Library entry normally points to the package root containing both folders, not directly to its Scenery subfolder. Custom locations are valid, but the folder relationship must remain intact.
4. Remove accidental extra folder levels. Archives often extract as <package>\<package>\Scenery. If FSX is pointed at the outer folder, the real texture directory may not be searched. Geometry can also load when somebody has copied only the BGL into an active folder and left its textures elsewhere.
5. Reinstall the complete matching release. Back up any personal changes, move the old package outside active scenery, and extract the FSX edition again. Do not combine a library BGL from one release with textures from another, or mix files labelled for FS2004, FSX and Prepar3D unless the package instructions explicitly require it. Our detailed FSX missing-texture checks cover nested folders, incomplete archives and broken fallback paths.
6. Look for duplicate object libraries. A mistake we see repeatedly is the same static-aircraft library copied into several airport folders. Different versions may define the same library objects while expecting different texture sets. If the fault began after an update, disable old add-on copies one at a time by moving them outside active scenery; do not remove stock FSX files.
7. Check AI livery names separately. In an AI aircraft's aircraft.cfg, an entry such as texture=blue requires a folder named texture.blue. A blank texture= entry normally uses the plain texture folder. If only one livery is black, inspect its files and any texture.cfg fallback before changing global graphics settings.
8. Disable DirectX 10 Preview. Untick Preview DirectX 10 in FSX's display settings, close the simulator fully and start it again. This returns FSX to its normal DirectX 9 rendering path. If the colours return, the installation is probably intact and the model is incompatible with the preview renderer.

Why does DirectX 10 Preview make old static aircraft black?

DirectX 10 Preview handles some legacy materials differently from the DirectX 9 renderer for which many FS2004-era static models were built.

These objects can retain correct geometry while their diffuse texture or material effect fails, leaving an all-black aircraft. The practical choices are:

• Keep DirectX 10 Preview disabled when using older scenery libraries.
• Install the package's FSX-native model and texture set if one is supplied.
• Replace the affected object with a compatible model if no FSX version exists.

If one model stays black in DirectX 9 after a verified clean installation while neighbouring objects display correctly, its compiled material definition or texture reference is probably defective. That fault must be corrected in the source model or replaced package; repeatedly changing global FSX settings will not repair it.

What if the static aircraft are black only at night?

An aircraft that is correctly textured by day but black after sunset usually has an unsuitable night material, not a missing daytime livery.

Scenery-based static aircraft do not operate navigation, beacon or cabin lights like live AI aircraft. Some basic library objects therefore become very dark by design. Other packages use a separate night or light-map texture, often identified by an _LM suffix; reinstall that companion texture if the package is meant to include one.

If no night material was created for the model, changing scenery priority or copying unrelated textures will not help. The object must be replaced or rebuilt with suitable night materials.

What if the whole airport is turning black?

Black aircraft accompanied by black buildings, runways or terrain indicate a broader rendering or scenery problem rather than one missing static-aircraft texture.

Test a default airport in daylight and temporarily disable the affected add-on scenery. If default objects are also wrong, work through our checks for black airport buildings, terrain, DX10 conflicts and shader-cache faults instead of reinstalling a single aircraft library.

Should I convert or rename the texture files?

Do not convert textures until the folder structure, package version and rendering mode have been checked.

Renaming a .bmp file to .dds does not convert it. Unnecessary conversion can reverse texture orientation, damage alpha channels or use compression the legacy model does not expect. Copying every texture into a global FSX texture directory is also a poor fix: it hides the broken installation and can create file-name conflicts with other scenery.