Fix a microphone not working in online flight simulators: check permissions, input devices, push-to-talk, voice clients, radios and Bluetooth audio.
In online flight simulators, a microphone usually fails because the operating system has blocked access, the voice client has selected the wrong input, push-to-talk is unbound or conflicting, or the radio connection is not active. Test the mic in the operating system first, then select it explicitly in the online-network client and verify push-to-talk.
The same fault pattern applies across Microsoft Flight Simulator, X-Plane, FSX and Prepar3D. A mistake we see constantly is changing simulator sound settings when the microphone is actually controlled by a separate pilot or voice client.
How do I fix my flight simulator microphone?
Work through the audio chain in order, stopping as soon as the signal disappears.
- Test the microphone outside the simulator. Use the operating system's input-level meter or recording test. Check the headset's physical mute switch, reconnect its USB plug and try a direct computer port rather than an unpowered hub. If the system meter does not move, the simulator and online client cannot use the mic.
- Allow microphone access. In the operating system's privacy settings, permit microphone access for desktop apps and for the relevant client where it is listed. Restart the voice client after changing permission; an app already running may not recognise the new access.
- Select the named input device. Open the pilot client's audio settings and choose the microphone explicitly instead of leaving it on
Default. Windows can change its default after connecting a webcam, controller headset, VR headset or Bluetooth device. For VATSIM, our device-selection, level and push-to-talk checks cover the client-specific setup. - Check the input meter and level. Speak normally and look for movement in the client's microphone meter. No movement means the wrong device or blocked permission; barely visible movement suggests low input gain or excessive distance from the mic. A meter pinned at maximum indicates clipping, so reduce the level.
- Bind push-to-talk in the voice client. The simulator's own radio or intercom binding may not operate the online client. Choose a keyboard or controller button that is not assigned to another function, then confirm that the client's transmit indicator appears while it is held. Running the simulator and client with different administrator privileges can prevent a keyboard binding from being detected; run both normally at the same privilege level.
- Confirm the network and radio state. Connect the pilot client, tune the controller's frequency as the active frequency rather than standby, select the correct COM transmitter and power the aircraft's avionics or audio panel. If the mic meter and transmit indicator both work, the remaining fault is usually radio configuration, client connectivity or the absence of anyone monitoring that frequency.
What does each microphone symptom mean?
The point at which the signal fails usually identifies the faulty setting.
| Symptom | Most likely cause | What to check |
|---|---|---|
| No operating-system input movement | Muted, disconnected or unrecognised microphone | Physical mute, cable, USB port and system input selection |
| System detects speech, but the client does not | Wrong client input or blocked app permission | Client audio device, privacy access and an app restart |
| Client meter moves, but no transmit indicator appears | Push-to-talk is missing or conflicting | Client binding, duplicate assignments and app privileges |
| Transmit indicator appears, but nobody hears you | Radio, frequency or network connection problem | Active COM frequency, transmit selection and voice connection |
| Speech is broken or robotic | Bluetooth profile, clipping, USB instability or connection loss | Input gain, headset profile, direct USB connection and network stability |
Why can I hear ATC but they cannot hear me?
If you can hear ATC but cannot transmit, the output side is working while the microphone, push-to-talk or transmit-radio selection is not.
Watch both the input meter and transmit indicator. If the meter does not move, reselect the microphone and check permissions. If it moves but the transmit indicator stays off, repair the push-to-talk binding. If both work, check that the correct COM radio is selected for transmission and that the frequency is active.
Microsoft Flight Simulator's built-in ATC audio settings do not configure a separate online-network client. MSFS users should check the separate pilot-client and radio setup used for VATSIM rather than repeatedly changing the simulator's voice or ATC volume.
Does online multiplayer automatically include voice chat?
Online multiplayer does not automatically provide an ATC voice channel, and some flight simulators display other aircraft without offering open voice communication at all.
Networks such as VATSIM normally use a separate desktop pilot client to carry voice and synchronise radio frequencies. Our explanation of how online ATC clients handle voice and radio data clarifies what runs inside the simulator and what runs separately. On a console, do not assume that a desktop network client is supported simply because the simulator itself has multiplayer.
Why does a Bluetooth microphone sound bad or stop working?
Many Bluetooth headsets switch from high-quality stereo playback to a lower-bandwidth hands-free profile when their microphone becomes active.
Select the headset's intended communications input and output explicitly in both the operating system and voice client. If it continues to disconnect, distort or switch devices, use a wired or USB microphone for radio work. Also avoid stacking aggressive noise suppression or automatic gain from the headset utility, operating system and voice client, as combined processing can clip words or suppress quieter speech.