Player Guide/SRS - Revision history

Shifty: Player Guide import 2026-05-17 (VRSWiki repo, content/pages/)

2026-05-28T03:37:40Z

Player Guide import 2026-05-17 (VRSWiki repo, content/pages/)

← Older revision		Revision as of 23:37, 27 May 2026
Line 19:		Line 19:
	Hit '''Connect'''. Once connected, SRS will sit in the background and route radio audio through your aircraft's tuned frequencies. With the in-game plugin installed, you can change frequencies in the cockpit and SRS will follow.		Hit '''Connect'''. Once connected, SRS will sit in the background and route radio audio through your aircraft's tuned frequencies. With the in-game plugin installed, you can change frequencies in the cockpit and SRS will follow.

	'''Important:''' ~~the name you set in SRS '''must match''' your in-game DCS name. Several~~ VRS services (Focus, CSAR, the stats site) identify you by name~~, and a mismatch will make you invisible to them~~.		'''Important:''' VRS services (Focus, CSAR, the stats site) identify you by your in-game DCS name. Current versions of SRS read that name straight from DCS once you're connected to the server with the in-game plugin running - you do '''not''' need to type it into SRS by hand. Just set your DCS name correctly (see [[#Setting your callsign in DCS\|below]]) and SRS picks it up automatically.

	~~If the version~~ of SRS you ~~are~~ running ~~doesn~~'~~t have this option, (a place~~ to type in your callsign) it ~~will be~~ automatically ~~derived from what you have entered in the Name field in the server browser~~.

	== Setting your callsign in DCS ==		== Setting your callsign in DCS ==
Line 31:		Line 29:
	# Launch DCS World.		# Launch DCS World.
	# Click '''MULTIPLAYER'''.		# Click '''MULTIPLAYER'''.
	# In the server browser, find the '''Name''' field at the top.		# In the server browser, find the '''Name''' field at the top right.
	# Type your callsign in the format <code>Callsign 1 \| yourname</code> (see [[#Choosing your callsign\|Choosing your callsign]] below).		# Type your callsign in the format <code>Callsign 1 \| yourname</code> (see [[#Choosing your callsign\|Choosing your callsign]] below).
	# Join the VRS server.		# Join the VRS server.

	~~Make sure the~~ name ~~you type matches what you~~'~~ll connect to SRS as~~ - ~~it's~~ the ~~same string, just entered in two places~~.		You only set this name in '''one''' place - the DCS server browser. When you join with SRS running, SRS reads it from DCS for you. (Older SRS versions made you type your name into SRS as well and keep the two in sync by hand; current versions don't.)

	~~If the version of~~ SRS ~~you are~~ running ~~doesn't have this option~~, (~~a place to~~ type in your ~~callsign) it will be automatically derived from what you have entered in~~ the ~~Name field~~ in ~~the server browser~~.

	== Choosing your callsign ==		== Choosing your callsign ==

	A good VRS callsign is structured so that the [[Player Guide/SkyEye\|Focus GCI bot]] can ~~recognize~~ it reliably over voice. Pick a name like <code>Mobius 1 \| Reaper</code> or <code>Hitman 11 \| Monarch</code> - that is:		A good VRS callsign is structured so that the [[Player Guide/SkyEye\|Focus GCI bot]] can recognise it reliably over voice. Pick a name like <code>Mobius 1 \| Reaper</code> or <code>Hitman 11 \| Monarch</code> - that is:

	# A '''2-3 syllable English word''' (the callsign itself).		# A '''2-3 syllable English word''' (the callsign itself).
Line 53:		Line 49:
	* Numbers are pronounced individually: <code>Spare 15</code> is said <em>"Spare One Five"</em>, not <em>"Spare Fifteen"</em>.		* Numbers are pronounced individually: <code>Spare 15</code> is said <em>"Spare One Five"</em>, not <em>"Spare Fifteen"</em>.
	* Content inside <code>[]</code> is ignored - <code>[VRS] Mobius 1</code> reads as <code>Mobius 1</code>.		* Content inside <code>[]</code> is ignored - <code>[VRS] Mobius 1</code> reads as <code>Mobius 1</code>.
	* Callsigns are ~~normalized~~ in ~~capitalization~~, numbers, and separation - <code>WARDOG 14</code>, <code>Wardog 14</code>, <code>wardog14</code>, and <code>Wardog 1 4</code> all count as the same callsign.		* Callsigns are normalised in capitalisation, numbers, and separation - <code>WARDOG 14</code>, <code>Wardog 14</code>, <code>wardog14</code>, and <code>Wardog 1 4</code> all count as the same callsign.
	* Your callsign should be unique within a server. Duplicates will get inconsistent responses from Focus.		* Your callsign should be unique within a server. Duplicates will get inconsistent responses from Focus.

47.12.42.190: /* Setting your callsign in DCS */ comment to include that on newer versions of SRS, entering a callsign/name is not necessary as it is picked up from the DCS MP server.

2026-05-27T20:55:18Z

Setting your callsign in DCS: comment to include that on newer versions of SRS, entering a callsign/name is not necessary as it is picked up from the DCS MP server.

← Older revision		Revision as of 16:55, 27 May 2026
Line 20:		Line 20:

	'''Important:''' the name you set in SRS '''must match''' your in-game DCS name. Several VRS services (Focus, CSAR, the stats site) identify you by name, and a mismatch will make you invisible to them.		'''Important:''' the name you set in SRS '''must match''' your in-game DCS name. Several VRS services (Focus, CSAR, the stats site) identify you by name, and a mismatch will make you invisible to them.

			If the version of SRS you are running doesn't have this option, (a place to type in your callsign) it will be automatically derived from what you have entered in the Name field in the server browser.

	== Setting your callsign in DCS ==		== Setting your callsign in DCS ==
Line 34:		Line 36:

	Make sure the name you type matches what you'll connect to SRS as - it's the same string, just entered in two places.		Make sure the name you type matches what you'll connect to SRS as - it's the same string, just entered in two places.

			If the version of SRS you are running doesn't have this option, (a place to type in your callsign) it will be automatically derived from what you have entered in the Name field in the server browser.

	== Choosing your callsign ==		== Choosing your callsign ==

	A good VRS callsign is structured so that the [[Player Guide/SkyEye\|Focus GCI bot]] can ~~recognise~~ it reliably over voice. Pick a name like <code>Mobius 1 \| Reaper</code> or <code>Hitman 11 \| Monarch</code> - that is:		A good VRS callsign is structured so that the [[Player Guide/SkyEye\|Focus GCI bot]] can recognize it reliably over voice. Pick a name like <code>Mobius 1 \| Reaper</code> or <code>Hitman 11 \| Monarch</code> - that is:

	# A '''2-3 syllable English word''' (the callsign itself).		# A '''2-3 syllable English word''' (the callsign itself).
Line 49:		Line 53:
	* Numbers are pronounced individually: <code>Spare 15</code> is said <em>"Spare One Five"</em>, not <em>"Spare Fifteen"</em>.		* Numbers are pronounced individually: <code>Spare 15</code> is said <em>"Spare One Five"</em>, not <em>"Spare Fifteen"</em>.
	* Content inside <code>[]</code> is ignored - <code>[VRS] Mobius 1</code> reads as <code>Mobius 1</code>.		* Content inside <code>[]</code> is ignored - <code>[VRS] Mobius 1</code> reads as <code>Mobius 1</code>.
	* Callsigns are ~~normalised~~ in ~~capitalisation~~, numbers, and separation - <code>WARDOG 14</code>, <code>Wardog 14</code>, <code>wardog14</code>, and <code>Wardog 1 4</code> all count as the same callsign.		* Callsigns are normalized in capitalization, numbers, and separation - <code>WARDOG 14</code>, <code>Wardog 14</code>, <code>wardog14</code>, and <code>Wardog 1 4</code> all count as the same callsign.
	* Your callsign should be unique within a server. Duplicates will get inconsistent responses from Focus.		* Your callsign should be unique within a server. Duplicates will get inconsistent responses from Focus.

Shifty: Player Guide import 2026-05-17 (VRSWiki repo, content/pages/)

2026-05-24T02:44:03Z

Player Guide import 2026-05-17 (VRSWiki repo, content/pages/)

← Older revision		Revision as of 22:44, 23 May 2026
Line 82:		Line 82:
	'''Other players can't hear you, or you can't hear them.''' Check that SRS is connected (not just running), check that your push-to-talk key is bound in SRS Settings, and check that you're tuned to the same frequency. The in-game plugin only works if you've enabled it in DCS - the SRS installer should have handled this automatically.		'''Other players can't hear you, or you can't hear them.''' Check that SRS is connected (not just running), check that your push-to-talk key is bound in SRS Settings, and check that you're tuned to the same frequency. The in-game plugin only works if you've enabled it in DCS - the SRS installer should have handled this automatically.

	'''Focus doesn't see you.''' Confirm that the name you set in SRS matches your DCS multiplayer name exactly, including capitalisation and the pipe-separated suffix.		'''Focus or CSAR doesn't see you.''' Confirm that the name you set in SRS matches your DCS multiplayer name exactly, including capitalisation and the pipe-separated suffix.

	== See also ==		== See also ==

Shifty: remove csar message

2026-05-21T04:22:01Z

remove csar message

← Older revision		Revision as of 00:22, 21 May 2026
Line 82:		Line 82:
	'''Other players can't hear you, or you can't hear them.''' Check that SRS is connected (not just running), check that your push-to-talk key is bound in SRS Settings, and check that you're tuned to the same frequency. The in-game plugin only works if you've enabled it in DCS - the SRS installer should have handled this automatically.		'''Other players can't hear you, or you can't hear them.''' Check that SRS is connected (not just running), check that your push-to-talk key is bound in SRS Settings, and check that you're tuned to the same frequency. The in-game plugin only works if you've enabled it in DCS - the SRS installer should have handled this automatically.

	'''Focus ~~or CSAR~~ doesn't see you.''' Confirm that the name you set in SRS matches your DCS multiplayer name exactly, including capitalisation and the pipe-separated suffix.		'''Focus doesn't see you.''' Confirm that the name you set in SRS matches your DCS multiplayer name exactly, including capitalisation and the pipe-separated suffix.

	== See also ==		== See also ==

Shifty: Player Guide import 2026-05-17 (VRSWiki repo, content/pages/)

2026-05-21T04:12:24Z

Player Guide import 2026-05-17 (VRSWiki repo, content/pages/)

New page

« [[Player Guide]]

'''SRS''' (DCS [https://github.com/ciribob/DCS-SimpleRadioStandalone Simple Radio Standalone]) is the third-party voice radio layer DCS players use to talk to each other and to the AI services on the server. VRS uses SRS for coalition voice comms, for the [[Player Guide/SkyEye|Focus GCI bot]], for [[Player Guide/CSAR and Salvage|CSAR]] coordination, and more.

If you intend to fly on VRS, you need SRS installed and running alongside DCS.

__TOC__

== Installing SRS ==

Download SRS from the [https://github.com/ciribob/DCS-SimpleRadioStandalone/releases official releases page] and run the installer. SRS only needs to be installed once; on launch it will offer to install or update the in-game DCS plugin as well.

== Connecting to the VRS SRS server ==

Open SRS, then in the connection bar at the top enter:

server.victorromeosierra.com:10220

Hit '''Connect'''. Once connected, SRS will sit in the background and route radio audio through your aircraft's tuned frequencies. With the in-game plugin installed, you can change frequencies in the cockpit and SRS will follow.

'''Important:''' the name you set in SRS '''must match''' your in-game DCS name. Several VRS services (Focus, CSAR, the stats site) identify you by name, and a mismatch will make you invisible to them.

== Setting your callsign in DCS ==

Your "callsign" on VRS is just your '''DCS multiplayer name''' - what you set in the DCS server browser before joining. This is the name that appears on the in-game scoreboard, in the chat window, in Tacview, and to every server-side service.

To set it:

# Launch DCS World.
# Click '''MULTIPLAYER'''.
# In the server browser, find the '''Name''' field at the top.
# Type your callsign in the format <code>Callsign 1 | yourname</code> (see [[#Choosing your callsign|Choosing your callsign]] below).
# Join the VRS server.

Make sure the name you type matches what you'll connect to SRS as - it's the same string, just entered in two places.

== Choosing your callsign ==

A good VRS callsign is structured so that the [[Player Guide/SkyEye|Focus GCI bot]] can recognise it reliably over voice. Pick a name like <code>Mobius 1 | Reaper</code> or <code>Hitman 11 | Monarch</code> - that is:

# A '''2-3 syllable English word''' (the callsign itself).
# '''1-3 digits''' (the flight number).
# A pipe character (<code>|</code>).
# Your normal username, after the pipe.

A few rules of thumb:

* Each digit is worth 2-3 letters in error correction - '''do not skip the numbers'''.
* Numbers are pronounced individually: <code>Spare 15</code> is said "Spare One Five", not "Spare Fifteen".
* Content inside <code>[]</code> is ignored - <code>[VRS] Mobius 1</code> reads as <code>Mobius 1</code>.
* Callsigns are normalised in capitalisation, numbers, and separation - <code>WARDOG 14</code>, <code>Wardog 14</code>, <code>wardog14</code>, and <code>Wardog 1 4</code> all count as the same callsign.
* Your callsign should be unique within a server. Duplicates will get inconsistent responses from Focus.

'''Avoid:'''

* Names that sound like brevity codewords: alpha, radio, comm, bogey, picture, declare, snaplock, spiked, bullseye. For example, "Spade" can be misheard as "SPIKE".
* Names that sound similar to numbers - "Knight" sounds like "Nine", "Fort" sounds like "Four".
* Hard-to-distinguish pairs - "Spare" vs "Spear", "Jester" vs "Gesture", "Witch" vs "Which".
* Names that aren't widely recognised English words - "Razgriz", "Beskar". The bot will try, but is less accurate.
* Names without digits. The bot will try, but the digits make a very large difference in error correction.
* Very short callsigns (2-3 characters). A single misheard letter is uncorrectable.
* Names in poor taste.

If you fly with a regular wingman, both of you using '''strict callsigns''' - a word plus '''exactly two digits''' - lets Focus combine calls for the whole flight into one transmission. For example, <code>Marauder One flight, threat bullseye 070/20...</code> instead of naming every aircraft individually.

== What VRS uses SRS for ==

{| class="wikitable"
! Service !! Frequency !! Notes
|-
| Coalition voice comms || varies || Talk to your wingman and other players on the same frequency.
|-
| [[Player Guide/SkyEye|Focus]] (AI GCI bot) || 251.00 AM, 133.00 AM || See the [[Player Guide/SkyEye|SkyEye page]] for how to talk to Focus.
|-
| [[Player Guide/CSAR and Salvage|CSAR]] || 30.00 FM || Helo recovery channel.
|}

== Troubleshooting ==

'''SRS won't connect.''' Double-check the server address and port (<code>server.victorromeosierra.com:10220</code>). Confirm you can reach the VRS website in a browser - if the website is also down, the server may be restarting.

'''Other players can't hear you, or you can't hear them.''' Check that SRS is connected (not just running), check that your push-to-talk key is bound in SRS Settings, and check that you're tuned to the same frequency. The in-game plugin only works if you've enabled it in DCS - the SRS installer should have handled this automatically.

'''Focus or CSAR doesn't see you.''' Confirm that the name you set in SRS matches your DCS multiplayer name exactly, including capitalisation and the pipe-separated suffix.

== See also ==

* [[Player Guide/SkyEye|SkyEye]] - the Focus GCI bot, what to say, request types.
* [[Player Guide/CSAR and Salvage|CSAR and Salvage]] - Combat Search and Rescue procedures.
* [https://github.com/ciribob/DCS-SimpleRadioStandalone DCS-SimpleRadioStandalone on GitHub] - source, releases, documentation.