Difference between revisions of "Player-controlled AWACS"

From UOAF Codex
Jump to navigation Jump to search
Line 1: Line 1:
−
[[File:awacs.jpg||none|500px|left|]]<br />
+
[[File:awacs.jpg|alt=AWACS in flight|frameless|right|upright=1.5]]
  
 
=Learning objectives=
 
=Learning objectives=
 
#Configure IVC for human-controlled AWACS
 
#Configure IVC for human-controlled AWACS
−
#Understand how to use BMS labels
+
#Install Online Squadron Collection
−
#Understand how to give BRAA and Bullseye calls
+
#Understand how to use BMS labels (TBD)
−
#Understand key brevity
+
#Understand how to give BRAA and Bullseye calls (TBD)
 +
#Understand key brevity (TBD)
  
 
=Basics=
 
=Basics=
  
−
When utilising a human GCI/AWACS it is prudent to have a common UHF channel for the package the AWACS is supporting. As AWACS you should tune your UHF radio to the package channel so you can hear MAGIC calls by your wingmen.
+
* 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.
  
−
The 2D keybindings are as follows:
+
=Configuring IVC=
−
- F1 - UHF radio
 
−
- F2 - VHF radio
 
−
- F3 - GUARD channel(243.0Mhz), all players are tuned to this frequency and will hear you talk!
 
  
−
All players will automatically receive on GUARD(F3), so you can give out calls there. However in order for 3D players to transmit on GUARD, they either have to flip the COM1 switch from SQ to GD(picture) or switch their UHF radio to 243Mhz.  
+
''Note: The instructions given here are for 64-bit installations. If you are still somehow running BMS in 32-bit, then you will need to make the adjustments to the correct IVC directory.''
  
−
Due to the amount of extra flipping of switches we propose to use a single UHF frequency for all flights, which is then monitored by AWACS for calls. Although UHF13 is designated as team frequency, you should choose another frequency, since AI will be spamming UHF13. UOAF typically uses UHF17 for package communication.
+
# 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:
 +
#:<pre>#outsiders = none</pre>
 +
#Change the above to this:
 +
#:<pre>outsiders = all</pre>
  
−
As soon as you connect to a BMS server(even in 2D), some values in the IVC Client.ini will get overruled by BMS(such as frequency, nickname, key-hook etc.), this can only be circumvented by using force-local=1. This allows the AWACS player to use the IVC keybindings even if he does not have BMS/IVC as focus(for example for 3rd party tools like F4AWACS).
+
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==
  
−
A good SOP is still to be determined.
+
#Find the following line:
 +
#: <pre>#force-local = 0</pre>
 +
#Change it to this:
 +
#:<pre>force-local = 1</pre>
  
−
=IVC_Client.ini=
+
After this, human GCI/AWACS must manually set the UHF frequency that will be used to communicate with the flights he will support.
  
−
IVC config for 3D pilots
+
=Online Squadron Collection=
  
−
# See chapter 14.5 of the BMS manual for detailed explanation of available options.
+
==Installing==
−
<nowiki>#</nowiki> File to be saved in //localinstall/bin/x86/IVC/
 
−
<nowiki>#duplex = 0
 
−
#server =  
 
−
#connect = 1
 
−
#nickname =  
 
−
#port =
 
−
#key-hook = 1
 
−
#quick = 0
 
−
#</nowiki>word = password
 
−
<nowiki>#</nowiki>capture = sound_device
 
−
<nowiki>#nofx = 0
 
−
#</nowiki>playback = sound_device
 
−
<nowiki>#tone = 
 
−
#loudness = 0
 
−
#fuzz = 0 
 
−
#</nowiki>hum-level = -18
 
−
<nowiki>#</nowiki>hiss-level = -18
 
−
<nowiki>#toneVol = 0
 
−
#uhf = 359300
 
−
#vhf = 1234
 
−
#uhfVol = 6
 
−
#vhfVol = 6
 
−
outsiders = Awacs
 
−
#log = 0
 
−
#minimize = 0
 
−
#</nowiki>force-local = 0
 
−
<nowiki>#</nowiki>selfblock = 0
 
  
 +
# 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.
  
−
IVC config for AWACS(will not work for normal flying). It is automatically tuned to UHF17(uhf value).
+
==Running==
  
−
# See chapter 14.5 of the BMS manual for detailed explanation of available options.
+
===ONLY for SERVER===
−
# File to be saved in //localinstall/bin/x86/IVC/
+
 
−
#duplex = 0
+
# Run OSC SQServer.
−
server =  ivc_ip
+
 
−
connect = 1
+
===ONLY for PILOTS===
−
nickname = your_nick
+
 
−
#port = xxxx
+
# Run OSC Validator at mission time.
−
key-hook = 1
+
# Enter your in-game callsign in capital letters (ie. GAMBLE 11)
−
#quick = 0
+
# Connect to the server.
−
#word = password
+
 
−
#capture = sound_device
+
===ONLY for Human GCI/AWACS===
−
#nofx = 0
+
 
−
#playback = sound_device
+
# Run OSC AISpy.
−
#tone = 
+
# Connect to server.
−
#loudness = 0
+
# Run OSC F4AWACS.
−
#fuzz = 0 
+
# Connect to server.
−
hum-level = -18
+
 
−
hiss-level = -18
+
=SOP for GCI/AWACS=
−
#toneVol = 0
+
'''Coming soon.'''
−
uhf = 359300
 
−
vhf = 1234
 
−
uhfVol = 6
 
−
vhfVol = 6
 
−
outsiders = Awacs
 
−
log = 1
 
−
#minimize = 0
 
−
force-local = 1
 
−
#selfblock = 0
 
  
 
{{Nav UOAF}}
 
{{Nav UOAF}}

Revision as of 00:33, 28 March 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

Note: The instructions given here are for 64-bit installations. If you are still somehow running BMS in 32-bit, then you will need to make the adjustments to the correct IVC directory.

  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

  1. Find the following line: 
    #force-local = 0
  2. Change it to this: 
    force-local = 1

After this, human GCI/AWACS must manually set the UHF frequency that will be used to communicate with the flights he will support.

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.

SOP for GCI/AWACS

Coming soon.

{{#invoke:Navbox|navbox}}

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