Player-controlled AWACS

From UOAF Codex
Jump to navigation Jump to search
AWACS in flight

Learning objectives

  1. Configure IVC for human-controlled AWACS
  2. Install Online Squadron Collection
  3. Understand how to use BMS labels (TBD)
  4. Understand how to give BRAA and Bullseye calls
  5. Understand key brevity


Example Radio Chatter with Human GCI/AWACS "Showtime"
Speaker Message Notes
Falcon 1-1 Showtime, Falcon 1: Declare contact bullseye 315/89 12000. Falcon 1 uses his flight callsign in this example. This is the callsign Showtime will reply to. This may be confusing if other members of Falcon are trying to declare. He should probably use his own callsign, which is Falcon 1-1.
Showtime Falcon 1, Showtime: Contact is hostile. 2 ship. Showtime probably doesn't know exactly what type of aircraft these are.
Gamble 2-1 Showtime, Gamble 2-1: Bogey Dope. Gamble 2-1 MUST use his ship callsign and not his flight callsign, since the reply is dependent upon his location.
Showtime Gamble 2-1, Showtime: nearest threat is one group bullseye 215/13; 25,000; hot; hostile; MiG-29 singleton Showtime knows the type of aircraft.
Viper 1-3 Showtime, Viper 1-3, Bogey Dope. This is equivalent to "request vector to (nearest) target."
Showtime Viper 1-3, Showtime: Say ownship bullseye. Showtime is most likely unable to see Viper 1-3 on scope. This is because BMS only shows one single ship in the 2D screen to represent an entire flight. If Showtime is using OSC F4AWACS, then Viper 1-3's chances of being seen are increased dramatically by running the OSC Validator.
  • All pilots must configure IVC in order to hear the human AWACS/GCI.
  • If using the Online Squadron Collection (OSC):
    • All pilots flying in the mission need to run the OSC Validator during the mission.
    • The human AWACS/GCI needs to run the OSC AISpy and OSC F4AWACS.
    • The server flight needs to run the OSC SQServer.
  • The preferred channel for talking with human AWACS/GCI will be briefed.

Configuring IVC

  1. Locate the relevant IVC ini file.
    1. Default location for 64-bit installations is Falcon BMS 4.34\Bin\x64\IVC\IVC Client.ini
    2. Default location for 32-bit installations is Falcon BMS 4.34\Bin\x86\IVC\IVC Client.ini
  2. Open the relevant IVC ini file, and then apply whichever changes apply to the situation:

Changes ONLY for Pilots

  1. Find the following line:
    #outsiders = none
  2. Change the above to this:
    outsiders = all

This ensures that pilots can hear the human AWACS/GCI no matter where he's seated in the 2D World. If a user has outsiders=none, then that pilot will have transmissions from human AWACS/GCI affected by distance and terrain.

Note: Please note that the beginning of the line should lack the '#'. This is because '#' tells IVC to ignore the rest of the line and treat it as a comment.

Changes ONLY for GCI/AWACS

Human GCI/AWACS must manually configure IVC via the IVC Client, including setting the UHF frequency to that which will be used to communicate with the flights he will support.

If he is using BMS to connect to the IVC server, then after connecting to the hosted TE/Campaign, he should do the following:

  1. Find the open IVC client instance.
  2. Click on Force Local Control. This will probably disconnect the IVC Client from the IVC Server.
  3. Click on Connect.
  4. If participating in a planned event that require pre-flight IVC checks, assign the appropriate frequencies:
    1. Enter "339750" (without the quotes) for UHF and click on Change Frequency. (Click Change Frequency even if the frequency is already correctly entered.)
    2. Enter "1234" (without the quotes) for VHF and click on Change Frequency. (Click Change Frequency even if the frequency is already correctly entered.)
  5. Write down the necessary frequencies associated with the mission. (For example, if human GCI/AWACS is supporting only one package, the UHF 6 frequency for that package should probably be written down or stored within OSC F4AWACS.)
  6. Upon everyone committing to flight, switch to the mission frequency upon which human GCI/AWACS should be waiting to receive requests or check-ins.

Online Squadron Collection


  1. Download OSC v2.0.2:
  2. Install it.
  3. Run the OSC MONSTER UPDATER program. It should update OSC to v2.0.6.



  1. Run OSC SQServer.


  1. Run OSC Validator at mission time.
  2. Enter your in-game callsign in capital letters (ie. GAMBLE 11)
  3. Connect to the server.


  1. Run OSC AISpy.
  2. Connect OSC AISpy to the server.
  3. Run OSC F4AWACS.
  4. Perform any initial OSC F4AWACS startup procedures as necessary.
  5. Connect OSC F4AWACS to the server.
  6. Proceed as desired to customize the environment according to the mission.


Startup Procedure

F4AWACS is a very complex program, however, there are certain steps that should be done to get started before a mission.

  1. A mission file and at least one corresponding INI file should be retrieved from the mission.
  2. Load the proper theater in F4AWACS. If the theater in question isn't KTO, it will need to be imported it.
  3. Click Tools->Falcon Tools->Get bullseye from tac/cam/trn. Load the mission file mentioned above.
  4. Click Tools->Falcon Tools->Import Areas from Falcon INI files. Load the INI file mentioned above.
  5. Connect to the SQServer instance for this mission.

Known Bugs/Issues

  1. Sometimes the "Areas" box disappears and becomes unavailable. It can be retrieved by right-clicking on the map, and clicking "Add New Icon Area" and then canceling.
  2. Sometimes the "Bullseye" menu disappears.


These SOPs are the general guidelines for how human GCI/AWACS will be used.

Note: Deviations from SOPs for a mission should be explicitly mentioned in the mission briefing.


The following should be explicitly briefed:

  • GCI/AWACS callsign. It may be preferable to avoid callsigns such as "Magic" because there may be existing flights with these callsigns. Possible callsigns that do not appear to be in BMS are as follows:
    • Bandsaw
    • Baron
    • Focus
    • Showtime
    • Thumper
    • Overlord


  • Human GCI/AWACS should speak
    • as infrequently as possible; and
    • as little as possible.
  • Unlike with AI AWACS, communication between pilots and GCI/AWACS can jam comms and marks a distinct disadvantage.
  • Human GCI/AWACS should provide some advantages over AI GCI/AWACS in that the human can provide more clarity to a situation than the AI can.


  • Package Flights are led by the Package Lead, unless explicitly directed otherwise.
  • Package Flights check-in with GCI/AWACS.
  • GCI/AWACS can hold and relay information for the package when Flight Leads are unavailable (perhaps due to terrain occlusion).


Check-In Example with Human GCI/AWACS "Showtime"
Order Flight Speaker Message
1 Falcon 1 Falcon 1-1 "Showtime, Falcon 1, check-in. 4 good ships."
Showtime "Falcon 1, copy check-in. Awaiting Package Lead."
Falcon 1-1 "Falcon 1"
2 Gamble 2 Gamble 2-1 "Showtime, Gamble 2, check-in. 4 good ships."
Showtime "Gamble 2, Showtime, copy check-in. Awaiting Package Lead."
Gamble 2 "Gamble 2"
3 Hawkeye 1

(Package Lead)

Hawkeye 1-1 "Showtime, Hawkeye 1, check-in. 2 good ships."
Showtime "Hawkeye 1, Showtime, copy check-in. Previous check-ins Falcon 1 4-ship, Gamble 2, 4-ship."
Hawkeye 1 "Hawkeye 1"
4 Viper 1 Gamble 2-1 "Showtime, Viper 1, check-in. 4 good ships."
Showtime "Viper 1, Showtime, copy check-in. Package Lead available on this frequency."
Viper 1 "Viper 1."
  1. Flight Leads check in with GCI/AWACS with their flight callsign and the number of good ships in the flight available for tasking.
  2. GCI/AWACS acknowledges the check-in:
    1. For Flight Leads that are not Package Lead, GCI/AWACS informs them if Package Lead has already checked in or not.
    2. When Package Lead checks in, he informs how many Flights in this package already checked in and how many good ships were reported in each.
  3. While any other Flights tuning into Tactical (ie. UHF 6) should continue to check in with GCI/AWACS, the Package Lead may direct the package at any time for those that are available.

Note: In the event of an emergency, such as their flight being intercepted, GCI/AWACS may skip the check-in procedure and warn them they are being intercepted.


  • GCI/AWACS will NOT continuously guide onto targets unless asked to be updated by a flight.
  • Updates will cease if picture becomes vast and busy or if flight or package lead calls "Judy."
  • GCI/AWACS may warn about bandits intercepting friendly aircraft within the "alert range." Unless otherwise briefed, this range is 80nm. This warning is not guaranteed to happen, and will be less likely to happen when the air picture is busy.



Below is an incomplete list of brevity that may be communicated between pilots and human GCI/AWACS:

  • "Check-in"
  • "Alfa Check"
  • "Judy."
  • "Request Picture."
  • "Declare <Bullseye>"
  • "Request vector to tanker/base/(nearest) target/alternate."
  • "Bogey Dope"
  • "Request relief."
  • "Threat."

Bullseye vs BRAA

Call Formats
BRAA Bullseye
Bearing, Range, Altitude, and Aspect.
  • Bullseye is an arbitrary location on the map, usually somewhat close to the AO of a mission.
  • In BMS, there is only one official bullseye. In real life, the bullseye would have a name.
When using BRAA, GCI/AWACS is giving locations relative to the jet to whom it is speaking.
  • Like BRAA, a bullseye reference can use bearing, range, altitude, and aspect.
  • Unlike BRAA, GCI/AWACS is giving locations relative to bullseye, although the aspect is still relative to the jet to whom GCI/AWACS is speaking.
Example reply from GCI/AWACS using BRAA:
  • "Viper 2-1, Showtime: Nearest threat BRAA 287/24. 12000. Hot."
  • This means that Viper 2-1 has a hostile 24nm away at 12000ft flying directly at him. If Viper 2-1 is flying 287, he is flying a direct course to intercept.
Example reply from GCI/AWACS using bullseye:
  • "Warhawk 3-3, Showtime: Nearest threat Bullseye 135/12. 25000. Dragging."
  • This means that Warhawk 3-3's nearest threat is 12nm away from bullseye. If one were to be directly on bullseye, he would be facing the threat is he turned to heading 135.
  • This does NOT mean that Warhawk 3-3 should necessarily turn to heading 135 if he wants to face the threat, nor does it necessarily mean that Warhawk 3-3 is 12nm away from the threat. This is only true if Warhawk 3-3 is actually on bullseye, which he is probably not. Warhawk 3-3 must determine:
    1. where the threat is from bullseye;
    2. where he himself is from bullseye; and then based on both pieces of information
    3. where he and the threat are in relation to each other.
The BRAA format is typically used in BMS when the nearest threat is within 25nm of the friendly aircraft querying AWACS. Bullseye is stored in STPT 25 of the Viper. A pilot can change STPT 25 before takeoff or in the air. This effectively moves the bullseye in his ship's computer, which can be used to correct certain rare instances where bullseye fails to load in the pilot's DTC correctly. This should NOT be done unless prebriefed or if an alfa check has failed.


For either bullseye or BRAA references, the location should be read digit by digit while the range should be read as a single number.


  • Bullseye 180/56. 12000ft: "Bullseye One eight zero." <pause> "Fifty six" <pause> "Twelve thousand."
  • BRAA 95/21. 25000ft: "BRAA Nine five." <pause> "Twenty-one" <pause> "Twenty five thousand."