Find why VASI or PAPI lights are missing in FSX and fix add-on AFCAD conflicts, scenery priority, absent libraries and display issues.
VASI or PAPI lights are usually missing in FSX and FSX: Steam Edition because the runway end has no visual-slope entry in its airport BGL, or an add-on AFCAD has overridden the default without one. Other causes are viewing the opposite end, excessive zoom-out, and an absent custom-object library.
Why FSX airports lose VASI or PAPI lights
Most cases are airport-data omissions or scenery conflicts, not faults with the aircraft. FSX stores each Precision Approach Path Indicator (PAPI) or Visual Approach Slope Indicator (VASI) in the airport scenery data, separately for each runway end.
“AFCAD” is common shorthand for an airport-layout BGL. A replacement airport BGL often uses delete flags to suppress the stock layout before drawing its own version. If the replacement omits a visual-slope indicator, the original lights do not shine through from underneath.
Stock FSX scenery represents its release-era airport layout. A PAPI fitted or relocated at the real airport later will therefore be absent unless updated scenery supplies it. Some add-ons also replace native FSX lights with custom models, textures or effects; those disappear when a required library or file has not been installed.
Is the VASI or PAPI actually missing?
A short, controlled approach test distinguishes missing scenery from lights that are merely difficult to see.
- Check the runway end. Runway 09 and Runway 27 have separate definitions. A PAPI fitted to one end need not exist at the other, and its lamps are directional rather than equally visible from behind.
- Identify the correct light system. PAPI is normally a horizontal row, while VASI uses separate light bars. Our visual comparison of PAPI and VASI layouts helps distinguish them. Neither should be confused with the approach-lighting system extending out from the threshold.
- Test from a normal final approach. Line up with the runway from a few miles away, use a sensible cockpit zoom and try dusk conditions. Dusk is only a visibility test; native visual-slope lights are not supposed to require darkness.
- Compare another stock airport. If several known default airports display their indicators correctly, the renderer is working and the affected airport's BGL is the likely cause.
What does the failure pattern reveal?
| What you see | Most likely cause |
|---|---|
| Only one runway end is affected | No VASI/PAPI entry for that end, or the indicator is on the opposite side or end |
| The whole airport changed after installing scenery | Replacement or duplicate airport-layout BGL |
| Lamp boxes appear but emit no useful colour | Missing custom texture or effect, or a rendering problem |
| Custom buildings appear but custom lights do not | Required object library was not installed or activated |
| Several default airports have lost multiple kinds of lighting | Global display setting, DirectX 10 Preview issue or damaged FSX files |
| The real airport has PAPI but FSX has VASI or nothing | Release-era airport data or an inaccurate add-on |
How do I restore missing VASI or PAPI lights in FSX?
Restore the stock airport first, then add scenery back until the conflicting layer is identified.
- Back up the scenery. Copy any suspected BGL before moving or replacing it. Do not edit or delete stock FSX scenery files during diagnosis.
- Disable the airport add-on temporarily. Untick the relevant airport and regional layers in the FSX Scenery Library, let FSX rebuild its scenery index, restart the simulator and retest. If the stock lights return, the add-on is replacing them.
- Find duplicate airport layouts. Search all active scenery folders for files associated with the airport's ICAO code. Airport files may also arrive with AI traffic or regional packages. Move one suspected layout BGL at a time outside every active scenery folder; merely changing layer order will not always cure two competing airport definitions. Do not remove object, terrain or texture BGLs solely because their names contain the same ICAO code.
- Correct the scenery priority. Place the intended airport above broad regional airport packages and other scenery that modifies the same location. The override principle is demonstrated in our FSX scenery installation and layer-priority notes. Keep only one active airport-layout definition for that ICAO unless the package instructions explicitly require otherwise.
- Restore custom dependencies. Reinstall the complete airport package and check its documentation for object libraries, textures and effects. An add-on may otherwise look complete while its lighting objects remain absent; this airport package with a separate lighting-object dependency is a practical example of that arrangement.
- Add the missing system only when the airport data truly lacks it. With an FSX-compatible airport editor, assign the correct PAPI or VASI type to the correct runway end and match its side, slope and spacing to the airport being represented. Compile the correction into a separate, higher-priority scenery layer rather than overwriting a stock BGL.
If visual-slope indicators fail at several stock airports, turn off DirectX 10 Preview, restart FSX and test again. Temporarily raise Scenery Complexity if the missing lights are custom objects, although native VASI and PAPI definitions do not depend on autogen or AI traffic. Light bloom changes their halo; it cannot create an omitted airport entry.
When runway, taxiway and visual-slope lighting are all affected, follow our broader FSX airport-lighting checks. If default scenery remains broken, use Steam's file verification for FSX: Steam Edition or the installation repair option for boxed FSX. Back up modified stock files first because a repair can replace them.
Can FSX show VASI when the real airport has PAPI?
Yes. FSX may represent an older airport configuration, or an add-on designer may have selected the wrong visual-slope system. Each runway end is independent, so one end can correctly have PAPI while the reciprocal end has VASI or no indicator at all.
The ILS glideslope and the visual indicator are also separate airport records. A working ILS does not prove that PAPI should be present, and adding PAPI will not repair a missing or incorrect ILS. For accurate scenery, match the visual system and its slope to the airport configuration the add-on is intended to depict rather than assuming every runway uses a three-degree PAPI.