Find why FSX taxiway signs are missing and fix AFCAD conflicts, scenery priority, complexity, textures and airport elevation problems.
Taxiway signs are usually missing at an FSX or FSX: Steam Edition add-on airport because the airport’s AFCAD/facility BGL is inactive, overridden by another airport file, or contains no sign records. Low Scenery Complexity, missing custom-object textures, and elevation conflicts can also hide them even when the terminal scenery loads.
What controls taxiway signs in FSX?
In FSX, standard taxiway signs are definitions inside the airport facility BGL, commonly called the AFCAD even when it was created with a newer airport editor. This file also controls runways, taxi paths, parking positions and related airport data.
The terminal, apron textures and other visual objects may be stored in separate BGLs. Seeing those objects therefore does not prove that the correct facility file is active. This example of an airport facility BGL and its installation location shows how airport data can be supplied separately from the visual scenery.
Some developers replace FSX-generated signs with custom 3D models. Those signs also require the supplied object library and textures. Progressive Taxi does not create physical taxiway signs; it only draws route guidance over the airport.
Which symptom identifies the likely cause?
The pattern of failure usually identifies whether the fault lies with the add-on, a conflicting airport file or FSX itself.
| What you see | Likely cause | First check |
|---|---|---|
| Signs are missing at one add-on airport only | Inactive, incomplete or overridden facility BGL | Scenery activation, priority and duplicate airport files |
| Signs show old or incorrect taxiway labels | A stock or third-party AFCAD is taking precedence | Other BGLs for the same ICAO code |
| Sign structures appear blank or black | Missing custom textures or an incompatible material | The add-on’s texture and object-library folders |
| Signs are partly buried or floating | Airport elevation or flatten conflict | Supplied elevation-correction files and competing scenery |
| Signs are absent at default airports as well | Global setting or damaged FSX files | Scenery Complexity and the simulator installation |
How do I restore missing FSX taxiway signs?
Test the scope first, then check display settings, scenery activation, library priority and duplicate airport files in that order.
- Compare another airport. Load a default FSX airport and a second add-on airport. If signs work elsewhere, reinstalling the entire simulator is unnecessary; the problem belongs to the affected airport package or a file competing with it.
- Raise Scenery Complexity temporarily. Move the Scenery Complexity slider to its highest setting and reload the airport. Some add-ons attach custom signs to a complexity level. Autogen Density and AI traffic settings do not restore missing sign definitions.
- Confirm every scenery component is installed. The activated parent folder should normally contain a
scenerysubfolder for BGLs and, where required, atexturesubfolder. Install any separate object library or elevation component named in the add-on documentation. If the area is not active, follow our FSX scenery activation and folder checks. - Correct the Scenery Library priority. Place the complete airport above regional scenery, older versions of the same airport and airport files installed by AI traffic packages. Leave FSX’s default scenery areas below add-on airports rather than deleting them.
- Isolate duplicate AFCAD files. Close FSX and search third-party scenery folders for BGL filenames containing the airport’s ICAO code. This catches many duplicates, though not every developer uses the ICAO code in filenames. Rename one suspected third-party file from
.bglto.off, restart FSX and test again. Never delete or rename the simulator’s stock APX files. - Check textures, rendering and elevation. If only custom sign models are invisible or blank, reinstall the supplied textures and object libraries. Testing with DirectX 10 Preview disabled can expose a legacy custom-material problem. Buried signs instead point to an elevation or flatten conflict; restore any elevation-adjustment file exactly where the airport documentation specifies.
- Decide whether the signs were ever included. If the correct facility BGL is active, no conflict exists and the airport has never displayed signs, the developer may simply have omitted the sign records. FSX has no setting that can generate a complete sign layout automatically.
Can I replace the airport AFCAD to add the signs?
You can replace or edit the facility BGL, but it must match the exact version of the visual airport scenery. An unrelated AFCAD may restore signboards while moving taxiways, parking positions and AI paths through buildings.
An example of a stock-airport AFCAD modification illustrates how updated airport data can change taxiway signage and layout. For a payware or freeware add-on airport, use a correction made specifically for that scenery, or edit a backup of its own facility file with an FSX-compatible airport editor.
Keep only the intended third-party facility file active while testing. Separate object, terrain and texture BGLs belonging to the same airport should remain enabled.
Are missing taxiway signs and lights the same problem?
No. Taxiway signs come from facility records or custom scenery objects, while edge and centreline lights are controlled by different airport definitions and rendering conditions. If the illuminated pavement lights are missing rather than the signboards, use our separate taxiway-light troubleshooting steps.