Find why your FSX add-on aircraft has no sound and fix sound folders, sound.cfg aliases, missing WAV files, A320 variants and Steam paths.
If an FSX or FSX: Steam Edition add-on aircraft has no sound, first load a default aircraft. If that works, check the add-on’s selected sound folder, sound.cfg, WAV files and any alias. If all aircraft are silent, fix the simulator or Windows output settings before changing the add-on.
Is the fault in my FSX installation or the aircraft?
Silence in one aircraft points to its package; silence in every aircraft points to FSX or Windows. Load an untouched default aircraft and check both cockpit and external views before editing any files.
If everything is silent, check the FSX sound on/off command—Q is the default key unless reassigned—along with the simulator’s volume sliders and the Windows volume mixer. FSX may retain the playback device available when it started, so restart it after changing speakers, headphones or audio outputs. Follow our simulator-wide FSX audio checklist if default aircraft and ATC are also silent.
| Symptom | Likely cause |
|---|---|
| Default and add-on aircraft are silent | FSX mute, volume or Windows output problem |
| Only one add-on is silent | Missing folder, invalid sound.cfg or broken alias |
| Only one livery or engine variant is silent | Wrong sound= value in its [fltsim.x] entry |
| Engine audio works but warnings or switches do not | Missing gauge, module, shared file or electrical power |
| Only the AI version is silent | Missing or faulty soundai setup |
Which FSX sound folder is the aircraft actually using?
FSX loads the folder selected by the active livery’s sound= line in aircraft.cfg. It does not automatically use every folder whose name begins with “sound”.
- Close FSX and make backups. Copy
aircraft.cfgandsound.cfgbefore editing either file. - Find the active aircraft folder. Starting from the folder containing
FSX.exe, openSimObjects\Airplanesand then the add-on’s folder. Itsaircraft.cfgshould normally sit beside the model, panel, texture and sound folders. - Check for an extra folder level. A mistake we see constantly is an archive extracted as
AircraftName\AircraftName\aircraft.cfg, or a sound set placed atsound\sound\sound.cfg. FSX will not find those files where the configuration expects them. - Find the selected
[fltsim.x]section. Match the aircraft or livery shown in the FSX selection menu, then inspect itssound=line. - Match the value to the folder. An empty
sound=entry selects the folder namedsound. A value such assound=RRselectssound.RR. - Inspect the chosen folder. It needs a valid
sound.cfgand either the referenced WAV files or a working alias to another installed aircraft. - Restart and retest. Save configuration files as plain text, restart FSX and load the same variant again.
Do not put a normal aircraft engine-sound package in FSX’s top-level Sound directory unless its documentation explicitly identifies shared gauge audio. Aircraft engine files normally belong inside the aircraft folder. If the package itself appears misplaced, compare it with the expected FSX aircraft folder layout.
Why does only one livery or engine variant have no sound?
One silent variant almost always has a different sound= value from the working variants. For example, one livery may select sound.CFM while another mistakenly selects a missing sound.IAE folder.
Correct that variant’s entry or install the sound folder it was designed to use; do not rename unrelated folders until you know what the package expects. Our explanation of how each [fltsim.x] entry chooses aircraft sounds covers the relationship between liveries, variants and folder suffixes.
How do I repair a broken sound.cfg alias?
A broken alias is repaired by making its donor path match a real aircraft folder in the same active FSX installation. An alias-only file commonly contains an entry resembling [fltsim] alias=DonorFolder\sound.
- Use the donor aircraft’s exact folder name under
SimObjects\Airplanes, not its title in the FSX aircraft menu. - Confirm that the donor’s named sound folder exists and contains its own working
sound.cfgand WAV files. - Restore a removed default aircraft when the add-on was designed to use its sounds.
- Check older FS2004 conversions carefully; they may reference an aircraft folder that FSX never installed.
- Make sure the alias does not point into a boxed FSX installation while you are running Steam Edition, or the reverse.
Repair the alias when the intended donor is available and suits the same engine type. Install a dedicated package when the donor is absent or inappropriate; pointing a piston aircraft, turboprop and jet at the same convenient sound folder produces incorrect engine stages and behaviour. Use the correct folder and configuration method for custom FSX engine sounds.
Why does my FSX A320 add-on have no sound?
An FSX A320 usually becomes silent because its variant selects a missing engine folder or its alias expects the default Airbus A321. FSX includes a stock A321 rather than a stock A320, so many A320 packages either bundle their own sounds or borrow an installed donor set.
- If the A320’s
sound.cfgaliasesAirbus_A321\sound, confirm that the default A321 folder and its sounds remain installed in the active copy of FSX. - If
aircraft.cfguses values such assound=CFMorsound=IAE, verify that the matchingsound.CFMorsound.IAEfolder was included. - If engine audio works but Airbus call-outs, warning tones or switch clicks are absent, install the documented gauges, modules and shared files supplied with that particular A320.
- If warnings work only after start-up, check the aircraft’s electrical power and required start procedure before treating the silence as a file fault.
Do not copy files from an unrelated A320 package merely because the aircraft names match. Different add-ons can use different gauges, engine variants and sound-event definitions.
What if sound.cfg exists but the aircraft is still silent?
The presence of sound.cfg proves only that a configuration file exists; it may still reference missing or unreadable WAV files. Enable file-name extensions in Windows and make sure it has not been saved as sound.cfg.txt.
- No interior sound: check the interior entries and their referenced WAV files.
- No exterior sound: check the external engine entries and files rather than replacing the whole package immediately.
- Only some engine stages are missing: the archive may be incomplete, or individual file names may not match the configuration.
- No switches, call-outs or warnings: these may be generated by panel gauges or modules instead of the main aircraft sound folder.
- No sound while used as AI traffic: inspect the aircraft’s
soundaifolder and configuration; the flyable-aircraftsoundfolder is a separate setup.
Extract the complete original archive while preserving its directory structure. Add only the gauges, modules and shared files documented for that aircraft; installing unrelated DLL files is not a safe sound repair.
Does FSX: Steam Edition use a different sound system?
FSX: Steam Edition uses the same basic aircraft sound folders, sound.cfg files and aliases as boxed FSX. The usual Steam-specific failure is an installer writing into a different or obsolete FSX directory.
Locate the copy of FSX.exe you actually launch, then inspect its SimObjects\Airplanes directory. If boxed FSX and Steam Edition have both been installed, confirm that the aircraft, donor aircraft and sound files all reside in the same active installation.