Difference between revisions of "Player-controlled AWACS"
Jump to navigation
Jump to search
BibleClinger (talk | contribs) |
BibleClinger (talk | contribs) |
||
| Line 79: | Line 79: | ||
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. | 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 === | + | ===Philosophy=== |
| − | * '''Human GCI/AWACS should speak''' | + | *'''Human GCI/AWACS should speak''' |
| − | ** '''as infrequently as possible; and''' | + | **'''as infrequently as possible; and''' |
| − | ** '''as little as possible.''' | + | **'''as little as possible.''' |
| − | * Unlike with AI AWACS, communication between pilots and GCI/AWACS can jam comms and marks a distinct disadvantage. | + | *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. | + | *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 === | + | ===Authority=== |
| − | * '''Package Flights are led by the Package Lead, unless explicitly directed otherwise.''' | + | *'''Package Flights are led by the Package Lead, unless explicitly directed otherwise.''' |
| − | * Package Flights check-in with GCI/AWACS. | + | *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). | + | *GCI/AWACS can hold and relay information for the package when Flight Leads are unavailable (perhaps due to terrain occlusion). |
| − | === Check-Ins === | + | ===Check-Ins=== |
{| class="wikitable" style="margin-left: 10px; float:right;" | {| class="wikitable" style="margin-left: 10px; float:right;" | ||
! colspan="4" |Check-In Example | ! colspan="4" |Check-In Example | ||
| Line 102: | Line 102: | ||
!Message | !Message | ||
|- | |- | ||
| − | | rowspan="3" | 1 | + | | rowspan="3" |1 |
| − | | rowspan="3" | Falcon 1 | + | | rowspan="3" |Falcon 1 |
| − | | Falcon 1-1 | + | |Falcon 1-1 |
|"Showtime, Falcon 1, check-in. 4 good ships." | |"Showtime, Falcon 1, check-in. 4 good ships." | ||
|- | |- | ||
| − | | Showtime | + | |Showtime |
| − | | "Falcon 1, copy check-in. Awaiting Package Lead." | + | |"Falcon 1, copy check-in. Awaiting Package Lead." |
|- | |- | ||
| − | | Falcon 1-1 | + | |Falcon 1-1 |
| − | | "Falcon 1" | + | |"Falcon 1" |
|- | |- | ||
| − | | rowspan="3" | 2 | + | | rowspan="3" |2 |
| − | | rowspan="3" | Gamble 2 | + | | rowspan="3" |Gamble 2 |
| − | | Gamble 2-1 | + | |Gamble 2-1 |
|"Showtime, Gamble 2, check-in. 4 good ships." | |"Showtime, Gamble 2, check-in. 4 good ships." | ||
|- | |- | ||
| − | | Showtime | + | |Showtime |
|"Gamble 2, Showtime, copy check-in. Awaiting Package Lead." | |"Gamble 2, Showtime, copy check-in. Awaiting Package Lead." | ||
|- | |- | ||
| − | | Gamble 2 | + | |Gamble 2 |
|"Gamble 2" | |"Gamble 2" | ||
|- | |- | ||
| Line 127: | Line 127: | ||
| rowspan="3" |Hawkeye 1 | | rowspan="3" |Hawkeye 1 | ||
(Package Lead) | (Package Lead) | ||
| − | | Hawkeye 1-1 | + | |Hawkeye 1-1 |
|"Showtime, Hawkeye 1, check-in. 2 good ships." | |"Showtime, Hawkeye 1, check-in. 2 good ships." | ||
|- | |- | ||
| − | | Showtime | + | |Showtime |
|"Hawkeye 1, Showtime, copy check-in. Previous check-ins Falcon 1 4-ship, Gamble 2, 4-ship." | |"Hawkeye 1, Showtime, copy check-in. Previous check-ins Falcon 1 4-ship, Gamble 2, 4-ship." | ||
|- | |- | ||
| − | | Hawkeye 1 | + | |Hawkeye 1 |
|"Hawkeye 1" | |"Hawkeye 1" | ||
|- | |- | ||
| rowspan="3" |4 | | rowspan="3" |4 | ||
| − | | rowspan="3" | Viper 1 | + | | rowspan="3" |Viper 1 |
| − | | Gamble 2-1 | + | |Gamble 2-1 |
|"Showtime, Viper 1, check-in. 4 good ships." | |"Showtime, Viper 1, check-in. 4 good ships." | ||
|- | |- | ||
| − | | Showtime | + | |Showtime |
|"Viper 1, Showtime, copy check-in. Package Lead available on this frequency." | |"Viper 1, Showtime, copy check-in. Package Lead available on this frequency." | ||
|- | |- | ||
| − | | Viper 1 | + | |Viper 1 |
|"Viper 1." | |"Viper 1." | ||
|- | |- | ||
|} | |} | ||
| − | # Flight Leads check in with GCI/AWACS with their flight callsign and the number of good ships in the flight available for tasking. | + | #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: | + | #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. | + | ##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. | + | ##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. | + | #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.'' | '''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 === | + | === Scope === |
| + | |||
| + | * 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 may warn about bandits intercepting friendly aircraft within the "alert range." Unless otherwise briefed, this is 80nm. This warning is not guaranteed to happen, and will be less likely to happen when the air picture is busy. | ||
| + | |||
| + | ===Brevity=== | ||
Below is an incomplete list of [[Communications_and_brevity#Brevity_Code_Masterlist|brevity]] that may be communicated between pilots and human GCI/AWACS: | Below is an incomplete list of [[Communications_and_brevity#Brevity_Code_Masterlist|brevity]] that may be communicated between pilots and human GCI/AWACS: | ||
| − | * "Check-in" | + | *"Check-in" |
| − | * "Alfa Check" | + | *"Alfa Check" |
| − | * "Judy." | + | *"Judy." |
| − | * "Request Picture." | + | *"Request Picture." |
| − | * "Bogey Dope" | + | *"Bogey Dope" |
| − | * "Declare <Bullseye>" | + | *"Declare <Bullseye>" |
| − | * "Request vector to tanker/base/(nearest) target/alternate." | + | *"Request vector to tanker/base/(nearest) target/alternate." |
| − | * "Request relief." | + | *"Request relief." |
<br />{{Nav UOAF}} | <br />{{Nav UOAF}} | ||
Revision as of 10:09, 5 April 2020
Contents
Learning objectives
- Configure IVC for human-controlled AWACS
- Install Online Squadron Collection
- Understand how to use BMS labels (TBD)
- Understand how to give BRAA and Bullseye calls (TBD)
- 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
- 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 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:
Changes ONLY for Pilots
- Find the following line:
#outsiders = none
- 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:
- Find the open IVC client instance.
- Click on Force Local Control. This will probably disconnect him from the server.
- Click on Connect.
- Assign himself the frequencies for 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 "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.)
- 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
- Download OSC v2.0.2: http://programs.sakgiok.gr/OSC/Downloads/OSC%20v2.0.2_setup.zip
- Install it.
- Run the OSC MONSTER UPDATER program. It should update OSC to v2.0.6.
Running
ONLY for SERVER
- Run OSC SQServer.
ONLY for PILOTS
- Run OSC Validator at mission time.
- Enter your in-game callsign in capital letters (ie. GAMBLE 11)
- Connect to the server.
ONLY for Human GCI/AWACS
- Run OSC AISpy.
- Connect to server.
- Run OSC F4AWACS.
- 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
| Check-In Example | |||
|---|---|---|---|
| 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." | ||
- 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.
Scope
- 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 may warn about bandits intercepting friendly aircraft within the "alert range." Unless otherwise briefed, this is 80nm. This warning is not guaranteed to happen, and will be less likely to happen when the air picture is busy.
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}}
