How do I enable and use aircraft smoke effects in FSX?
Enable FSX aircraft smoke with the I key, install .fx files correctly, edit [SMOKESYSTEM], and fix missing smoke or touchdown effects.
In FSX and FSX: Steam Edition, press I to toggle aircraft smoke, provided the aircraft has a valid [SMOKESYSTEM] section and every referenced .fx file is in the active installation’s Effects folder. If nothing appears, check the control assignment, filename, folder path and reload the aircraft after editing aircraft.cfg.
How do I install a smoke effect in FSX?
An FSX smoke effect needs two parts: the physical .fx file in the simulator’s main Effects folder and a matching entry in the chosen aircraft’s aircraft.cfg.
- Find the active FSX installation. Locate the folder containing
fsx.exe. The required destination is itsEffectsfolder, not an Effects folder created inside the aircraft directory. Boxed FSX and Steam Edition may coexist, so confirm which copy you actually launch. - Find and back up aircraft.cfg. Aircraft are normally under
SimObjects\Airplanes, although a custom installation can use another registered SimObject path. Make a copy of the configuration file before editing it; our safe aircraft.cfg editing instructions cover permissions, backups and finding the correct variant. - Copy every supplied effect component. Put
.fxfiles directly in the mainEffectsfolder. Put accompanying texture files in the destination named by the package, commonlyEffects\texture. A mistake we see constantly is an extra nested directory such asEffects\Effects. - Add or edit the smoke section. Use the effect name and coordinates supplied by the add-on. If
[SMOKESYSTEM]already exists, merge or replace its numbered entries rather than adding a second section. - Save as plain text and reload. Switch to another aircraft and back after saving. Restart FSX if it still appears to be using the old configuration.
A two-emitter configuration has this general form: [SMOKESYSTEM], followed by entries such as smoke.0 = -12.0, -16.0, 0.0, fx_example_smoke and smoke.1 = -12.0, 16.0, 0.0, fx_example_smoke. Those coordinates and that effect name are examples only.
Number entries consecutively from smoke.0. Reference the effect’s base filename, normally without the .fx extension: a file called fx_example_smoke.fx is entered as fx_example_smoke. Do not rename it casually, because an effect can also depend on supplied textures or other effect files.
For a practical installation to compare against your own files, this worked Boeing 737-800 engine-smoke package includes the usual .fx, [SMOKESYSTEM] and I-key arrangement.
How are FSX smoke positions set?
Each smoke.N line contains three offsets in feet from the aircraft model’s reference datum, followed by the effect name.
| Value | Meaning |
|---|---|
| First | Longitudinal position: positive forward, negative aft |
| Second | Lateral position: positive right, negative left |
| Third | Vertical position: positive above, negative below |
| Final field | Effect base filename, normally without .fx |
Coordinates copied from another aircraft often put the plume in the wrong place because models use different reference datums. Change one axis at a time in small increments, reload the aircraft and observe which way the emitter moves.
How do I turn the FSX smoke system on and off?
Load the configured aircraft and press I to operate the standard Smoke System toggle; press it again to switch the system off.
- Select an external view so you can see the emitters clearly.
- Press I by itself. Do not add Shift or Ctrl. Existing particles may remain visible briefly after the system is switched off.
- Check the assignment if nothing happens. In the FSX control settings, find
Smoke System (on/off)and assign a keyboard key or controller button. - Raise Special Effects Detail for testing. A very low effects setting can suppress or simplify particle effects.
The standard command activates every entry in [SMOKESYSTEM] together. It cannot select individual colours, engines or emitters unless the aircraft includes a separate gauge or controller.
Localised installations do not change the configuration syntax. The displayed control label may use the local word for smoke or fumée, but [SMOKESYSTEM], smoke.0 and the effect filename must remain as written. The same applies when a fault is described as “nie ma dymu” or “no me va”: translating the CFG entries will stop them working.
Why is there no smoke effect in FSX?
If the smoke command produces nothing, the most likely causes are a missing .fx file, a mismatched name, the wrong aircraft.cfg or an unassigned smoke-system control.
- The I key does nothing: verify the
Smoke System (on/off)assignment. Some add-ons use a panel gauge instead, in which case the standard key may be deliberately bypassed. - No emitter produces smoke: compare each CFG effect name with the file in the active installation’s
Effectsfolder. Check that Windows has not created a hidden double extension such aseffect.fx.txt. - Only one plume appears: look for duplicated
smoke.Nnumbers, a typo on one line, missing dependent files or coordinates that place one emitter inside the model. - There is smoke, but it is in the wrong place: adjust the three position values. Moving the
.fxfile or renaming it cannot correct an emitter’s position. - Smoke continues with the engine stopped: that is normal for the standard system.
[SMOKESYSTEM]responds to its toggle, not engine RPM, throttle, N1 or combustion state. - The smoke is made of black, white or opaque squares: the effect is running, but its texture or blend mode is failing. Confirm that all supplied textures were installed. Older effects can also render badly with FSX’s DirectX 10 Preview, so disabling Preview is a useful diagnostic test.
- Your edits have no effect: make sure you changed the configuration belonging to the loaded aircraft, saved it as plain text and reloaded the aircraft. Program Files permissions and multiple FSX installations frequently lead people to edit or save the wrong copy.
What does “No effect files .fx found in the effect search paths” mean?
“No effect files .fx found in the effect search paths” means the simulator component or effects tool searched its configured folders and found no legacy FSX effect files; pressing I cannot fix a missing search path.
- Point the search path at the actual Effects folder. It should be the
Effectsdirectory beside thefsx.exebeing used, not merely the parent FSX folder. - Inspect the folder directly. Confirm that it contains files ending in
.fxand that they are not inside another nested directory. - Check for multiple installations. A tool configured for boxed FSX will not automatically find files installed only in Steam Edition, or the reverse.
- Restore missing stock files if necessary. If the active Effects folder contains no default effects at all, use the simulator installation’s repair or file-verification facility. Back up custom effects first because a repair is not a substitute for reinstalling third-party files.
The extension matters here: FSX .fx files are its legacy particle-effect definitions. They are not interchangeable with unrelated shader files that happen to use the same extension.
Is touchdown FX controlled by the FSX smoke system?
No. Tyre smoke at touchdown is normally an automatic aircraft effect defined under [EFFECTS], not a manual [SMOKESYSTEM] emitter, so the I key does not control it.
| Effect | FSX configuration | Trigger |
|---|---|---|
| Display or manually configured engine smoke | [SMOKESYSTEM] | Smoke System (on/off), normally I |
| Touchdown tyre smoke | [EFFECTS] touchdown entry | Wheel contact and landing conditions |
| Water spray, wake, dirt or sparks | [EFFECTS] entries | Surface contact or movement |
A common stock-style touchdown entry is touchdown=fx_tchdwn, 1. Use the line supplied with the aircraft rather than overwriting working parameters blindly, and confirm that the referenced effect exists in the main Effects folder.
Touchdown smoke can be difficult to see after an exceptionally gentle landing, from some camera angles or with low effects settings. If touchdown FX and water wakes are both absent, work through our targeted checks for missing landing smoke and water wakes; a shared graphics or Effects-folder problem is then more likely than an aircraft-specific smoke-system fault.
Does FSX touchdown FX work in MSFS 2020 or MSFS 2024?
No. Microsoft Flight Simulator 2020 and Microsoft Flight Simulator 2024 use their modern visual-effects and package systems rather than FSX’s legacy fx_tchdwn.fx workflow.
Copying an FSX .fx file into an MSFS Community package will not enable touchdown smoke. Use an effect or aircraft package explicitly built for the relevant MSFS generation and platform; FSX [SMOKESYSTEM] and [EFFECTS] entries are not drop-in MSFS configuration.
Can FSX use coloured smoke or automatic engine smoke?
Yes, FSX can display coloured or engine-positioned smoke, but automatic behaviour requires more than a basic [SMOKESYSTEM] section.
- Manual display smoke: use ordinary smoke entries when all emitters should switch together with
I. - Fixed engine smoke: place emitters at the engine exhausts, but expect them to remain manually controlled unless the package says otherwise.
- Selectable colours: use multiple effect files with a custom selector, such as this gauge-controlled coloured-smoke package.
- Automatic engine-dependent smoke: choose an add-on with gauge or controller logic that monitors engine variables. Other solutions may use panel switches or custom XML gauges, so their activation instructions replace the normal
I-key procedure.