User avatar
Matthew Kramer
Deputy Air Traffic Manager
Posts: 192
Joined: Thu May 17, 2007 11:56 am
VATSIM CID: 845421
Location: Los Angeles

Using the Audio for VATSIM Standalone Client

Thu Oct 03, 2019 12:26 pm

ZLA pals, I've written a quick tutorial for you to get familiar with using the new standalone AFV client with VRC, vSTARS, and vERAM. Eventually the new codec will be integrated fully into those clients, but in the meantime, you can follow the steps below to get started.

The full AFV Manual can be found here.

Too Long; Won't Read:
  • Open your radar client
  • Set vis centers (VRC ONLY)
  • Connect to network
  • Prime frequency - PRIME ONLY, DO NOT CONFIGURE OTHER AUDIO OPTIONS
  • Open the AFV Standalone Client
  • Connect
  • Optionally, click "XC" to enable cross coupling for large coverage areas

How Do I Configure My Audio?
Step 0: Check Your Settings
It's important you configure the settings panel before connecting to the network. It should look familiar to you as it's quite similar to the existing settings panels in our clients. You can find details on the settings in the AFV Manual section 3.1.3.
Image


Step 1: Connect to Network
The easy and familiar part, open VRC/vSTARS/vEARM normally and set your vis centers if required. Connect to the network as you would, and then Prime, and only Prime, your frequency:
VRC
Image
vSTARS
Image
vERAM
Image

Step 2: Open AFV and Connect
Let's say I'm logging on as LAX_CTR. We have preconfigured the frequency panel for the standalone client, and because it detects a configured position, it will automatically set your transmission and receive antenna sites.
Image

Step 3: Cross Couple
Large facilities, like SOCAL or LA Center, should depress the "XC" Button. The new codec takes range into account. An airplane on the ground and LAX will not hear an airplane on the ground as LAS, even if they are both on 125.80 because they are too far away from each other. This is realistic and expected. Because VATSIM is what it is, you can cross-couple your frequency so airplanes far away from each other can still hear one another, and thus you won't be subject to two airplanes transmitting at the same time.
Image


How Do I Relieve Another Controller?
Step 1: Follow the previous steps
Use your relief (e.g. LAX_1_CTR; LAX_1_TWR) callsign instead, but follow all the same steps to connect. As the position is "not configured," AFV will place a transmitter at your vis center.
Image

Step 2: Add a Callsign
At the bottom of the frequency section, called the VCCS, there is a small + button. Click it and add the callsign you will be monitoring or assuming. For example, SCT_1_APP should type, "SCT_APP." LAX_M_TWR should type "LAX_TWR."
Image

Step 3: Cross Couple
Deselect the reliever/instructor callsign and select TX/RX and XC on the position you are monitoring or taking over for.
Image

Now in video format:
https://www.youtube.com/watch?v=Ry8aBVbTdrM

Question/Comments/Concerns?

User avatar
Matthew Kramer
Deputy Air Traffic Manager
Posts: 192
Joined: Thu May 17, 2007 11:56 am
VATSIM CID: 845421
Location: Los Angeles

Re: Using the Audio for VATSIM Standalone Client

Sat Oct 12, 2019 11:17 am

Just a note: when you're taking over for a position, the default will be for the client to use your visibility center as transceivers. You MUST add the default callsign of the position you're assuming, and then TX/RX (and potentially XC) on THAT callsign, otherwise pilots may have trouble hearing you.

Chris Carstens
Facility Engineer
Posts: 98
Joined: Tue Aug 22, 2017 6:00 pm
VATSIM CID: 935697

Re: Using the Audio for VATSIM Standalone Client

Mon Oct 14, 2019 8:21 am

Just another note: the above is also (mostly) true for observers wishing to listen in. You MUST add the default callsign of the position you're observing, and then RX on THAT callsign, otherwise you may not hear anything.

By default callsign, we mean that if you see someone with a position relief callsign (e.g. LAX_1_CTR) or a solo/student callsign (e.g. SAN_S_TWR, SCT_S_APP), you should add the position without the _1_ (LAX_CTR) or _S_ (SAN_TWR, SCT_APP).

Note that there are a few event callsigns with an _S_ in them (e.g. LAX_S_TWR, LAX_S_DEP, LAS_S_DEP, etc.). If you're in doubt, just ask the controller you're trying to listen to.
Chris Carstens
ZLA Facility Engineer

Return to “ZLA Main Forum”

Who is online

Users browsing this forum: No registered users and 1 guest