Fix no sound in Prepar3D by checking mute controls, Windows audio routing, add-on sound.cfg files, configuration resets and repair options.
No sound in Prepar3D is usually caused by the simulator being muted, its audio sliders being down, Windows routing audio to the wrong device, or an aircraft add-on with missing files. Test a default aircraft first, then check Prepar3D’s sound settings, Windows Volume Mixer and the selected output before repairing anything.
| Symptom | Likely cause | First check |
|---|---|---|
| Every application is silent | Windows, driver or hardware problem | Play a Windows system sound |
| Only Prepar3D is silent | Mute command, mixer level or wrong output | Prepar3D sound controls and Volume Mixer |
| Only one aircraft is silent | Missing files, broken alias or incompatible add-on | Load a default aircraft with engines running |
| Engines work but ATC is silent | Voice volume, communications device or missing voice content | Check whether ATC text appears |
| Only call-outs or warnings are missing | Incompatible custom sound module | Confirm the add-on supports your Prepar3D generation |
How do I restore sound in Prepar3D?
Work through the audio chain in order; changing several settings at once makes the fault harder to identify.
- Load a controlled test: start a scenario with an included Prepar3D aircraft already running. A cold-and-dark aircraft may correctly remain quiet until its electrical system, fuel and engines are operating.
- Cancel the simulator mute: use the assigned Sound On/Off command, normally
Qin a default control set. Press it once, wait a few seconds and test again; customised control profiles may use another key. - Check Prepar3D’s sound options: confirm sound is enabled and raise the relevant engine, cockpit, environment and voice sliders. The exact labels differ between Prepar3D generations.
- Open Windows Volume Mixer: do this while a scenario is running so
Prepar3D.exeappears. Make sure the application is not muted and that its individual volume has not been reduced to zero. - Select the correct output: Windows may route Prepar3D to an HDMI monitor, disconnected headset, VR headset or Bluetooth communications endpoint. Set the intended device as the Windows output and, where your Prepar3D version offers device selectors, choose the same device there.
- Restart after changing devices: close Prepar3D completely, connect the required speakers or headset, select them in Windows, then relaunch the simulator. Prepar3D may retain the device available when it started rather than following a later Windows change.
- Remove audio-processing conflicts: temporarily disable spatial sound, device enhancements and exclusive-mode access. Also close virtual mixers, voice applications and third-party sound utilities while testing. Re-enable them individually once ordinary audio works.
If other applications are also silent, the fault is outside Prepar3D. Check the physical connection, Windows output, device volume and audio driver before changing simulator files.
Why does only one Prepar3D aircraft have no sound?
If default aircraft produce sound, Prepar3D and Windows are functioning; the silent aircraft package is incomplete, incorrectly installed or incompatible.
A conventional aircraft package normally contains a file such as SimObjects\Airplanes\AircraftName\sound\sound.cfg together with its WAV files. Some packages instead use an alias= entry that points to another aircraft’s sound folder. That target must exist in your installation.
- Confirm that the aircraft has a
soundfolder and a readablesound.cfg. - Check that filenames referenced by
sound.cfgmatch files actually present in the folder. - If the configuration uses an alias, verify that the named aircraft and its sound folder exist. Aircraft copied from FSX often reference a default FSX model that is absent from Prepar3D.
- Run the aircraft’s proper installer rather than copying only its aircraft folder. Shared modules and dependencies may be installed elsewhere.
- Use a package built for your Prepar3D generation. Later 64-bit Prepar3D releases cannot load old 32-bit gauge or sound modules, although ordinary WAV-based aircraft sounds may still work.
Our example of a complete Prepar3D-compatible jet sound package is useful for comparing the expected folder, configuration and WAV-file structure. Do not overwrite a payware aircraft’s files without making a backup.
If the same aircraft also has blank panels or missing instruments, treat it as a wider installation problem rather than an audio setting. Follow our checks for incomplete Prepar3D aircraft dependencies and gauges.
Why can I hear engines but not ATC in Prepar3D?
ATC silence usually affects the voice channel or its content rather than the main aircraft audio system.
Open the ATC window and request a transmission. If the response appears as text but produces no speech, raise the voice or communications volume and check any separate voice-output selector exposed by your Prepar3D version. Windows can also assign its default communications device to a headset while engine audio continues through speakers.
If neither text nor speech appears, check the aircraft’s electrical power, radio tuning and active frequency first; that is not necessarily an audio failure. When all ATC text works but every voice remains absent after routing checks, repair the installed Prepar3D content using the installer that exactly matches your installed release.
Should I reset or reinstall Prepar3D to fix missing sound?
Reset the simulator configuration before attempting a full reinstall, but only after checking mute, routing and aircraft-specific files.
- Exit Prepar3D: ensure it is no longer running.
- Back up the configuration: locate
%APPDATA%\Lockheed Martin\Prepar3D vX\Prepar3D.cfg, replacingvXwith your installed generation, and rename it toPrepar3D.cfg.old. - Launch and retest: Prepar3D will create a fresh configuration. Test an included aircraft before restoring add-ons or changing settings.
This reset changes many simulator options, so record important graphics and control settings first. If it makes no difference, close Prepar3D and restore the backup.
Use the matching Prepar3D installer’s repair or maintenance option when default sound folders, ATC voice content or core application files are missing. Back up modified aircraft and configuration files first. A complete reinstall should be the final step: it will not repair a Windows routing problem, and leftover third-party modules can reproduce the same fault immediately.