How do I install custom engine sounds in FSX?

To install custom engine sounds in FSX or FSX: Steam Edition, close the simulator, back up the aircraft’s existing sound folder, then copy the add-on’s sound.cfg and WAV files into it. Keep the supplied folder structure intact, restart FSX, and test engine start, power changes and both cockpit and external views.

Where does an FSX sound pack go?

Aircraft-specific engine sounds belong in the relevant aircraft folder under SimObjects\Airplanes, not in FSX’s main Sound directory.

The finished structure should normally be:

FSX\SimObjects\Airplanes\[aircraft folder]\sound\sound.cfg

Common default locations are:

• Boxed FSX: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes
• FSX: Steam Edition: C:\Program Files (x86)\Steam\steamapps\common\FSX\SimObjects\Airplanes

The path will differ if FSX or the Steam library was installed elsewhere. Our guide to finding the correct FSX aircraft folder covers boxed and Steam installations without assuming the default path.

A mistake we see constantly is putting aircraft WAV files in FSX\Sound. That directory holds simulator-wide audio; a flyable aircraft normally reads engine audio from its own active sound or sound.[suffix] folder.

I cannot find the folder (“non trovo la cartella” or “non c’è”)

If the expected folder is missing, start with the installation containing fsx.exe, then open SimObjects\Airplanes. Steam users can use Steam’s option for browsing the game’s installed files rather than guessing the path.

Inside the chosen aircraft folder, look for aircraft.cfg. If there is no plain sound folder, inspect the relevant [fltsim.x] entry for a value such as sound=PW; that variant uses sound.PW instead. An advanced aircraft may also generate some audio through gauges or modules, in which case its own documentation takes precedence.

What should a custom FSX sound package contain?

A complete FSX engine sound pack normally contains sound.cfg plus the WAV recordings that the configuration references.

Do not combine two complete sets unless you are prepared to edit and verify sound.cfg. A configuration written for one collection of filenames will not automatically find recordings taken from another. Our practical jet sound-set example shows the usual relationship between cockpit WAV files, engine WAV files and the replacement configuration.

How do I get sound and install the pack safely?

Use a sound package made for FSX and for the intended aircraft or engine type, then install it manually so that you can verify the destination and retain a working backup.

1. Close FSX completely. Do not replace files while the simulator has the aircraft or its sounds loaded.
2. Extract the download. Unpack the ZIP or other archive into a temporary folder before copying anything into FSX.
3. Read the included instructions. Check whether the package replaces a complete folder, selected WAV files, a particular engine variant or AI sounds.
4. Identify the target aircraft. Open its folder under SimObjects\Airplanes and confirm that it contains the expected aircraft.cfg, model and texture folders.
5. Back up the existing sound set. Copy the active sound or sound.[suffix] folder outside the FSX installation. Back up aircraft.cfg too if you will edit its sound= entries.
6. Copy the new files at the correct level. The active sound folder must contain sound.cfg and the WAV files directly. If the result is sound\sound\sound.cfg, it is nested one level too deep.
7. Check the real file extension. With Windows file extensions visible, confirm that the configuration has not been saved as sound.cfg.txt.
8. Restart and test. Listen at engine start, idle, increasing power and shutdown. Test the cockpit and an external view because FSX can assign different files and volume behaviour to each.

If an old automatic installer points to the wrong FSX directory, cancel it and install the extracted files manually where possible. Copying into a protected Program Files location may also require Windows permission.

Which sound pack should I use for PW or a Singapore Airlines repaint?

Choose the pack by the simulated engine variant, not merely by the airline name or livery painted on the aircraft.

PW usually means Pratt & Whitney, but it does not identify one universal sound. A package labelled for a particular PW engine family should be used only with the aircraft and engine variant for which it was configured. The same principle applies to General Electric, Rolls-Royce, piston and turboprop packages.

A Singapore Airlines repaint does not automatically need a unique engine sound folder. Check the repaint’s base aircraft, model and documentation to establish which engine option it represents. If several liveries share one base model and the same unsuffixed sound folder, replacing that folder changes the sound for all of them.

If “Singapore Airlines sounds” means boarding music, safety audio or cabin announcements rather than engine noise, those use a different installation method; see our instructions for adding cabin announcements and passenger audio to FSX.

Can different liveries use different engine sounds?

Yes. FSX can select a separate sound folder for each aircraft variant through the sound= entry in its [fltsim.x] section.

• A blank sound= entry uses the standard sound folder.
• sound=PW uses a folder named sound.PW.
• sound=GE uses sound.GE, provided that folder exists and contains a valid configuration.

Edit the particular [fltsim.x] section belonging to the livery or variant. If several variants need the new set, change each relevant entry and retain unique, sequential section numbers.

Another method is an alias. A small sound.cfg can contain a [fltsim] section and an entry such as alias=DonorAircraft\sound. The receiving aircraft points to the donor aircraft’s sound folder, not the other way around. The donor folder and referenced sound set must remain installed.

Changing a donor sound folder also changes every aircraft that aliases it. Use a suffixed folder instead when only one livery or engine option should receive the replacement.

Why is there no sound after installation?

Most missing FSX sound problems are caused by an extra folder level, an inactive sound suffix, a broken alias or a sound.cfg that references WAV files which are not present.

• The original sound still plays: Confirm that you modified the aircraft actually selected in FSX. Check its sound= value and whether the active folder is an alias.
• The aircraft is completely silent: Make sure sound.cfg is directly inside the active sound folder. Verify that FSX sound is enabled, its volume sliders are above zero and Windows is using the intended playback device.
• Only start, shutdown or certain power ranges are silent: The configuration probably calls for a missing or differently named WAV file. Restore the package as a complete set rather than mixing it with another one.
• Only cockpit or external sound changed: Some packages replace only one group of recordings. This may be intentional rather than an installation fault.
• The copied files seem to disappear or remain unchanged: Check that you are editing the active boxed or Steam installation and approve any Windows permission request for the protected folder.
• AI traffic remains silent: A flyable sound folder does not necessarily provide the aircraft’s AI audio. Install the supplied soundai folder and configuration only as directed by the package.
• A complex add-on ignores the replacement: Gauge-controlled or module-controlled audio may bypass parts of FSX’s standard sound system. Replacing the normal folder may affect only native engine events.

Restore the backed-up folder before trying a second installation. Once the original audio works, compare the new sound.cfg, its filenames and the active aircraft variant. For a closer diagnosis, use our checklist for fixing an FSX add-on aircraft with no sound.

Do FSX sound packs work in FSX: Steam Edition?

Yes. Most standard FSX engine sound packs work in FSX: Steam Edition because it retains the same aircraft sound-folder system.

The common failure is not audio compatibility but installation location. Older installers may target a boxed FSX directory even when only Steam Edition is in use. Install manually into the Steam copy’s actual SimObjects\Airplanes folder, preserve the archive structure and restart the simulator before testing.