Afterburner not working in FSX? Check Shift+F4, throttle calibration, effect files, gauges, aircraft.cfg and Steam Edition install paths.
In FSX and FSX: Steam Edition, a non-working afterburner usually means the aircraft does not support it, uses a different trigger, never reaches the required throttle threshold, or is missing an effect, gauge or configuration entry. Try Shift+F4 in a supported jet, then test full throttle with F4 and check the add-on’s instructions.
How does an FSX afterburner work?
FSX treats afterburner thrust and the visible exhaust flame as separate parts of the aircraft.
The flight model determines whether additional thrust and fuel consumption are available. One or more .fx files produce the flame, while a gauge, configuration entry or cockpit control decides when to display it. This is why a jet can accelerate without showing a plume, or display a convincing flame without producing extra thrust.
Aircraft developers use several different triggers:
- The standard
Shift+F4afterburner command. - An automatic gauge activated above a set throttle position.
- A cockpit switch or simulated throttle detent.
- A light circuit controlled by the panel or keyboard.
- The smoke command, commonly
Ion an unchanged keyboard profile.
Not every military aircraft includes a functional afterburner. Some packages provide a cosmetic effect only, and many default civilian aircraft ignore the command completely. Our guide to FSX afterburner controls and activation methods explains how the standard command differs from aircraft-specific triggers.
How do I fix an FSX afterburner that will not engage?
Work through these checks in order so that a control problem is not mistaken for a damaged installation.
- Confirm that the aircraft supports afterburner. Read the package documentation and check that you selected the correct model or variant. Look for references to
Shift+F4, full throttle, smoke, lights or a virtual-cockpit switch. Do not assume that every fighter model includes working thrust and flame effects. - Test the keyboard commands. Start the engines, advance the throttle and press
Shift+F4. Separately, pressF4to command full throttle; this tests aircraft that activate their burner automatically above a threshold. Use an external view to check the plume, but also watch for a change in thrust or fuel flow. - Check the control assignments. Open the FSX control settings and confirm that another command has not replaced the afterburner assignment. Add-on control software or custom profiles may also intercept the key. If the cockpit switch works but
Shift+F4does not, the aircraft probably uses custom logic rather than the standard FSX event. - Test the throttle axis. If
F4activates the burner but the physical lever does not, the axis is failing to reach the gauge’s trigger point. Recalibrate it and check its maximum travel, sensitivity, reversed-axis setting and duplicate assignments on other controllers. Our FSX joystick and throttle troubleshooting steps cover the wider control checks without requiring aircraft-file edits. - Verify the active installation folder. A mistake we see constantly is an older installer writing support files into a boxed FSX directory while Steam Edition is the simulator being run. Multiple Steam libraries can cause the same problem. Confirm that the aircraft is in the active
SimObjects\Airplanesdirectory and that its support files went into the root folder of that same FSX installation. - Inspect the effect and configuration files. The supplied
.fxfiles normally belong in the mainEffectsfolder, with dependent textures commonly placed inEffects\texture. Follow the package’s structure if it specifies something different. Back upaircraft.cfg, then inspect relevant[lights]and[smokesystem]entries for missing effect names, duplicate index numbers and references to files that do not exist. Effect references normally omit the.fxextension. - Check the gauge installation. Automatic systems often depend on an XML or compiled gauge loaded through
panel.cfg. A missing gauge, broken panel entry or incorrectly unpacked folder can stop both the trigger and the flame. If FSX displayed a security prompt and the gauge was declined, it will not run; permit only files from packages you trust. See our guide to installing and diagnosing FSX gauges for the correct folder and panel checks. - Reload FSX and test the rendering settings. Restart the simulator after changing panel or gauge files, because switching aircraft does not always reload them cleanly. Raise Special effects detail while testing. If a legacy plume is invisible, blocky or displayed as a square, disable DX10 Preview and restart FSX; some older effects are not compatible with that renderer.
What does each afterburner symptom mean?
The combination of thrust, flame and control behaviour usually identifies which part has failed.
| Symptom | Most likely cause | Next check |
|---|---|---|
| No flame and no extra thrust | Unsupported aircraft, wrong trigger, low throttle range or missing controlling gauge | Test Shift+F4 and F4, then verify the aircraft instructions |
| Extra thrust but no flame | Missing effect or texture, incorrect effect reference, low effects setting or rendering conflict | Inspect the Effects folder and test without DX10 Preview |
| Flame but no extra thrust | Cosmetic-only effect or incomplete flight-model data | Check whether the package claims to simulate performance as well as visuals |
| Only one engine shows a flame | Missing second effect entry, incorrect exhaust coordinates or single-engine gauge logic | Compare both engine entries in the supplied configuration |
Works with F4 but not the throttle lever | The hardware axis never crosses the activation threshold | Calibrate the axis and remove conflicting throttle assignments |
| Flame appears as a square or solid block | Missing texture or an old effect that renders badly under DX10 Preview | Restore the supplied texture and test the alternative renderer |
Why does the flame appear without extra thrust?
A visible flame does not prove that FSX is applying afterburner thrust. Light- and smoke-triggered effects can be entirely cosmetic.
Functional performance requires suitable turbine-engine and flight-model data as well as the visual effect. Avoid copying arbitrary engine values from another jet: dry thrust, burner performance, fuel flow and engine count must match the aircraft. Otherwise the apparent repair can create unrealistic acceleration and fuel consumption.
If the developer describes the afterburner as a visual effect, flame without added thrust is expected. Conversely, if acceleration increases but the plume is absent, concentrate on the effect files and rendering settings rather than altering the flight model.
Can I add a missing afterburner effect manually?
You can add a visual plume if the aircraft permits modification and you can identify the correct exhaust positions.
Our manual afterburner installation and positioning tutorial explains how to connect an effect and adjust it for single- or twin-engine aircraft. This adds the visual component; it does not automatically create accurate afterburner thrust.
Choose manual installation when the aircraft works normally but lacks a plume. Reinstall the original package instead when gauges, textures and configuration sections are all missing, because adding one effect line will not repair an incomplete add-on.