Skip to content

Home

Jump to bottom
OzDeaDMeaT edited this page May 2, 2021 · 67 revisions

Welcome to the DCS-SimpleRadio Stand Alone wiki!

If you find any information in this wiki/documentation which requires correction or updating, please leave a comment, contact one of the contributors, or leave a message on the SRS discord.

Contents

Features & Project Goal

The DCS SimpleRadio Standalone (DCS-SRS) is a project originating as a TeamSpeak 3 plugin called DCS-SimpleRadio.

The goal of this project is to bring integrated Radio Comms into DCS similar to my existing TS plugin and other plugins (Aries, UniversRadio, TARS), however, without relying on TeamSpeak.

SimpleRadio Standalone is meant to complement other VOIP software, such as TeamSpeak or Discord, allowing players to use "full radio voice comms" in DCS World, should the player desire, along with the option for the SRS client to automatically connect to a DCS-SRS multiplayer server. TS/Discord is then used as a fall back to establish frequencies, or for those that don't have the radio.

As of September 26th, 2016, the following features are available:

  • All FC3 Aircraft with Realistic Radios and Frequencies + Guard Frequencies.
  • All "Full Fidelity Clickable" cockpit aircraft including the Gazelle.
  • Hotkeys for PTT + Switching Active Radio (Gazelle + A10C + FC3 only)*.
  • In Cockpit PTT (UH-1H, Mi-8, L-39, F-86, MiG-15, MiG-19, Mig-21, F-5E, P-51D/TF-51D, Yak-52, F-14)*.
  • Intercom Support in the L-39, UH-1H, SA342 Gazelle, *.
  • GCI / CA / ATC Radio
  • Voice encryption for A-10C / Mirage / A-10A / F-15C / Gazelle / F/A-18C
  • Radio Overlay indicating current frequencies, selected radio and active light when Transmitting or Receiving
  • Built from Scratch voice protocol using OPUS encoding - allows much greater flexibility as I'm not dependent on TS3 or Mumble.
  • Client Microphone Boost
  • Audio Separation - Left, Right or Both
  • Radio Effects for voice
  • Optional Line of Sight limitations (Server side)
  • Optional Radio Distance Limitations (Server Side)
  • Signal fading (volume) for Line of Sight Loss and over Distance
  • Expansion Radios - Ability to expand the existing radio set on the aircraft for training and ease of communication. (Server Side)
  • Optional IRL Transmit behaviour - Stops you hearing transmissions when transmitting on a radio (Server Side)

*likely requires updating and/or corrections

Installation & Setup

  1. Download and extract the .zip containing the latest release - available here: https://github.com/ciribob/DCS-SimpleRadioStandalone/releases

  2. Run the Installer.exe NOTE: If Windows prevents the .exe from running, click "Show More" followed by "Run Anyway"; this applies to the Client and Server executables as well.

  3. Step 1: Pick Install Location - This is the arbitrary install path for SimpleRadio Standalone, typically something like C:\Program Files\DCS-SimpleRadio-Standalone Note this path, so you are able to navigate to the program folder after installation

  4. Step 2: Locate Saved Games - Locate the folder that DCS settings are saved to, typically C:\Users\CurrentUser\Saved Games. NOTE: If your 1.5 and 2.0 saved games are in different parent folders, it is recommend to consolidate their Saved Games location in order to have SimpleRadio function on both DCS branches

  5. Step 3: Install Or Remove - To install or update to the latest version of DCS-SimpleRadio Standalone, click the 'Install/Update SimpleRadio' button. The installer may hang or become unresponsive until the dialogue indicating installation has completed appears. Updating should not change your keybindings! (We're thinking of you <3)

  6. All done! The folder you selected for 'Step 1: Pick Install Location' should now open. If you would like, create a shortcut for the 'SR-ClientRadio.exe' and/or 'SR_Server.exe' depending on which you would like to use.

How to Uninstall

Run the 'Installer.exe' and click the 'Remove DCS-SimpleRadio Standalone' button; If you have any feedback that would have prevented the uninstallation, please contact the project owner on GitHub!

Client Setup

First, you must run the 'SR-ClientRadio.exe' in order to configure (and connect to servers of) SimpleRadio!

General

Here you can select your Input (Microphone), Output Device (Speakers), modify the boost for both, preview your input audio, connect to a server, and toggle the radio overlay.

Preview audio will also preview any voice modulation; you hear what the server hears.

Controls

Here is where you set up your Key Bindings for SimpleRadio Each radio slot functions the same; they will be combined below

  • Radio # - Set the key/button you want to change the active radio to Radio #
  • Radio # Modifier - If this is set, this key must also be pressed in order to change radios
  • Common PTT - Button used to enable Push to Talk (PTT)
  • Common PTT Modifier - If this is set, this key must also be pressed to enable Push To Talk
  • Overlay Toggle - Hide or Display the SimpleRadio overlay. The only Modules that allow the User to interact with the overlay are the FC3 Aircraft, SU-25T and GCI / Spectators Slot
  • Overlay Toggle Modifier - If this is set, this key must also be pressed to Hide or Display the SimpleRadio overlay

Settings

  • Auto Connect Prompt - Enabled Auto-Connect notification, otherwise it will connect silently
  • Radio Rx/Tx Effects - Enabled the simulation of squelch & mic click at the start and end of a transmission
  • Radio Encryption Effects - Enables simulation of Encryption & Decryption audio tones from a KY-58
  • Radio Switch works as PTT - When this button reads 'On', the keybinding used to switch between radios will also act as Push to Talk in addition to switching your active radio. Common PTT will still function
  • Radio # Audio Channel - If you have Stereo audio enabled for your Output Device, this determines which channels the relevant radio audio will be sent. Left for the Left Channel, Right for the Right Channel, Both for the Left AND Right channels simultaneously
  • Intercom Audio Channel - Same as radio audio channels, but for the intercom on multi-crew ships
  • Reset Radio Overlay - Clicking the RESET button will hide the overlay and anchor in the default position on your desktop with full Opacity (fully visible)

SimpleRadio in DCS

In order to move the SimpleRadio overlay, left-click on a Channel Name or Frequecy and drag. SimpleRadio WILL NOT FUNCTION if you are not connected to a server; troubleshooting must be done while connected to a SimpleRadio server

FC3/Su-25T Modules

In the Lo-Fidelity modules (referred to here as FC3 modules) or spectator / CA / GCI slot there are no In-Game controls for SimpleRadio, everything must be done through the overlay and SimpleRadio keybinds

  • Frequency Change - 4 clickable buttons above and below the relevant radio Channel will increase and decrease the frequency respectively
  • Volume Control - the slider below a channel controls that channels volume
  • Guard - Right click on the frequency of a Channel to enable Guard for the mission specific channel Guard; a G will follow the frequency if this is enabled; the frequency text will turn Red instead of white if receiving on Guard.
  • Active Channel - The dot next to the active channel will be Green when no audio is being sent through; it will appear white if audio is being received on that channel; You can make a radio active by clicking on the frequency
  • Inactive Channel - The dot next to inactive (but not disabled) channels will be Orange
  • Disabled Channel - The dot next to disabled channels will be Red and either cannot be switched to in any manner while using the select module/aircraft

Hi-Fidelity DCS Modules

In Hi-Fidielty DCS modules, DCS-SRS, when properly installed, will link directly to the In-Game Cockpit radio settings. What you see in DCS is what DCS-SRS will follow, this includes Radio Frequencies, Radio Channels, Radio Volume, Channel Guard, etc...

There are a few exceptions, namely the A-10C/Gazelle/M2000-C : In order to change the active radio channel, you must use the Keybindings set in the SimpleRadio Client as these Aircraft in RL have HOTAS radio controls or in the case of the Gazelle, no animated controls yet.

Encryption TODO

SRS Server Setup

In order to host a DCS-SimpleRadio server, you must forward the following TCP and UDP port 5002. Once the necessary ports are open, simply run the 'SR-Server.exe'. It does not have to be run on a PC running DCS! You can edit the default server port by editing the server.cfg.

If you edit - make sure to update your port forwarding and always forward both protocols TCP and UDP

Start/Stop Server

Start and stop the server

Clients:

number of SR-Clients connected to the server

Client Admin

View names of connected clients; The names of the clients will be displayed as follows:

  • if the Client is not in a DCS mission
  • 'player' if the Client is in a Single Player DCS mission
  • if the Client is in a Multi Player DCS mission Kick a client to kick that client Ban a client to ban that client

Secure Coalition Radios On/Off

When turned ON - Each coalition can only hear other radios of the same Coalition. I.e. Red to Red, Blue to Blue, Spectator to Spectator

When turned OFF - Any coalition can hear any other coalitions radio. To keep your radio secure from eavesdropping, don't publish your frequencies to the enemy or if available, use encryption 👍

Spectator Audio:

When the button shows 'Enabled' spectators are given the ability to use SimpleRadio as if they were in a FC3 ship and may send/receive on any channel they select.

Auto Connect Feature - Server Owners ONLY - Clients don't need this file!

To enable SRS clients to be prompted automatically to connect just add the DCS-SRS-AutoConnectGameGUI.lua to the appropriate DCS Saved Games folder e.g. DCS.openbeta/Scripts/Hooks, DCS.openalpha/Scripts/Hooks or jut DCS/Scripts/Hooks

Edit the line shown below in your DCS-SRS-AutoConnectGameGUI.lua to your server address where SRS server is running. Port is optional. DCS must be restarted on the server for this file and any changes to take effect.

-- CHANGE FROM
SRSAuto.SERVER_SRS_HOST = "127.0.0.1" -- Port optional e.g. "127.0.0.1:5002"

--TO
SRSAuto.SERVER_SRS_HOST = "5.189.162417:5014" -- BuddySpike One
-- OR
SRSAuto.SERVER_SRS_HOST = " 37.59.10.136" -- TAW One (port optional)

Auto Export List:

Outputs JSON every 30 seconds to clients-list.json. This can be used to show what users are connected to the server on a separate webpage or app.

If this is your first time hosting a server, there are plenty of guides on the internet already dedicated to port forwarding! If you believe you have your ports forwarded and are still unable to get users connected to your server, make sure you have forwarded the ports on EVERY ROUTER between you and your ISP. Many times, your ISP will have a sort of virtual router installed or a physical router specific to your connection, somewhere in the physical node of your area. You are typically free to edit these, though the IP address to connect to them can vary. Call your ISP if you believe this is the case and cannot find the relevant IP to connect through

DCS Server Setup

TODO for Export requirements

Roadmap/Wishlist:

  • Server Favourites / History
  • Signal / white noise when near the edge of radio range

Troubleshooting:

  • Backup and then delete your Export.lua from Saved Games\DCS\Scripts, Saved Games\DCS.openalpha\Scripts, Saved Games\DCS.openbeta\Scripts. Then run the installer again.

  • Follow the FULL list of instructions here https://forums.eagle.ru/showpost.php?p=2963204&postcount=1122

  • Contact me on the forums (http://forums.eagle.ru/showthread.php?t=169387) or (more easily) Discord - https://discord.gg/baw7g3t with a screenshot of you Scripts folder, DCS.log, SimpleRadio logs, your Export.lua, operating system and any antivirus or firewall used and I'll help.

  • If you are unable to hook into dcs, delete your DCS-SR Install folder and run the installer again. Your settings WILL be saved.

  • If others hear an echo of your voice please read this post: http://forums.eagle.ru/showpost.php?p=2885040&postcount=631 Big thank you to Redacuragsr for solving it

  • If your device is not being detected try enabling Allow More Inputs and restarting SRS - this may cause issues with Audio and other inputs. If there are problems - disable "Allow More Inputs" - Open your clientlog.txt and look for the device info like so:

Found Device ID:c537046d-0000-0000-0000-504944564944 USB Receiver Usage: Generic Type: Device Found Device ID:c537046d-0000-0000-0000-504944564944 USB Receiver Usage: VendorDefinedBegin Type: Device Found Device ID:c33a046d-0000-0000-0000-504944564944 G413 Carbon Mechanical Gaming Keyboard Usage: Consumer Type: Device Found Device ID:c33a046d-0000-0000-0000-504944564944 G413 Carbon Mechanical Gaming Keyboard Usage: -189 Type: Device Found Device ID:c537046d-0000-0000-0000-504944564944 USB Receiver Usage: VendorDefinedBegin Type: Device Found Device ID:c33a046d-0000-0000-0000-504944564944 G413 Carbon Mechanical Gaming Keyboard Usage: -189 Type: Device Found Device ID:c537046d-0000-0000-0000-504944564944 USB Receiver Usage: -128 Type: Device

Find the device you want to use e.g. Found Device ID:c537046d-0000-0000-0000-504944564944 USB Receiver Usage: -128 Type: Device Copy the ID c537046d-0000-0000-0000-504944564944 And add into a file called whitelist.txt in your SRS Folder

Acknowledgements & Thanks:

Clone this wiki locally