FlightGear sound not working? Fix audio, flight music and OpenAL errors, Bluetooth headphones, muted mixers, missing files and wrong output routing.
FlightGear sound usually fails because audio is muted, the operating system has routed the simulator to the wrong device, OpenAL could not initialise, or an aircraft package is missing its sound files. Enable sound, check both mixers, select the output before launch, restart FlightGear, and test a bundled aircraft.
How do I enable audio in FlightGear?
To enable audio in FlightGear, check the simulator controls, operating-system mixer and output device in that order.
- Load a reliable test aircraft. Choose an aircraft included with FlightGear and start with its engine running if that option is available. Check cockpit and external views. A mistake we see constantly is testing a cold-and-dark aircraft that is correctly producing little or no sound.
- Enable FlightGear sound. Open the sound or audio controls available in your FlightGear build. Confirm that sound is enabled, mute is off, and the master, engine and effects levels are above zero. Saved launcher profiles can preserve muted channels; use our guide to isolating engine, ATC and cockpit volume settings if only part of the mix is missing.
- Check the operating-system mixer. Leave FlightGear running while inspecting the mixer because some systems show an application only after it creates an audio stream. Confirm that FlightGear itself is unmuted and assigned to the intended speakers, monitor or headset. Hearing another application does not prove that FlightGear uses the same output.
- Select the output before launching. Quit FlightGear completely, connect the required USB, HDMI or Bluetooth device, make it the system output, then relaunch. OpenAL normally opens an audio endpoint during start-up and may not follow a device change made afterwards.
- Remove sound-disabling options. Inspect saved launcher profiles and additional command-line arguments for
--disable-sound. Remove it. Using--enable-soundtemporarily can confirm that a stored option was overriding the normal setting. - Read the first relevant log error. Open the launcher log, console output or terminal output and search for
OpenAL,ALC,sound,.xmland.wav. The first audio-related failure is usually the cause; the warnings after it may only be consequences.
Use the symptom to choose the next fix
The pattern of missing sound usually identifies which part of the audio chain has failed.
| Symptom | Likely cause | Best next action |
|---|---|---|
| Every aircraft is silent | Mute, disabled sound, wrong output or OpenAL failure | Check both mixers, restart with the correct output, then inspect the log |
| Only one add-on aircraft is silent | Missing, incompatible or incorrectly installed aircraft sound files | Test a bundled aircraft, then reinstall only the affected package |
| Sound stopped after connecting headphones or a monitor | FlightGear remains attached to the previous endpoint | Set the new device as the output and restart FlightGear |
| Chrome has sound but FlightGear does not | The applications are routed or muted independently | Inspect FlightGear's own mixer entry and output assignment |
| Engine sound works but radio audio does not | Unpowered avionics, tuning, reception or audio-panel settings | Check the aircraft's electrical system, radios and channel volumes |
| Aircraft sounds work but there is no background music | Normal FlightGear behaviour | Do not treat the absence of continuous music as an audio failure |
| Sound crackles when frame rate collapses | Audio underruns or a problematic device mode | Reduce simulator load and test a standard stereo output |
What if the headphones are Bluetooth?
Bluetooth headphones work with FlightGear, but they should be connected and selected before the simulator starts.
Choose the normal stereo media endpoint, often described by the operating system as stereo or A2DP, rather than a hands-free, headset or call profile. The hands-free profile is intended for simultaneous microphone use and can produce poor-quality mono audio or cause a device mode that OpenAL cannot use reliably.
If the system switches profiles when another application activates the headset microphone, close that application or test without the Bluetooth microphone. Then quit and reopen FlightGear. A headset showing “connected” is not enough: it must also be the active playback endpoint.
On Windows, per-application routing can leave FlightGear assigned to old speakers even after the default changes. Our Windows 11 checks for app-specific audio routing and device changes cover that part of the diagnosis.
Why does Chrome have sound when FlightGear does not?
Chrome audio and FlightGear audio are separate streams, so one can work while the other is muted or routed elsewhere.
The standard FlightGear desktop application does not play through Chrome. Browser audio proves that the speakers or headphones can produce sound, but not that OpenAL opened the same device. Conversely, muting a Chrome tab does not mute FlightGear. Compare each application's mixer entry while both are running.
What does a “flight music error” mean in FlightGear?
“Flight music error” is not a standard FlightGear diagnostic category, so the exact symptom or log message determines the fix.
A normal flight is built around aircraft, cockpit, wind, environmental and radio sounds rather than a required continuous music track. If those sounds work but no background music plays, there is usually nothing to repair. Music or cabin audio supplied by a particular add-on is part of that aircraft package, not a test of FlightGear's global sound system.
If “flight music error” means that the entire flight is silent, follow the enable-audio procedure above. If the log names OpenAL or an audio device, troubleshoot the output device. If it names a missing sound XML or WAV file, repair the affected aircraft or base-data package. The correct flight music fix depends on which of those messages appears first.
Why is only one aircraft or audio channel silent?
If a bundled aircraft produces sound, FlightGear's global audio system and OpenAL output are working.
Aircraft packages provide their own sound definitions and samples. One model can therefore be silent because its archive was extracted incompletely, its sound paths use the wrong letter case on a case-sensitive file system, its files were merged with an older copy, or the package was made for an incompatible FlightGear data generation.
Remove or rename the affected aircraft folder and install a clean copy without merging it over the old files. Preserve the archive's internal directory structure. Do not copy WAV files from an unrelated aircraft: its sound configuration may expect different names, paths and simulation properties.
If engine and environmental sounds work but radio or navigation identifiers do not, reinstalling OpenAL is the wrong fix. Confirm that the battery, avionics and radios are powered; the correct frequency is tuned; the transmitter is receivable; and the relevant audio-panel channel and volume are enabled. Aircraft differ in how closely they model those controls.
What do OpenAL and missing-file errors mean?
An OpenAL device error indicates a global output or audio-library problem, while a missing-file error usually identifies damaged or mismatched FlightGear data.
- OpenAL or device initialisation errors: select a conventional stereo output, close software that may have taken exclusive control of it, and restart FlightGear. If the same error remains on every aircraft, repair FlightGear and the audio components supplied through the same installation method.
- Missing aircraft sound XML or WAV files: replace the affected aircraft if only that model fails. A malformed aircraft sound configuration can also stop some or all of its samples from loading.
- Missing files on bundled aircraft: repair the base-data installation and verify that it matches the FlightGear executable. Our explanation of FlightGear data-file and
FG_ROOTerrors covers mismatched or incomplete data packages. - Errors after moving folders: make sure a custom
FG_ROOTpoints to the complete matching base-data directory, not an aircraft, scenery or individual sound subfolder. - Permission errors: confirm that the simulator can read its installation and aircraft directories. Do not run FlightGear permanently as an administrator merely to conceal incorrect ownership or permissions.
- Linux library conflicts: avoid combining a FlightGear executable from one packaging method with OpenAL libraries or base data from another. Repair the installation as one consistent set.
Do not download a loose audio DLL or substitute random sound files. That often replaces a clear missing-component error with a harder library or configuration mismatch.
Is the FlightGear sound system good?
FlightGear's sound system is capable, but the audible quality depends heavily on the aircraft package, its recordings and its sound configuration.
OpenAL can position sources and respond to cockpit or external viewpoints, while aircraft definitions decide which samples play and how they change with engine state and other simulation properties. A carefully authored aircraft can therefore sound convincing, while an older or incomplete model may have sparse, repetitive or poorly balanced audio.
Output hardware also matters. A Bluetooth hands-free profile can make a good sound set seem thin or distorted, and testing a stationary aircraft with its engine off says little about the system. Compare a bundled aircraft in cockpit and external views using a normal stereo output before judging the installation.
When should I reset FlightGear or reinstall it?
Reset preferences only after checking sound controls, routing, launch arguments and the log; reinstall only the smallest component implicated by your tests.
- Reset user preferences when every aircraft is affected and a saved setting or launcher profile appears responsible. Back up and rename the per-user settings file or directory so FlightGear creates clean preferences at the next start. Exact locations vary by operating system and packaging method.
- Reinstall one aircraft when bundled models work and only that aircraft reports missing or invalid sound files.
- Repair the base data when bundled aircraft also report missing sound XML or sample files, particularly after changing
FG_ROOTor combining releases. - Repair FlightGear and its packaged audio components when OpenAL cannot initialise with any aircraft or output device.
Reinstalling the application may leave per-user settings untouched, so it will not necessarily remove a saved mute or --disable-sound option. When several parts of the installation behave incorrectly, use our clean first-time FlightGear setup procedure to establish a known-good baseline with bundled content before restoring add-ons.