Find why airport buildings are missing in FSX and restore terminals by checking scenery complexity, add-on layers, exclusions and object libraries.
Airport buildings are usually missing in FSX and FSX: Steam Edition because Scenery Complexity is set too low, an add-on airport is inactive, a required object library was omitted, or another scenery file is excluding the buildings. If only newer terminals are absent, FSX's ageing default airport data may simply pre-date them.
What does the missing scenery pattern tell you?
The scope and appearance of the problem usually reveal which part of FSX scenery has failed.
| What you see | Likely cause |
|---|---|
| Buildings missing at many airports | Low Scenery Complexity, disabled default scenery or damaged core files |
| Only one add-on airport is affected | Inactive scenery area, incomplete installation or missing object library |
| Runways appear but terminals do not | Only the airport-layout file loaded, or another file excluded the buildings |
| Old terminal appears but a newer one does not | The default FSX airport predates the real-world development |
| Buildings appear black, white or transparent | Missing or incompatible textures rather than missing objects |
| Only surrounding houses and trees are absent | Autogen Density is too low; this setting normally does not control placed terminal models |
If the runway, taxiways and airport entry are missing as well, use our steps for restoring an entire missing airport; that is a different fault from absent buildings.
How do I restore missing airport buildings in FSX?
Start with the display setting, then test the scenery installation before repairing FSX itself.
- Raise Scenery Complexity. Open FSX's display scenery settings and move Scenery Complexity to Extremely Dense for testing. Reload the airport or restart FSX. If the buildings return, lower the slider one step at a time to find an acceptable performance balance.
- Test a default airport. Load an airport that has no add-on scenery installed. Buildings at default airports mean the simulator itself is working and the fault belongs to the affected add-on.
- Check the Scenery Library. Confirm that the airport's scenery area is present, enabled and pointing to the folder actually containing its
Scenerysubfolder. This matters particularly when an older installer sends files to a boxed-FSX directory while FSX: Steam Edition is installed elsewhere. - Confirm every dependency. Some packages contain only placement instructions and depend on a separate object-library BGL for the building models. Keep the supplied
SceneryandTexturefolders together unless the installation instructions explicitly say otherwise. Our Anguilla scenery's library requirement and activation notes show how a dependency can determine whether airport objects appear. - Disable conflicting airport files. Temporarily deactivate other scenery packages covering the same ICAO code or region, then restart FSX. Old AFCAD files, traffic add-ons and previous airport versions may contain exclusion rectangles that remove the default terminal without supplying a working replacement. Do not delete files until you have identified the conflict.
- Check scenery priority. Keep the airport above older versions and broad regional packages when the add-on instructions require it. Priority cannot repair a missing library, but it can decide which airport placement and exclusion files take effect.
- Repair only a widespread default-scenery fault. If buildings are missing across many untouched default airports with Scenery Complexity at maximum, verify the FSX: Steam Edition installation or run the boxed edition's repair option. Back up altered default files and configuration data first, because repair tools can restore original versions.
A mistake we see constantly is copying a single airport BGL while overlooking its library files and textures. Activate the complete package, allow FSX to rebuild its scenery database, and test again before moving individual files.
Why are the runway and taxiways present but the terminal is not?
Runways and buildings are often supplied by different files, so a partially installed airport can retain its layout while losing every terminal object.
An FSX airport package may contain an airport-facility file for runways, parking and taxiways; a placement file for buildings; exclusion data that removes default objects; one or more model libraries; and a Texture folder. Loading only the facility file can produce a detailed apron with no terminal, while loading an exclusion file without its replacement objects can leave an otherwise empty airport.
If the model is visible but its surfaces are blank, dark or transparent, follow our guide to diagnosing missing FSX textures instead. Changing scenery priority rarely fixes a genuinely absent texture file.
Does FSX need newer airport scenery?
FSX needs add-on scenery to represent terminals and airport developments built after the simulator's original airport database was compiled.
A correctly working default installation can therefore show an older terminal arrangement, an obsolete concourse or open ground where a newer building now stands. This is not file corruption. Install an airport update designed for FSX, making sure it matches the airport rather than a different simulator version; for example, our FSX update for Dallas-Fort Worth supplies airport scenery absent from the older default representation.
Use one complete airport package at a time. Combining several versions is more likely to create duplicated taxiways, floating jetways or exclusion conflicts than to produce a more accurate airport.