Victor Romeo Sierra Wiki - User contributions [en]

Player Guide/Downloads

2026-05-29T06:31:29Z

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

« [[Player Guide]]

This page collects the downloadable artifacts VRS provides to its players - mod packs, kneeboards, charts, and anything else you should grab before flying on our server.

If you're new to mod managers, read [[Player Guide/Open Mod Manager|Open Mod Manager]] first. VRS publishes two network repositories (one per DCS install location) so OMM users can one-click install and auto-update mod packs.

__TOC__

== One-click install via the VRS repositories ==

If you've followed [[Player Guide/Open Mod Manager|the OMM setup guide]] and created the two Channels (DCS Install + DCS Saved Games), subscribe each to its matching repo:

{| class="wikitable"
! Channel !! Base URL !! Name !! What's in it
|-
| '''DCS Install''' || <code>https://victorromeosierra.com</code> || <code>VRSInstall</code> || Auto Starts (and any future install-root mods).
|-
| '''DCS Saved Games''' || <code>https://victorromeosierra.com</code> || <code>VRSSavedGames</code> || 22 per-aircraft livery sub-packs.
|}

Enter the bare Name (without <code>.xml</code>) - OMM appends the extension. See [[Player Guide/Open Mod Manager#Subscribing to the VRS repositories (recommended)|the OMM page]] for the full walkthrough.

The repositories currently list:

{| class="wikitable"
! Pack !! Ident !! Channel !! Size
|-
| [[#Auto Starts|Auto Starts]] || <code>VRS_AutoStarts_v1.0.0</code> || DCS Install || ~50 KB
|-
| Liveries (per aircraft, 22 packs) || <code>Liveries_<Aircraft></code> || DCS Saved Games || see [[#Liveries|Liveries]] below
|}

== Mod packs ==

=== Auto Starts ===

Quick-start macros for the airframes VRS flies (A-10C II, AH-64D, FA-18C, Ka-50 III, Mi-24P, Mi-8MTV2, SA342, UH-1H). Each one runs a consistent VRS Quick Start sequence on an in-game keybind.

'''Install via OMM (recommended):''' on your '''DCS Install''' Channel, subscribe to <code>VRSInstall</code> as described [[#One-click install via the VRS repositories|above]], then download and install <code>VRS_AutoStarts</code>.

'''Manual install (OMM or OvGME):''' download [https://github.com/VictorRomeoSierra/VRSMods/releases/latest/download/VRS_AutoStarts.zip VRS_AutoStarts.zip] (latest release on the [https://github.com/VictorRomeoSierra/VRSMods VictorRomeoSierra/VRSMods] repo). Drop the <code>.zip</code> into your manager's Library folder, then install/enable it. Don't rename the zip - OMM and OvGME both require the inner folder name to match the filename.

The Auto Starts pack modifies aircraft startup scripts that live under the DCS '''install''' folder. DCS patches can overwrite these on update, so this pack '''must''' be installed through a mod manager (OMM or OvGME), not by hand.

=== Liveries ===

VRS squadron and unit liveries for the airframes our pilots fly. The pack is split into '''one sub-pack per aircraft''' so updates to a single airframe don't force you to re-download the whole pile.

Made a livery you'd like in the pack? See [[Player Guide/Contributing Liveries|Contributing Liveries]] for how to upload it.

'''Install via OMM (recommended):''' on your '''DCS Saved Games''' Channel, subscribe to <code>VRSSavedGames</code> as described [[#One-click install via the VRS repositories|above]], then Query and pick the per-aircraft packs you want. Each one installs into <code>Saved Games\DCS\Liveries\<Aircraft>\</code> via OMM's normal flow - no special channel target needed.

Current per-aircraft sub-packs (as of 2026-05-26):

{| class="wikitable"
! Aircraft !! Sub-pack ident
|-
| A-10A (Flaming Cliffs) || <code>Liveries_A-10A</code>
|-
| A-10C Warthog || <code>Liveries_A-10C</code>
|-
| A-10C II Tank Killer || <code>Liveries_A-10C_2</code>
|-
| A-4E-C Skyhawk || <code>Liveries_A-4E-C</code>
|-
| AH-64D Apache (cockpit only) || <code>Liveries_AH-64D</code>
|-
| AV-8B Harrier || <code>Liveries_AV8BNA</code>
|-
| CH-47F Chinook || <code>Liveries_CH-47F</code>
|-
| F-14B Tomcat || <code>Liveries_F-14B</code>
|-
| F-16C Viper || <code>Liveries_F-16C_50</code>
|-
| F/A-18C Hornet || <code>Liveries_FA-18C_hornet</code>
|-
| Il-76MD Candid || <code>Liveries_IL-76MD</code>
|-
| Ka-50 Black Shark 2 || <code>Liveries_Ka-50</code>
|-
| Ka-50 Black Shark 3 || <code>Liveries_Ka-50_3</code>
|-
| Mirage 2000C || <code>Liveries_M-2000C</code>
|-
| Mi-24P Hind || <code>Liveries_Mi-24P</code>
|-
| Mi-8MTV2 Hip || <code>Liveries_Mi-8MT</code>
|-
| MiG-21bis Fishbed || <code>Liveries_MiG-21bis</code>
|-
| Su-25T (Flaming Cliffs, cockpit only) || <code>Liveries_Su-25T</code>
|-
| Su-33 Flanker-D || <code>Liveries_Su-33</code>
|-
| UH-1H Huey || <code>Liveries_UH-1H</code>
|-
| UH-60A Black Hawk || <code>Liveries_UH-60A</code>
|-
| UH-60L Black Hawk || <code>Liveries_UH-60L</code>
|}

'''Alternative: monolithic download (OvGME or manual extract).''' If you don't want OMM, VRS still publishes the full pack as a single zip: [https://victorromeosierra.com/Mods/Liveries.zip Liveries.zip] (~9 GB). Extract it directly into <code>C:\Users\<you>\Saved Games\DCS\</code> - the archive's top-level <code>Liveries</code> folder merges into <code>Saved Games\DCS\Liveries\</code>. This is the legacy path; OMM users should prefer the per-aircraft repo above since updates are smaller.

== Voice Attack profiles ==

[https://voiceattack.com/ Voice Attack] is a third-party voice-command program that pairs with DCS to let you speak commands instead of clicking them. VRS provides a profile tailored to the AI mission's F10 menu and the [[Player Guide/Air Support|CORE / UTILITY MARK]] system.

'''Voice Attack itself is separate software''' - install it from voiceattack.com first. VRS only provides the profile (.vap) file you import into Voice Attack; it does not install or modify Voice Attack itself.

Downloads (latest [https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack/releases/tag/VRS-AI-v0.5 VRS-AI-v0.5] release):

* '''[https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack/releases/download/VRS-AI-v0.5/VRS.AI.v0.5-Profile.vap VRS.AI.v0.5-Profile.vap]''' (~2.6 MB) - the full profile with embedded audio.
* '''[https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack/releases/download/VRS-AI-v0.5/VRS.AI-Profile.vap VRS.AI-Profile.vap]''' (~62 KB) - the profile without bundled audio (smaller, but you'll need to record your own command audio).
* '''[https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack/releases/download/VRS-AI-v0.5/VRS.AI-Profile.html VRS.AI-Profile.html]''' (~133 KB) - HTML reference of every voice command in the profile. Open in a browser, no Voice Attack required.

To install: in Voice Attack, click the '''Import Profile''' button (or '''Options → Import Profile'''), point at the downloaded <code>.vap</code>, and it'll appear in your profile list.

These profiles are not managed by OMM (Voice Attack stores profiles in its own application folder, not under DCS).

== See also ==

* [[Player Guide/Open Mod Manager|Open Mod Manager]] - the mod manager used to install the mod packs above.
* [[Player Guide/Contributing Liveries|Contributing Liveries]] - upload your own livery to the pack.
* [[Player Guide/SRS|SRS]] - voice radio, required for VRS server.

Player Guide/CSAR and Salvage

2026-05-29T06:31:28Z

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

« [[Player Guide]]

'''CSAR SRS frequency: 30.00 FM.''' Tune here in your helo to coordinate with other rescuers and downed pilots. See [[Player Guide/SRS|SRS]] for setup.

'''ADF homing:''' Each downed pilot broadcasts on its own ADF beacon frequency. Tune that frequency on your helo's ADF radio to home in on the survivor; the frequency is provided for each active pickup.

How it works:

F10 layout: Personal / CSAR / CTLD / Salvage / Interrogation / Factory Menu.

The Rescue Duty toggle is in the Personal Menu. Most active rescue and salvage actions require Rescue Duty ON.

CSAR Menu

* List Active Pickups

* Show Pickups on Map

* Pick up nearby rescue

* Check Onboard

* Offload Pickups

* Request Signal Flare

* Request Smoke

CSAR / SAR flow

: 1. Turn ON Rescue Duty (Personal Menu -> Toggle Rescue Duty).

: 2. Show Pickups on Map or List Active Pickups to find rescue markers.

: 3. Tune the survivor's ADF beacon frequency on your radio to home in on them.

: 4. Request Signal Flare / Request Smoke to localize a friendly survivor when needed.

: 5. Land near the survivor and use Pick up nearby rescue.

: 6. To move survivors toward a safer pickup, place a map mark with text: CSAR exfil. Nearby rescue locations move toward the mark.

: 7. Land near a friendly airbase and Offload Pickups.

[[File:UH-60-CSAR.jpg|614x333px]]

''UH-60 on CSAR duty -- ready to pluck your pilots out of the water if needed''

[[File:UH-60-carrier-approach.jpg|600px|center|UH-60 returning to the boat after a CSAR pickup.]]

''UH-60 returning to the boat - survivors aboard.''

Salvage Menu

* Pick up nearby (250 kg)

* Pick up nearby (500 kg)

* Pick up nearby (1000 kg)

* Pick up nearby (All remaining)

* Drop off

* Emergency Jett!

* List salvage jobs map wide

* Show Salvage on Map

Salvage flow

: 1. Show Salvage on Map (markers are separate from CSAR markers).

: 2. Salvage pickup requires a helicopter, Rescue Duty ON, and landing near the wreck.

: 3. Choose pickup amount: 250 kg / 500 kg / 1000 kg / All remaining.

: 4. Drop off to unload. Factory drop-offs and airbase drop-offs both pay but use different payout multipliers.

: 5. Coalition salvage credit feeds the salvage pot, which funds Factory production.

: 6. Emergency Jett! discards all onboard rescue/salvage payload.

: 7. Landing near a valid airbase or factory can auto-trigger offload after a short delay where enabled.

Interrogation Menu

* Request status

* Request collected info

* Initiate 'mind games'

* Initiate 'chat with knuckles'

* Initiate 'hydro-persuation'

* Initiate 'oil planking'

Interrogation actions operate on captured RED pilots. They are fed by successful recovery and offload outcomes.

Player Guide/Contributing Liveries

2026-05-29T06:31:28Z

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

« [[Player Guide]]

Got a livery you'd like to see on the VRS server? You can upload it yourself. VRS runs an automated pipeline that checks new uploads and, if your livery is packaged correctly, adds it to the livery pack for everyone -- [[Player Guide/Open Mod Manager|OMM]] users pick it up on their next launch and it's announced in the <code>#liveries</code> Discord channel. In the normal case there's no staff hand-off.

__TOC__

== 1. Get an upload account ==

Liveries are uploaded through the VRS file-share (ProjectSend) at [https://victorromeosierra.com/upload/ victorromeosierra.com/upload]. Use the '''Register''' link on the login page to create an account, then log in. This is a separate account from Discord and from the game server.

== 2. Package your livery ==

Zip your livery in the standard DCS livery layout, with the '''aircraft folder at the top of the zip''':

<pre>
FA-18C_hornet/ <- DCS aircraft folder name (top level)
My Squadron Skin/ <- your livery's name
description.lua <- the standard livery definition
textures.dds <- your texture files
preview.jpg <- optional (see below)
</pre>

Key rules:

* '''The top-level folder must be the aircraft's DCS folder name''' -- the exact name DCS uses under <code>Saved Games\DCS\Liveries\</code> (for example <code>FA-18C_hornet</code>, <code>F-16C_50</code>, <code>A-10C_2</code>, <code>Mi-24P</code>). The [[Player Guide/Downloads#Liveries|Downloads page]] lists the folder name for every aircraft we carry.
* '''Include only livery files''' -- textures (<code>.dds</code>), <code>description.lua</code>, and images. <code>description.lua</code> should be the normal livery definition (the list of texture mappings) and nothing more; don't add extra scripting.
* '''One livery per upload''' is the cleanest approach. The per-aircraft pack is rebuilt for you, so you don't need to bundle anything else.

== 3. (Optional) Add a preview image ==

If you want a thumbnail shown in the <code>#liveries</code> announcement, drop a <code>preview.jpg</code> in your livery's folder:

* Filename <code>preview.jpg</code> (lowercase), at the root of the <code><livery>/</code> folder.
* JPEG, sRGB, at most '''256x256''', under about '''50 KB'''.

Leave it out and the VRS logo is used instead. A missing or oversized preview won't get your livery held back.

== 4. Upload ==

Log in to [https://victorromeosierra.com/upload/ the file-share] and upload your <code>.zip</code>. There's no special category to pick or form to fill in -- just upload the file.

== 5. What happens next ==

* Within a few minutes the upload is detected and checked automatically.
* '''If it's a valid livery''', it's added to that aircraft's pack and published. OMM users auto-update on their next launch, and a post appears in <code>#liveries</code>.
* '''You won't get an individual success or error message.''' If your livery doesn't show up in <code>#liveries</code> within a few minutes, ask in the <code>#liveries</code> Discord channel and staff will take a look.

== Replacing or removing a livery ==

To replace a livery, upload the corrected zip, then rename your '''old''' file on the share to include '''Old - Do Not Use''' in its name. The pipeline skips files flagged that way, so only your new version gets published.

== See also ==

* [[Player Guide/Downloads|Downloads]] -- installing the livery packs, and the per-aircraft folder names.
* [[Player Guide/Open Mod Manager|Open Mod Manager]] -- the manager that auto-installs published liveries.

Player Guide

2026-05-29T06:31:27Z

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

[[File:VRS-Logo.png|256x256px|center|VRS - Victor Romeo Sierra]]

Welcome to our Victor Romeo Sierra (VRS) community -- a laid-back group of virtual pilots brought together by a shared passion for flying, teamwork, and having a good time in the skies. Built around Digital Combat Simulator, our group is focused on creating a relaxed, welcoming environment where both experienced aviators and new recruits can enjoy everything from casual flights to coordinated missions without the pressure of hardcore mil-sim expectations. Whether you're here to learn, fly, or simply unwind after a long day, there's always a seat on the flight line for you at VRS!

Please take time to review the VRS Player Guide to help familiarize yourself with VRS, our server, and other important information. If you have any questions feel free to post in the #questions Discord channel.

This guide explains how to play the VRS mission from the BLUE side.

It is intentionally light on REDFOR internals and focused on what players can do.

== Sections ==

* [[Player Guide/Mission Mindset|Mission Mindset]] - Three parallel loops that shape every flight.
* [[Player Guide/Air Support|Air Support]] - CORE / UTILITY MARK system: how to call AWACS, tankers, CAP, escorts via F10 map marks.
* [[Player Guide/SRS|SRS]] - Installing Simple Radio Standalone, connecting to the VRS server, picking your callsign.
* [[Player Guide/Open Mod Manager|Open Mod Manager]] - Managing DCS install-folder mods non-destructively, plus subscribing to the VRS network repository for one-click install and auto-updates.
* [[Player Guide/Downloads|Downloads]] - VRS mod packs (Auto Starts, Liveries) and other player-facing artifacts.
* [[Player Guide/Contributing Liveries|Contributing Liveries]] - Upload your own livery so the automated pipeline adds it to the pack.
* [[Player Guide/SkyEye|SkyEye]] - Talking to the AI GCI bot over SRS: callsign format, requests, brevity.
* [[Player Guide/Personal Escorts|Personal Escorts]] - Credit-funded personal escorts.
* [[Player Guide/Intel Reporting|Intel Reporting]] - Reporting RED activity via the Personal Menu.
* [[Player Guide/CTLD Logistics|CTLD Logistics]] - Building factories, Fat Cows, and force-multiplier deployment.
* [[Player Guide/CSAR and Salvage|CSAR and Salvage]] - Combat Search and Rescue, SAR, and battlefield Salvage.
* [[Player Guide/Credits and Progression|Credits and Progression]] - Credit economy + intel progression.
* [[Player Guide/Red Behavior|Red Behavior]] - How REDFOR adapts to BLUE pressure.
* [[Player Guide/Reporting a Bug|Reporting a Bug]] - How to file bug reports.
* [[Player Guide/Team Play|Team Play]] - Patterns that work for coordinated coalition play.
* [[Player Guide/Penalties|Penalties]] - The penalty-point system for team-kills and friendly fire: how points are earned, how they fade, and what triggers a move-to-spec or ban.
* [[Player Guide/Quick Command Card|Quick Command Card]] - One-screen reference card for all CORE / UTILITY MARK commands.
* [[Player Guide/Discord Commands|Discord Commands]] - Player-facing slash commands the VRS bot exposes in Discord.
* [[Player Guide/In-Game Chat Commands|In-Game Chat Commands]] - <code>-</code> prefix commands the bot listens for in the DCS chat window.

Player Guide/Penalties

2026-05-28T13:38:16Z

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

« [[Player Guide]]

VRS runs an automated '''penalty point''' system to discourage team-killing and careless flying around friendlies. Hitting or killing your own side earns points. Nothing happens to you until your total crosses a threshold, points fade on their own over time, and the player you wronged can always wave it off. The goal is to deter griefing, not to punish honest accidents.

__TOC__

== How points are earned ==

Penalty points are assigned when you damage or destroy a friendly. Killing a human teammate costs the most; brushing an AI wingtip costs the least.

{| class="wikitable"
! Incident !! Against a human !! Against AI
|-
| Killing a team member || 30 || 18
|-
| Killing a team member in a collision || 20 || 12
|-
| Friendly fire (hitting a team member) || 12 || 8
|-
| Colliding with a team member || 5 || 1
|}

Two things smooth out the raw numbers:

* '''Grouped events''' -- everything that happens within about a minute counts as a single event, so one messy gun run or CBU drop doesn't stack into a huge total.
* '''Flight-hours weighting''' -- the bot scales your points by how long you've flown on VRS servers, so brand-new arrivals are held to a tighter standard than regulars:

{| class="wikitable"
! Total flight time !! Points multiplier
|-
| New (under 3 hours) || 1.4x
|-
| 3+ hours || 1x (as listed above)
|-
| 10+ hours || 0.7x
|}

So a brand-new pilot who kills a human teammate picks up about 42 points (30 x 1.4), while a 10-hour regular picks up about 21 (30 x 0.7) for the same incident.

== What happens at each level ==

{| class="wikitable"
! Points !! Consequence
|-
| Under 100 || Nothing automated -- the points are recorded, but you keep flying.
|-
| 100 || You're moved to spectators.
|-
| 500 || 3-day temporary ban.
|}

There's a delay between the incident and any action -- this is the window your victim has to forgive you (see below).

== Checking your points ==

Type <code>-penalty</code> in the in-game chat at any time to see your current total. This always works, no matter how many points you have.

The bot will '''not''' nag you about points on its own until you're actually near a consequence -- you'll only get an unsolicited "you have ''N'' penalty points" message once you've reached the spectator threshold. Below that, the points are quietly accruing and decaying in the background; use <code>-penalty</code> if you want to check.

== Points fade over time ==

Penalty points decay on their own, so an old mistake doesn't follow you forever:

* After '''3 days''', about a quarter of the points are gone.
* After '''30 days''', only about a quarter remain.
* After '''60 days''', they're cleared completely.

== Forgiveness ==

If someone hits or kills you, you have '''15 minutes''' to type <code>-forgive</code> in the in-game chat. This cancels the pending penalty for that incident before any action triggers and wipes the related events. Use it for honest accidents -- a wingman who clipped you on the taxiway doesn't need to eat a move-to-spec for it.

See also: [[Player Guide/In-Game Chat Commands|In-Game Chat Commands]].

Player Guide/In-Game Chat Commands

2026-05-28T13:38:16Z

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

« [[Player Guide]]

These are the player-facing '''in-game chat commands''' the VRS bot listens for. Type them in the DCS chat window (usually <code>Enter</code> opens chat) - the bot uses the <code>-</code> prefix, then the command name, then any arguments.

Example: type <code>-credits</code> in chat to see your credit balance.

'''Notation'''

* <code><arg></code> - required argument
* <code>[arg]</code> - optional argument
* Admin-only chat commands (kick, ban, restart, etc.) are role-gated and not documented here.

__TOC__

== Profile + help ==

{| class="wikitable"
! Command !! Description
|-
| <code>-help</code> || The help command
|-
| <code>-linkme</code> || link your user to Discord
|-
| <code>-911</code> || send an alert to admins (misuse will be punished!)
|}

== Server + mission info ==

{| class="wikitable"
! Command !! Description
|-
| <code>-timeleft</code> || Time to the next restart
|-
| <code>-atis</code> || display ATIS information
|-
| <code>-coalition</code> || displays your current coalition
|-
| <code>-password</code> (aliases: <code>-passwd</code>) || displays the coalition password
|}

== Credits ==

{| class="wikitable"
! Command !! Description
|-
| <code>-credits <server></code> || Shows your current credits
|-
| <code>-donate</code> || Donate credits to another player
|-
| <code>-tip</code> || Tip a GCI with points
|}

== Voting ==

{| class="wikitable"
! Command !! Description
|-
| <code>-vote</code> || start a voting or vote for a change
|}

== Acknowledgement + penalty ==

{| class="wikitable"
! Command !! Description
|-
| <code>-ack</code> || acknowledge a user message
|-
| <code>-forgive</code> || forgive a teammate who hit or killed you, cancelling their pending penalty. Time-limited (about 15 minutes after the incident).
|-
| <code>-penalty</code> || displays your current penalty points on demand
|}

See [[Player Guide/Penalties|Penalties]] for how points are earned, how they fade, and what happens at each threshold.

Player Guide

2026-05-28T13:38:14Z

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

[[File:VRS-Logo.png|256x256px|center|VRS - Victor Romeo Sierra]]

Welcome to our Victor Romeo Sierra (VRS) community -- a laid-back group of virtual pilots brought together by a shared passion for flying, teamwork, and having a good time in the skies. Built around Digital Combat Simulator, our group is focused on creating a relaxed, welcoming environment where both experienced aviators and new recruits can enjoy everything from casual flights to coordinated missions without the pressure of hardcore mil-sim expectations. Whether you're here to learn, fly, or simply unwind after a long day, there's always a seat on the flight line for you at VRS!

Please take time to review the VRS Player Guide to help familiarize yourself with VRS, our server, and other important information. If you have any questions feel free to post in the #questions Discord channel.

This guide explains how to play the VRS mission from the BLUE side.

It is intentionally light on REDFOR internals and focused on what players can do.

== Sections ==

* [[Player Guide/Mission Mindset|Mission Mindset]] - Three parallel loops that shape every flight.
* [[Player Guide/Air Support|Air Support]] - CORE / UTILITY MARK system: how to call AWACS, tankers, CAP, escorts via F10 map marks.
* [[Player Guide/SRS|SRS]] - Installing Simple Radio Standalone, connecting to the VRS server, picking your callsign.
* [[Player Guide/Open Mod Manager|Open Mod Manager]] - Managing DCS install-folder mods non-destructively, plus subscribing to the VRS network repository for one-click install and auto-updates.
* [[Player Guide/Downloads|Downloads]] - VRS mod packs (Auto Starts, Liveries) and other player-facing artifacts.
* [[Player Guide/SkyEye|SkyEye]] - Talking to the AI GCI bot over SRS: callsign format, requests, brevity.
* [[Player Guide/Personal Escorts|Personal Escorts]] - Credit-funded personal escorts.
* [[Player Guide/Intel Reporting|Intel Reporting]] - Reporting RED activity via the Personal Menu.
* [[Player Guide/CTLD Logistics|CTLD Logistics]] - Building factories, Fat Cows, and force-multiplier deployment.
* [[Player Guide/CSAR and Salvage|CSAR and Salvage]] - Combat Search and Rescue, SAR, and battlefield Salvage.
* [[Player Guide/Credits and Progression|Credits and Progression]] - Credit economy + intel progression.
* [[Player Guide/Red Behavior|Red Behavior]] - How REDFOR adapts to BLUE pressure.
* [[Player Guide/Reporting a Bug|Reporting a Bug]] - How to file bug reports.
* [[Player Guide/Team Play|Team Play]] - Patterns that work for coordinated coalition play.
* [[Player Guide/Penalties|Penalties]] - The penalty-point system for team-kills and friendly fire: how points are earned, how they fade, and what triggers a move-to-spec or ban.
* [[Player Guide/Quick Command Card|Quick Command Card]] - One-screen reference card for all CORE / UTILITY MARK commands.
* [[Player Guide/Discord Commands|Discord Commands]] - Player-facing slash commands the VRS bot exposes in Discord.
* [[Player Guide/In-Game Chat Commands|In-Game Chat Commands]] - <code>-</code> prefix commands the bot listens for in the DCS chat window.

Main Page

2026-05-28T03:40:34Z

Shifty: Restore Olympus description (custom community missions) - re-applying manual wiki edit clobbered by repo sync

'''<big>Welcome to VRS!</big>'''

Victor Romeo Sierra is a set of DCS Servers. They are currently:

Victor Romeo Sierra - Dynamic AI Driven Campaign -- Our main server with an AI REDFOR and an AI AWACS System

Victor Romeo Sierra [Olympus] - Our server running the Olympus game master software (mostly used for custom community missions)

VRSWW2 - Our WWII warbird server.

== Player Guide ==

[[File:VRS-Logo.png|128x128px|right|link=Player Guide]]
The current player-facing documentation lives in the '''[[Player Guide]]''' - mission mindset, BLUE air support (CORE / UTILITY MARK commands), CTLD logistics, CSAR & salvage, and more.

== Getting started ==
* '''[[Player Guide]]''' - current VRS gameplay reference (start here)
* [https://map.victorromeosierra.com/servers/VRS Live Map of VRS Dynamic AI Server]
* [https://stats.victorromeosierra.com/ Player Stats Page]
* [https://discord.gg/victorromeosierra Discord]
* [https://www.patreon.com/c/VictorRomeoSierra/ Patreon]

----

Legacy XSAF-era docs are preserved at [[XSAF]] for historical reference.

Player Guide/SRS

2026-05-28T03:37:40Z

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

« [[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:''' 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.

== 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 right.
# Type your callsign in the format <code>Callsign 1 | yourname</code> (see [[#Choosing your callsign|Choosing your callsign]] below).
# Join the VRS server.

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.)

== 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.

Main Page

2026-05-28T03:37:26Z

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

'''<big>Welcome to VRS!</big>'''

Victor Romeo Sierra is a set of DCS Servers. They are currently:

Victor Romeo Sierra - Dynamic AI Driven Campaign -- Our main server with an AI REDFOR and an AI AWACS System

Victor Romeo Sierra [Olympus] - Our server running the Olympus game master software (mostly used for testing)

VRSWW2 - Our WWII warbird server.

== Player Guide ==

[[File:VRS-Logo.png|128x128px|right|link=Player Guide]]
The current player-facing documentation lives in the '''[[Player Guide]]''' - mission mindset, BLUE air support (CORE / UTILITY MARK commands), CTLD logistics, CSAR & salvage, and more.

== Getting started ==
* '''[[Player Guide]]''' - current VRS gameplay reference (start here)
* [https://map.victorromeosierra.com/servers/VRS Live Map of VRS Dynamic AI Server]
* [https://stats.victorromeosierra.com/ Player Stats Page]
* [https://discord.gg/victorromeosierra Discord]
* [https://www.patreon.com/c/VictorRomeoSierra/ Patreon]

----

Legacy XSAF-era docs are preserved at [[XSAF]] for historical reference.

Main Page

2026-05-26T14:17:20Z

Shifty:

XSAF

2026-05-26T14:12:27Z

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

{{XSAF-era}}

== Legacy XSAF-era documentation ==

These pages predate the current [[Player Guide]] and are kept here as historical reference for anyone curious about how VRS worked during the XSAF era (pre-2026 rebuild). For up-to-date guidance on the current server, start at the '''[[Player Guide]]'''.

* [[XSAF/New player guide|New Player Guide]] - the old player onboarding doc
* [[XSAF/FAQ|FAQ]] - frequently asked questions, XSAF era
* [[XSAF/CSAR|CSAR]] - combat search and rescue, legacy implementation (current docs: [[Player Guide/CSAR and Salvage|Player Guide: CSAR and Salvage]])
* [[XSAF/Salvage|Salvage]] - wreck recovery, legacy implementation (current docs: [[Player Guide/CSAR and Salvage|Player Guide: CSAR and Salvage]])
* [[XSAF/Logistics|Logistics]] - CTLD precursor docs (current docs: [[Player Guide/CTLD Logistics|Player Guide: CTLD Logistics]])
* [[XSAF/FOCUS|FOCUS]] - earlier AI GCI implementation (predecessor to [[Player Guide/SkyEye|SkyEye]])

Main Page

2026-05-26T14:12:19Z

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

'''<big>Welcome to VRS!</big>'''

Victor Romeo Sierra is a set of DCS Servers. They are currently:

Victor Romeo Sierra - Dynamic AI Driven Campaign -- Our main server with an AI REDFOR and an AI AWACS System

Victor Romeo Sierra [Olympus] - Our server running the Olympus game master software (mostly used for testing)

VRSWW2 - Our WWII warbird server.

== Player Guide ==

[[File:VRS-Logo.png|128x128px|right|link=Player Guide]]
The current player-facing documentation lives in the '''[[Player Guide]]''' - mission mindset, BLUE air support (CORE / UTILITY MARK commands), CTLD logistics, CSAR & salvage, and more.

== Getting started ==
* '''[[Player Guide]]''' - current VRS gameplay reference (start here)
* [https://map.victorromeosierra.com/servers/VRS Live Map of VRS Dynamic AI Server]
* [https://stats.victorromeosierra.com/ Player Stats Page]
* [https://discord.gg/victorromeosierra Discord]
* [https://www.patreon.com/c/VictorRomeoSierra/ Patreon]

----

Legacy XSAF-era docs are preserved at [[XSAF]] for historical reference.

XSAF/Salvage

2026-05-26T14:12:11Z

Shifty: Shifty moved page Salvage to XSAF/Salvage without leaving a redirect: Archive XSAF-era page: move to XSAF/ subpage per legacy archive plan

{{XSAF-era}}

This page will detail the Salvage System in use on VRS

== Salvage Operations ==

* Job Persistence: Salvage jobs now save and reload after a server restart, preventing resets between sessions.
* Map Markers: Player-requested map markers for Salvage jobs now appear for 30 seconds to aid navigation.
* Job Listings: The Salvage job list now shows heading and distance to the 10 nearest jobs, making navigation easier.
* Task Interaction Menu (F10 → F2 → F6 → F1):
** Pick up jobs
** Drop off jobs
** Show jobs on the map
** View job listing (with heading & distance)
* How to Sign Up:
* Salvage: <code>F10 → F2 → F6 → F4</code>

Screenshot showing Salvage Job on F10
[[File:Salvage Job on F10 map.png|alt=Screenshot showing Salvage Job on F10|left|thumb|'''Screenshot showing Salvage Job on F10'''[[File:Screen shows salvage site and location text tip.jpg|alt=screen shows salvage site and location text tip|left|thumb|screen shows salvage site and location text tip]][[File:Salvage site in the field.png|alt=Salvage site in the field|left|thumb|Salvage site in the field]]]]

XSAF/New player guide

2026-05-26T14:12:10Z

Shifty: Shifty moved page New player guide to XSAF/New player guide without leaving a redirect: Archive XSAF-era page: move to XSAF/ subpage per legacy archive plan

{{XSAF-era}}

'''VRS New Pilot Info and Suggestions'''

Besides the FAQ/Wiki, this document is more of a ‘what do I do’ thing if you’re new to VRS and want to know how to help BlueFor defeat RedFor in the Syrian theater.

VRS is more of a sandbox style mission. You aren’t going to be tasked by the AI, nor is there a ‘mission system’ like some of the other servers have. So how do you know what to do?

Well, that is all up to YOU! 😉 You can decide what kind of mission you want to do, be it CAP, A2G, Logistics, SEAD or CSAR. Load up your airframe of choice, and go pick a fight! But yes, opening the F10 map and being a bit overwhelmed by it is a normal and common experience! What to do?

My suggestion is to utilize some of the tools and resources you have available. We have a live map at <nowiki>https://map.victorromeosierra.com/</nowiki> You can take a look and see where various REDFOR Air and Ground forces are at. Then hop on the server and take care of business.

If that is a bit too meta for you, or you want a bit more mystery to your sortie, check out a couple channels in the discord, specifically the '''''VRS-Airboss''''' and '''''Situation Room''''' channels. Airboss is ‘reports’ by our admins and Game Masters and will often have suggestions of what to hit or problem areas to check out. Situation Room is an automated system that reports when bases are captured and will give some information about Red forces in general. Often there is a callout to a particularly productive BlueFor pilot, so that can be a goal of it’s own: Become a recognized threat to RedFor!

If you don’t want to do any of that, you still have some options in the sim itself:

Slot in to your airframe and load out of choice, take off and ask FOCUS, our AI Driven AWACS, for a Picture. They’ll also provide bogey dopes, merge calls, etc. It’s pretty proactive, so if you get distracted <s>taking screencaps</s> doing recon, she’ll let you know when you’re about to get bounced. Except for Manpads. You’re on your own there. Speaking of ground forces, there’s always something to do on the ground: finding convoys of RedFor, SEAD/DEAD operations, Logistics, CSAR, and even Salvage operations!

Finally, if you see other pilots online, feel free to call them up on your radio, or join a discord voice channel if you see players there, and ask what they’re up to, if they need help, or if they can task you something. Even if no one is on the server, you can ask in the discord and you’ll get somebody to respond with ‘well, there is some Redfor at SuchNSuch base that need to be cleared out’.

Most of the airframes in DCS are Multi-Role for just this kind of mission environment! There’s no reason in say a Viper to only take amraams! Use those other pylons for extra ordnance! Even if you’re going up for a CAP, can’t really hurt to take a couple Mavericks or a pair of cluster munitions along for the ride home.

Speaking of, we do have a warehouse mechanic. So you do want to RTB, land safely AND release the slot to ‘return’ the plane and weapons back to storage. Don’t just disco or lawn dart yourself to respawn just to save some time, please! (Landing is also required to get your points and kills recorded!)

XSAF/Logistics

2026-05-26T14:12:10Z

Shifty: Shifty moved page Logistics to XSAF/Logistics without leaving a redirect: Archive XSAF-era page: move to XSAF/ subpage per legacy archive plan

{{XSAF-era}}

This page will have information on the Logistic Systems in VRS.

Logistics/Warehousing/CTLD/: Most bases should have a place to pick up Crates and Troops. There is a warehouse structure, located in the Logistics Landing Zone shown on the F10 Map. (screencaps below)

It takes Large or 6 Small crates to build a FOB (FARPs are coming soon) 800m distance from fob.

To unpack crates, unload one unit type to unpack its crates before unloading other unit crates.

If you click on all cargo and select that cargo you will not find it in the rearm menu to load.

You can Sling Load as well.

==== Capacities: ====
Chinook: 6 small or 3 large crates.

Troops:

Mi8: 2 crates

Troops:

Hind:1

Huey:

Other AC:

P47 only crates

Warehousing: Players may need to unarm and defuel planes after landing to 'replace' that ordnance and fuel. Definitely try to land at a friendly base so you don’t ‘lose’ your airframe! You will also receive credit for your actions upon landing.

F10 Map showing Logistics Landing Area:
[[File:F10 logistics box.png|alt=F10 map showing logistics box|left|thumb|F10 map showing logistics box]]

In Game Shot of the Logistics Building:
[[File:Logistical Facility Building.png|alt=Logistics Building|left|thumb|Logistics Building]]

XSAF/FOCUS

2026-05-26T14:12:09Z

Shifty: Shifty moved page FOCUS to XSAF/FOCUS without leaving a redirect: Archive XSAF-era page: move to XSAF/ subpage per legacy archive plan

{{XSAF-era}}

'''<big>''FOCUS'' Player Guide</big>'''

(Blatantly stolen from the Skyeye github pages: https://github.com/dharmab/skyeye/blob/main/docs/PLAYER.md)

'''<big>Quickstart</big>'''

Set your in-game callsign to a simple callsign in the format Callsign 1 | yourname. (Note: That's a vertical bar (|), not the letter I.)

Join VRS

Get your aircraft up and running and airborne. (Or at least the radios, you can do some things on the ground, like a radio check)

Tune to any of the SkyEye frequencies in your aircraft (or SRS if you prefer to do it that way). (Currently 251.00AM, 133.00AM or 30.00FM in helos)

Say "FOCUS, Callsign 1, radio check" and see if the bot understands you.

Say "FOCUS, Callsign 1, picture" to be told about the highest priority threats to your coalition.

Say "FOCUS, Callsign 1, bogey" to get a bearing to the nearest threat to you.

⚠️ If the bot doesn't seem to respond to you

Double check you're saying "FOCUS" at the start of your message. This is a surprisingly common mistake that players often don't realize they are making!

Ask another player for a radio check to ensure you are clearly audible.

⚠️ If the bot responds but doesn't seem to see you on scope

Double check that your in-game name matches the callsign you are providing to the bot.

If you joined shortly after the mission started, try returning to spectators and re-slotting, or disconnecting and reconnecting. It seems that joining a mission too soon may sometimes make you invisible in TacView.

If you haven't moved your aircraft for a few minutes, try again after moving slightly. Sometimes TacView stops sending position updates for a stationary object to reduce bandwidth usage, and the bot may not consider you to be visible as a result.

If your aircraft took slight damage at some point, RTB and try returning to spectators and re-slotting. You may have become invisible due to the game marking your plane as destroyed. (In the F16, you will often be flying with a wingtip on fire, but everything seems fine. This is usually a 'dead man flying' situation)

FOCUS GCI is only one source of data to help you build situational awareness. It must not be considered an all-seeing eye. It does not replace your onboard sensors and communication tools such as your eyeballs, radio and attack radar - it assists you.

'''Choosing Your Callsign'''

You need a callsign to use SkyEye. SkyEye will make its best effort to figure out your callsign from your in-game name, but it works best if you have a name like Mobius 1 | Reaper (MOBIUS ONE) or Hitman 11 | Monarch (HITMAN ONE ONE).

''Callsign Tips:''

A two or three syllable English word.

One to three digits.

A pipe character (|)

Your non-callsign username after the pipe.

Your callsign should be unique within a server. If multiple players have the same callsign, SkyEye will respond but you may receive inconsistent information. Note that callsigns are normalized in capitalization, numbers, and separation - "WARDOG 14", "Wardog 14", "wardog14" and "Wardog 1 4" are all considered to be the same callsign.

Numbers are pronounced individually - "Spare 15" is pronounced "Spare One Five", not "Spare Fifteen".

If your name contains any content within brackets [], that content is ignored, For example, "[ISAF] Mobius 1" is read as "Mobius 1".

Avoid:

Names that contain or are similar to brevity codewords, including "alpha", "radio", "comm", "bogey", "picture", "declare", "snaplock", "spiked", "bullseye". For example, "Spade" can be difficult to distinguish from "SPIKE"

Names that are hard to distinguish, like "Spare"/"Spear", "Jester"/"Gesture", "Witch"/"Which". The bot will make a best effort, but may be less accurate.

Names that sound similar to numbers. For example, "Knight" sounds similar to "Nine", "Fort" sounds like "Four"

Names that aren't widely recognized words in common parlance, like "Razgriz" or "Beskar". The bot will make a best effort, but may be less accurate.

Names without the 1-3 digits. The bot will make a best effort, but the digits make a very large difference in error correction! Each digit added to a callsign is equivalent to 2-3 letters in terms of improved accuracy.

Callsigns that are very short. If your callsign is only 2-3 characters, a single misheard letter will be an uncorrectable error. The two to three syllable rule of thumb tends to result in callsigns that are correctable when misheard.

Names in poor taste.

If your callsign doesn't follow this format, SkyEye makes a best effort to understand it while still applying its parser rules. A bare username like "Jeff" (with no numbers) may still work, but do not expect this to work reliably.
----<big>'''Using''' '''''FOCUS'''''</big>

You can send a request to FOCUS by speaking on any SkyEye frequency in SRS.

The format of the request is:

GCI_CALLSIGN YOUR_CALLSIGN (...) REQUEST_TYPE (...) (REQUEST_ARGUMENTS...) (...)

Where:

GCI_CALLSIGN is FOCUS.

YOUR_CALLSIGN is your chosen callsign, e.g. "Mobius One" or "Hitman One One"

REQUEST_TYPE is a keyword indicating what kind of request you're sending (discussed below)

REQUEST_ARGUMENTS are optional modifiers to the request (discussed below)

Example: "FOCUS, Mobius One, spiked One Five Zero" is parsed as GCI_CALLSIGN="FOCUS", YOUR_CALLSIGN="mobius 1", REQUEST_TYPE=SPIKED, REQUEST_ARGUMENTS=[150]

The (...) indicates that you can say extra words in those spots and SkyEye will do its best to figure out what you mean.

Example: "FOCUS, Mobius One, Alpha Check" and "FOCUS, Mobius One, good morning. Alpha Check bullseye" are both parsed to GCI_CALLSIGN="FOCUS", YOUR_CALLSIGN="mobius 1", REQUEST_TYPE=ALPHA_CHECK, REQUEST_ARGUMENTS=[].

Some types of requests require you to provide numeric arguments.

Compass bearings must be given by speaking all three digits individually. Say "Zero Six Five", not "Six Five" or "Sixty-Five."

All other numbers should be given normally - "Seventeen", not "One Seven"

Do not use ICAO pronunciation; pronounce numbers normally. Say "Three", "Five", "Nine", not "Tree", "Fife", "Niner".

When providing bullseye coordinates, you may either say "bullseye" before the coordinates, or omit the word "bullseye". That is, both "Bullseye Zero Six Five, Ninety-Nine" and "Zero Six Five, Ninety-Nine" are acceptable.

When providing bullseye coordinates, speak at a steady and measured pace with a slight pause between each number. Not too fast, not too slow. Don't mush your numbers together.

If the bot has trouble understanding your bullseye coordinates, you may use the separators "at" or "altitude" between the range and altitude. That is "Bullseye Zero Six Five, Ninety-Nine, at Twelve Thousand"

''Tips:''

Think about what you want to say before you say it.

Speak clearly at a measured pace, as if you were recording a vlog or talking to colleagues in a meeting room. Speaking too quickly or excessively slowly can confuse the bot.

If you misspeak, release your Push-to-Talk key and start over rather than trying to correct yourself.

Avoid excessive chatter on SkyEye frequencies. This may delay responses to actual requests.

'''<big>Available Requests</big>'''

'''RADIO CHECK'''

Keyword: RADIO or COMM

Function: FOCUS will respond if they heard you. They will also inform you if they cannot see you on the radar scope.

Use: Testing communication with the bot.

''Examples:''

MOBIUS 1: "Thunderhead Mobius One radio check"

THUNDERHEAD: "Mobius One, five by five."

HITMAN 11: "Galaxy Hitman One One how's my radio working?"

GALAXY: "Hitman One One, Lima Charlie" [LIMA CHARLIE meaning LOUD & CLEAR]

YELLOW 13: "Goliath Yellow One Three radio"

GOLIATH: "Yellow One Three, loud and clear"

''Tips:''

Note that if your aircraft is still sitting on the ramp, you may not be visible on the radar scope yet.

'''ALPHA CHECK'''

Keyword: ALPHA

Function: FOCUS will check if they see you on scope and tell you your approximate current location in bullseye format.

Use: You can use this to coarsely check your INS navigation system in an aircraft without GPS. It is accurate to within several miles (accounting for potential lag time between when the bot checks the scope and when the response is sent on the radio).

''Examples:''

MOBIUS 1: "Thunderhead Mobius One alpha check"

THUNDERHEAD: "Mobius One, Thunderhead, contact, alpha check bullseye 010/122"

HITMAN 11: "Galaxy Hitman One One checking in as fragged, request alpha check bullseye"

GALAXY: "Hitman One One, Galaxy, contact, alpha check bullseye 144/28"

YELLOW 13: "Goliath Yellow One Three alpha"

GOLIATH: "Yellow One Three, Goliath, contact, alpha check bullseye 088/5"

'''BOGEY DOPE'''

Keyword: BOGEY

Function: FOCUS will give you the Bearing, Range, Altitude and Aspect from your aircraft to the nearest air-to-air threat.

Use: Get a vector to the nearest hostile aircraft.

Arguments:

Filter (optional): Either "airplanes" or "helicopters" to filter by a category of aircraft.

''Examples:''

MOBIUS 1: "Thunderhead Mobius One bogey dope"

THUNDERHEAD: "Mobius One, threat group BRAA 071/13, 17000, flank south, hostile, Flanker"

HITMAN 11: "Galaxy Hitman One One looking for a bogey - anything interesting?"

GALAXY: "Hitman One One, group BRAA 055/71, 22000, flank north, hostile, Tomcat"

YELLOW 13: "Goliath Yellow One Three bogey"

GOLIATH: "Yellow One Three, group BRAA 188/45, 8000, hot, hostile, Eagle"

''Tips:''

Make this request repeatedly during a BVR timeline to build and maintain situational awareness.

Note: Specific filters such as "MiG-29" or "Flanker" do not work. You can only filter to airplanes or helicopters.

If you are a fixed-wing aircraft, hostile fixed-wing aircraft are prioritized over hostile helicopters, regardless of range.

'''DECLARE'''

Keyword: DECLARE

Function: You provide the position of a radar contact on your scope. FOCUS will look for contacts in that area and tell you if they are hostile, friendly, a furball (mixed) or clean (nothing on scope). You can provide the position using either Bullseye or BRAA format .

Use: Additional source of Identify Friend or Foe (IFF)

Arguments:

Bullseye (bearing and distance) or BR (bearing and range) (required)

Altitude (optional)

Track direction (optional)

Providing the optional arguments can help FOCUS distinguish between contacts. If there's a friendly at 5000 feet and a hostile at 25000 feet, you may get a FURBALL response if you only provide the bullseye, or a specific response if you also provide altitude.

''Examples:''

HITMAN 1: Galaxy, Hitman One, declare one two four, five.

GALAXY: Hitman One, bullseye 122/51, 7000, track west, hostile, 2 contacts, Fitter.

MOBUIS 1: Thunderhead, Mobius One, declare two three zero, twelve, twelve thousand.

THUNDERHEAD: Mobius One, group bullseye 273/27, 2200, track east, hostile, Flanker.

EAGLE 12: Disco, Eagle One Two, declare BRAA zero nine zero, twenty five.

DISCO: Eagle One Two, group bullseye 072/52, 8000, track north, hostile, Flogger.

''Tips:''

You must provide either bullseye or BRAA coordinates. Due to limitations within DCS, the bot cannot receive your locked/bugged target via datalink.

'''PICTURE'''

Keyword: PICTURE

Function: FOCUS will rank threats by priority, then report the top three. Threats are considered relative to the coalition as a whole, not to an individual.

Use: General situational awareness.

Arguments:

Filter (optional)

''Examples:''

MOBIUS 1: "Thunderhead Mobius One, picture"

THUNDERHEAD: "Thunderhead, 5 groups. Group bullseye 192/41, 21000, track south, hostile, Flanker. Group bullseye 178/32, 9000, track east, hostile, Frogfoot. Group bullseye 181/44, 20000, track northwest, hostile, Frogfoot."

HITMAN 11: "Galaxy Hitman One One how's the picture looking?"

GALAXY: "Hitman One One, 6 groups. Group bullseye 211/27, 18000, track northwest, hostile, Frogfoot. Group bullseye 226/12, 7000, track northwest, hostile, Fulcrum. Group bullseye 193/47, 36000, track northeast, hostile, Foxhound."

''Tips:''

Repeat this call at regular intervals to maintain situational awareness.

Air combat is highly complex and the threat ranking algorithm is imperfect. FOCUS might omit a highly dangerous adversary from the response. Exercise caution!

Be considerate of your allies on the channel. The response contains a great deal of useful information, but can occupy the channel for 20-30 seconds.

'''SNAPLOCK'''

Keyword: SNAPLOCK

Function: This is a faster form of DECLARE intended for use during a BVR timeline. You tell FOCUS the BRA (bearing, range, altitude) of a threat on your radar scope. FOCUS will look for a group in that area and response with information.

Use: IFF during a BVR timeline.

Arguments:

Bearing from you to the contact (required)

Range from you to the contact (required)

Altitude of the contact (required)

''Examples:''

MOBIUS 1: "Thunderhead Mobius One, snaplock one two five, ten, eight thousand"

THUNDERHEAD: "Mobius 1, threat group BRAA 125/10, 8000, hot, hostile, two contacts, Flanker."

'''SPIKED'''

Keyword: SPIKED

Function: You tell FOCUS the approximate bearing to an airborne threat on your Radar Warning Receiver (RWR). FOCUS responds with information about the nearest potential source within a 30 degree cone in that direction.

Use: Can be used to get ranging information to a threat that is visible on the RWR but not the attack radar (or if your aircraft has no attack radar).

Arguments:

Bearing to the airborne radar threat (required)

''Examples:''

MOBIUS 1: "Thunderhead Mobius One, spiked zero eight zero"

THUNDERHEAD: "Mobius One, spike range 35, 16000, flank northeast, hostile, single contact."

HITMAN 11: "Galaxy Hitman One One sees a spike at zero six zero"

GALAXY: "Hitman One One, spike range 45, 8000, hot, hostile, single contact."

YELLOW 13: "Goliath Yellow One Three spiked three six zero"

GOLIATH: "Yellow One Three, Goliath clean three six zero"

''Tips:''

The accuracy of this call is imperfect. The information you receive is a best effort guess. FOCUS may misidentify the actual source of the radar signal.

'''Broadcast Calls'''

'''SUNRISE'''

When FOCUS controller comes online, it will announced that its services are available using the code word "SUNRISE".

If you hear this in the middle of a mission, it probably means the bot crashed and had to be restarted!

'''PICTURE'''

Server operators may optionally configure the GCI controller to automatically broadcast a PICTURE at regular intervals. The content and format is the same as described in the PICTURE request above.

Requesting a PICTURE will reset the interval on any automatic broadcast.

'''THREAT'''

FOCUS monitors for threats which are near or approaching friendly aircraft. Any hostile aircraft within a pre-briefed range (default 25NM) is always considered a threat. At further ranges, the bandit's aircraft capabilities are also considered. Threat calls are broadcast every few minutes for as long as the threat criteria are met. THREAT calls about rotary-wing threats are only broadcast to other rotary-wing aircraft. A plane won't receive warnings about helicopter threats.

Threat locations are given in BRAA format if they are relevant to a single friendly aircraft, or in bullseye format if they are relevant to multiple friendly aircraft.

Your own aircraft must be on a SkyEye SRS frequency, and using the same name in DCS and in SRS, to receive THREAT monitoring.

''Examples:''

WIZARD: RAVEN Three One, threat group BRAA 070/20, 1000, hot, hostile, 2 contacts, Fishbed.

GALAXY: HITMAN One One, threat group bullseye 040/96, 10000, track south, hostile, 2 contacts, Flanker.

'''MERGED'''

If any fixed-wing threats close within 3 nautical miles of a friendly aircraft, FOCUS will transmit a MERGED call. MERGED calls only apply to fixed-wing threats. You won't receive a MERGED call about a helicopter threat.

Your own aircraft must be on the SRS frequency, and using the same name in DCS and in SRS, to receive MERGED calls.

You will only receive one MERGED call every 30 seconds. If you merge with multiple threats within 30 seconds, you will only receive one MERGED call.

''Example:''

THUNDERHEAD: "Mobius one, merged."

'''FADED'''

When FOCUS sees a hostile contact within weapons range of a friendly aircraft disappear from the radar scope for at least 30 seconds, it will announce the hostile contact is FADED.

This is not a confirmation that the contact has been destroyed! In DCS, it is possible for aircraft to be marked dead while they are still alive and dangerous.

''Example:''

THUNDERHEAD: "Thunderhead, single contact faded, bullseye 146/123, track west, hostile, Flanker"

XSAF/FAQ

2026-05-26T14:12:09Z

Shifty: Shifty moved page FAQ to XSAF/FAQ without leaving a redirect: Archive XSAF-era page: move to XSAF/ subpage per legacy archive plan

{{XSAF-era}}

== Welcome to VRS! ==
(A very rough, work-in-progress FAQ)

=== Server Info ===
Victor Romeo Sierra - VRS [Dynamic AI Driven Campaign]
IP(s) 67.170.11.154:10319

Patreon: https://www.patreon.com/c/victorromeosierra/posts

website/wiki: https://victorromeosierra.com (work in progress, will eventually have player/server info)

Discord: Permanent Link: https://discord.gg/nc7uFgDuud

==== Radio Freqs: ====
Focus AWACS: 251.00AM

Guard: 133.00 AM

Helos: 30.00FM

SRS in use: server.victorromeosierra.com:10220 (Should autoconnect)

Live Map: https://map.victorromeosierra.com/

TacFiles: https://tacview.victorromeosierra.com

==== Extra Details: ====
Password: none

Easy Flight: No

Labels: No,but is using the New Dots of Patch 2.9.12.5336.1

RealWeather: Using real time weather data from Damascus international airport

=== Server Basics ===
Description: VRS is a PvE server with AI managed RedFor (Skynet) and an AI AWACS system (SkyEye). Players can fly fixed wing or rotary aircraft, in a variety of tasks that include: Air to air combat, Air to Ground combat, attack helicopter action, utility helicopters that include logistics and CSAR. There is a Life Limit on each airframe, a warehouse mechanic to control ordnance and airframes, and more! You can fly any module regardless of Era or Faction, even warbirds!

Map: Syria

Mission: Operation Syrian Sun

PvE: BlueFor Human Players vs AI Driven RedFor
Era and Restrictions: Modern, and pretty much anything goes. Airframes are not faction locked, so you can fly Red Aircraft on Bluefor (Blackshark, MiG21, Hind, etc)

Dynamic Slots in Use

==== MODS IN USE: ====
UH-60 Blackhawk [https://www.patreon.com/posts/uh60l-mod-2-0-138859868 Blackhawk 2.0]

C-130 https://www.mediafire.com/file/y5qov91ds5gvofv/Hercules_ver_6.8.2.zip/file

A-4 Skyhawk https://github.com/Community-A-4E/community-a4e-c/releases/tag/v2.2

OH-6A Little Bird: https://github.com/tobi-be/DCS-OH-6A

SU-30: https://drive.google.com/file/d/1uyBYxwla-YhzK5vXFGVVO0LSY32_S6qR/view?usp=sharing

Logistics/Warehousing/CTLD/Salvage: Most bases should have a place to pick up Crates and Troops. Should be a literal warehouse structure (insert pic?) The F10 Map should also have an indication of where to land to get troops and crates. Large or 6 Small crates to build a FOB (FARPs are coming soon) 800m distance from fob to unpack crates unload one unit type to unpack its crates before unloading other unit crates if you click on all cargo and select that cargo you will not find it in the rearm menu to load

You can Sling Load as well

==== Capacities: ====
Chinook: 6 small or 3 large crates.

Troops:

Mi8: 2 crates

Troops:

Hind:1

Huey:

Other AC:

P47 only crates

Salvage (WiP):

Warehousing: Players may need to unarm and defuel planes after landing to 'replace' that ordnance and fuel. Definitely try to land at a friendly base so you don’t ‘lose’ your airframe! You will also receive credit for your actions upon landing. Will be able to gather up 'wrecks' and bring them to a factory. They will be converted to $$$ or Points that will provide supplies.

Lives: 3 per airframe. Replaced after 24 hrs. Can rescue them via CSAR mechanics.

=== Skynet AI: ===
Solo players can find things to do. RedFor fixed wings flying around, and SAM nets defending things. RedFor ground forces and defenses, supply convoys. Redfor will attack and take over bases. The Logistics system is working, utility helicopters can do CSAR, CTLD, build things.

4 players is when you'll see Skynet start to ramp up its efforts. The AI will continue to ‘fight’ and do things once they have spawned, regardless of if players are online or not, so they will take over bases and shoot down tankers, etc.

==== SkyEye AI AWACS (Focus) ====
Callsign: Focus 251.00 AM

Uses SRS. She can do radio checks, Picture, Bogey Dopes, Merge, and Fade calls. Uses Bullseye reference. No need to constantly ask for BD or Pictures, it will use the Magic of AI to let you know what's going on around you.

Base Capturing: All Redfor needs to be dead, and need at least one BlueFor inside the 2km range around the base.

Combined Arms/JTAC: Combined Arms allows anyone w/CA to move ground units. There is an ED bug that once things get off-road (troops or vehicles) and move much more than a mile, good luck) JTAC? Other CA tasks available? Or is this reserved for Game Masters only?

OTHER: Server Resets: how long does it run for? Right now, it runs till one side wins which usually takes a couple of months.

Victory Conditions: Simple. Shove RedFor all the way off the map by capturing all of their bases.

XSAF/CSAR

2026-05-26T14:12:08Z

Shifty: Shifty moved page CSAR to XSAF/CSAR without leaving a redirect: Archive XSAF-era page: move to XSAF/ subpage per legacy archive plan

{{XSAF-era}}

This page will detail information on the CSAR system in use on VRS

== SAR Operations ==

* Job Persistence: Active SAR jobs now save and reload after a server restart, preventing resets between sessions.
* Map Markers: Player-requested map markers for SAR jobs now appear for 30 seconds to aid navigation.
* Job Listings: The SAR job list now shows heading and distance to the 10 nearest jobs, making navigation easier.
* Task Interaction Menu (F10 → F2 → F6 → F1):
** Pick up jobs
** Drop off jobs
** Show jobs on the map
** View job listing (with heading & distance)
* How to Sign Up:
** SAR: <code>F10 → F2 → F6 → F2</code>

[[File:SAR Jobs on F10.png|alt=SAR Jobs on F10|left|thumb|SAR Jobs on F10]]

Player Guide/Open Mod Manager

2026-05-26T13:56:27Z

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

« [[Player Guide]]

'''Open Mod Manager''' (OMM, also written OpenModMan) is a free mod manager for Windows, originally created by Sedenion (Eri M.) and now maintained as the successor to the older [https://wiki.hoggitworld.com/view/OVGME OvGME]. It enables and disables DCS mods non-destructively: mods live in a separate folder, OMM stages them into DCS when enabled, and restores the originals when disabled. Nothing in your DCS install is permanently overwritten.

VRS recommends OMM for any mod you install for our server. OMM solves the three problems players hit most often:

* '''DCS updates.''' DCS patches frequently overwrite files that mods touch. With OMM you flip every mod off before patching, run the update, then flip them back on.
* '''Server integrity checks.''' OMM lets you disable a mod for one server and re-enable it for another in seconds.
* '''Diagnosing conflicts.''' When something breaks, you can disable mods one at a time to find the culprit, without reinstalling anything.

The big upgrade over OvGME: '''VRS publishes two network repositories''', one for install-root mods (Auto Starts, etc.) and one for Saved Games mods (the per-aircraft livery packs). Subscribe each in OMM and you get one-click install plus automatic update notifications for [[Player Guide/Downloads|the VRS mod packs]].

* '''VRSInstall.xml''' → <code>https://victorromeosierra.com/VRSInstall.xml</code> → goes in a Channel pointed at your DCS '''install''' folder.
* '''VRSSavedGames.xml''' → <code>https://victorromeosierra.com/VRSSavedGames.xml</code> → goes in a Channel pointed at your '''Saved Games\DCS''' folder.

The split exists because the two folders live in different roots, and OMM has one Target Destination per Channel. We use two Channels.

__TOC__

== Installing OMM ==

Download OMM 1.3.5 or later from the [https://github.com/iquercorb/OpenModMan/releases iquercorb/OpenModMan releases page]. Two flavours are offered:

* '''Installer''' (<code>OpenModMan_1-3-5-x64_setup.exe</code>) - installs OMM like a normal Windows program. Pick this if you want a Start-menu shortcut.
* '''Portable ZIP''' (<code>OpenModMan_1-3-5-x64_Portable.zip</code>) - unpack anywhere and run <code>OpenModMan.exe</code> directly. No installer.

Either is fine. There are also 32-bit (x86) builds if you need them, but the 64-bit builds are what most players want.

== First-run setup ==

OMM organises mods as '''Mod Hubs''' (think "profile" - one per software you mod) containing one or more '''Mod Channels''' (one per destination folder). For VRS you'll create one Hub for DCS, with '''two''' Channels: one for your DCS install folder, one for your DCS Saved Games folder.

Launch OMM, then:

# Click '''File → New Mod Hub...''' Give it a name like <code>DCS</code> and pick a folder to store its config (anywhere; e.g. <code>D:\OMM\DCS-Hub</code>).
# In the new Hub, click '''Edit → Add Target Location...''' (some builds label this '''Add Mod Channel...''').
# Fill in the '''DCS Install''' channel:

{| class="wikitable"
! Field !! What to enter
|-
| '''Channel name''' (or "Indicative name") || <code>DCS Install</code>.
|-
| '''Target Destination folder''' || Your DCS '''install''' folder, typically: <code>C:\Program Files\Eagle Dynamics\DCS World</code> or, for Steam installs: <code>C:\Program Files (x86)\Steam\steamapps\common\DCSWorld</code> This is the folder that contains <code>bin/</code>, <code>Mods/</code>, <code>Scripts/</code>, etc. - '''not''' your Saved Games folder.
|-
| '''Library folder''' || Leave the default (a subfolder inside the Channel's home folder). This is where mod packages will be staged.
|-
| '''Backup folder''' || Leave the default. This is where OMM stores the originals it replaces.
|}

# Then add the second Channel: '''Edit → Add Target Location...''' again. Fill in the '''DCS Saved Games''' channel:

{| class="wikitable"
! Field !! What to enter
|-
| '''Channel name''' || <code>DCS Saved Games</code>.
|-
| '''Target Destination folder''' || Your DCS '''Saved Games''' folder: <code>C:\Users\<you>\Saved Games\DCS</code> (or <code>...\Saved Games\DCS.openbeta</code> if you run open beta separately - check what DCS actually uses by looking inside <code>C:\Users\<you>\Saved Games\</code>). This is the folder that contains <code>Liveries/</code>, <code>Missions/</code>, <code>Tracks/</code>, <code>Config/</code>, etc.
|-
| '''Library folder''' / '''Backup folder''' || Leave the defaults, as above.
|}

You only do this once. After that, OMM remembers the Hub and opens straight to the mod list.

'''Why two channels?''' DCS stores mods in two different roots: the install folder (where DCS itself lives, e.g. <code>C:\Program Files\Eagle Dynamics\DCS World</code>) and the Saved Games folder (your per-user state, e.g. <code>C:\Users\<you>\Saved Games\DCS</code>). Auto Starts and script edits go in the install root; liveries, kneeboards, and missions go in Saved Games. OMM has one Target Destination per Channel, so one Channel per root.

The install Channel is the one that protects you on patch day - DCS updates rewrite files there, and OMM's backup-and-restore is what makes those mods survive. Saved Games is safe from patches by design, but having OMM manage liveries too gives you auto-updates when VRS publishes new ones.

For the specific VRS packs - what to install where, and where to download them - see [[Player Guide/Downloads|Downloads]].

== Subscribing to the VRS repositories (recommended) ==

The fastest way to install and stay up-to-date with VRS mod packs. You'll subscribe each Channel to its matching repository.

'''DCS Install channel → VRSInstall repo:'''

# In your Hub, select the '''DCS Install''' Channel.
# Click '''Edit → Target Location properties...''' and switch to the '''Network Library''' tab.
# Click '''Add Network Repository'''.
# Enter:
#* '''Base URL:''' <code>https://victorromeosierra.com</code>
#* '''Name:''' <code>VRSInstall</code> ('''without''' the <code>.xml</code> extension - OMM appends it automatically)
# Click '''Test''' to confirm the repository is reachable, then '''OK''' to save.

'''DCS Saved Games channel → VRSSavedGames repo:'''

# Select the '''DCS Saved Games''' Channel.
# '''Edit → Target Location properties...''' → '''Network Library''' tab → '''Add Network Repository'''.
# Enter:
#* '''Base URL:''' <code>https://victorromeosierra.com</code>
#* '''Name:''' <code>VRSSavedGames</code>
# '''Test''' → '''OK'''.

'''Then for each Channel:'''

# Back in the main window, switch to the '''Network Library''' tab and click '''Query'''. OMM fetches the list of available mods.
# Select the packs you want, click '''Download Selected''', and OMM downloads them into your Library.
# Enable them in the Library tab as usual.

When VRS publishes an update, the repo's hash for that pack changes; OMM flags an update on its next Query. Click '''Download''' again and the new version replaces the old. With the per-aircraft livery split, a typical livery update only re-downloads the affected aircraft's pack (tens to hundreds of MB), not the full 9 GB pile.

== Installing a mod manually ==

If you'd rather skip the repository and download files yourself (or for any one-off mod not in the VRS repo):

# Download the mod as a <code>.zip</code>.
# Drop the <code>.zip</code> directly into your Channel's '''Library''' folder. OMM picks it up automatically; no need to unpack.
# In OMM, the mod appears in the Library tab with a status icon. Select it, click '''Install Selected''' (or double-click).
# Launch DCS. The mod is active.

'''Important:''' '''do not rename the <code>.zip</code>.''' OMM (and OvGME) require the top-level folder inside the zip to match the filename. <code>VRS_AutoStarts.zip</code> contains a <code>VRS_AutoStarts/</code> folder; rename the zip and the parse will fail.

== Updating and removing mods ==

'''To update a mod to a new version''' (manual install only - subscribed repos handle this automatically):

# In OMM, '''uninstall''' the existing version (it goes back to "available" status).
# Delete the old <code>.zip</code> from your Library folder.
# Drop the new <code>.zip</code> in.
# Click '''Install Selected'''.

'''To remove a mod entirely:'''

# Uninstall it in OMM.
# Delete the <code>.zip</code> from your Library folder.

'''Never''' delete a Library <code>.zip</code> while the mod is installed - that strands the modded files in DCS with no clean way to restore the originals. Always uninstall first.

== Before a DCS update ==

DCS patches can rewrite the same files some mods overwrite. The clean routine is:

# Open OMM and '''uninstall everything''' (select all in the Library tab, click '''Uninstall Selected''').
# Quit OMM.
# Run the DCS updater and let it finish.
# Re-open OMM and re-install your mods.

If you forget and run the patch with mods installed, DCS may overwrite OMM's backup with the patched file, and you'll lose the ability to cleanly uninstall the mod later. In that case, delete the mod from OMM, delete the staged file, re-download a fresh copy, and re-install.

== Migrating from OvGME ==

If you were previously using OvGME for VRS mods, do this '''before''' configuring OMM, or you'll end up with two managers fighting over the same DCS files:

# In OvGME, '''disable every mod''' (select all, click "Disable Selected"). OvGME restores the original DCS files.
# Verify the install dir looks clean (the <code>Mods/aircraft/*/Cockpit/Scripts/Macro_sequencies.lua</code> files should be back to stock or absent).
# Quit OvGME. You can uninstall it if you want, or just leave it idle - it won't conflict as long as nothing is enabled.
# Now follow [[#First-run setup|First-run setup]] above to configure OMM.
# Subscribe to the VRS repository or install packs manually as described.

OvGME backups and OMM backups are stored differently and not interchangeable. Don't try to import OvGME's mod list into OMM - just re-download the packs through OMM.

=== Bringing your existing OvGME library across ===

If your OvGME Mods folder contains other mods (personal weapon packs, cockpit tweaks, third-party autostarts, etc.), you don't have to re-download all of them. Copy the contents of your OvGME Mods folder into your new OMM Channel's Library folder:

# Locate your OMM Channel's Library folder. In OMM, select the Channel and check '''Edit → Target Location properties → Local Library''' tab. By default it sits at <code><HubFolder>\<ChannelName>\Library\</code>.
# Copy every mod from your OvGME Mods folder into that Library, '''except''' <code>VRS_AutoStarts.zip</code> and <code>Liveries.zip</code> (you'll get those via the VRSInstall and VRSSavedGames repo subscriptions instead - and VRS now publishes liveries as per-aircraft sub-packs, not one monolith) and any OvGME-specific README files.
# In OMM's Channel properties → '''Local Library''' tab, tick '''Developer mode'''. This lets OMM recognise folder-form mods (mods that you previously unzipped into the OvGME Mods folder rather than left as <code>.zip</code> files). Without Developer mode, OMM only sees <code>.zip</code> files.
# Restart OMM (or refresh the Library view). All your previous mods now appear in OMM's Library tab.

'''Watch for overlap.''' If any of your previous OvGME mods touched the same files as a VRS pack (e.g. another autostart for an airframe also covered by VRS_AutoStarts), only one can be installed at a time. Install your personal autostart '''or''' VRS_AutoStarts, not both.

== Troubleshooting ==

'''The mod is installed in OMM but nothing changed in DCS.''' The internal folder layout of the mod is wrong - the folders inside the mod's top-level directory must match DCS's '''install''' folder layout (e.g. <code>Mods/aircraft/FA-18C/Cockpit/Scripts/...</code>, <code>Scripts/...</code>). Open a working mod and compare. (Note: if the mod is actually a livery or kneeboard, it belongs in Saved Games, not in OMM.)

'''OMM rejects the <code>.zip</code> as "unknown or wrong Mod Pack architecture".''' The filename and the top-level folder inside the zip don't match. <code>VRS_AutoStarts.zip</code> must contain a folder called exactly <code>VRS_AutoStarts/</code> at its root. Don't rename downloaded zips.

'''DCS won't join the VRS server after installing a mod.''' VRS does not enforce strict integrity, but some mods (especially weapon/flight model edits) can still cause problems. Uninstall the mod, re-join, and ask in <code>#questions</code> on Discord before re-installing.

'''OMM says a file conflict / overlap occurred.''' Two installed mods both want to write the same file. The one installed last wins. Uninstall both, decide which one you want, install only that one.

'''Repository "Query" fails / 404.''' Double-check the Base URL is <code>https://victorromeosierra.com</code> (with <code>https</code>, no trailing slash) and the Name is the bare repo name '''without''' the <code>.xml</code> extension - OMM appends it itself, so writing <code>VRSInstall.xml</code> as the Name makes OMM fetch <code>VRSInstall.xml.xml</code> and 404. Confirm you can reach https://victorromeosierra.com/VRSInstall.xml (or https://victorromeosierra.com/VRSSavedGames.xml ) in a browser - if not, the repo may be temporarily offline.

== See also ==

* [[Player Guide/Downloads|Downloads]] - the VRS mod packs and other player-facing artifacts.
* [[Player Guide/SRS|SRS]] - the other piece of client-side setup every VRS pilot needs.
* [https://github.com/iquercorb/OpenModMan iquercorb/OpenModMan on GitHub] - source, releases, issue tracker.
* [https://github.com/iquercorb/OpenModMan/releases Open Mod Manager releases] - downloads for all versions.

Player Guide/Downloads

2026-05-26T13:56:26Z

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

« [[Player Guide]]

This page collects the downloadable artifacts VRS provides to its players - mod packs, kneeboards, charts, and anything else you should grab before flying on our server.

If you're new to mod managers, read [[Player Guide/Open Mod Manager|Open Mod Manager]] first. VRS publishes two network repositories (one per DCS install location) so OMM users can one-click install and auto-update mod packs.

__TOC__

== One-click install via the VRS repositories ==

If you've followed [[Player Guide/Open Mod Manager|the OMM setup guide]] and created the two Channels (DCS Install + DCS Saved Games), subscribe each to its matching repo:

{| class="wikitable"
! Channel !! Base URL !! Name !! What's in it
|-
| '''DCS Install''' || <code>https://victorromeosierra.com</code> || <code>VRSInstall</code> || Auto Starts (and any future install-root mods).
|-
| '''DCS Saved Games''' || <code>https://victorromeosierra.com</code> || <code>VRSSavedGames</code> || 22 per-aircraft livery sub-packs.
|}

Enter the bare Name (without <code>.xml</code>) - OMM appends the extension. See [[Player Guide/Open Mod Manager#Subscribing to the VRS repositories (recommended)|the OMM page]] for the full walkthrough.

The repositories currently list:

{| class="wikitable"
! Pack !! Ident !! Channel !! Size
|-
| [[#Auto Starts|Auto Starts]] || <code>VRS_AutoStarts_v1.0.0</code> || DCS Install || ~50 KB
|-
| Liveries (per aircraft, 22 packs) || <code>Liveries_<Aircraft></code> || DCS Saved Games || see [[#Liveries|Liveries]] below
|}

== Mod packs ==

=== Auto Starts ===

Quick-start macros for the airframes VRS flies (A-10C II, AH-64D, FA-18C, Ka-50 III, Mi-24P, Mi-8MTV2, SA342, UH-1H). Each one runs a consistent VRS Quick Start sequence on an in-game keybind.

'''Install via OMM (recommended):''' on your '''DCS Install''' Channel, subscribe to <code>VRSInstall</code> as described [[#One-click install via the VRS repositories|above]], then download and install <code>VRS_AutoStarts</code>.

'''Manual install (OMM or OvGME):''' download [https://github.com/VictorRomeoSierra/VRSMods/releases/latest/download/VRS_AutoStarts.zip VRS_AutoStarts.zip] (latest release on the [https://github.com/VictorRomeoSierra/VRSMods VictorRomeoSierra/VRSMods] repo). Drop the <code>.zip</code> into your manager's Library folder, then install/enable it. Don't rename the zip - OMM and OvGME both require the inner folder name to match the filename.

The Auto Starts pack modifies aircraft startup scripts that live under the DCS '''install''' folder. DCS patches can overwrite these on update, so this pack '''must''' be installed through a mod manager (OMM or OvGME), not by hand.

=== Liveries ===

VRS squadron and unit liveries for the airframes our pilots fly. The pack is split into '''one sub-pack per aircraft''' so updates to a single airframe don't force you to re-download the whole pile.

'''Install via OMM (recommended):''' on your '''DCS Saved Games''' Channel, subscribe to <code>VRSSavedGames</code> as described [[#One-click install via the VRS repositories|above]], then Query and pick the per-aircraft packs you want. Each one installs into <code>Saved Games\DCS\Liveries\<Aircraft>\</code> via OMM's normal flow - no special channel target needed.

Current per-aircraft sub-packs (as of 2026-05-26):

{| class="wikitable"
! Aircraft !! Sub-pack ident
|-
| A-10A (Flaming Cliffs) || <code>Liveries_A-10A</code>
|-
| A-10C Warthog || <code>Liveries_A-10C</code>
|-
| A-10C II Tank Killer || <code>Liveries_A-10C_2</code>
|-
| A-4E-C Skyhawk || <code>Liveries_A-4E-C</code>
|-
| AH-64D Apache (cockpit only) || <code>Liveries_AH-64D</code>
|-
| AV-8B Harrier || <code>Liveries_AV8BNA</code>
|-
| CH-47F Chinook || <code>Liveries_CH-47F</code>
|-
| F-14B Tomcat || <code>Liveries_F-14B</code>
|-
| F-16C Viper || <code>Liveries_F-16C_50</code>
|-
| F/A-18C Hornet || <code>Liveries_FA-18C_hornet</code>
|-
| Il-76MD Candid || <code>Liveries_IL-76MD</code>
|-
| Ka-50 Black Shark 2 || <code>Liveries_Ka-50</code>
|-
| Ka-50 Black Shark 3 || <code>Liveries_Ka-50_3</code>
|-
| Mirage 2000C || <code>Liveries_M-2000C</code>
|-
| Mi-24P Hind || <code>Liveries_Mi-24P</code>
|-
| Mi-8MTV2 Hip || <code>Liveries_Mi-8MT</code>
|-
| MiG-21bis Fishbed || <code>Liveries_MiG-21bis</code>
|-
| Su-25T (Flaming Cliffs, cockpit only) || <code>Liveries_Su-25T</code>
|-
| Su-33 Flanker-D || <code>Liveries_Su-33</code>
|-
| UH-1H Huey || <code>Liveries_UH-1H</code>
|-
| UH-60A Black Hawk || <code>Liveries_UH-60A</code>
|-
| UH-60L Black Hawk || <code>Liveries_UH-60L</code>
|}

'''Alternative: monolithic download (OvGME or manual extract).''' If you don't want OMM, VRS still publishes the full pack as a single zip: [https://victorromeosierra.com/Mods/Liveries.zip Liveries.zip] (~9 GB). Extract it directly into <code>C:\Users\<you>\Saved Games\DCS\</code> - the archive's top-level <code>Liveries</code> folder merges into <code>Saved Games\DCS\Liveries\</code>. This is the legacy path; OMM users should prefer the per-aircraft repo above since updates are smaller.

== Voice Attack profiles ==

[https://voiceattack.com/ Voice Attack] is a third-party voice-command program that pairs with DCS to let you speak commands instead of clicking them. VRS provides a profile tailored to the AI mission's F10 menu and the [[Player Guide/Air Support|CORE / UTILITY MARK]] system.

'''Voice Attack itself is separate software''' - install it from voiceattack.com first. VRS only provides the profile (.vap) file you import into Voice Attack; it does not install or modify Voice Attack itself.

Downloads (latest [https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack/releases/tag/VRS-AI-v0.5 VRS-AI-v0.5] release):

* '''[https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack/releases/download/VRS-AI-v0.5/VRS.AI.v0.5-Profile.vap VRS.AI.v0.5-Profile.vap]''' (~2.6 MB) - the full profile with embedded audio.
* '''[https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack/releases/download/VRS-AI-v0.5/VRS.AI-Profile.vap VRS.AI-Profile.vap]''' (~62 KB) - the profile without bundled audio (smaller, but you'll need to record your own command audio).
* '''[https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack/releases/download/VRS-AI-v0.5/VRS.AI-Profile.html VRS.AI-Profile.html]''' (~133 KB) - HTML reference of every voice command in the profile. Open in a browser, no Voice Attack required.

To install: in Voice Attack, click the '''Import Profile''' button (or '''Options → Import Profile'''), point at the downloaded <code>.vap</code>, and it'll appear in your profile list.

These profiles are not managed by OMM (Voice Attack stores profiles in its own application folder, not under DCS).

== See also ==

* [[Player Guide/Open Mod Manager|Open Mod Manager]] - the mod manager used to install the mod packs above.
* [[Player Guide/SRS|SRS]] - voice radio, required for VRS server.

Player Guide/Downloads

2026-05-24T03:08:12Z

Shifty: /* Voice Attack profiles */

« [[Player Guide]]

This page collects the downloadable artifacts VRS provides to its players - mod packs, kneeboards, charts, and anything else you should grab before flying on our server.

If you're new to mod managers, read [[Player Guide/Open Mod Manager|Open Mod Manager]] first. VRS publishes a network repository so OMM users can one-click install and auto-update mod packs.

__TOC__

== One-click install via the VRS repository ==

If you've followed [[Player Guide/Open Mod Manager|the OMM setup guide]], the fastest install path is to subscribe to the VRS repository:

* '''Base URL:''' <code>https://victorromeosierra.com</code>
* '''Name:''' <code>Mods/repo</code> ('''without''' the <code>.xml</code> extension - OMM appends it automatically)

In OMM, on your DCS Channel: '''Edit → Target Location properties → Network Repositories → Add'''. Then back on the main window, '''Network Library → Query → Download Selected'''. See [[Player Guide/Open Mod Manager#Subscribing to the VRS repository (recommended)|the OMM page]] for the full walkthrough.

The repository currently lists:

{| class="wikitable"
! Pack !! Ident !! Size
|-
| [[#Auto Starts|Auto Starts]] || <code>VRS_AutoStarts_v1.0.0</code> || ~50 KB
|-
| [[#Liveries|Liveries]] || <code>Liveries_v1.0.0</code> || 9.7 GB
|}

== Mod packs ==

=== Auto Starts ===

Quick-start macros for the airframes VRS flies (A-10C II, AH-64D, FA-18C, Ka-50 III, Mi-24P, Mi-8MTV2, SA342, UH-1H). Each one runs a consistent VRS Quick Start sequence on an in-game keybind.

'''Install via OMM (recommended):''' subscribe to the VRS repository as above, then download and install the <code>VRS_AutoStarts</code> pack from the Repositories tab. The pack auto-installs into your DCS install Channel.

'''Manual install (OMM or OvGME):''' download [https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack/releases/latest/download/VRS_AutoStarts.zip VRS_AutoStarts.zip] (latest release on the [https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack VictorRomeoSierra/DCS-LUAs-VoiceAttack] repo). Drop the <code>.zip</code> into your manager's Library folder, then install/enable it. Don't rename the zip - OMM and OvGME both require the inner folder name to match the filename.

The Auto Starts pack modifies aircraft startup scripts that live under the DCS '''install''' folder. DCS patches can overwrite these on update, so this pack '''must''' be installed through a mod manager (OMM or OvGME), not by hand.

=== Liveries ===

VRS squadron and unit liveries for the airframes our pilots fly.

'''Recommended install: manual copy into Saved Games.''' DCS patches leave Saved Games alone, so a plain extract is the simplest path:

# Download [https://victorromeosierra.com/Mods/Liveries.zip Liveries.zip] (9.7 GB - this takes a while).
# Open <code>C:\Users\<you>\Saved Games\DCS\</code> in Explorer.
# Extract the zip into that folder. The archive's top-level <code>Liveries</code> folder merges with (or creates) <code>Saved Games\DCS\Liveries\</code>.
# Restart DCS. The liveries appear in the aircraft loadout screen.

To remove or update a livery later, edit the contents of <code>Saved Games\DCS\Liveries\</code> directly.

'''Alternative: managed install via OMM.''' If you want OMM to track liveries (so you can subscribe for auto-update notifications when VRS publishes a new pack), set up a second Mod Channel:

# In your DCS Mod Hub, '''Edit → Add Target Location...'''
# '''Channel name:''' <code>DCS Liveries</code> (or similar).
# '''Target Destination:''' <code>C:\Users\<you>\Saved Games\DCS\Liveries</code> - the <code>Liveries</code> subfolder, '''not''' the parent <code>DCS</code> folder. Create the <code>Liveries</code> folder first if it doesn't exist.
# Add the same VRS repository (Base URL <code>https://victorromeosierra.com</code>, Name <code>Mods/repo</code>) to this Channel too.
# Query, then download and install <code>Liveries</code>.

Why the unusual Target setting: OMM strips the top-level folder of a mod when installing. Liveries.zip's top-level folder is <code>Liveries/</code>; if your Target is <code>Saved Games\DCS\</code>, the <code>Liveries/</code> wrapper is consumed and files land at the wrong path. Pointing Target one level deeper at <code>Saved Games\DCS\Liveries\</code> compensates.

== Voice Attack profiles ==

[https://voiceattack.com/ Voice Attack] is a third-party voice-command program that pairs with DCS to let you speak commands instead of clicking them. VRS provides a profile tailored to the AI mission's F10 menu and the [[Player Guide/Air Support|CORE / UTILITY MARK]] system.

'''Voice Attack itself is separate software''' - install it from voiceattack.com first. VRS only provides the profile (.vap) file you import into Voice Attack; it does not install or modify Voice Attack itself.

Downloads (latest [https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack/releases/tag/VRS-AI-v0.5 VRS-AI-v0.5] release):

* '''[https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack/releases/download/VRS-AI-v0.5/VRS.AI-Profile.vap VRS.AI-Profile.vap]''' (~62 KB) - the profile without bundled audio (smaller, but you'll need to record your own command audio).
* '''[https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack/releases/download/VRS-AI-v0.5/VRS.AI-Profile.html VRS.AI-Profile.html]''' (~133 KB) - HTML reference of every voice command in the profile. Open in a browser, no Voice Attack required.

To install: in Voice Attack, click the '''Import Profile''' button (or '''Options → Import Profile'''), point at the downloaded <code>.vap</code>, and it'll appear in your profile list.

These profiles are not managed by OMM (Voice Attack stores profiles in its own application folder, not under DCS).

== See also ==

* [[Player Guide/Open Mod Manager|Open Mod Manager]] - the mod manager used to install the mod packs above.
* [[Player Guide/SRS|SRS]] - voice radio, required for VRS server.

Player Guide/SRS

2026-05-24T02:44:03Z

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

« [[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.

Player Guide/Open Mod Manager

2026-05-24T02:44:00Z

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

« [[Player Guide]]

'''Open Mod Manager''' (OMM, also written OpenModMan) is a free mod manager for Windows, originally created by Sedenion (Eri M.) and now maintained as the successor to the older [https://wiki.hoggitworld.com/view/OVGME OvGME]. It enables and disables DCS mods non-destructively: mods live in a separate folder, OMM stages them into DCS when enabled, and restores the originals when disabled. Nothing in your DCS install is permanently overwritten.

VRS recommends OMM for any mod you install for our server. OMM solves the three problems players hit most often:

* '''DCS updates.''' DCS patches frequently overwrite files that mods touch. With OMM you flip every mod off before patching, run the update, then flip them back on.
* '''Server integrity checks.''' OMM lets you disable a mod for one server and re-enable it for another in seconds.
* '''Diagnosing conflicts.''' When something breaks, you can disable mods one at a time to find the culprit, without reinstalling anything.

The big upgrade over OvGME: '''VRS publishes a network repository''' at <code>https://victorromeosierra.com/Mods/repo.xml</code>. Subscribe once in OMM and you get one-click install plus automatic update notifications for [[Player Guide/Downloads|the VRS mod packs]].

__TOC__

== Installing OMM ==

Download OMM 1.3.5 or later from the [https://github.com/iquercorb/OpenModMan/releases iquercorb/OpenModMan releases page]. Two flavours are offered:

* '''Installer''' (<code>OpenModMan_1-3-5-x64_setup.exe</code>) - installs OMM like a normal Windows program. Pick this if you want a Start-menu shortcut.
* '''Portable ZIP''' (<code>OpenModMan_1-3-5-x64_Portable.zip</code>) - unpack anywhere and run <code>OpenModMan.exe</code> directly. No installer.

Either is fine. There are also 32-bit (x86) builds if you need them, but the 64-bit builds are what most players want.

== First-run setup ==

OMM organises mods as '''Mod Hubs''' (think "profile" - one per software you mod) containing one or more '''Mod Channels''' (one per destination folder). For VRS, you'll create one Hub for DCS, with one Channel targeting your DCS install folder.

Launch OMM, then:

# Click '''File → New Mod Hub...''' Give it a name like <code>DCS</code> and pick a folder to store its config (anywhere; e.g. <code>D:\OMM\DCS-Hub</code>).
# In the new Hub, click '''Edit → Add Target Location...''' (some builds label this '''Add Mod Channel...''').
# Fill in the Channel:

{| class="wikitable"
! Field !! What to enter
|-
| '''Channel name''' (or "Indicative name") || Anything you like, e.g. <code>DCS Install</code>.
|-
| '''Target Destination folder''' || Your DCS '''install''' folder, typically: <code>C:\Program Files\Eagle Dynamics\DCS World</code> or, for Steam installs: <code>C:\Program Files (x86)\Steam\steamapps\common\DCSWorld</code> This is the folder that contains <code>bin/</code>, <code>Mods/</code>, <code>Scripts/</code>, etc. - '''not''' your Saved Games folder.
|-
| '''Library folder''' || Leave the default (a subfolder inside the Channel's home folder). This is where mod packages will be staged.
|-
| '''Backup folder''' || Leave the default. This is where OMM stores the originals it replaces.
|}

You only do this once. After that, OMM remembers the Hub and opens straight to the mod list.

'''Why the install folder and not Saved Games?''' OMM exists to protect you from DCS overwriting your mods on patch day, and the '''install''' folder is the one DCS patches rewrite. Mods that live there - aircraft auto-starts, script edits, anything that touches core module files - need OMM's backup-and-restore so a patch can't wipe them silently.

Saved Games is the opposite case: DCS patches don't touch it, so mods that go there (liveries, kneeboards, missions) are safe with a plain folder copy and don't need a manager.

For the specific VRS packs - what to install where, and where to download them - see [[Player Guide/Downloads|Downloads]].

== Subscribing to the VRS repository (recommended) ==

The fastest way to install and stay up-to-date with VRS mod packs:

# In your Hub, select the Channel you just created.
# Click '''Edit → Target Location properties...''' and switch to the '''Network Library''' tab.
# Click the '''Add Network Repository''' button.
# Enter:
#* '''Base URL:''' <code>https://victorromeosierra.com</code>
#* '''Name:''' <code>Mods/repo</code> ('''without''' the <code>.xml</code> extension - OMM appends it automatically)
# Click '''Test''' to confirm the repository is reachable, then '''OK''' to save.
# Back in the main window, switch to the '''Network Library''' tab and click '''Query'''. OMM fetches the list of available mods.
# Select the packs you want, click '''Download Selected''', and OMM downloads them into your Library.
# Enable them in the Library tab as usual.

When VRS publishes an update, the repo's hash for that pack changes; OMM flags an update on its next Query. Click '''Download''' again and the new version replaces the old.

== Installing a mod manually ==

If you'd rather skip the repository and download files yourself (or for any one-off mod not in the VRS repo):

# Download the mod as a <code>.zip</code>.
# Drop the <code>.zip</code> directly into your Channel's '''Library''' folder. OMM picks it up automatically; no need to unpack.
# In OMM, the mod appears in the Library tab with a status icon. Select it, click '''Install Selected''' (or double-click).
# Launch DCS. The mod is active.

'''Important:''' '''do not rename the <code>.zip</code>.''' OMM (and OvGME) require the top-level folder inside the zip to match the filename. <code>VRS_AutoStarts.zip</code> contains a <code>VRS_AutoStarts/</code> folder; rename the zip and the parse will fail.

== Updating and removing mods ==

'''To update a mod to a new version''' (manual install only - subscribed repos handle this automatically):

# In OMM, '''uninstall''' the existing version (it goes back to "available" status).
# Delete the old <code>.zip</code> from your Library folder.
# Drop the new <code>.zip</code> in.
# Click '''Install Selected'''.

'''To remove a mod entirely:'''

# Uninstall it in OMM.
# Delete the <code>.zip</code> from your Library folder.

'''Never''' delete a Library <code>.zip</code> while the mod is installed - that strands the modded files in DCS with no clean way to restore the originals. Always uninstall first.

== Before a DCS update ==

DCS patches can rewrite the same files some mods overwrite. The clean routine is:

# Open OMM and '''uninstall everything''' (select all in the Library tab, click '''Uninstall Selected''').
# Quit OMM.
# Run the DCS updater and let it finish.
# Re-open OMM and re-install your mods.

If you forget and run the patch with mods installed, DCS may overwrite OMM's backup with the patched file, and you'll lose the ability to cleanly uninstall the mod later. In that case, delete the mod from OMM, delete the staged file, re-download a fresh copy, and re-install.

== Migrating from OvGME ==

If you were previously using OvGME for VRS mods, do this '''before''' configuring OMM, or you'll end up with two managers fighting over the same DCS files:

# In OvGME, '''disable every mod''' (select all, click "Disable Selected"). OvGME restores the original DCS files.
# Verify the install dir looks clean (the <code>Mods/aircraft/*/Cockpit/Scripts/Macro_sequencies.lua</code> files should be back to stock or absent).
# Quit OvGME. You can uninstall it if you want, or just leave it idle - it won't conflict as long as nothing is enabled.
# Now follow [[#First-run setup|First-run setup]] above to configure OMM.
# Subscribe to the VRS repository or install packs manually as described.

OvGME backups and OMM backups are stored differently and not interchangeable. Don't try to import OvGME's mod list into OMM - just re-download the packs through OMM.

=== Bringing your existing OvGME library across ===

If your OvGME Mods folder contains other mods (personal weapon packs, cockpit tweaks, third-party autostarts, etc.), you don't have to re-download all of them. Copy the contents of your OvGME Mods folder into your new OMM Channel's Library folder:

# Locate your OMM Channel's Library folder. In OMM, select the Channel and check '''Edit → Target Location properties → Local Library''' tab. By default it sits at <code><HubFolder>\<ChannelName>\Library\</code>.
# Copy every mod from your OvGME Mods folder into that Library, '''except''' <code>VRS_AutoStarts.zip</code> (you get that via the repo subscription instead) and any OvGME-specific README files.
# In OMM's Channel properties → '''Local Library''' tab, tick '''Developer mode'''. This lets OMM recognise folder-form mods (mods that you previously unzipped into the OvGME Mods folder rather than left as <code>.zip</code> files). Without Developer mode, OMM only sees <code>.zip</code> files.
# Restart OMM (or refresh the Library view). All your previous mods now appear in OMM's Library tab.

'''Watch for overlap.''' If any of your previous OvGME mods touched the same files as a VRS pack (e.g. another autostart for an airframe also covered by VRS_AutoStarts), only one can be installed at a time. Install your personal autostart '''or''' VRS_AutoStarts, not both.

== Troubleshooting ==

'''The mod is installed in OMM but nothing changed in DCS.''' The internal folder layout of the mod is wrong - the folders inside the mod's top-level directory must match DCS's '''install''' folder layout (e.g. <code>Mods/aircraft/FA-18C/Cockpit/Scripts/...</code>, <code>Scripts/...</code>). Open a working mod and compare. (Note: if the mod is actually a livery or kneeboard, it belongs in Saved Games, not in OMM.)

'''OMM rejects the <code>.zip</code> as "unknown or wrong Mod Pack architecture".''' The filename and the top-level folder inside the zip don't match. <code>VRS_AutoStarts.zip</code> must contain a folder called exactly <code>VRS_AutoStarts/</code> at its root. Don't rename downloaded zips.

'''DCS won't join the VRS server after installing a mod.''' VRS does not enforce strict integrity, but some mods (especially weapon/flight model edits) can still cause problems. Uninstall the mod, re-join, and ask in <code>#questions</code> on Discord before re-installing.

'''OMM says a file conflict / overlap occurred.''' Two installed mods both want to write the same file. The one installed last wins. Uninstall both, decide which one you want, install only that one.

'''Repository "Query" fails / 404.''' Double-check the Base URL is <code>https://victorromeosierra.com</code> (with <code>https</code>, no trailing slash) and the Name is <code>Mods/repo</code> ('''without''' <code>.xml</code> - OMM appends the extension itself, so writing <code>Mods/repo.xml</code> makes OMM fetch <code>Mods/repo.xml.xml</code> and 404). Confirm you can reach https://victorromeosierra.com/Mods/repo.xml in a browser - if not, the repo may be temporarily offline.

== See also ==

* [[Player Guide/Downloads|Downloads]] - the VRS mod packs and other player-facing artifacts.
* [[Player Guide/SRS|SRS]] - the other piece of client-side setup every VRS pilot needs.
* [https://github.com/iquercorb/OpenModMan iquercorb/OpenModMan on GitHub] - source, releases, issue tracker.
* [https://github.com/iquercorb/OpenModMan/releases Open Mod Manager releases] - downloads for all versions.

Player Guide/Downloads

2026-05-24T02:43:58Z

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

« [[Player Guide]]

This page collects the downloadable artifacts VRS provides to its players - mod packs, kneeboards, charts, and anything else you should grab before flying on our server.

If you're new to mod managers, read [[Player Guide/Open Mod Manager|Open Mod Manager]] first. VRS publishes a network repository so OMM users can one-click install and auto-update mod packs.

__TOC__

== One-click install via the VRS repository ==

If you've followed [[Player Guide/Open Mod Manager|the OMM setup guide]], the fastest install path is to subscribe to the VRS repository:

* '''Base URL:''' <code>https://victorromeosierra.com</code>
* '''Name:''' <code>Mods/repo</code> ('''without''' the <code>.xml</code> extension - OMM appends it automatically)

In OMM, on your DCS Channel: '''Edit → Target Location properties → Network Repositories → Add'''. Then back on the main window, '''Network Library → Query → Download Selected'''. See [[Player Guide/Open Mod Manager#Subscribing to the VRS repository (recommended)|the OMM page]] for the full walkthrough.

The repository currently lists:

{| class="wikitable"
! Pack !! Ident !! Size
|-
| [[#Auto Starts|Auto Starts]] || <code>VRS_AutoStarts_v1.0.0</code> || ~50 KB
|-
| [[#Liveries|Liveries]] || <code>Liveries_v1.0.0</code> || 9.7 GB
|}

== Mod packs ==

=== Auto Starts ===

Quick-start macros for the airframes VRS flies (A-10C II, AH-64D, FA-18C, Ka-50 III, Mi-24P, Mi-8MTV2, SA342, UH-1H). Each one runs a consistent VRS Quick Start sequence on an in-game keybind.

'''Install via OMM (recommended):''' subscribe to the VRS repository as above, then download and install the <code>VRS_AutoStarts</code> pack from the Repositories tab. The pack auto-installs into your DCS install Channel.

'''Manual install (OMM or OvGME):''' download [https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack/releases/latest/download/VRS_AutoStarts.zip VRS_AutoStarts.zip] (latest release on the [https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack VictorRomeoSierra/DCS-LUAs-VoiceAttack] repo). Drop the <code>.zip</code> into your manager's Library folder, then install/enable it. Don't rename the zip - OMM and OvGME both require the inner folder name to match the filename.

The Auto Starts pack modifies aircraft startup scripts that live under the DCS '''install''' folder. DCS patches can overwrite these on update, so this pack '''must''' be installed through a mod manager (OMM or OvGME), not by hand.

=== Liveries ===

VRS squadron and unit liveries for the airframes our pilots fly.

'''Recommended install: manual copy into Saved Games.''' DCS patches leave Saved Games alone, so a plain extract is the simplest path:

# Download [https://victorromeosierra.com/Mods/Liveries.zip Liveries.zip] (9.7 GB - this takes a while).
# Open <code>C:\Users\<you>\Saved Games\DCS\</code> in Explorer.
# Extract the zip into that folder. The archive's top-level <code>Liveries</code> folder merges with (or creates) <code>Saved Games\DCS\Liveries\</code>.
# Restart DCS. The liveries appear in the aircraft loadout screen.

To remove or update a livery later, edit the contents of <code>Saved Games\DCS\Liveries\</code> directly.

'''Alternative: managed install via OMM.''' If you want OMM to track liveries (so you can subscribe for auto-update notifications when VRS publishes a new pack), set up a second Mod Channel:

# In your DCS Mod Hub, '''Edit → Add Target Location...'''
# '''Channel name:''' <code>DCS Liveries</code> (or similar).
# '''Target Destination:''' <code>C:\Users\<you>\Saved Games\DCS\Liveries</code> - the <code>Liveries</code> subfolder, '''not''' the parent <code>DCS</code> folder. Create the <code>Liveries</code> folder first if it doesn't exist.
# Add the same VRS repository (Base URL <code>https://victorromeosierra.com</code>, Name <code>Mods/repo</code>) to this Channel too.
# Query, then download and install <code>Liveries</code>.

Why the unusual Target setting: OMM strips the top-level folder of a mod when installing. Liveries.zip's top-level folder is <code>Liveries/</code>; if your Target is <code>Saved Games\DCS\</code>, the <code>Liveries/</code> wrapper is consumed and files land at the wrong path. Pointing Target one level deeper at <code>Saved Games\DCS\Liveries\</code> compensates.

== Voice Attack profiles ==

[https://voiceattack.com/ Voice Attack] is a third-party voice-command program that pairs with DCS to let you speak commands instead of clicking them. VRS provides a profile tailored to the AI mission's F10 menu and the [[Player Guide/Air Support|CORE / UTILITY MARK]] system.

'''Voice Attack itself is separate software''' - install it from voiceattack.com first. VRS only provides the profile (.vap) file you import into Voice Attack; it does not install or modify Voice Attack itself.

Downloads (latest [https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack/releases/tag/VRS-AI-v0.5 VRS-AI-v0.5] release):

* '''[https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack/releases/download/VRS-AI-v0.5/VRS.AI.v0.5-Profile.vap VRS.AI.v0.5-Profile.vap]''' (~2.6 MB) - the full profile with embedded audio.
* '''[https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack/releases/download/VRS-AI-v0.5/VRS.AI-Profile.vap VRS.AI-Profile.vap]''' (~62 KB) - the profile without bundled audio (smaller, but you'll need to record your own command audio).
* '''[https://github.com/VictorRomeoSierra/DCS-LUAs-VoiceAttack/releases/download/VRS-AI-v0.5/VRS.AI-Profile.html VRS.AI-Profile.html]''' (~133 KB) - HTML reference of every voice command in the profile. Open in a browser, no Voice Attack required.

To install: in Voice Attack, click the '''Import Profile''' button (or '''Options → Import Profile'''), point at the downloaded <code>.vap</code>, and it'll appear in your profile list.

These profiles are not managed by OMM (Voice Attack stores profiles in its own application folder, not under DCS).

== See also ==

* [[Player Guide/Open Mod Manager|Open Mod Manager]] - the mod manager used to install the mod packs above.
* [[Player Guide/SRS|SRS]] - voice radio, required for VRS server.

Player Guide

2026-05-24T02:43:56Z

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

[[File:VRS-Logo.png|256x256px|center|VRS - Victor Romeo Sierra]]

Welcome to our Victor Romeo Sierra (VRS) community -- a laid-back group of virtual pilots brought together by a shared passion for flying, teamwork, and having a good time in the skies. Built around Digital Combat Simulator, our group is focused on creating a relaxed, welcoming environment where both experienced aviators and new recruits can enjoy everything from casual flights to coordinated missions without the pressure of hardcore mil-sim expectations. Whether you're here to learn, fly, or simply unwind after a long day, there's always a seat on the flight line for you at VRS!

Please take time to review the VRS Player Guide to help familiarize yourself with VRS, our server, and other important information. If you have any questions feel free to post in the #questions Discord channel.

This guide explains how to play the VRS mission from the BLUE side.

It is intentionally light on REDFOR internals and focused on what players can do.

== Sections ==

* [[Player Guide/Mission Mindset|Mission Mindset]] - Three parallel loops that shape every flight.
* [[Player Guide/Air Support|Air Support]] - CORE / UTILITY MARK system: how to call AWACS, tankers, CAP, escorts via F10 map marks.
* [[Player Guide/SRS|SRS]] - Installing Simple Radio Standalone, connecting to the VRS server, picking your callsign.
* [[Player Guide/Open Mod Manager|Open Mod Manager]] - Managing DCS install-folder mods non-destructively, plus subscribing to the VRS network repository for one-click install and auto-updates.
* [[Player Guide/Downloads|Downloads]] - VRS mod packs (Auto Starts, Liveries) and other player-facing artifacts.
* [[Player Guide/SkyEye|SkyEye]] - Talking to the AI GCI bot over SRS: callsign format, requests, brevity.
* [[Player Guide/Personal Escorts|Personal Escorts]] - Credit-funded personal escorts.
* [[Player Guide/Intel Reporting|Intel Reporting]] - Reporting RED activity via the Personal Menu.
* [[Player Guide/CTLD Logistics|CTLD Logistics]] - Building factories, Fat Cows, and force-multiplier deployment.
* [[Player Guide/CSAR and Salvage|CSAR and Salvage]] - Combat Search and Rescue, SAR, and battlefield Salvage.
* [[Player Guide/Credits and Progression|Credits and Progression]] - Credit economy + intel progression.
* [[Player Guide/Red Behavior|Red Behavior]] - How REDFOR adapts to BLUE pressure.
* [[Player Guide/Reporting a Bug|Reporting a Bug]] - How to file bug reports.
* [[Player Guide/Team Play|Team Play]] - Patterns that work for coordinated coalition play.
* [[Player Guide/Quick Command Card|Quick Command Card]] - One-screen reference card for all CORE / UTILITY MARK commands.
* [[Player Guide/Discord Commands|Discord Commands]] - Player-facing slash commands the VRS bot exposes in Discord.
* [[Player Guide/In-Game Chat Commands|In-Game Chat Commands]] - <code>-</code> prefix commands the bot listens for in the DCS chat window.

Player Guide/SRS

2026-05-21T04:22:01Z

Shifty: remove csar message

« [[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 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.

Player Guide/CSAR and Salvage

2026-05-21T04:16:06Z

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

« [[Player Guide]]

'''CSAR SRS frequency: 30.00 FM.''' Tune here in your helo to coordinate with other rescuers and downed pilots. See [[Player Guide/SRS|SRS]] for setup.

How it works:

F10 layout: Personal / CSAR / CTLD / Salvage / Interrogation / Factory Menu.

The Rescue Duty toggle is in the Personal Menu. Most active rescue and salvage actions require Rescue Duty ON.

CSAR Menu

* List Active Pickups

* Show Pickups on Map

* Pick up nearby rescue

* Check Onboard

* Offload Pickups

* Request Signal Flare

* Request Smoke

CSAR / SAR flow

: 1. Turn ON Rescue Duty (Personal Menu -> Toggle Rescue Duty).

: 2. Show Pickups on Map or List Active Pickups to find rescue markers.

: 3. Request Signal Flare / Request Smoke to localize a friendly survivor when needed.

: 4. Land near the survivor and use Pick up nearby rescue.

: 5. To move survivors toward a safer pickup, place a map mark with text: CSAR exfil. Nearby rescue locations move toward the mark.

: 6. Land near a friendly airbase and Offload Pickups.

[[File:UH-60-CSAR.jpg|614x333px]]

''UH-60 on CSAR duty -- ready to pluck your pilots out of the water if needed''

[[File:UH-60-carrier-approach.jpg|600px|center|UH-60 returning to the boat after a CSAR pickup.]]

''UH-60 returning to the boat - survivors aboard.''

Salvage Menu

* Pick up nearby (250 kg)

* Pick up nearby (500 kg)

* Pick up nearby (1000 kg)

* Pick up nearby (All remaining)

* Drop off

* Emergency Jett!

* List salvage jobs map wide

* Show Salvage on Map

Salvage flow

: 1. Show Salvage on Map (markers are separate from CSAR markers).

: 2. Salvage pickup requires a helicopter, Rescue Duty ON, and landing near the wreck.

: 3. Choose pickup amount: 250 kg / 500 kg / 1000 kg / All remaining.

: 4. Drop off to unload. Factory drop-offs and airbase drop-offs both pay but use different payout multipliers.

: 5. Coalition salvage credit feeds the salvage pot, which funds Factory production.

: 6. Emergency Jett! discards all onboard rescue/salvage payload.

: 7. Landing near a valid airbase or factory can auto-trigger offload after a short delay where enabled.

Interrogation Menu

* Request status

* Request collected info

* Initiate 'mind games'

* Initiate 'chat with knuckles'

* Initiate 'hydro-persuation'

* Initiate 'oil planking'

Interrogation actions operate on captured RED pilots. They are fed by successful recovery and offload outcomes.

Player Guide/Team Play

2026-05-21T04:12:24Z

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

« [[Player Guide]]

* CAP + tanker + strike package timing instead of solo pushes.

* Dedicated logistics window protected by escort / CAP.

* Rescue coverage during high-tempo strike periods.

* Shared intel callouts before major moves.

[[File:Carrier-cat-shot.jpg|614x333px]]

''Cat shot ready -- coordinated launches keep the tempo up.''

[[File:F18-cat-shot-director.jpg|600px|center|F/A-18C cat shot with shooter giving the launch signal.]]

''Shooter calling the launch - coordinated cat shots keep the tempo.''

Player Guide/SRS

2026-05-21T04:12:24Z

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

« [[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.

Player Guide/SkyEye

2026-05-21T04:12:23Z

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

« [[Player Guide]]

'''SkyEye''' is an AI-powered Ground Controlled Intercept (GCI) bot that listens on SRS and talks back to you in plain English. It replaces the DCS in-game AWACS with a controller that understands proper [https://en.wikipedia.org/wiki/Brevity_code brevity] - PICTURE, BOGEY DOPE, DECLARE, SPIKED, and friends - and can monitor the battlespace for threats and announce them automatically.

On the VRS server the SkyEye GCI's callsign is '''Focus'''. You can also address it as '''Anyface''' - that's the SkyEye-wide alias and is always accepted.

SkyEye is open source and maintained by [https://github.com/dharmab dharmab]. The upstream player guide lives at [https://github.com/dharmab/skyeye/blob/main/docs/PLAYER.md github.com/dharmab/skyeye/docs/PLAYER.md].

__TOC__

== Quickstart ==

# Set your in-game callsign in the DCS server browser. See [[Player Guide/SRS|SRS]] for the format and tips on picking a good one.
# Connect to the VRS [[Player Guide/SRS|SRS server]] with your SRS name matching your DCS name.
# Get airborne (you may not appear on the GCI scope while still on the ramp).
# Tune to a Focus SRS frequency in your aircraft (or in SRS directly). The current Focus frequencies on VRS are:
#* '''251.00 AM'''
#* '''133.00 AM'''
# Key your radio and say: <code>"Focus, Callsign 1, radio check"</code>. If you hear back, you're in business.
# Try: <code>"Focus, Callsign 1, picture"</code> for the top threats, or <code>"Focus, Callsign 1, bogey"</code> for the nearest threat to you.

== Picking a callsign ==

Your callsign matters a lot for voice recognition. The short version: pick a 2-3 syllable English word followed by 1-3 digits, a pipe (<code>|</code>), then your normal name - <code>Mobius 1 | Reaper</code>, <code>Hitman 11 | Monarch</code>.

See [[Player Guide/SRS#Choosing your callsign|Choosing your callsign]] on the SRS page for the full set of do's, don'ts, and the reasoning.

== How to talk to SkyEye ==

The request format is:

Focus YOUR_CALLSIGN (...) REQUEST_TYPE (...) (ARGS...) (...)

The <code>(...)</code> bits are filler - SkyEye ignores extra chatter around the keywords. "Focus, Mobius One, good morning. Alpha check bullseye" parses the same as "Focus, Mobius One, alpha check".

A few things to remember when speaking numbers:

* '''Compass bearings''' - say all three digits individually. "Zero Six Five", not "Six Five" or "Sixty-Five".
* '''All other numbers''' - say them normally. "Seventeen", not "One Seven".
* '''Do not use ICAO pronunciation.''' Say "Three", "Five", "Nine", '''not''' "Tree", "Fife", "Niner".
* '''Bullseye coordinates''' - leave a slight pause between range and altitude. If the bot struggles, insert "at" or "altitude": "Bullseye Zero Six Five, Ninety-Nine, at Twelve Thousand".

General tips:

* Think about what you want to say before you key the mic.
* Speak at a measured, conversational pace - too fast or too slow degrades recognition.
* If you misspeak, release PTT and start over rather than trying to correct yourself mid-transmission.
* Avoid chatter on SkyEye frequencies - it delays responses for everyone.

== Requests you can make ==

{| class="wikitable"
! Keyword !! What it does
|-
| <code>RADIO</code> / <code>COMM</code> || '''Radio check.''' Focus replies if it heard you, and tells you if you're not visible on scope.
|-
| <code>ALPHA</code> || '''Alpha check.''' Focus reports your current position in bullseye format. Useful for coarse INS verification in non-GPS aircraft.
|-
| <code>VECTOR</code> || '''Vector to a point.''' Defaults to bullseye; you can also ask for a vector to tanker (nearest compatible) or to a [[#Named locations|named location]] like Home Plate.
|-
| <code>BOGEY</code> || '''Bogey dope.''' Bearing, range, altitude, aspect to the nearest air-to-air threat. Optional filter: airplanes or helicopters.
|-
| <code>DECLARE</code> || '''IFF a contact you can see on your scope.''' Provide bullseye or BR, optionally altitude and track. Focus replies hostile / friendly / furball / clean.
|-
| <code>PICTURE</code> || '''Top three threats to the coalition.''' Long response (~20-30 s of channel time) - use sparingly.
|-
| <code>SNAPLOCK</code> || '''Fast IFF during a BVR timeline.''' Provide BRA (bearing, range, altitude) of a contact on your radar - Focus confirms what's there.
|-
| <code>SPIKED</code> / <code>STROBE</code> || '''Find the source of a radar spike.''' Provide bearing only; Focus looks in a 30° cone and reports the nearest likely source.
|}

For full examples of each request, see the [https://github.com/dharmab/skyeye/blob/main/docs/PLAYER.md upstream player guide].

=== Named locations ===

For VECTOR-TO requests, VRS has a small set of named locations you can use instead of coordinates. As of this writing the list covers blue-coalition start bases on Syria:

* '''Home Plate''' (also "Incirlik" / "Incirlik Air Base")
* '''Adana''' (also "Adana Sakirpasa")
* '''Akrotiri''' (also "RAF Akrotiri")

Example: "Focus, Eagle One One, vector to Home Plate".

The carrier group is deliberately not in the list - its position moves, and a static lat/lon would lie. The reserved names Bullseye and Tanker are always available as well.

== Things SkyEye says on its own ==

Some calls come from Focus without you asking:

* '''SUNRISE''' - broadcast when the controller comes online. Mid-mission SUNRISE usually means the bot crashed and restarted.
* '''PICTURE''' - the server may be configured to broadcast a PICTURE on a timer. Requesting one resets the timer.
* '''THREAT''' - broadcast when a hostile aircraft is near or approaching a friendly. BRAA format if it's relevant to one aircraft, bullseye if it's relevant to several. Helicopter THREATs only go to other rotary-wing aircraft.
* '''MERGED''' - broadcast when a fixed-wing hostile closes within 3 NM of you. Fixed-wing only; one MERGED per 30 seconds.
* '''FADED''' - broadcast when a hostile within weapons range disappears from the scope for at least 30 seconds. '''This is not a kill confirmation''' - DCS sometimes marks live aircraft as dead.

To receive THREAT and MERGED calls, your aircraft '''must''' be tuned to a SkyEye SRS frequency '''and''' your SRS name must match your DCS in-game name.

== Troubleshooting ==

'''Focus doesn't respond at all.''' Check that you said "Focus" (or "Anyface") at the start of your transmission - this is the most common mistake. Ask another player for a radio check to confirm you're audible.

'''Focus responds but says it can't see you.'''

* Confirm your in-game name matches the callsign you're giving.
* If you joined right after mission start, return to spectators, re-slot, or fully reconnect - joining too early can leave you invisible to Tacview.
* If you've been stationary for several minutes, move slightly. Tacview throttles position updates for non-moving objects.
* If your aircraft took even minor damage, re-slot - the game can mark it as destroyed even when it's flyable.

== Mindset ==

Focus is good at counting contacts and computing angles. It is '''not''' good at understanding tactics or strategy - that's still on you. Treat it as one source among many alongside your own radar, RWR, eyeballs, and human flight-mates. And remember: DCS sometimes marks live aircraft as dead, so a "FADED" or "clean" call is never a guarantee.

== See also ==

* [[Player Guide/SRS|SRS]] - install, server connect, callsign format.
* [[Player Guide/Air Support|Air Support]] - F10 map-mark commands, including the AWACS marks (<code>awacs</code>, <code>focus</code>, <code>skyeye</code>, <code>overlord</code>) that spawn in-mission AWACS aircraft.
* [[FOCUS]] - earlier, longer FOCUS page (tagged XSAF-era) with more verbose examples for each request.
* [https://github.com/dharmab/skyeye dharmab/skyeye on GitHub] - source, releases, admin guide.
* [https://github.com/dharmab/skyeye/blob/main/docs/PLAYER.md Upstream player guide] - full request reference and examples.
* [https://github.com/dharmab/skyeye/blob/main/docs/PRIVACY.md Privacy statement] - how SkyEye uses voice and gameplay data.

Player Guide/In-Game Chat Commands

2026-05-21T04:12:21Z

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

« [[Player Guide]]

These are the player-facing '''in-game chat commands''' the VRS bot listens for. Type them in the DCS chat window (usually <code>Enter</code> opens chat) - the bot uses the <code>-</code> prefix, then the command name, then any arguments.

Example: type <code>-credits</code> in chat to see your credit balance.

'''Notation'''

* <code><arg></code> - required argument
* <code>[arg]</code> - optional argument
* Admin-only chat commands (kick, ban, restart, etc.) are role-gated and not documented here.

__TOC__

== Profile + help ==

{| class="wikitable"
! Command !! Description
|-
| <code>-help</code> || The help command
|-
| <code>-linkme</code> || link your user to Discord
|-
| <code>-911</code> || send an alert to admins (misuse will be punished!)
|}

== Server + mission info ==

{| class="wikitable"
! Command !! Description
|-
| <code>-timeleft</code> || Time to the next restart
|-
| <code>-atis</code> || display ATIS information
|-
| <code>-coalition</code> || displays your current coalition
|-
| <code>-password</code> (aliases: <code>-passwd</code>) || displays the coalition password
|}

== Credits ==

{| class="wikitable"
! Command !! Description
|-
| <code>-credits <server></code> || Shows your current credits
|-
| <code>-donate</code> || Donate credits to another player
|-
| <code>-tip</code> || Tip a GCI with points
|}

== Voting ==

{| class="wikitable"
! Command !! Description
|-
| <code>-vote</code> || start a voting or vote for a change
|}

== Acknowledgement + penalty ==

{| class="wikitable"
! Command !! Description
|-
| <code>-ack</code> || acknowledge a user message
|-
| <code>-forgive</code> || forgive another user for their infraction
|-
| <code>-penalty <server></code> || displays your penalty points
|}

Player Guide/Discord Commands

2026-05-21T04:12:20Z

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

« [[Player Guide]]

These are the player-facing '''Discord slash commands''' the VRS bot exposes. Type <code>/</code> in a VRS Discord channel to see the autocompleter; only commands you have permission to run will appear.

'''Notation'''

* <code><arg></code> - required argument
* <code>[arg]</code> - optional argument
* Admin-only commands (server management, bans, mission control, etc.) are not documented here. Ask in <code>#questions</code> if you need one.

__TOC__

== Linking your account ==

{| class="wikitable"
! Command !! Description
|-
| <code>/linkme</code> || Link your DCS and Discord user
|-
| <code>/find <name></code> || Find a player by name
|-
| <code>/info <member></code> || Shows player information
|}

== Player + squadron stats ==

{| class="wikitable"
! Command !! Description
|-
| <code>/statistics [period] [user]</code> || Shows player statistics
|-
| <code>/highscore [server] [period] [limit]</code> || Displays the top players of your server(s)
|-
| <code>/squadron info <squadron_id></code> || Info about a squadron
|-
| <code>/squadron join <squadron_id></code> || Join a squadron
|-
| <code>/squadron leave <squadron_id></code> || Leave a squadron
|-
| <code>/squadron list <squadron_id></code> || List members of a squadron
|-
| <code>/squadron credits <squadron_id></code> || Credit points of a squadron
|-
| <code>/squadron donate <squadron_id> <points> [server]</code> || Donate credit points to a squadron
|}

== Mission statistics ==

{| class="wikitable"
! Command !! Description
|-
| <code>/missionstats <server></code> || Display Mission Statistics
|-
| <code>/sorties [user] [period]</code> || Display statistics about sorties
|-
| <code>/modulestats [user] [module] [period]</code> || Module statistics
|-
| <code>/refuelings [user] [period]</code> || Refueling statistics
|-
| <code>/nemesis [user] [period]</code> || Find who killed you most
|-
| <code>/antagonist [user] [period]</code> || Find who you've killed the most
|-
| <code>/history [user] [start] [end]</code> || Event History
|}

== Credits ==

{| class="wikitable"
! Command !! Description
|-
| <code>/credits info</code> || Shows your current credits
|-
| <code>/credits donate <to> <donation></code> || Donate credits to another member
|}

== CSAR ==

{| class="wikitable"
! Command !! Description
|-
| <code>/csar stats [user]</code> || Shows CSAR rescue stats
|-
| <code>/csar lives [user] [server]</code> || Shows your slot lives for airframes with active CSARs
|}

== Voting ==

{| class="wikitable"
! Command !! Description
|-
| <code>/vote list</code> || Lists the current votes
|-
| <code>/vote create <server> <what></code> || Create a vote
|-
| <code>/vote cancel <server></code> || Cancel a vote
|}

== Mission + server info ==

{| class="wikitable"
! Command !! Description
|-
| <code>/mission info <server></code> || Info about the running mission
|-
| <code>/mission briefing <server></code> || Shows briefing of the active mission
|-
| <code>/server timeleft <server></code> || Time until server / mission restart
|-
| <code>/serverlist [search]</code> || List registered DCS servers
|-
| <code>/campaign list [active]</code> || Lists all (active) campaigns
|-
| <code>/campaign info <campaign></code> || Campaign info
|}

== Tacview ==

{| class="wikitable"
! Command !! Description
|-
| <code>/tacview download <server> <file></code> || Download a Tacview
|}

== Help ==

{| class="wikitable"
! Command !! Description
|-
| <code>/help <cmd></code> || The help command
|-
| <code>/doc <what> [fmt] [role] [channel]</code> || Generate Documentation
|}

Player Guide/CSAR and Salvage

2026-05-21T04:12:20Z

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

« [[Player Guide]]

How it works:

F10 layout: Personal / CSAR / CTLD / Salvage / Interrogation / Factory Menu.

The Rescue Duty toggle is in the Personal Menu. Most active rescue and salvage actions require Rescue Duty ON.

CSAR Menu

* List Active Pickups

* Show Pickups on Map

* Pick up nearby rescue

* Check Onboard

* Offload Pickups

* Request Signal Flare

* Request Smoke

CSAR / SAR flow

: 1. Turn ON Rescue Duty (Personal Menu -> Toggle Rescue Duty).

: 2. Show Pickups on Map or List Active Pickups to find rescue markers.

: 3. Request Signal Flare / Request Smoke to localize a friendly survivor when needed.

: 4. Land near the survivor and use Pick up nearby rescue.

: 5. To move survivors toward a safer pickup, place a map mark with text: CSAR exfil. Nearby rescue locations move toward the mark.

: 6. Land near a friendly airbase and Offload Pickups.

[[File:UH-60-CSAR.jpg|614x333px]]

''UH-60 on CSAR duty -- ready to pluck your pilots out of the water if needed''

[[File:UH-60-carrier-approach.jpg|600px|center|UH-60 returning to the boat after a CSAR pickup.]]

''UH-60 returning to the boat - survivors aboard.''

Salvage Menu

* Pick up nearby (250 kg)

* Pick up nearby (500 kg)

* Pick up nearby (1000 kg)

* Pick up nearby (All remaining)

* Drop off

* Emergency Jett!

* List salvage jobs map wide

* Show Salvage on Map

Salvage flow

: 1. Show Salvage on Map (markers are separate from CSAR markers).

: 2. Salvage pickup requires a helicopter, Rescue Duty ON, and landing near the wreck.

: 3. Choose pickup amount: 250 kg / 500 kg / 1000 kg / All remaining.

: 4. Drop off to unload. Factory drop-offs and airbase drop-offs both pay but use different payout multipliers.

: 5. Coalition salvage credit feeds the salvage pot, which funds Factory production.

: 6. Emergency Jett! discards all onboard rescue/salvage payload.

: 7. Landing near a valid airbase or factory can auto-trigger offload after a short delay where enabled.

Interrogation Menu

* Request status

* Request collected info

* Initiate 'mind games'

* Initiate 'chat with knuckles'

* Initiate 'hydro-persuation'

* Initiate 'oil planking'

Interrogation actions operate on captured RED pilots. They are fed by successful recovery and offload outcomes.

Player Guide/Air Support

2026-05-21T04:12:19Z

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

« [[Player Guide]]

Air support is called in by placing "map marks" on the F10 map and inserting "command text" as the mark label.

How to place "CORE MARK" and "UTILITY MARK" commands on the F10 map:

#1. Place a "Map Marker" on the F10 map by clicking the "Mark Label" button.

[[File:F10-mark-label-button.jpg|480x275px]]

#2. Place the "circle map marker" at your desired location (see red arrow).

[[File:F10-circle-marker-place.jpg|480x317px]]

#3. "Type" one of the following commands into the text window of the map marker (green arrow). Specific commands are listed below.

[[File:F10-marker-text-window.jpg|480x317px]]

VRS "CORE MARK" commands: "Type" one of the following into the text window.

AWACS

: awacs awacs orbit awacs racetrack

: focus focus orbit focus racetrack

: '''skyeye overlord 
:

''The radio voice you'll hear from these AWACS is the [[Player Guide/SkyEye|SkyEye]] GCI bot, callsign Focus.''

Tanker (boom + MPRS pair)

: tanker tanker orbit tanker racetrack

: tankers tankers orbit tankers racetrack

: fuel gas aar

Boom Tanker (KC-135 / Texaco)

: aar boom aar boom orbit aar boom racetrack

: boom boom tanker texaco

MPRS Tanker (KC-135MPRS / Arco)

: aar mprs aar mprs orbit aar mprs racetrack mprs

: drogue basket probe arco

Specops Tanker (KC-130 / Shell)

: aar specops specops special ops

: hc130 c130 shell

[[File:KC-135-Texaco-boom.jpg|614x333px]]

''Boom contact -- KC-135 Texaco at Angels 20.''

[[File:F18-KC135-boom-refuel.jpg|600px|center|F/A-18C plugged into a KC-135 boom.]]

''F/A-18C topping off from a KC-135 - boom contact over the hills.''

When refueling, the tankers will be on station at these speeds, altitudes, frequencies, and TACANs:

{| class="wikitable"
|-
! '''KC-135 Boom-Texaco'''
! '''280 kts'''
! '''Angels 20'''
! '''Freq: 252.000'''
! '''TACAN: 40Y'''
|-
| '''KC-135 Boom-Reserve'''
| '''280 kts'''
| '''Angels 20'''
| '''Freq: 254.000'''
| '''TACAN: 42Y'''
|-
| '''KC-135 MPRS-Arco'''
| '''280 kts'''
| '''Angels 20'''
| '''Freq: 253.000'''
| '''TACAN: 41Y'''
|-
| '''KC-135 MPRS-Reserve'''
| '''280 kts'''
| '''Angels 20'''
| '''Freq: 255.000'''
| '''TACAN: 43Y'''
|-
| '''KC-130 Specops-Shell'''
| '''130 kts'''
| '''Angels 5'''
| '''Freq: 256.000'''
| '''TACAN: 44Y'''
|}

[[File:KC-135MPRS-Arco-drogue.jpg|480x260px]]

''Probe-and-drogue plug -- Arco over the hills.''

[[File:F-16-probe-drogue.jpg|600px|center|F-16CM holding the basket on a probe-and-drogue tanker.]]

''F-16CM holding the basket - probe-and-drogue contact.''

CAP

: cap f14 cap f-14 cap f 14

: cap f15 cap f-15 cap f 15

: cap f16 cap f-16 cap f 16

: cap f18 cap f-18 cap f 18

Drone Recon (MQ-9 / Reaper-1)

: drone recon recon drone scout drone reaper recon

Drone CAS (MQ-9 / Reaper-2)

: drone cas cas drone attack drone reaper cas

VRS "UTILITY MARK" commands: "Type" one of the following into the text window.

* flare

* smoke white

* smoke blue

* smoke red

* smoke green

* smoke orange

#4. To finalize the task, "minimize (-)" or "close (X)" the text box (see blue arrow on the screenshot above).

If correctly interpreted, you will receive a confirmation message in the upper right-hand corner of the F10 map screen, and your VRS direct player AI air support is on the way.

[[File:F10-marker-confirmation.jpg|614x333px]]

[[File:F18-F14-CAPs.jpg|614x324px]]

''Map markers can call multiple flights at once -- here, F-18 and F-14 CAPs simultaneously.''

What each support type does:

* AWACS: BLUE airborne picture anchor. Can be re-tasked by placing a new AWACS mark on the F10 map.

* Tankers (Boom / MPRS / Specops): Refueling anchors with racetrack or orbit behavior.

* CAP support (map-mark and menu-driven escorts): AI CAP flights. Map mark for area station; menu for personal escort.

* Drones: Per-player MQ-9 support; not shared with the coalition.

: drone recon -- 340 Cr + 65 intel. Callsign: Reaper-1, orbits at ~25,000 ft for area ISR.

: drone cas -- 680 Cr + 65 intel. Callsign: Reaper-2, same orbit profile, weapons-capable.

* Only one drone active at a time. A second request while one is up is denied at no cost.

* 30-minute personal cooldown starts only after a successful dispatch.

* Denied requests (threat zone, no intel, another active drone) do not start a cooldown and refund all resources.

* Drones use the same threat-avoidance logic as AWACS/tankers; move the mark farther from threat belts if denied.

Important "campaign support behavior" players should expect:

* Safety logic: If the marker is placed in an "unsafe" location, you get a chat message and the requested asset finds the nearest safe location on its own.

* Auto-relief: Low-fuel support assets RTB and can auto-replace to hold station continuity.

* Tanker scaling: If requests are far apart, additional tanker slot(s) can spawn.

* Continuous adaptation: Campaign assets can reposition if the threat picture changes.

Practical air support tips:

* Place support marks behind your current BLUE engagement edge, not on it.

* Racetrack for sustained lane support; orbit for compact local support.

* As the frontline moves, move your campaign assets forward or back to match.

* Think of tankers and AWACS as campaign assets: defend the airspace around them.

Player Guide

2026-05-21T04:12:19Z

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

[[File:VRS-Logo.png|256x256px|center|VRS - Victor Romeo Sierra]]

Welcome to our Victor Romeo Sierra (VRS) community -- a laid-back group of virtual pilots brought together by a shared passion for flying, teamwork, and having a good time in the skies. Built around Digital Combat Simulator, our group is focused on creating a relaxed, welcoming environment where both experienced aviators and new recruits can enjoy everything from casual flights to coordinated missions without the pressure of hardcore mil-sim expectations. Whether you're here to learn, fly, or simply unwind after a long day, there's always a seat on the flight line for you at VRS!

Please take time to review the VRS Player Guide to help familiarize yourself with VRS, our server, and other important information. If you have any questions feel free to post in the #questions Discord channel.

This guide explains how to play the VRS mission from the BLUE side.

It is intentionally light on REDFOR internals and focused on what players can do.

== Sections ==

* [[Player Guide/Mission Mindset|Mission Mindset]] - Three parallel loops that shape every flight.
* [[Player Guide/Air Support|Air Support]] - CORE / UTILITY MARK system: how to call AWACS, tankers, CAP, escorts via F10 map marks.
* [[Player Guide/SRS|SRS]] - Installing Simple Radio Standalone, connecting to the VRS server, picking your callsign.
* [[Player Guide/SkyEye|SkyEye]] - Talking to the AI GCI bot over SRS: callsign format, requests, brevity.
* [[Player Guide/Personal Escorts|Personal Escorts]] - Credit-funded personal escorts.
* [[Player Guide/Intel Reporting|Intel Reporting]] - Reporting RED activity via the Personal Menu.
* [[Player Guide/CTLD Logistics|CTLD Logistics]] - Building factories, Fat Cows, and force-multiplier deployment.
* [[Player Guide/CSAR and Salvage|CSAR and Salvage]] - Combat Search and Rescue, SAR, and battlefield Salvage.
* [[Player Guide/Credits and Progression|Credits and Progression]] - Credit economy + intel progression.
* [[Player Guide/Red Behavior|Red Behavior]] - How REDFOR adapts to BLUE pressure.
* [[Player Guide/Reporting a Bug|Reporting a Bug]] - How to file bug reports.
* [[Player Guide/Team Play|Team Play]] - Patterns that work for coordinated coalition play.
* [[Player Guide/Quick Command Card|Quick Command Card]] - One-screen reference card for all CORE / UTILITY MARK commands.
* [[Player Guide/Discord Commands|Discord Commands]] - Player-facing slash commands the VRS bot exposes in Discord.
* [[Player Guide/In-Game Chat Commands|In-Game Chat Commands]] - <code>-</code> prefix commands the bot listens for in the DCS chat window.

Main Page

2026-05-21T04:12:18Z

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

'''<big>Welcome to VRS!</big>'''

Victor Romeo Sierra is a set of DCS Servers. They are currently:

Victor Romeo Sierra - Dynamic AI Driven Campaign -- Our main server with an AI REDFOR and an AI AWACS System

Victor Romeo Sierra [Olympus] - Our server running the Olympus game master software (mostly used for testing)

VRSWW2 - Our WWII warbird server.

== Player Guide ==

[[File:VRS-Logo.png|128x128px|right|link=Player Guide]]
The current player-facing documentation lives in the '''[[Player Guide]]''' - mission mindset, BLUE air support (CORE / UTILITY MARK commands), CTLD logistics, CSAR & salvage, and more.

== Getting started ==
* '''[[Player Guide]]''' - current VRS gameplay reference (start here)
* [[FAQ|VRS FAQ]] (XSAF-era)
* [[New player guide|New Player Guide]] (XSAF-era)
* [[FOCUS|FOCUS User Guide]] (XSAF-era)
* [[Logistics]] (XSAF-era)
* [[CSAR]] (XSAF-era)
* [[Salvage]] (XSAF-era)
* [https://map.victorromeosierra.com/servers/VRS Live Map of VRS Dynamic AI Server]
* [https://stats.victorromeosierra.com/ Player Stats Page]
* [https://discord.gg/victorromeosierra Discord]
* [https://www.patreon.com/c/VictorRomeoSierra/ Patreon]

Player Guide/SkyEye

2026-05-21T04:02:03Z

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

« [[Player Guide]]

'''SkyEye''' is an AI-powered Ground Controlled Intercept (GCI) bot that listens on SRS and talks back to you in plain English. It replaces the DCS in-game AWACS with a controller that understands proper [https://en.wikipedia.org/wiki/Brevity_code brevity] — PICTURE, BOGEY DOPE, DECLARE, SPIKED, and friends — and can monitor the battlespace for threats and announce them automatically.

On the VRS server the SkyEye GCI's callsign is '''Focus'''. You can also address it as '''Anyface''' — that's the SkyEye-wide alias and is always accepted.

SkyEye is open source and maintained by [https://github.com/dharmab dharmab]. The upstream player guide lives at [https://github.com/dharmab/skyeye/blob/main/docs/PLAYER.md github.com/dharmab/skyeye/docs/PLAYER.md].

__TOC__

== Quickstart ==

# Set your in-game name to a callsign in the format <code>Callsign 1 | yourname</code> — a 2–3 syllable English word, 1–3 digits, a pipe (<code>|</code>), then your normal name. Example: <code>Mobius 1 | Reaper</code>.
# Join the VRS server with [https://github.com/ciribob/DCS-SimpleRadioStandalone SRS] running. The SRS server is <code>server.victorromeosierra.com:10220</code>.
# Get airborne (you may not appear on the GCI scope while still on the ramp).
# Tune to a Focus SRS frequency in your aircraft (or in SRS directly). The current Focus frequencies on VRS are:
#* '''251.00 AM'''
#* '''133.00 AM'''
#* '''30.00 FM''' (helicopters)
# Key your radio and say: <code>"Focus, Callsign 1, radio check"</code>. If you hear back, you're in business.
# Try: <code>"Focus, Callsign 1, picture"</code> for the top threats, or <code>"Focus, Callsign 1, bogey"</code> for the nearest threat to you.

== Picking a callsign ==

SkyEye recognises your callsign best when it follows the format above. A few rules of thumb:

* Use a '''2–3 syllable English word''' followed by '''1–3 digits''', then <code>|</code>, then your name.
* 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 — <code>WARDOG 14</code>, <code>Wardog 14</code>, <code>wardog14</code>, and <code>Wardog 1 4</code> are all the same.

Avoid:

* Names that sound like brevity words: alpha, radio, comm, bogey, picture, declare, snaplock, spiked, bullseye (e.g. "Spade" can be misheard as "SPIKE").
* Names that sound like numbers — "Knight" ≈ "Nine", "Fort" ≈ "Four".
* Hard-to-distinguish pairs — "Spare"/"Spear", "Jester"/"Gesture", "Witch"/"Which".
* Obscure or made-up words — "Razgriz", "Beskar" — the bot will try, but is less accurate.
* Very short callsigns (2–3 characters). A single misheard letter is uncorrectable.

If you fly with a regular wingman, both of you using '''strict callsigns''' — a word plus '''exactly two digits''' — lets SkyEye 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.

== How to talk to SkyEye ==

The request format is:

Focus YOUR_CALLSIGN (...) REQUEST_TYPE (...) (ARGS...) (...)

The <code>(...)</code> bits are filler — SkyEye ignores extra chatter around the keywords. "Focus, Mobius One, good morning. Alpha check bullseye" parses the same as "Focus, Mobius One, alpha check".

A few things to remember when speaking numbers:

* '''Compass bearings''' — say all three digits individually. "Zero Six Five", not "Six Five" or "Sixty-Five".
* '''All other numbers''' — say them normally. "Seventeen", not "One Seven".
* '''Do not use ICAO pronunciation.''' Say "Three", "Five", "Nine", '''not''' "Tree", "Fife", "Niner".
* '''Bullseye coordinates''' — leave a slight pause between range and altitude. If the bot struggles, insert "at" or "altitude": "Bullseye Zero Six Five, Ninety-Nine, at Twelve Thousand".

General tips:

* Think about what you want to say before you key the mic.
* Speak at a measured, conversational pace — too fast or too slow degrades recognition.
* If you misspeak, release PTT and start over rather than trying to correct yourself mid-transmission.
* Avoid chatter on SkyEye frequencies — it delays responses for everyone.

== Requests you can make ==

{| class="wikitable"
! Keyword !! What it does
|-
| <code>RADIO</code> / <code>COMM</code> || '''Radio check.''' Focus replies if it heard you, and tells you if you're not visible on scope.
|-
| <code>ALPHA</code> || '''Alpha check.''' Focus reports your current position in bullseye format. Useful for coarse INS verification in non-GPS aircraft.
|-
| <code>VECTOR</code> || '''Vector to a point.''' Defaults to bullseye; you can also ask for a vector to tanker (nearest compatible) or to a [[#Named locations|named location]] like Home Plate.
|-
| <code>BOGEY</code> || '''Bogey dope.''' Bearing, range, altitude, aspect to the nearest air-to-air threat. Optional filter: airplanes or helicopters.
|-
| <code>DECLARE</code> || '''IFF a contact you can see on your scope.''' Provide bullseye or BR, optionally altitude and track. Focus replies hostile / friendly / furball / clean.
|-
| <code>PICTURE</code> || '''Top three threats to the coalition.''' Long response (~20–30 s of channel time) — use sparingly.
|-
| <code>SNAPLOCK</code> || '''Fast IFF during a BVR timeline.''' Provide BRA (bearing, range, altitude) of a contact on your radar — Focus confirms what's there.
|-
| <code>SPIKED</code> / <code>STROBE</code> || '''Find the source of a radar spike.''' Provide bearing only; Focus looks in a 30° cone and reports the nearest likely source.
|}

For full examples of each request, see the [https://github.com/dharmab/skyeye/blob/main/docs/PLAYER.md upstream player guide].

=== Named locations ===

For VECTOR-TO requests, VRS has a small set of named locations you can use instead of coordinates. As of this writing the list covers blue-coalition start bases on Syria:

* '''Home Plate''' (also "Incirlik" / "Incirlik Air Base")
* '''Adana''' (also "Adana Sakirpasa")
* '''Akrotiri''' (also "RAF Akrotiri")

Example: "Focus, Eagle One One, vector to Home Plate".

The carrier group is deliberately not in the list — its position moves, and a static lat/lon would lie. The reserved names Bullseye and Tanker are always available as well.

== Things SkyEye says on its own ==

Some calls come from Focus without you asking:

* '''SUNRISE''' — broadcast when the controller comes online. Mid-mission SUNRISE usually means the bot crashed and restarted.
* '''PICTURE''' — the server may be configured to broadcast a PICTURE on a timer. Requesting one resets the timer.
* '''THREAT''' — broadcast when a hostile aircraft is near or approaching a friendly. BRAA format if it's relevant to one aircraft, bullseye if it's relevant to several. Helicopter THREATs only go to other rotary-wing aircraft.
* '''MERGED''' — broadcast when a fixed-wing hostile closes within 3 NM of you. Fixed-wing only; one MERGED per 30 seconds.
* '''FADED''' — broadcast when a hostile within weapons range disappears from the scope for at least 30 seconds. '''This is not a kill confirmation''' — DCS sometimes marks live aircraft as dead.

To receive THREAT and MERGED calls, your aircraft '''must''' be tuned to a SkyEye SRS frequency '''and''' your SRS name must match your DCS in-game name.

== Troubleshooting ==

'''Focus doesn't respond at all.''' Check that you said "Focus" (or "Anyface") at the start of your transmission — this is the most common mistake. Ask another player for a radio check to confirm you're audible.

'''Focus responds but says it can't see you.'''

* Confirm your in-game name matches the callsign you're giving.
* If you joined right after mission start, return to spectators, re-slot, or fully reconnect — joining too early can leave you invisible to Tacview.
* If you've been stationary for several minutes, move slightly. Tacview throttles position updates for non-moving objects.
* If your aircraft took even minor damage, re-slot — the game can mark it as destroyed even when it's flyable.

== Mindset ==

Focus is good at counting contacts and computing angles. It is '''not''' good at understanding tactics or strategy — that's still on you. Treat it as one source among many alongside your own radar, RWR, eyeballs, and human flight-mates. And remember: DCS sometimes marks live aircraft as dead, so a "FADED" or "clean" call is never a guarantee.

== See also ==

* [[Player Guide/Air Support|Air Support]] — F10 map-mark commands, including the AWACS marks (<code>awacs</code>, <code>focus</code>, <code>skyeye</code>, <code>overlord</code>) that spawn in-mission AWACS aircraft.
* [[FOCUS]] — earlier, longer FOCUS page (tagged XSAF-era) with more verbose examples for each request.
* [https://github.com/dharmab/skyeye dharmab/skyeye on GitHub] — source, releases, admin guide.
* [https://github.com/dharmab/skyeye/blob/main/docs/PLAYER.md Upstream player guide] — full request reference and examples.
* [https://github.com/dharmab/skyeye/blob/main/docs/PRIVACY.md Privacy statement] — how SkyEye uses voice and gameplay data.

Player Guide/SkyEye

2026-05-21T04:00:33Z

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

« [[Player Guide]]

'''SkyEye''' is an AI-powered Ground Controlled Intercept (GCI) bot that listens on SRS and talks back to you in plain English. It replaces the DCS in-game AWACS with a controller that understands proper [https://en.wikipedia.org/wiki/Brevity_code brevity] — PICTURE, BOGEY DOPE, DECLARE, SPIKED, and friends — and can monitor the battlespace for threats and announce them automatically.

On the VRS server the SkyEye GCI's callsign is '''Focus'''. You can also address it as '''Anyface''' — that's the SkyEye-wide alias and is always accepted.

SkyEye is open source and maintained by [https://github.com/dharmab dharmab]. The upstream player guide lives at [https://github.com/dharmab/skyeye/blob/main/docs/PLAYER.md github.com/dharmab/skyeye/docs/PLAYER.md].

__TOC__

== Quickstart ==

# Set your in-game name to a callsign in the format <code>Callsign 1 | yourname</code> — a 2–3 syllable English word, 1–3 digits, a pipe (<code>|</code>), then your normal name. Example: <code>Mobius 1 | Reaper</code>.
# Join the VRS server with [https://github.com/ciribob/DCS-SimpleRadioStandalone SRS] running. The SRS server is <code>server.victorromeosierra.com:10220</code>.
# Get airborne (you may not appear on the GCI scope while still on the ramp).
# Tune to a SkyEye SRS frequency — check the server briefing or ask in <code>#questions</code> on Discord for the current frequencies.
# Key your radio and say: <code>"Focus, Callsign 1, radio check"</code>. If you hear back, you're in business.
# Try: <code>"Focus, Callsign 1, picture"</code> for the top threats, or <code>"Focus, Callsign 1, bogey"</code> for the nearest threat to you.

== Picking a callsign ==

SkyEye recognises your callsign best when it follows the format above. A few rules of thumb:

* Use a '''2–3 syllable English word''' followed by '''1–3 digits''', then <code>|</code>, then your name.
* 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 — <code>WARDOG 14</code>, <code>Wardog 14</code>, <code>wardog14</code>, and <code>Wardog 1 4</code> are all the same.

Avoid:

* Names that sound like brevity words: alpha, radio, comm, bogey, picture, declare, snaplock, spiked, bullseye (e.g. "Spade" can be misheard as "SPIKE").
* Names that sound like numbers — "Knight" ≈ "Nine", "Fort" ≈ "Four".
* Hard-to-distinguish pairs — "Spare"/"Spear", "Jester"/"Gesture", "Witch"/"Which".
* Obscure or made-up words — "Razgriz", "Beskar" — the bot will try, but is less accurate.
* Very short callsigns (2–3 characters). A single misheard letter is uncorrectable.

If you fly with a regular wingman, both of you using '''strict callsigns''' — a word plus '''exactly two digits''' — lets SkyEye 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.

== How to talk to SkyEye ==

The request format is:

Focus YOUR_CALLSIGN (...) REQUEST_TYPE (...) (ARGS...) (...)

The <code>(...)</code> bits are filler — SkyEye ignores extra chatter around the keywords. "Focus, Mobius One, good morning. Alpha check bullseye" parses the same as "Focus, Mobius One, alpha check".

A few things to remember when speaking numbers:

* '''Compass bearings''' — say all three digits individually. "Zero Six Five", not "Six Five" or "Sixty-Five".
* '''All other numbers''' — say them normally. "Seventeen", not "One Seven".
* '''Do not use ICAO pronunciation.''' Say "Three", "Five", "Nine", '''not''' "Tree", "Fife", "Niner".
* '''Bullseye coordinates''' — leave a slight pause between range and altitude. If the bot struggles, insert "at" or "altitude": "Bullseye Zero Six Five, Ninety-Nine, at Twelve Thousand".

General tips:

* Think about what you want to say before you key the mic.
* Speak at a measured, conversational pace — too fast or too slow degrades recognition.
* If you misspeak, release PTT and start over rather than trying to correct yourself mid-transmission.
* Avoid chatter on SkyEye frequencies — it delays responses for everyone.

== Requests you can make ==

{| class="wikitable"
! Keyword !! What it does
|-
| <code>RADIO</code> / <code>COMM</code> || '''Radio check.''' Focus replies if it heard you, and tells you if you're not visible on scope.
|-
| <code>ALPHA</code> || '''Alpha check.''' Focus reports your current position in bullseye format. Useful for coarse INS verification in non-GPS aircraft.
|-
| <code>VECTOR</code> || '''Vector to a point.''' Defaults to bullseye; you can also ask for a vector to tanker (nearest compatible) or to a [[#Named locations|named location]] like Home Plate.
|-
| <code>BOGEY</code> || '''Bogey dope.''' Bearing, range, altitude, aspect to the nearest air-to-air threat. Optional filter: airplanes or helicopters.
|-
| <code>DECLARE</code> || '''IFF a contact you can see on your scope.''' Provide bullseye or BR, optionally altitude and track. Focus replies hostile / friendly / furball / clean.
|-
| <code>PICTURE</code> || '''Top three threats to the coalition.''' Long response (~20–30 s of channel time) — use sparingly.
|-
| <code>SNAPLOCK</code> || '''Fast IFF during a BVR timeline.''' Provide BRA (bearing, range, altitude) of a contact on your radar — Focus confirms what's there.
|-
| <code>SPIKED</code> / <code>STROBE</code> || '''Find the source of a radar spike.''' Provide bearing only; Focus looks in a 30° cone and reports the nearest likely source.
|}

For full examples of each request, see the [https://github.com/dharmab/skyeye/blob/main/docs/PLAYER.md upstream player guide].

=== Named locations ===

For VECTOR-TO requests, VRS has a small set of named locations you can use instead of coordinates. As of this writing the list covers blue-coalition start bases on Syria:

* '''Home Plate''' (also "Incirlik" / "Incirlik Air Base")
* '''Adana''' (also "Adana Sakirpasa")
* '''Akrotiri''' (also "RAF Akrotiri")

Example: "Focus, Eagle One One, vector to Home Plate".

The carrier group is deliberately not in the list — its position moves, and a static lat/lon would lie. The reserved names Bullseye and Tanker are always available as well.

== Things SkyEye says on its own ==

Some calls come from Focus without you asking:

* '''SUNRISE''' — broadcast when the controller comes online. Mid-mission SUNRISE usually means the bot crashed and restarted.
* '''PICTURE''' — the server may be configured to broadcast a PICTURE on a timer. Requesting one resets the timer.
* '''THREAT''' — broadcast when a hostile aircraft is near or approaching a friendly. BRAA format if it's relevant to one aircraft, bullseye if it's relevant to several. Helicopter THREATs only go to other rotary-wing aircraft.
* '''MERGED''' — broadcast when a fixed-wing hostile closes within 3 NM of you. Fixed-wing only; one MERGED per 30 seconds.
* '''FADED''' — broadcast when a hostile within weapons range disappears from the scope for at least 30 seconds. '''This is not a kill confirmation''' — DCS sometimes marks live aircraft as dead.

To receive THREAT and MERGED calls, your aircraft '''must''' be tuned to a SkyEye SRS frequency '''and''' your SRS name must match your DCS in-game name.

== Troubleshooting ==

'''Focus doesn't respond at all.''' Check that you said "Focus" (or "Anyface") at the start of your transmission — this is the most common mistake. Ask another player for a radio check to confirm you're audible.

'''Focus responds but says it can't see you.'''

* Confirm your in-game name matches the callsign you're giving.
* If you joined right after mission start, return to spectators, re-slot, or fully reconnect — joining too early can leave you invisible to Tacview.
* If you've been stationary for several minutes, move slightly. Tacview throttles position updates for non-moving objects.
* If your aircraft took even minor damage, re-slot — the game can mark it as destroyed even when it's flyable.

== Mindset ==

Focus is good at counting contacts and computing angles. It is '''not''' good at understanding tactics or strategy — that's still on you. Treat it as one source among many alongside your own radar, RWR, eyeballs, and human flight-mates. And remember: DCS sometimes marks live aircraft as dead, so a "FADED" or "clean" call is never a guarantee.

== See also ==

* [[Player Guide/Air Support|Air Support]] — F10 map-mark commands, including the AWACS marks (<code>awacs</code>, <code>focus</code>, <code>skyeye</code>, <code>overlord</code>) that spawn in-mission AWACS aircraft.
* [https://github.com/dharmab/skyeye dharmab/skyeye on GitHub] — source, releases, admin guide.
* [https://github.com/dharmab/skyeye/blob/main/docs/PLAYER.md Upstream player guide] — full request reference and examples.
* [https://github.com/dharmab/skyeye/blob/main/docs/PRIVACY.md Privacy statement] — how SkyEye uses voice and gameplay data.

Player Guide/In-Game Chat Commands

2026-05-21T04:00:31Z

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

« [[Player Guide]]

These are the player-facing '''in-game chat commands''' the VRS bot listens for. Type them in the DCS chat window (usually <code>Enter</code> opens chat) — the bot uses the <code>-</code> prefix, then the command name, then any arguments.

Example: type <code>-credits</code> in chat to see your credit balance.

'''Notation'''

* <code><arg></code> — required argument
* <code>[arg]</code> — optional argument
* Admin-only chat commands (kick, ban, restart, etc.) are role-gated and not documented here.

__TOC__

== Profile + help ==

{| class="wikitable"
! Command !! Description
|-
| <code>-help</code> || The help command
|-
| <code>-linkme</code> || link your user to Discord
|-
| <code>-911</code> || send an alert to admins (misuse will be punished!)
|}

== Server + mission info ==

{| class="wikitable"
! Command !! Description
|-
| <code>-timeleft</code> || Time to the next restart
|-
| <code>-atis</code> || display ATIS information
|-
| <code>-coalition</code> || displays your current coalition
|-
| <code>-password</code> (aliases: <code>-passwd</code>) || displays the coalition password
|}

== Credits ==

{| class="wikitable"
! Command !! Description
|-
| <code>-credits <server></code> || Shows your current credits
|-
| <code>-donate</code> || Donate credits to another player
|-
| <code>-tip</code> || Tip a GCI with points
|}

== Voting ==

{| class="wikitable"
! Command !! Description
|-
| <code>-vote</code> || start a voting or vote for a change
|}

== Acknowledgement + penalty ==

{| class="wikitable"
! Command !! Description
|-
| <code>-ack</code> || acknowledge a user message
|-
| <code>-forgive</code> || forgive another user for their infraction
|-
| <code>-penalty <server></code> || displays your penalty points
|}

Player Guide/Air Support

2026-05-21T04:00:29Z

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

« [[Player Guide]]

Air support is called in by placing "map marks" on the F10 map and inserting "command text" as the mark label.

How to place "CORE MARK" and "UTILITY MARK" commands on the F10 map:

#1. Place a "Map Marker" on the F10 map by clicking the "Mark Label" button.

[[File:F10-mark-label-button.jpg|480x275px]]

#2. Place the "circle map marker" at your desired location (see red arrow).

[[File:F10-circle-marker-place.jpg|480x317px]]

#3. "Type" one of the following commands into the text window of the map marker (green arrow). Specific commands are listed below.

[[File:F10-marker-text-window.jpg|480x317px]]

VRS "CORE MARK" commands: "Type" one of the following into the text window.

AWACS

: awacs awacs orbit awacs racetrack

: focus focus orbit focus racetrack

: '''skyeye overlord 
:

''The radio voice you'll hear from these AWACS is the [[Player Guide/SkyEye|SkyEye]] GCI bot, callsign Focus.''

Tanker (boom + MPRS pair)

: tanker tanker orbit tanker racetrack

: tankers tankers orbit tankers racetrack

: fuel gas aar

Boom Tanker (KC-135 / Texaco)

: aar boom aar boom orbit aar boom racetrack

: boom boom tanker texaco

MPRS Tanker (KC-135MPRS / Arco)

: aar mprs aar mprs orbit aar mprs racetrack mprs

: drogue basket probe arco

Specops Tanker (KC-130 / Shell)

: aar specops specops special ops

: hc130 c130 shell

[[File:KC-135-Texaco-boom.jpg|614x333px]]

''Boom contact -- KC-135 Texaco at Angels 20.''

[[File:F18-KC135-boom-refuel.jpg|600px|center|F/A-18C plugged into a KC-135 boom.]]

''F/A-18C topping off from a KC-135 — boom contact over the hills.''

When refueling, the tankers will be on station at these speeds, altitudes, frequencies, and TACANs:

{| class="wikitable"
|-
! '''KC-135 Boom-Texaco'''
! '''280 kts'''
! '''Angels 20'''
! '''Freq: 252.000'''
! '''TACAN: 40Y'''
|-
| '''KC-135 Boom-Reserve'''
| '''280 kts'''
| '''Angels 20'''
| '''Freq: 254.000'''
| '''TACAN: 42Y'''
|-
| '''KC-135 MPRS-Arco'''
| '''280 kts'''
| '''Angels 20'''
| '''Freq: 253.000'''
| '''TACAN: 41Y'''
|-
| '''KC-135 MPRS-Reserve'''
| '''280 kts'''
| '''Angels 20'''
| '''Freq: 255.000'''
| '''TACAN: 43Y'''
|-
| '''KC-130 Specops-Shell'''
| '''130 kts'''
| '''Angels 5'''
| '''Freq: 256.000'''
| '''TACAN: 44Y'''
|}

[[File:KC-135MPRS-Arco-drogue.jpg|480x260px]]

''Probe-and-drogue plug -- Arco over the hills.''

[[File:F-16-probe-drogue.jpg|600px|center|F-16CM holding the basket on a probe-and-drogue tanker.]]

''F-16CM holding the basket — probe-and-drogue contact.''

CAP

: cap f14 cap f-14 cap f 14

: cap f15 cap f-15 cap f 15

: cap f16 cap f-16 cap f 16

: cap f18 cap f-18 cap f 18

Drone Recon (MQ-9 / Reaper-1)

: drone recon recon drone scout drone reaper recon

Drone CAS (MQ-9 / Reaper-2)

: drone cas cas drone attack drone reaper cas

VRS "UTILITY MARK" commands: "Type" one of the following into the text window.

* flare

* smoke white

* smoke blue

* smoke red

* smoke green

* smoke orange

#4. To finalize the task, "minimize (-)" or "close (X)" the text box (see blue arrow on the screenshot above).

If correctly interpreted, you will receive a confirmation message in the upper right-hand corner of the F10 map screen, and your VRS direct player AI air support is on the way.

[[File:F10-marker-confirmation.jpg|614x333px]]

[[File:F18-F14-CAPs.jpg|614x324px]]

''Map markers can call multiple flights at once -- here, F-18 and F-14 CAPs simultaneously.''

What each support type does:

* AWACS: BLUE airborne picture anchor. Can be re-tasked by placing a new AWACS mark on the F10 map.

* Tankers (Boom / MPRS / Specops): Refueling anchors with racetrack or orbit behavior.

* CAP support (map-mark and menu-driven escorts): AI CAP flights. Map mark for area station; menu for personal escort.

* Drones: Per-player MQ-9 support; not shared with the coalition.

: drone recon -- 340 Cr + 65 intel. Callsign: Reaper-1, orbits at ~25,000 ft for area ISR.

: drone cas -- 680 Cr + 65 intel. Callsign: Reaper-2, same orbit profile, weapons-capable.

* Only one drone active at a time. A second request while one is up is denied at no cost.

* 30-minute personal cooldown starts only after a successful dispatch.

* Denied requests (threat zone, no intel, another active drone) do not start a cooldown and refund all resources.

* Drones use the same threat-avoidance logic as AWACS/tankers; move the mark farther from threat belts if denied.

Important "campaign support behavior" players should expect:

* Safety logic: If the marker is placed in an "unsafe" location, you get a chat message and the requested asset finds the nearest safe location on its own.

* Auto-relief: Low-fuel support assets RTB and can auto-replace to hold station continuity.

* Tanker scaling: If requests are far apart, additional tanker slot(s) can spawn.

* Continuous adaptation: Campaign assets can reposition if the threat picture changes.

Practical air support tips:

* Place support marks behind your current BLUE engagement edge, not on it.

* Racetrack for sustained lane support; orbit for compact local support.

* As the frontline moves, move your campaign assets forward or back to match.

* Think of tankers and AWACS as campaign assets: defend the airspace around them.

Player Guide

2026-05-21T04:00:29Z

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

[[File:VRS-Logo.png|256x256px|center|VRS — Victor Romeo Sierra]]

Welcome to our Victor Romeo Sierra (VRS) community -- a laid-back group of virtual pilots brought together by a shared passion for flying, teamwork, and having a good time in the skies. Built around Digital Combat Simulator, our group is focused on creating a relaxed, welcoming environment where both experienced aviators and new recruits can enjoy everything from casual flights to coordinated missions without the pressure of hardcore mil-sim expectations. Whether you're here to learn, fly, or simply unwind after a long day, there's always a seat on the flight line for you at VRS!

Please take time to review the VRS Player Guide to help familiarize yourself with VRS, our server, and other important information. If you have any questions feel free to post in the #questions Discord channel.

This guide explains how to play the VRS mission from the BLUE side.

It is intentionally light on REDFOR internals and focused on what players can do.

== Sections ==

* [[Player Guide/Mission Mindset|Mission Mindset]] — Three parallel loops that shape every flight.
* [[Player Guide/Air Support|Air Support]] — CORE / UTILITY MARK system: how to call AWACS, tankers, CAP, escorts via F10 map marks.
* [[Player Guide/SkyEye|SkyEye]] — Talking to the AI GCI bot over SRS: callsign format, requests, brevity.
* [[Player Guide/Personal Escorts|Personal Escorts]] — Credit-funded personal escorts.
* [[Player Guide/Intel Reporting|Intel Reporting]] — Reporting RED activity via the Personal Menu.
* [[Player Guide/CTLD Logistics|CTLD Logistics]] — Building factories, Fat Cows, and force-multiplier deployment.
* [[Player Guide/CSAR and Salvage|CSAR and Salvage]] — Combat Search and Rescue, SAR, and battlefield Salvage.
* [[Player Guide/Credits and Progression|Credits and Progression]] — Credit economy + intel progression.
* [[Player Guide/Red Behavior|Red Behavior]] — How REDFOR adapts to BLUE pressure.
* [[Player Guide/Reporting a Bug|Reporting a Bug]] — How to file bug reports.
* [[Player Guide/Team Play|Team Play]] — Patterns that work for coordinated coalition play.
* [[Player Guide/Quick Command Card|Quick Command Card]] — One-screen reference card for all CORE / UTILITY MARK commands.
* [[Player Guide/Discord Commands|Discord Commands]] — Player-facing slash commands the VRS bot exposes in Discord.
* [[Player Guide/In-Game Chat Commands|In-Game Chat Commands]] — <code>-</code> prefix commands the bot listens for in the DCS chat window.

Player Guide/In-Game Chat Commands

2026-05-20T04:38:57Z

Shifty:

« [[Player Guide]]

These are the player-facing '''in-game chat commands''' the VRS bot listens for. Type them in the DCS chat window (usually <code>Shift Tab</code> opens chat)

<big>'''The bot uses the <code>-</code> prefix, then the command name, then any arguments.'''</big>

Example: type <code>-credits</code> in chat to see your credit balance.

'''Notation'''

* <code><arg></code> — required argument
* <code>[arg]</code> — optional argument
* Admin-only chat commands (kick, ban, restart, etc.) are role-gated and not documented here.

__TOC__

== Profile + help ==

{| class="wikitable"
! Command !! Description
|-
| <code>-help</code> || The help command
|-
| <code>-linkme</code> || link your user to Discord
|-
| <code>-911</code> || send an alert to admins (misuse will be punished!)
|}

== Server + mission info ==

{| class="wikitable"
! Command !! Description
|-
| <code>-timeleft</code> || Time to the next restart
|-
| <code>-atis</code> || display ATIS information
|-
| <code>-password</code> (aliases: <code>-passwd</code>) || displays the coalition password
|}

== Credits ==

{| class="wikitable"
! Command !! Description
|-
| <code>-credits <server></code> || Shows your current credits
|-
| <code>-donate</code> || Donate credits to another player
|-
| <code>-tip</code> || Tip a GCI with points
|}

== Voting ==

{| class="wikitable"
! Command !! Description
|-
| <code>-vote restart</code> || start a voting session to restart the mission
|}

== Acknowledgement + penalty ==

{| class="wikitable"
! Command !! Description
|-
| <code>-ack</code> || acknowledge a user message
|-
| <code>-forgive</code> || forgive another user for their infraction
|-
| <code>-penalty <server></code> || displays your penalty points
|}

Player Guide/In-Game Chat Commands

2026-05-20T04:36:39Z

Shifty:

« [[Player Guide]]

These are the player-facing '''in-game chat commands''' the VRS bot listens for. Type them in the DCS chat window (usually <code>Shift Tab</code> opens chat)

''<big>The bot uses the <code>-</code> prefix, then the command name, then any arguments.</big>''

Example: type <code>-credits</code> in chat to see your credit balance.

'''Notation'''

* <code><arg></code> — required argument
* <code>[arg]</code> — optional argument
* Admin-only chat commands (kick, ban, restart, etc.) are role-gated and not documented here.

__TOC__

== Profile + help ==

{| class="wikitable"
! Command !! Description
|-
| <code>-help</code> || The help command
|-
| <code>-linkme</code> || link your user to Discord
|-
| <code>-911</code> || send an alert to admins (misuse will be punished!)
|}

== Server + mission info ==

{| class="wikitable"
! Command !! Description
|-
| <code>-timeleft</code> || Time to the next restart
|-
| <code>-atis</code> || display ATIS information
|-
| <code>-password</code> (aliases: <code>-passwd</code>) || displays the coalition password
|}

== Credits ==

{| class="wikitable"
! Command !! Description
|-
| <code>-credits <server></code> || Shows your current credits
|-
| <code>-donate</code> || Donate credits to another player
|-
| <code>-tip</code> || Tip a GCI with points
|}

== Voting ==

{| class="wikitable"
! Command !! Description
|-
| <code>-vote</code> || start a voting or vote for a change
|}

== Acknowledgement + penalty ==

{| class="wikitable"
! Command !! Description
|-
| <code>-ack</code> || acknowledge a user message
|-
| <code>-forgive</code> || forgive another user for their infraction
|-
| <code>-penalty <server></code> || displays your penalty points
|}

Player Guide/In-Game Chat Commands

2026-05-20T04:35:37Z

Shifty:

« [[Player Guide]]

These are the player-facing '''in-game chat commands''' the VRS bot listens for. Type them in the DCS chat window (usually <code>Shift Tab</code> opens chat) — the bot uses the <code>-</code> prefix, then the command name, then any arguments.

Example: type <code>-credits</code> in chat to see your credit balance.

'''Notation'''

* <code><arg></code> — required argument
* <code>[arg]</code> — optional argument
* Admin-only chat commands (kick, ban, restart, etc.) are role-gated and not documented here.

__TOC__

== Profile + help ==

{| class="wikitable"
! Command !! Description
|-
| <code>-help</code> || The help command
|-
| <code>-linkme</code> || link your user to Discord
|-
| <code>-911</code> || send an alert to admins (misuse will be punished!)
|}

== Server + mission info ==

{| class="wikitable"
! Command !! Description
|-
| <code>-timeleft</code> || Time to the next restart
|-
| <code>-atis</code> || display ATIS information
|-
| <code>-password</code> (aliases: <code>-passwd</code>) || displays the coalition password
|}

== Credits ==

{| class="wikitable"
! Command !! Description
|-
| <code>-credits <server></code> || Shows your current credits
|-
| <code>-donate</code> || Donate credits to another player
|-
| <code>-tip</code> || Tip a GCI with points
|}

== Voting ==

{| class="wikitable"
! Command !! Description
|-
| <code>-vote</code> || start a voting or vote for a change
|}

== Acknowledgement + penalty ==

{| class="wikitable"
! Command !! Description
|-
| <code>-ack</code> || acknowledge a user message
|-
| <code>-forgive</code> || forgive another user for their infraction
|-
| <code>-penalty <server></code> || displays your penalty points
|}

Player Guide/In-Game Chat Commands

2026-05-20T04:32:03Z

Shifty:

« [[Player Guide]]

These are the player-facing '''in-game chat commands''' the VRS bot listens for. Type them in the DCS chat window (usually <code>Shift Tab</code> opens chat) — the bot uses the <code>-</code> prefix, then the command name, then any arguments.

Example: type <code>-credits</code> in chat to see your credit balance.

'''Notation'''

* <code><arg></code> — required argument
* <code>[arg]</code> — optional argument
* Admin-only chat commands (kick, ban, restart, etc.) are role-gated and not documented here.

__TOC__

== Profile + help ==

{| class="wikitable"
! Command !! Description
|-
| <code>-help</code> || The help command
|-
| <code>-linkme</code> || link your user to Discord
|-
| <code>-911</code> || send an alert to admins (misuse will be punished!)
|}

== Server + mission info ==

{| class="wikitable"
! Command !! Description
|-
| <code>-timeleft</code> || Time to the next restart
|-
| <code>-atis</code> || display ATIS information
|-
| <code>-coalition</code> || displays your current coalition
|-
| <code>-password</code> (aliases: <code>-passwd</code>) || displays the coalition password
|}

== Credits ==

{| class="wikitable"
! Command !! Description
|-
| <code>-credits <server></code> || Shows your current credits
|-
| <code>-donate</code> || Donate credits to another player
|-
| <code>-tip</code> || Tip a GCI with points
|}

== Voting ==

{| class="wikitable"
! Command !! Description
|-
| <code>-vote</code> || start a voting or vote for a change
|}

== Acknowledgement + penalty ==

{| class="wikitable"
! Command !! Description
|-
| <code>-ack</code> || acknowledge a user message
|-
| <code>-forgive</code> || forgive another user for their infraction
|-
| <code>-penalty <server></code> || displays your penalty points
|}

Player Guide/In-Game Chat Commands

2026-05-20T04:24:48Z

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

Player Guide/Discord Commands

2026-05-20T04:24:48Z

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

« [[Player Guide]]

These are the player-facing '''Discord slash commands''' the VRS bot exposes. Type <code>/</code> in a VRS Discord channel to see the autocompleter; only commands you have permission to run will appear.

'''Notation'''

* <code><arg></code> — required argument
* <code>[arg]</code> — optional argument
* Admin-only commands (server management, bans, mission control, etc.) are not documented here. Ask in <code>#questions</code> if you need one.

__TOC__

== Linking your account ==

{| class="wikitable"
! Command !! Description
|-
| <code>/linkme</code> || Link your DCS and Discord user
|-
| <code>/find <name></code> || Find a player by name
|-
| <code>/info <member></code> || Shows player information
|}

== Player + squadron stats ==

{| class="wikitable"
! Command !! Description
|-
| <code>/statistics [period] [user]</code> || Shows player statistics
|-
| <code>/highscore [server] [period] [limit]</code> || Displays the top players of your server(s)
|-
| <code>/squadron info <squadron_id></code> || Info about a squadron
|-
| <code>/squadron join <squadron_id></code> || Join a squadron
|-
| <code>/squadron leave <squadron_id></code> || Leave a squadron
|-
| <code>/squadron list <squadron_id></code> || List members of a squadron
|-
| <code>/squadron credits <squadron_id></code> || Credit points of a squadron
|-
| <code>/squadron donate <squadron_id> <points> [server]</code> || Donate credit points to a squadron
|}

== Mission statistics ==

{| class="wikitable"
! Command !! Description
|-
| <code>/missionstats <server></code> || Display Mission Statistics
|-
| <code>/sorties [user] [period]</code> || Display statistics about sorties
|-
| <code>/modulestats [user] [module] [period]</code> || Module statistics
|-
| <code>/refuelings [user] [period]</code> || Refueling statistics
|-
| <code>/nemesis [user] [period]</code> || Find who killed you most
|-
| <code>/antagonist [user] [period]</code> || Find who you've killed the most
|-
| <code>/history [user] [start] [end]</code> || Event History
|}

== Credits ==

{| class="wikitable"
! Command !! Description
|-
| <code>/credits info</code> || Shows your current credits
|-
| <code>/credits donate <to> <donation></code> || Donate credits to another member
|}

== CSAR ==

{| class="wikitable"
! Command !! Description
|-
| <code>/csar stats [user]</code> || Shows CSAR rescue stats
|-
| <code>/csar lives [user] [server]</code> || Shows your slot lives for airframes with active CSARs
|}

== Voting ==

{| class="wikitable"
! Command !! Description
|-
| <code>/vote list</code> || Lists the current votes
|-
| <code>/vote create <server> <what></code> || Create a vote
|-
| <code>/vote cancel <server></code> || Cancel a vote
|}

== Mission + server info ==

{| class="wikitable"
! Command !! Description
|-
| <code>/mission info <server></code> || Info about the running mission
|-
| <code>/mission briefing <server></code> || Shows briefing of the active mission
|-
| <code>/server timeleft <server></code> || Time until server / mission restart
|-
| <code>/serverlist [search]</code> || List registered DCS servers
|-
| <code>/campaign list [active]</code> || Lists all (active) campaigns
|-
| <code>/campaign info <campaign></code> || Campaign info
|}

== Tacview ==

{| class="wikitable"
! Command !! Description
|-
| <code>/tacview download <server> <file></code> || Download a Tacview
|}

== Help ==

{| class="wikitable"
! Command !! Description
|-
| <code>/help <cmd></code> || The help command
|-
| <code>/doc <what> [fmt] [role] [channel]</code> || Generate Documentation
|}

Player Guide

2026-05-20T04:24:45Z

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

[[File:VRS-Logo.png|256x256px|center|VRS — Victor Romeo Sierra]]

Welcome to our Victor Romeo Sierra (VRS) community -- a laid-back group of virtual pilots brought together by a shared passion for flying, teamwork, and having a good time in the skies. Built around Digital Combat Simulator, our group is focused on creating a relaxed, welcoming environment where both experienced aviators and new recruits can enjoy everything from casual flights to coordinated missions without the pressure of hardcore mil-sim expectations. Whether you're here to learn, fly, or simply unwind after a long day, there's always a seat on the flight line for you at VRS!

Please take time to review the VRS Player Guide to help familiarize yourself with VRS, our server, and other important information. If you have any questions feel free to post in the #questions Discord channel.

This guide explains how to play the VRS mission from the BLUE side.

It is intentionally light on REDFOR internals and focused on what players can do.

== Sections ==

* [[Player Guide/Mission Mindset|Mission Mindset]] — Three parallel loops that shape every flight.
* [[Player Guide/Air Support|Air Support]] — CORE / UTILITY MARK system: how to call AWACS, tankers, CAP, escorts via F10 map marks.
* [[Player Guide/Personal Escorts|Personal Escorts]] — Credit-funded personal escorts.
* [[Player Guide/Intel Reporting|Intel Reporting]] — Reporting RED activity via the Personal Menu.
* [[Player Guide/CTLD Logistics|CTLD Logistics]] — Building factories, Fat Cows, and force-multiplier deployment.
* [[Player Guide/CSAR and Salvage|CSAR and Salvage]] — Combat Search and Rescue, SAR, and battlefield Salvage.
* [[Player Guide/Credits and Progression|Credits and Progression]] — Credit economy + intel progression.
* [[Player Guide/Red Behavior|Red Behavior]] — How REDFOR adapts to BLUE pressure.
* [[Player Guide/Reporting a Bug|Reporting a Bug]] — How to file bug reports.
* [[Player Guide/Team Play|Team Play]] — Patterns that work for coordinated coalition play.
* [[Player Guide/Quick Command Card|Quick Command Card]] — One-screen reference card for all CORE / UTILITY MARK commands.
* [[Player Guide/Discord Commands|Discord Commands]] — Player-facing slash commands the VRS bot exposes in Discord.
* [[Player Guide/In-Game Chat Commands|In-Game Chat Commands]] — <code>-</code> prefix commands the bot listens for in the DCS chat window.

Main Page

2026-05-20T04:24:45Z

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

'''<big>Welcome to VRS!</big>'''

Victor Romeo Sierra is a set of DCS Servers. They are currently:

Victor Romeo Sierra - Dynamic AI Driven Campaign -- Our main server with an AI REDFOR and an AI AWACS System

Victor Romeo Sierra [Olympus] - Our server running the Olympus game master software (mostly used for testing)

VRSWW2 - Our WWII warbird server.

== Player Guide ==

[[File:VRS-Logo.png|128x128px|right|link=Player Guide]]
The current player-facing documentation lives in the '''[[Player Guide]]''' — mission mindset, BLUE air support (CORE / UTILITY MARK commands), CTLD logistics, CSAR & salvage, and more.

== Getting started ==
* '''[[Player Guide]]''' — current VRS gameplay reference (start here)
* [[FAQ|VRS FAQ]] (XSAF-era)
* [[New player guide|New Player Guide]] (XSAF-era)
* [[FOCUS|FOCUS User Guide]] (XSAF-era)
* [[Logistics]] (XSAF-era)
* [[CSAR]] (XSAF-era)
* [[Salvage]] (XSAF-era)
* [https://map.victorromeosierra.com/servers/VRS Live Map of VRS Dynamic AI Server]
* [https://stats.victorromeosierra.com/ Player Stats Page]
* [https://discord.gg/victorromeosierra Discord]
* [https://www.patreon.com/c/VictorRomeoSierra/ Patreon]