Fix static aircraft that are completely black in FSX by checking scenery textures, DX10 Preview, folder paths and legacy model compatibility.
Static aircraft appear completely black in FSX, including Steam Edition, when geometry loads but material textures do not render. The usual causes are missing or misplaced files, an FS2004-era scenery model under DirectX 10 Preview, or a mismatched model and texture set. Reinstall the full package, test DirectX 9, and restart FSX.
How can I tell what is failing?
The pattern of the fault usually distinguishes an installation problem from a graphics or model-compatibility problem.
| What appears black | Most likely cause | Best first test |
|---|---|---|
| Static aircraft at one airport | Missing package textures or the wrong object-library version | Reinstall that scenery with its complete Texture folder |
| Most older static aircraft | Legacy materials conflicting with DirectX 10 Preview | Disable DirectX 10 Preview and restart FSX |
| One parked AI livery | Missing livery files or an incorrect aircraft.cfg texture reference | Check the aircraft's texture folder and texture= entry |
| Aircraft only after sunset | Absent or defective night material rather than a missing daytime texture | Retest at noon in clear weather |
| Aircraft plus unrelated scenery objects | Simulator-wide shader or graphics configuration fault | Test the default graphics configuration |
How do I fix black static aircraft?
Restore the correct model and texture files before changing drivers, shaders or texture formats.
- Test in daylight. Set the flight to noon with clear weather and view the aircraft from several directions. If markings or colours return, skip to the night-rendering section below.
- Identify the type of static aircraft. A scenery object is compiled into a scenery or object-library BGL. A parked AI aircraft is a SimObject, even if its traffic plan leaves it at the gate for long periods. For AI traffic, use our guide to locating the active aircraft directory in boxed and Steam editions.
- Restore the complete folder structure. A conventional scenery package has BGL files under
...\Addon Scenery\<package>\Sceneryand its BMP or DDS files under the sibling...\Addon Scenery\<package>\Texturefolder. The Scenery Library entry normally points to the package root, not directly to its Scenery subfolder. - Do not copy only the BGL. This is a mistake we see constantly with static-aircraft libraries. Geometry remains visible because the model BGL is present, but the required liveries were left in the archive or in an inactive Texture folder. Our FSX missing-texture checklist covers misplaced files, unreadable formats and fallback paths.
- Keep matching model and texture versions together. Replacing an object-library BGL while retaining textures from another release can leave every material unresolved. Extract the original package again rather than combining folders from FSX, FS2004 or Prepar3D editions.
- Check AI livery references separately. For parked AI, an entry such as
texture=bluemust correspond to a folder namedtexture.blue. A missing shared-texture fallback intexture.cfgcan also turn one livery black while the others remain normal. - Test without DirectX 10 Preview. Untick
Preview DirectX 10in FSX's graphics options, close the simulator completely, and start it again. FSX then uses its normal DirectX 9 rendering path.
Do not begin by renaming BMP files to DDS or converting every texture. Conversion can damage alpha channels, orientation and compression, while doing nothing to repair a material reference embedded in the compiled model.
Why does DirectX 10 Preview make old static aircraft black?
DirectX 10 Preview exposes material and shader assumptions in some FS2004-era scenery models that still appear correct under DirectX 9.
If disabling the preview immediately restores the colours, the texture location is probably correct. The practical choices are to remain in DirectX 9 mode or replace the static model with an FSX-native version designed for the chosen rendering path. Similar material failures can produce plain white aircraft instead of black ones.
If the aircraft remains black in DirectX 9 after a clean reinstall, while other objects display normally, the model or one of its textures is defective or incompatible. Bad material definitions and surface normals must be corrected in the source model; repainting the finished BGL is not a reliable cure.
When many unrelated aircraft, buildings or terrain surfaces are affected, treat it as a wider graphics-path problem. Remove custom shader overrides and work through our Direct3D configuration and reset checks for FSX rather than repeatedly reinstalling one airport.
What if the static aircraft are black only at night?
An aircraft that looks correct by day but black at night usually lacks a usable night or emissive material, not its main livery texture.
Scenery-based static aircraft do not operate navigation, beacon or cabin lights like live AI aircraft. Some simple library objects therefore become extremely dark after sunset by design. If the package was meant to include illuminated textures, reinstall its night-texture files; otherwise the model must be replaced or rebuilt with suitable night materials.