FSX afterburner not working? Check throttle triggers, Effects and Gauges files, aircraft.cfg entries, Steam paths and visual settings.
An afterburner usually fails in FSX because the aircraft’s effect files, controlling gauge or aircraft.cfg entries are missing, installed in the wrong FSX folder, or using a different trigger than expected. Add-ons may engage it at full throttle, through a light or smoke command, or from a cockpit switch.
How does an FSX afterburner actually work?
In FSX and FSX: Steam Edition, afterburner thrust and the visible flame are separate systems. The flight model controls any extra thrust and fuel consumption, while one or more .fx files create the exhaust plume. A gauge or aircraft configuration entry usually connects those parts to a trigger.
Common trigger methods include:
- An automatic gauge that activates above a set throttle position.
- An assigned afterburner control supported by that particular aircraft.
- A light circuit controlled manually or by a gauge.
- The smoke command, often the
Ikey on an unchanged keyboard profile. - A switch or throttle detent in the aircraft’s virtual cockpit.
Do not assume that every military jet model includes a working afterburner. Some freeware aircraft have only a visual plume, some simulate thrust without a flame, and others require optional files supplied separately.
How do I fix an afterburner that will not engage?
- Check the aircraft instructions. Identify the intended trigger before changing files. Look for references to full throttle, smoke, lights, a panel switch or an afterburner control assignment.
- Test with full keyboard throttle. With the engines running, press
F4and observe the aircraft from an external view. If the afterburner works withF4but not with your throttle lever, the hardware axis is probably stopping below the gauge’s activation threshold. Recalibrate the axis and check its sensitivity and maximum travel. - Verify the active FSX installation. A mistake we see constantly is an installer writing files into an old boxed FSX folder while the user is running Steam Edition, or creating an extra nested FSX directory. Our guide to the correct FSX add-on folder structure explains where aircraft and their support files belong. For Steam installations, also check these Steam Edition path and legacy-installer fixes.
- Inspect the effect files. The supplied
.fxfiles normally belong in the mainEffectsfolder, with any associated textures in the location specified by the package. The effect name inaircraft.cfgmust match the filename, normally without the.fxextension. A missing texture can make the plume invisible or display it incorrectly. - Check the configuration entries. Make a backup, then inspect
[lights],[smokesystem]and[TurbineEngineData]where applicable. Look for missing lines, duplicate entry numbers, altered light types or effect names that do not exist. Twin-engine aircraft normally need separate effect positions for each exhaust. If Windows prevents the activeaircraft.cfgfrom being overwritten, check file permissions and make sure the edit was not saved only to a virtualised copy. - Confirm that the controlling gauge loads. Gauge-based systems require the correct
panel.cfgentry and the supplied gauge files. Preserve the archive’s folder structure rather than unpacking or moving gauge components arbitrarily. If FSX presented a trust prompt for a known package and the gauge was not permitted to run, its automatic trigger will not work. This example of a throttle-triggered gauge and LIGHTS setup shows how this type of installation is connected. - Reload and test the visuals. Select another aircraft and return, or restart FSX after changing gauges or configuration files. Raise the Special effects detail setting for testing. If an old effect remains invisible or appears as a square, temporarily disable DX10 Preview and restart the simulator; some legacy effects do not render correctly with it.
What does each afterburner symptom indicate?
| Symptom | Likely cause |
|---|---|
| No flame and no extra thrust | Wrong trigger, throttle below the threshold, missing gauge or incomplete installation |
| Extra thrust but no flame | Missing .fx file or texture, incorrect effect name, low visual setting or rendering conflict |
| Flame but no extra thrust | Visual-only add-on or missing afterburner flight-model data |
| Only one engine shows a plume | Missing second effect entry, incorrect coordinates or a gauge configured for one engine |
Works with F4 but not the throttle lever | Axis calibration prevents the throttle from crossing the activation threshold |
Why does the flame appear without extra thrust?
A visible afterburner does not prove that FSX is producing afterburner thrust. Many effects are attached to a light or smoke event and are purely cosmetic. Functional thrust requires suitable flight-model data, commonly including afterburner settings under [TurbineEngineData] and supporting data in the aircraft’s flight model.
Avoid copying arbitrary performance values from another jet. Engine count, dry thrust, afterburner ratio and fuel consumption must suit the aircraft; otherwise the apparent fix can produce unrealistic acceleration or fuel flow. If the package describes its afterburner as a visual effect, flame without added thrust is expected behaviour.
Can I add a missing afterburner effect manually?
You can add a visual afterburner when the aircraft package permits modification and its engine positions are known. Our manual afterburner-effect installation and positioning procedure covers the required effect placement, configuration entries, size and intensity adjustments.
Choose manual installation when the aircraft has no plume but otherwise works. Reinstall the original package instead when several gauges, textures or configuration sections are missing, because repairing one effect line will not restore incomplete dependencies.