Why are add-on aircraft external lights not working in FSX?

An add-on aircraft’s external lights usually fail in FSX or FSX: Steam Edition because its referenced .fx files were not copied into the simulator’s Effects folder, the [LIGHTS] entries in aircraft.cfg are missing or incorrect, or the aircraft is unpowered. Test a default aircraft first, then verify the add-on’s configuration, effect files and textures.

How can I identify where the light failure is?

A comparison with a default FSX aircraft quickly separates an aircraft-specific fault from a simulator-wide problem. Use the same airport, time of day and external view for both tests.

How do I fix missing external lights in FSX?

The safest repair is to work from the aircraft’s power state through its configuration and support files, changing only one item at a time.

1. Power the aircraft and operate its own switches. Turn on the battery and any generator or alternator required by the aircraft, then use the virtual-cockpit beacon, navigation, strobe, taxi and landing-light switches. With an unchanged FSX control map, L toggles all lights, but a complex add-on may use custom electrical logic that the generic command does not satisfy.
2. Test a default aircraft. If its lights work, leave the global FSX files and control settings alone; the fault belongs to the add-on. If every aircraft is affected, check the light assignment, electrical power, special-effects setting and shared effect files.
3. Back up the active configuration. Copy the add-on’s aircraft.cfg from SimObjects\Airplanes\aircraft-folder before editing it. Some packages install separate folders for different models, so confirm that you are changing the variant selected in FSX.
4. Inspect the [LIGHTS] section. A conventional entry follows the pattern light.n = type, longitudinal, lateral, vertical, effect_name. Each light.n identifier should be unique, and the final field must match an installed effect. The position values are relative to the aircraft reference datum; incorrect coordinates can put a working light inside the fuselage or far from the aircraft.
5. Match every effect name to a file. An entry ending in effect_name normally expects Effects\effect_name.fx beneath the folder containing fsx.exe. The effect may also reference a texture that belongs in Effects\texture. A present .fx file with a missing texture can produce an invisible or malformed light.
6. Reinstall the package’s support folders. A mistake we see constantly is copying the aircraft model but overlooking the package’s separate Effects folder, or creating an incorrect nested path such as Effects\Effects. Our FSX add-on installation checklist explains how those support files should be merged without moving them into the aircraft folder.
7. Account for model-attached and gauge-controlled lights. Not every aircraft uses a visible [LIGHTS] section. Some attach effects to the compiled model or control them through panel gauges and custom systems. If the section is absent, verify that the package’s panel, gauge and module files were installed rather than adding generic entries immediately.
8. Restart FSX and test at dusk. Reloading the aircraft may refresh the configuration, but a complete restart is safer after replacing effects. If the DX10 Preview option is available, temporarily disable it and restart; old effects that return under the standard renderer need a compatible effect rather than new coordinates. Also raise the special-effects detail setting for the test.

Why do the switches move but no light appears?

A moving switch confirms its animation, not that the light effect or electrical command has loaded. Missing gauges, an unpowered electrical bus, absent .fx files and incomplete custom-system installation can all leave the switch animated while the aircraft remains dark.

If other lights on the same aircraft work, trace only the failed light’s configuration entry and effect. If none work and there is no conventional [LIGHTS] section, the aircraft probably relies on model-attached or gauge-controlled lighting.

Why is the light visible but not the runway beam?

A visible lamp halo and runway illumination are separate symptoms in FSX. When the halo works, the effect is loading; concentrate on its type, position, model attachment, renderer compatibility and the angle from which it disappears.

Legacy billboard-style effects can become faint or vanish from particular viewing angles, especially after an effect or halo texture has been replaced. The files and notes in our FSX landing-light effects package provide a useful reference for shared halo textures and positioning behaviour. Test at night before assuming a subtle daylight effect is broken.

Should I install an aircraft-specific light fix?

Use a light fix only when it names the exact aircraft or model version you have and explains which files it changes. Our aircraft-specific HS 748 light repair illustrates the correct approach: place the expected effect in FSX’s main Effects folder while preserving the filename referenced by the aircraft.

Do not replace similarly named default effects at random. Many aircraft share the same files, so changing one global effect can alter or disable lights across the fleet. Back up every existing .fx file before overwriting it; if default aircraft are already affected, back up custom effects before using Steam file validation or the boxed edition’s repair facility.