Difference between revisions of "Player-controlled AWACS"

From UOAF Codex
Jump to navigation Jump to search
Line 2: Line 2:
  
 
=Learning objectives=
 
=Learning objectives=
 +
 
#Configure IVC for human-controlled AWACS
 
#Configure IVC for human-controlled AWACS
 
#Install Online Squadron Collection
 
#Install Online Squadron Collection
Line 10: Line 11:
 
=Basics=
 
=Basics=
  
−
* All pilots must configure IVC in order to hear the human AWACS/GCI.
+
*All pilots must configure IVC in order to hear the human AWACS/GCI.
−
* If using the Online Squadron Collection (OSC):
+
*If using the Online Squadron Collection (OSC):
−
** All pilots flying in the mission need to run the OSC Validator during the mission.
+
**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 human AWACS/GCI needs to run the OSC AISpy and OSC F4AWACS.
−
** The server flight needs to run the OSC SQServer.
+
**The server flight needs to run the OSC SQServer.
−
* The preferred channel for talking with human AWACS/GCI will be briefed.
+
*The preferred channel for talking with human AWACS/GCI will be briefed.
  
 
=Configuring IVC=
 
=Configuring IVC=
  
−
# Locate the relevant IVC ini file.
+
#Locate the relevant IVC ini file.
−
## Default location for 64-bit installations is Falcon BMS 4.34\Bin\x64\IVC\IVC Client.ini
+
##Default location for 64-bit installations is Falcon BMS 4.34\Bin\x64\IVC\IVC Client.ini
−
## Default location for 32-bit installations is Falcon BMS 4.34\Bin\x86\IVC\IVC Client.ini
+
##Default location for 32-bit installations is Falcon BMS 4.34\Bin\x86\IVC\IVC Client.ini
−
# Open the relevant IVC ini file, and then apply whichever changes apply to the situation:
+
#Open the relevant IVC ini file, and then apply whichever changes apply to the situation:
 
      
 
      
 
==Changes ONLY for Pilots==
 
==Changes ONLY for Pilots==
Line 39: Line 40:
 
If he is using BMS to connect to the IVC server, then after connecting to the hosted TE/Campaign, he should do the following:
 
If he is using BMS to connect to the IVC server, then after connecting to the hosted TE/Campaign, he should do the following:
  
−
# Find the open IVC client instance.
+
#Find the open IVC client instance.
−
# Click on Force Local Control. This will probably disconnect him from the server.
+
#Click on Force Local Control. This will probably disconnect him from the server.
−
# Click on Connect.
+
#Click on Connect.
−
# Assign himself the frequencies for [[Radios#IVC_Check|pre-flight IVC checks]]:
+
#Assign himself the frequencies for [[Radios#IVC_Check|pre-flight IVC checks]]:
−
## Enter "339750" (without the quotes) for UHF and click on Change Frequency. (Click Change Frequency even if the frequency is already correctly entered.)
+
##Enter "339750" (without the quotes) for UHF and click on Change Frequency. (Click Change Frequency even if the frequency is already correctly entered.)
−
## Enter "1234" (without the quotes) for VHF and click on Change Frequency. (Click Change Frequency even if the frequency is already correctly entered.)
+
##Enter "1234" (without the quotes) for VHF and click on Change Frequency. (Click Change Frequency even if the frequency is already correctly entered.)
−
# Write down the necessary frequencies associated with his mission. (For example, if he is supporting only one package, he should probably write down the UHF 6 frequency for that package. SOPs will most likely vary at different organizations.)
+
#Write down the necessary frequencies associated with his mission. (For example, if he is supporting only one package, he should probably write down the UHF 6 frequency for that package. SOPs will most likely vary at different organizations.)
−
# Upon everyone committing to flight, he should switch to the mission frequency upon which he'll be waiting to receive requests or check-ins.
+
#Upon everyone committing to flight, he should switch to the mission frequency upon which he'll be waiting to receive requests or check-ins.
  
 
=Online Squadron Collection=
 
=Online Squadron Collection=
Line 52: Line 53:
 
==Installing==
 
==Installing==
  
−
# Download OSC v2.0.2: http://programs.sakgiok.gr/OSC/Downloads/OSC%20v2.0.2_setup.zip
+
#Download OSC v2.0.2: http://programs.sakgiok.gr/OSC/Downloads/OSC%20v2.0.2_setup.zip
−
# Install it.
+
#Install it.
−
# Run the OSC MONSTER UPDATER program. It should update OSC to v2.0.6.
+
#Run the OSC MONSTER UPDATER program. It should update OSC to v2.0.6.
  
 
==Running==
 
==Running==
Line 60: Line 61:
 
===ONLY for SERVER===
 
===ONLY for SERVER===
  
−
# Run OSC SQServer.
+
#Run OSC SQServer.
  
 
===ONLY for PILOTS===
 
===ONLY for PILOTS===
  
−
# Run OSC Validator at mission time.
+
#Run OSC Validator at mission time.
−
# Enter your in-game callsign in capital letters (ie. GAMBLE 11)
+
#Enter your in-game callsign in capital letters (ie. GAMBLE 11)
−
# Connect to the server.
+
#Connect to the server.
  
 
===ONLY for Human GCI/AWACS===
 
===ONLY for Human GCI/AWACS===
  
−
# Run OSC AISpy.
+
#Run OSC AISpy.
−
# Connect to server.
+
#Connect to server.
−
# Run OSC F4AWACS.
+
#Run OSC F4AWACS.
−
# Connect to server.
+
#Connect to server.
 +
 
 +
=UOAF SOP for GCI/AWACS=
 +
These SOPs are the general guidelines for how human GCI/AWACS will be used. Deviations from SOPs for a mission should be explicitly mentioned in the mission briefing.
 +
 
 +
=== Philosophy ===
 +
 
 +
* '''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.
 +
 
 +
=== Authority ===
 +
 
 +
* '''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-Ins ===
 +
 
 +
# Flight Leads check in with GCI/AWACS with their flight callsign and the number of good ships in the flight available for tasking.
 +
# GCI/AWACS acknowledges the check-in:
 +
## For Flight Leads that are not Package Lead, GCI/AWACS informs them if Package Lead has already checked in or not.
 +
## 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.
 +
# 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.''
 +
 
 +
=== Brevity ===
 +
Below is an incomplete list of brevity that may be communicated between pilots and human GCI/AWACS:
  
−
=SOP for GCI/AWACS=
+
* "Check-in"
−
'''Coming soon.'''
+
* "Alfa Check"
 +
* "Judy."
 +
* "Request Picture."
 +
* "Bogey Dope"
 +
* "Declare <Bullseye>"
 +
* "Request vector to tanker/base/(nearest) target/alternate."
 +
* "Request relief."
  
−
{{Nav UOAF}}
+
<br />{{Nav UOAF}}
  
 
[[Category:UOAF]]
 
[[Category:UOAF]]
 
[[Category:UOAF: BMS Codex]]
 
[[Category:UOAF: BMS Codex]]

Revision as of 09:33, 5 April 2020

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 (TBD)
  5. Understand key brevity (TBD)

Basics

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

Changes ONLY for GCI

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 him from the server.
  3. Click on Connect.
  4. Assign himself the frequencies for pre-flight IVC checks:
    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 his mission. (For example, if he is supporting only one package, he should probably write down the UHF 6 frequency for that package. SOPs will most likely vary at different organizations.)
  6. Upon everyone committing to flight, he should switch to the mission frequency upon which he'll be waiting to receive requests or check-ins.

Online Squadron Collection

Installing

  1. Download OSC v2.0.2: http://programs.sakgiok.gr/OSC/Downloads/OSC%20v2.0.2_setup.zip
  2. Install it.
  3. Run the OSC MONSTER UPDATER program. It should update OSC to v2.0.6.

Running

ONLY for SERVER

  1. Run OSC SQServer.

ONLY for PILOTS

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

ONLY for Human GCI/AWACS

  1. Run OSC AISpy.
  2. Connect to server.
  3. Run OSC F4AWACS.
  4. Connect to server.

UOAF SOP for GCI/AWACS

These SOPs are the general guidelines for how human GCI/AWACS will be used. Deviations from SOPs for a mission should be explicitly mentioned in the mission briefing.

Philosophy

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

Authority

  • 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-Ins

  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.

Brevity

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

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


{{#invoke:Navbox|navbox}}

Retrieved from "http://codex.uoaf.net/index.php?title=Player-controlled_AWACS&oldid=7423"