What is DCS-SRS, and how do I set it up in DCS World?

DCS-SRS (DCS SimpleRadio Standalone) is a separate voice client that links to DCS World and makes multiplayer communication behave like an aircraft radio. Install its client and DCS integration, select your microphone and headphones, bind radio push-to-talk controls, then connect to the SRS address used by your multiplayer server.

What does DCS-SRS do in DCS World?

DCS-SRS turns multiplayer voice into frequency-based radio traffic tied to your aircraft’s radio state. Its DCS integration reads details such as the selected radio, frequency and modulation; server settings can also enforce distance, line of sight, coalition restrictions and encryption.

Full-fidelity aircraft normally use their cockpit radio controls. Aircraft with simplified radio systems may rely more heavily on SRS bindings or its radio overlay. If the simulator itself is still unfamiliar, our primer to DCS multiplayer, controls and aircraft selection covers the basics to sort out first.

SRS is separate from DCS World’s built-in Voice Chat, and the two systems do not share users or transmissions. Ordinary players need only the SRS client; install the server component only if you are operating your own multiplayer voice server.

How do I install and configure DCS-SRS?

Install the client, point its integration at the active DCS Saved Games profile, configure audio and controls, and then connect using the address supplied by the multiplayer server.

1. Obtain the official installation package. Use the release published by the DCS-SRS project, or the compatible version specified by your multiplayer community. Avoid repackaged installers.
2. Close DCS World and install the SRS client. Give SRS its own application directory rather than placing it inside an aircraft, terrain or Mods folder. Allow the installer to elevate permissions if Windows requests this.
3. Select the correct DCS Saved Games folder. This is commonly %USERPROFILE%\Saved Games\DCS, although older or retained installations may use a folder such as DCS.openbeta. The mistake we see constantly is selecting the main DCS installation directory instead. Steam and standalone editions both use Saved Games for user integration; our explanation of their installation and update differences can help if both are present.
4. Install the DCS integration scripts. Let the SRS installer add or update the required files in the profile’s Scripts area. Depending on the SRS release, this may include an entry associated with Export.lua. Back up that file if you have edited it for other hardware or add-ons, and never replace the whole file with a generic copy.
5. Choose fixed audio devices. In the SRS client, select the actual microphone and headset or speakers rather than relying on Windows’ Default device. Speak into the microphone and confirm that the input meter moves; use the local audio preview to set a clear level without clipping.
6. Bind your radio controls in SRS. Assign a push-to-talk button and the radio-selection controls needed by your aircraft. You can either select a radio and use one common PTT, or enable the combined radio-switch/PTT behaviour. These are SRS bindings, not the DCS communications-menu key. Our HOTAS button-binding walkthrough explains how to avoid duplicated or conflicting assignments.
7. Connect to the SRS server. Start the client before joining DCS. Many multiplayer servers advertise an automatic SRS connection; accept the prompt if offered. Otherwise enter the supplied SRS host and port manually. Do not assume the DCS game port is also the SRS port.
8. Power and tune the cockpit radio. Join an aircraft, switch on the required electrical and radio systems, select the intended radio, tune the published frequency and check whether it uses AM or FM. Set an audible radio volume before requesting a radio check.

How can I tell whether SRS is working?

SRS is working when the client detects DCS World, displays populated aircraft radios and responds to both microphone input and PTT.

• The client or overlay should show the aircraft’s radio frequencies rather than empty or generic entries.
• The microphone meter should move when you speak.
• Holding PTT should highlight the radio you are transmitting on.
• Changing a cockpit frequency or selected radio should be reflected in SRS.
• A second player on the same frequency and modulation should hear a brief radio check, subject to the server’s realism restrictions.

The local microphone preview verifies audio quality but does not prove that the DCS integration, radio tuning or server connection works. Check each stage separately.

Why is SRS connected but I cannot hear or transmit?

A connected status proves only that the client reached the SRS server; wrong audio devices, missing DCS integration and incorrect cockpit radio settings can still prevent communication.

• DCS is not detected: rerun the installer against the profile DCS is actually using. The active profile usually contains the most recently updated Logs\dcs.log. If you maintain a customised Export.lua, check that the SRS entry remains present and that an earlier export script is not failing.
• The microphone meter is silent: select the physical input device explicitly and allow desktop applications to use the microphone in Windows privacy settings. Recheck this after changing a USB or Bluetooth headset.
• PTT does nothing: bind the button inside SRS, not only in DCS. Remove duplicate assignments and decide whether radio selection and PTT are separate controls or combined.
• You transmit but nobody hears you: verify radio power, selected radio, frequency, AM/FM modulation and encryption. Two radios showing the same number will not communicate if one is using AM and the other FM.
• You cannot hear other pilots: confirm the SRS output device and cockpit radio volume. The server may also enforce line of sight, maximum range, coalition security or spectator restrictions.
• Manual connection fails: use the dedicated SRS address and port supplied by the server. Permit the SRS client through Windows Firewall on the network profile you use. Players normally do not need router port forwarding; that is generally a server-hosting requirement.
• The server reports a version problem: update to the compatible client release requested by the operator, then rerun its installer so the application and integration scripts match.

Do I need DCS Voice Chat as well as SRS?

No. Use the communication system chosen by the multiplayer server; running DCS Voice Chat alongside SRS is optional and does not connect their users.

If both are enabled, do not assign the same PTT button to both unless the server specifically expects that arrangement. Otherwise one press can transmit twice, create echo or send a conversation to the wrong channel. For an SRS-based server, leaving DCS Voice Chat unbound or disabled is usually the clearest configuration.