UOAF SOPs

2017-06-22T01:05:18Z

Gusy: Created page with "'''1.0 Gameplay SOPs''' 1.1 The chain of command will be respected and enforced at all times. Leadership consists of a Package Commander, a Flight Leader, and an Element Lead..."

'''1.0 Gameplay SOPs'''

1.1 The chain of command will be respected and enforced at all times. Leadership consists of a Package Commander, a Flight Leader, and an Element Leader.

1.2 Under no circumstance will pilots be able to edit their load outs, it is lead's (#1) or element lead's (#3)'s decision to do so and theirs only.

1.3 Under no circumstance will pilots except Lead(#1) or the Package Commander change steer points in the 2D planner.

1.4 Under no circumstance will pilots edit or move ground troops without notifying or consulting a second party of their action.

1.5 Comms integrity will be maintained at all times and without exception.

1.6 Discipline will be maintained in the air and without exception.

1.7 Wingmen will follow their leads' orders and aircraft at all times and will respond to all directives appropriately. Failure to do so will result in a kick or ban from the community. Countermanding orders will lead to decisive disciplinary action.

1.8 Flights will function within their assigned roles and flight plans as part of the package at all times and without exception.

'''2.0 UOAF Event SOPs'''

2.1 UOAF events are open to all members of the UO community who consider themselves ready. UOAF’s most frequent event type is for BMS, though occasionally DCS events are organized.

2.2 Members of the UO community that wish to attend a UOAF event must RSVP on the event’s calendar post.

2.3 RSVP priority will be as follows; Roster members, UO Regulars, UO Donors, Old Guest, New Guest.

2.4 Players will show up on time with all hardware and installations ready to go.

2.5 Players will indicate unforeseen tardiness or absence in the event thread on the forum.

2.6 New Players flying their first Event will be required to have flown on a pickup flight with a player that has flown past events. This SOP can be overridden at Event Moderator's discretion.

2.7 All players will follow the directions of the Event Moderator/s.

'''3.0 UOAF Pickup SOPs'''

3.1 Players are welcome to create and run pickup flights outside of main events.

3.2 Players can join or create a pickup flight by asking in discord, teamspeak, or the forums.

3.3 Players are expected to follow flight standards laid out in 1.0 Gameplay SOPs.

'''4.0 UOAF Roster SOPs'''

4.1 Roster members are expected to be flight commander capable, possess a high degree of competence in flight simulation, and maintain a good reputation and behavior.

4.2 Roster members are governed by the Fellowship of the Wing, current and former leaders of the UOAF.

4.3 Roster members are expected to take flight leader and element leader positions during flights.

4.4 Roster members are to discuss changes and report player behavior using discord UOAF-Private channel.

Staff

2017-06-21T20:33:45Z

Gusy:

__NOTITLE__ __NOTOC__

<onlyinclude>{| class="wikitable" style="width: 80%; margin: 1em auto 1em auto;" align="left"

|- style="width: 50%;"
! colspan="1" style="width: 10%;" |
! colspan="1" style="width: 15%;" | [[UOTC|United Operations Training Center]]
! colspan="1" style="width: 15%;" | [[Web Service Office]]
! colspan="1" style="width: 15%;" | [[Mission Making Office]]
! colspan="1" style="width: 15%;" | [[Game Service Office]]
! colspan="1" style="width: 15%;" | [[Public Relations Office]]
! colspan="1" style="width: 15%;" | [[United Operations Air Force]]
|- style="vertical-align: top;" ! scope="row"
! '''Officers'''
|
* Azzwort
|
* Marvin
* Impulse 9
|
* Briland
|
* Impulse 9
* VPope
|
* Azzwort
* Headshot
* Impulse 9
|
* Darkfiber
* Gusy
|- style="vertical-align: top;" ! scope="row"
! '''Delegates'''
| ''Senior Instructors''
* Jimbo
* Zumorc
* Fox D
* Haribo
* Gusy
* Kail
* Dezel
* Pax'Jarome
* VPope
* S4dGuyInSn0
''Junior Instructors''
* Mixtrate
* Tripshot
*Whisper
* Graham1988

| ''Application Developer''
* Verox
* Briland
''Forum Moderators''
*j0zh94
*kalohepirate
| ''[[Mission Submission Moderator | Mission Submission Moderators]]''
* Blackhawk
* Blue
* Darksidesix
* Nathan
* Perfk
* TinfoilHate
''Mission Review Team Leaders''
*Blackhawk
''Mission Review Team - Volunteers''
*Sacher
*SgtDeadly12
| ''Game Moderators - Officers''
*Azzwort
*Briland
*DarkFib3r
*Gusy
*Headshot
*Impulse 9
*Marvin
*VPope
''Game Moderators - Regulars''
*Perfk
*Whisper
|
| ''UOAF - Mission Frag Team''
* Brainling - NORAD
* Nebosja - EURO
* Neruo - EURO
* Domestos - EURO
''UOAF - Training Team''
* Skosh - LEAD
* Nebojsa
* Ghostdog
* Sinu
</onlyinclude>
|}
<includeonly>
 
</includeonly>
__NOTOC__
__NOEDITSECTION__

File:UOAF Frag teams.png

2017-05-09T03:42:32Z

Gusy:

UOAF Event Checklist

2017-05-04T06:55:50Z

Gusy: /* Commit to 3D */

==Event Start==
#Bring up dedicated server
#Fill Reserved Slots
#Introduce Moderator/s
#Introduce Event
#Introduce Package Leader
#Handoff control to Package Leader
==Package Leader Briefing==
#Explain the Plan
#Answer Flight Leader questions
==Flight Briefing==
#Players move to Individual flight channels for briefing
#Flight leader explains the plan
#Answer questions
==Pre-Flight Procedures==
#Players return to Briefing Room
#Package Leader or Moderator/s answer any final questions
#IVC checks in flight order, as per briefing (F1)
#Take 3 minute break and sort out any IVC issues.
==Moderator read SOPs==
#TeamSpeak will be muted during the flight
#Use Shift-T to chat in game if you have technical issues
#If you have an issue close BMS and IVC. Get your issues sorted out, reconnect, verify that your issues are sorted and rejoin. Use Instant action to check flight controls.
#Landings at airbases follow the overhead break.
#After you land and exit BMS or if you get knocked out, jump down into an open channel to chat with others.
#We will commit as Taxi

==Commit to 3D==
#Save the Campaign
# Commit the server to 3D
#Doubleclick your flight and your seat and save your data cartridge
#Commit taxi in flight order, as per briefing (F1)
#Mute Teamspeak

UOAF Event Checklist

2017-04-22T19:00:11Z

Gusy: /* Moderator read SOPs */

==Event Start==
#Bring up dedicated server
#Fill Reserved Slots
#Introduce Moderator/s
#Introduce Event
#Introduce Package Leader
#Handoff control to Package Leader
==Package Leader Briefing==
#Explain the Plan
#Answer Flight Leader questions
==Flight Briefing==
#Players move to Individual flight channels for briefing
#Flight leader explains the plan
#Answer questions
==Pre-Flight Procedures==
#Players return to Briefing Room
#Package Leader or Moderator/s answer any final questions
#IVC checks in flight order, as per briefing (F1)
#Take 3 minute break and sort out any IVC issues.
==Moderator read SOPs==
#TeamSpeak will be muted during the flight
#Use Shift-T to chat in game if you have technical issues
#If you have an issue close BMS and IVC. Get your issues sorted out, reconnect, verify that your issues are sorted and rejoin. Use Instant action to check flight controls.
#Landings at airbases follow the overhead break.
#After you land and exit BMS or if you get knocked out, jump down into an open channel to chat with others.
#We will commit as Taxi

==Commit to 3D==
#Commit the server to 3D
#Doubleclick your flight and your seat and save your data cartridge
#Commit taxi in flight order, as per briefing (F1)
#Mute Teamspeak

ARMs

2017-03-22T00:46:38Z

Gusy: /* AGM-45B Shrike */

=Learning objectives=
#Know how to use HAD
#Know how to use WPN page
##Know when and how to use POS (EOM, PB, RUK)
##Know when and how to use HAS

=HAD=

Presents a map, similar to the HSD, but show different emitting radars on it. Lock on a radar and fire.

Biggest issue is co-located radars that overlap. Zooming in can sometimes help, but more often, switch to a HAS shot to surgically target a radar.

=WPN Modes=
[[File:HARM.jpg|thumb|right|HARM flight profiles]]
==POS==
POS will always slave to a selected steerpoint; no steerpoint means no shot in POS mode
*Manually select steerpoints or threat steers in HSD or jump to pre-planned target steerpoints using UFC
*Alternately, set mark points as references to radars to use POS mode
*In POS, you can use EOM (very fine control – you know exactly where the target is and it is on the current steerpoint), PB (wider control – the target is close to a threat steer point), or RUK (extremely wide control – the target is around your current position and will lock on to the first thing it sees). You still need a steerpoint, remember.
*RUK is LOAL, HAS is LOBL.
*RUK, PB, EOM are all three POS modes and all POS modes are steerpoint-directed in azimuth. The difference is in end game seeker activity and assumed range only. EOM and PB assume range = range to steerpoint. RUK assumes range = maximum.
**EOM = point
**PB = area
**RUK = lane
*RUK is for painting a long, wide stripe of ground with HARM coverage. PB is for a floodlight on an area. EOM is a laser pointer.

===Tips===
If you want to use POS shots, you need a reference steerpoint. If you detect a pop-up SAM, here is how you can set a steerpoint manually so you can still use POS:

#Lock the SAM target up on the FCR.
#Press CZ to zero out the cursor and remove any offset.
#Press ICP 7 (MARK) and make sure DED shows FCR.
#TMS Up to create a markpoint at your cursor.
#Press ICP 0 to automatically go to the steerpoint you just added.
#Select EOM for your POS shot to get the narrowest cone; you locked the target up so you don't need the wide PB cone for your shot.
#Fire when in range.

==HAS==
HARM as a Sensor allows you to lock onto a radar manually and have the ARM track that signal.

#Switch to WPN
#Switch to HAS
#Cycle tables to the one with the radar you want to track
#Lock up radar with cursor
#Wait until RDY displays
#Put the target in the box on the HUD
#Estimate if range is adequate
#Fire

=Weapons=
==AGM-88 ARM==
Standard ARM.

'''Range''': 25nm

==AGM-45B Shrike==
A Vietnam-era ARM. Low reliability.

'''Range''': 10nm

Tips to use effectively:
#Get to 30,000 feet
#Switch to WPN->HAS and select proper table
#Lock on radar
#Wait for a SAM launch
#Aim your FPM at the smoke trail; this will boresight your SHrike on the target and is how these weapons were employed historically.
# Fire
#Defend while closing to ensure radar stays on
 
[[File:Shrike_keyhole.png||none|600px|left|]]
 

==ALARM==
Parachute ARM carried by Tornado and Jaguar.

'''Range''': 24nm

==AGM-78 Standard==
Old school ARM.

'''Range''': 30nm

{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

ARMs

2017-03-22T00:46:08Z

Gusy: /* AGM-45B Shrike */

=Learning objectives=
#Know how to use HAD
#Know how to use WPN page
##Know when and how to use POS (EOM, PB, RUK)
##Know when and how to use HAS

=HAD=

Presents a map, similar to the HSD, but show different emitting radars on it. Lock on a radar and fire.

Biggest issue is co-located radars that overlap. Zooming in can sometimes help, but more often, switch to a HAS shot to surgically target a radar.

=WPN Modes=
[[File:HARM.jpg|thumb|right|HARM flight profiles]]
==POS==
POS will always slave to a selected steerpoint; no steerpoint means no shot in POS mode
*Manually select steerpoints or threat steers in HSD or jump to pre-planned target steerpoints using UFC
*Alternately, set mark points as references to radars to use POS mode
*In POS, you can use EOM (very fine control – you know exactly where the target is and it is on the current steerpoint), PB (wider control – the target is close to a threat steer point), or RUK (extremely wide control – the target is around your current position and will lock on to the first thing it sees). You still need a steerpoint, remember.
*RUK is LOAL, HAS is LOBL.
*RUK, PB, EOM are all three POS modes and all POS modes are steerpoint-directed in azimuth. The difference is in end game seeker activity and assumed range only. EOM and PB assume range = range to steerpoint. RUK assumes range = maximum.
**EOM = point
**PB = area
**RUK = lane
*RUK is for painting a long, wide stripe of ground with HARM coverage. PB is for a floodlight on an area. EOM is a laser pointer.

===Tips===
If you want to use POS shots, you need a reference steerpoint. If you detect a pop-up SAM, here is how you can set a steerpoint manually so you can still use POS:

#Lock the SAM target up on the FCR.
#Press CZ to zero out the cursor and remove any offset.
#Press ICP 7 (MARK) and make sure DED shows FCR.
#TMS Up to create a markpoint at your cursor.
#Press ICP 0 to automatically go to the steerpoint you just added.
#Select EOM for your POS shot to get the narrowest cone; you locked the target up so you don't need the wide PB cone for your shot.
#Fire when in range.

==HAS==
HARM as a Sensor allows you to lock onto a radar manually and have the ARM track that signal.

#Switch to WPN
#Switch to HAS
#Cycle tables to the one with the radar you want to track
#Lock up radar with cursor
#Wait until RDY displays
#Put the target in the box on the HUD
#Estimate if range is adequate
#Fire

=Weapons=
==AGM-88 ARM==
Standard ARM.

'''Range''': 25nm

==AGM-45B Shrike==
A Vietnam-era ARM. Low reliability.

'''Range''': 10nm

Tips to use effectively:
#Get to 30,000 feet
#Switch to WPN->HAS and select proper table
#Lock on radar
#Wait for a SAM launch
#Aim your FPM at the smoke trail; this will boresight your SHrike on the target and is how these weapons were employed historically.
# Fire
#Defend while closing to ensure radar stays on
 
[[File:Shrike_keyhole.png||none|600px|left|]]
 

==ALARM==
Parachute ARM carried by Tornado and Jaguar.

'''Range''': 24nm

==AGM-78 Standard==
Old school ARM.

'''Range''': 30nm

{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

2017-03-18T03:51:54Z

Gusy:

File:IVC File Location.png

2017-03-18T03:51:40Z

Gusy:

BMS Configuration and Setup

2017-03-15T22:06:35Z

Gusy: /* Enabling Borderless Windowed Mode */

[[File:home-pit.jpg||none|500px|left|]] 

=Learning objectives=
#Install BMS and update to the latest version
#Configure your controllers
#Configure the most common settings
#Set up windowed mode, if necessary

=Learning files=
*[https://www.youtube.com/watch?v=2haRQ6DCzSM Falcon 4 BMS 4.33 Essential Control and Key Setup]
**reference in \Docs\Key Files & Input\BMS Key File Manual.pdf for "advanced" users
* [https://www.youtube.com/watch?v=EvWwHwhz7zA Falcon BMS 4.33U3 - Install to Combat Ready in 1.67 Hours (Tutorial)]

=Installing BMS=
To install BMS you’ll need the original Falcon 4.0 install disk (not Allied Force) or iso of same, the BMS installer and the latest update.

'''Do not install Falcon from the disk.''' You only need it in the drive while BMS is installing.

Once you’ve gathered all the components do the following:

# Extract the “Falcon BMS 4.33 U1 Setup” folder from the zip file (from now on referred to as the Setup folder).
# Run the Update 2 executable, install it to the setup folder.
# Run the Update 3 executable, install it to the setup folder.
# In the setup folder, find and run setup.exe.
# Follow the instructions in the installer.

After the installation is finished, '''don’t delete the setup folder''', as you’ll need it to patch the game later. After installing BMS you will not need the Falcon 4.0 disk any more except for reinstalling the game.

==Patching BMS==
To update to a newer version of BMS, download the update and apply it in the same manner as the Update 3 executable above, then run setup.exe again. The game will automatically detect your install and patch the game to the downloaded version.

=Configuring BMS=
After installing the game, run the shortcut to the game and click Configuration in the launcher. In this window are options that cannot be changed in game, like advanced graphics options and avionics options. The settings are down to personal preference.
VKing recommends Color MFD, EPAF Radar Cues, Gray scale AG Radar, and Smaller HSD/Bullseye Symbols.

In the game, click Logbook at the top of the screen. This will show your player profile. Change both name and callsign to your nickname and pick a pilot picture and/or squadron patch if you like.

Go to the Setup screen and check “Radio calls use bullseye”, then configure the rest the way you like.

==Enabling Borderless Windowed Mode==
Enabling borderless windowed mode in BMS allows you the ability to alt-tab out and back in without crashing the bms client. To enable this mode open up your bms launcher and select configuration.
 
[[File:Windowed_mode_part_1.png||none|600px|left|]]
 
Under the Hardware -> External Displays You will see 1. Cockpit Displays to External Windows and 2. External Windows Always on Top. Enable both of these are you see in the pic above. Save your selection by clicking Apply Changes at the bottom right.

Next we need to configure the external windows we have enabled. In the bms launcher open Cockpit Display Extraction.
 
[[File:Windowed_mode_part_2.png||none|600px|left|]]
 
On the left we have 7 windows available for editing. We only want to enable the Main window, unless you are using a real life HUD/RWR/MFD/DED/PFL. In the Main window it will have the Enabled box selected and greyed out, unselect Borders. For the Adjust window rectangle select Left=0 and Top=0, Width and Height will be greyed out and selected as 0.
For the other windows(HUD,RWR,MFD,DED,PFL) make sure to unselect all enabled boxes, this will disable them from appearing. After completion save your changes by clicking Save & Close.

When opening up BMS it will be a smaller window in the top left of the screen. When entering into the 3D pit the window will open up to fullscreen windowed borderless and match your preset Resolution.

Using borderless windowed mode is highly recommended. This will allow you to alt-tab out and do other things like change channels in Teamspeak. When you rejoin back into the 3D pit you will see an annoying windows mouse cursor follow out of sync with the bms cursor. To disable the windows mouse cursor in bms simply click the combination CTRL+ALT+DELETE, and then ESCAPE key. It will lag for around 1-2 seconds then put you back into the 3D pit with the windows cursor gone.
 

=Setting up controls=
==Buttons==
Controls you absolutely need to know, and (as far as possible) should bind to your joystick:
{| class="wikitable"
! Function || Default (from BMS.key)
|-
| Trigger (Cannon) || "/" on english keyboards, "-" on most other european keyboards
|-
| Pickle (Fire missiles/bombs) || Space
|-
| TMS Up || Ctrl+Up arrow
|-
| TMS Down || Ctrl+Down arrow
|-
| DMS Down || Ctrl+Alt+Down arrow
|-
| Cursor slew || Arrow keys
|-
| Run countermeasure program || Z or X
|-
| Comm 1 and 2 transmit || Alt+1 and Alt+2
|-
| Wheel brakes || K
|-
| Nose wheel steering || Shift+/ or Shift+- (same difference as Trigger)
|-
| Gear up/down || G
|-
| Speed brakes out/in || B
|-
| Dogfight mode enable/cancel || D and C
|-
| Antenna tilt down/up || F5 and F7. F6 centers.
|}

Binding to joystick can be done via profiling software, or via in-game/DirectX assignments. See [http://forums.unitedoperations.net/index.php/topic/15693-bms-advanced-joystick-bindings-shift-states-without-joystick-software/ this thread].

==Axes==
Beyond the normal pitch, roll, throttle, and rudder axes, if your joystick has extra wheels or sliders, it’s recommended to assign them to the '''Radar antenna elevation''' and '''Range knob''' under advanced control settings.

==TrackIR==
BMS supports TrackIR and other head tracking systems natively. Enable TrackIR for 3D cockpit and TrackIR vector in the advanced control settings.

==Getting started==

===Setting up the Data Transfer Cartridge (DTC)===
After setting up your pilot, go to any Tactical Engagement then click on the DTC button on the right side of the map (second from the bottom, above the button with a sun and clouds).
Go to the '''EWS tab''' and click ''Reset'' followed by ''Save''. This will make sure you have a countermeasure program to use in game.
Then go to the '''MFD tab''' and do the same to. Later you can configure your DTC as you please, but if you don’t follow these steps you might not have any MFD pages or countermeasure programs when you play.

==Multiplayer==
===Connecting to a multiplayer game===
Connecting to a host in BMS is done in a older fashion than more modern games, to connect to someone hosting a BMS session you require the following pieces of information:
* '''The Server/Host external IP address''' (This can be acquired by accessing the UO main website and clicking "Server Info," or if privately hosting, searching for “What’s my I.P?” in Google).
* '''The Connection bandwidth'''. This is your allowed downstream and upstream to the host, normally this is recommended to be kept to '''1024 (kilobits)'''. This value may change depending on the host's total bandwidth allocated to the game, '''however it is important that ALL clients use the same connection bandwidth to avoid synchronization conflicts'''. If in doubt, ask the host.
* '''IVC IP address'''. This box can be left empty, or unchecked if not using IVC. An IP address needs only be entered if someone else is hosting the IVC server. (IVC is covered further on in this guide).

After getting this information, you can use the '''Comms''' button at the top of the main menu and create a bookmark with the information for the server you wish to connect to. Once completed, you may save the bookmark for future use.

{{Red|'''Forgetting to input a connection bandwidth value in the comms menu will break the multiplayer session for everyone. Double check that this value is entered.'''}}

Once connected to the host, you will return to the main screen. However the “Comms” button will now instead display a chat window for the main menu. This can be used for some pre-game chatter if IVC or Teamspeak is occupied. From here, you will now be able to proceed to either the Tactical Engagement or Campaign section and select the '''Online''' option. If the Host has a game running, their game will be displayed here and allow you to connect.
Please ensure that is is safe to join with the host first before connecting to a server, BMS can sometimes run into issues if someone joins whilst something is being changed.

* http://forums.unitedoperations.net/index.php/topic/15693-bms-advanced-joystick-bindings-shift-states-without-joystick-software/

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

BMS Configuration and Setup

2017-03-15T22:02:19Z

Gusy: /* Configuring BMS */

[[File:home-pit.jpg||none|500px|left|]] 

=Learning objectives=
#Install BMS and update to the latest version
#Configure your controllers
#Configure the most common settings
#Set up windowed mode, if necessary

=Learning files=
*[https://www.youtube.com/watch?v=2haRQ6DCzSM Falcon 4 BMS 4.33 Essential Control and Key Setup]
**reference in \Docs\Key Files & Input\BMS Key File Manual.pdf for "advanced" users
* [https://www.youtube.com/watch?v=EvWwHwhz7zA Falcon BMS 4.33U3 - Install to Combat Ready in 1.67 Hours (Tutorial)]

=Installing BMS=
To install BMS you’ll need the original Falcon 4.0 install disk (not Allied Force) or iso of same, the BMS installer and the latest update.

'''Do not install Falcon from the disk.''' You only need it in the drive while BMS is installing.

Once you’ve gathered all the components do the following:

# Extract the “Falcon BMS 4.33 U1 Setup” folder from the zip file (from now on referred to as the Setup folder).
# Run the Update 2 executable, install it to the setup folder.
# Run the Update 3 executable, install it to the setup folder.
# In the setup folder, find and run setup.exe.
# Follow the instructions in the installer.

After the installation is finished, '''don’t delete the setup folder''', as you’ll need it to patch the game later. After installing BMS you will not need the Falcon 4.0 disk any more except for reinstalling the game.

==Patching BMS==
To update to a newer version of BMS, download the update and apply it in the same manner as the Update 3 executable above, then run setup.exe again. The game will automatically detect your install and patch the game to the downloaded version.

=Configuring BMS=
After installing the game, run the shortcut to the game and click Configuration in the launcher. In this window are options that cannot be changed in game, like advanced graphics options and avionics options. The settings are down to personal preference.
VKing recommends Color MFD, EPAF Radar Cues, Gray scale AG Radar, and Smaller HSD/Bullseye Symbols.

In the game, click Logbook at the top of the screen. This will show your player profile. Change both name and callsign to your nickname and pick a pilot picture and/or squadron patch if you like.

Go to the Setup screen and check “Radio calls use bullseye”, then configure the rest the way you like.

==Using fullscreen windowed mode==
Enabling fullscreen windowed mode in BMS allows you the ability to alt-tab out and back in without crashing the bms client. To enable this mode open up your bms launcher and select configuration.
 
[[File:Windowed_mode_part_1.png||none|600px|left|]]
 
Under the Hardware -> External Displays You will see 1. Cockpit Displays to External Windows and 2. External Windows Always on Top. Enable both of these are you see in the pic above. Save your selection by clicking Apply Changes at the bottom right.

Next we need to configure the external windows we have enabled. In the bms launcher open Cockpit Display Extraction.
 
[[File:Windowed_mode_part_2.png||none|600px|left|]]
 
On the left we have 7 windows available for editing. We only want to enable the Main window, unless you are using a real life HUD/RWR/MFD/DED/PFL. In the Main window it will have the Enabled box selected and greyed out, unselect Borders. For the Adjust window rectangle select Left=0 and Top=0, Width and Height will be greyed out and selected as 0.
For the other windows(HUD,RWR,MFD,DED,PFL) make sure to unselect all enabled boxes, this will disable them from appearing. After completion save your changes by clicking Save & Close.

When opening up BMS it will be a smaller window in the top left of the screen. When entering into the 3D pit the window will open up to fullscreen windowed borderless and match your preset Resolution.

Using windowed mode is highly recommended. This will allow you to alt-tab out and do other things like change channels in Teamspeak. When you rejoin back into the 3D pit you will see an annoying windows mouse cursor follow out of sync with the bms cursor. To disable the windows mouse cursor in bms simply click the combination CTRL+ALT+DELETE, and then ESCAPE key. It will lag for around 1-2 seconds then put you back into the 3D pit with the windows cursor gone.
 

=Setting up controls=
==Buttons==
Controls you absolutely need to know, and (as far as possible) should bind to your joystick:
{| class="wikitable"
! Function || Default (from BMS.key)
|-
| Trigger (Cannon) || "/" on english keyboards, "-" on most other european keyboards
|-
| Pickle (Fire missiles/bombs) || Space
|-
| TMS Up || Ctrl+Up arrow
|-
| TMS Down || Ctrl+Down arrow
|-
| DMS Down || Ctrl+Alt+Down arrow
|-
| Cursor slew || Arrow keys
|-
| Run countermeasure program || Z or X
|-
| Comm 1 and 2 transmit || Alt+1 and Alt+2
|-
| Wheel brakes || K
|-
| Nose wheel steering || Shift+/ or Shift+- (same difference as Trigger)
|-
| Gear up/down || G
|-
| Speed brakes out/in || B
|-
| Dogfight mode enable/cancel || D and C
|-
| Antenna tilt down/up || F5 and F7. F6 centers.
|}

Binding to joystick can be done via profiling software, or via in-game/DirectX assignments. See [http://forums.unitedoperations.net/index.php/topic/15693-bms-advanced-joystick-bindings-shift-states-without-joystick-software/ this thread].

==Axes==
Beyond the normal pitch, roll, throttle, and rudder axes, if your joystick has extra wheels or sliders, it’s recommended to assign them to the '''Radar antenna elevation''' and '''Range knob''' under advanced control settings.

==TrackIR==
BMS supports TrackIR and other head tracking systems natively. Enable TrackIR for 3D cockpit and TrackIR vector in the advanced control settings.

==Getting started==

===Setting up the Data Transfer Cartridge (DTC)===
After setting up your pilot, go to any Tactical Engagement then click on the DTC button on the right side of the map (second from the bottom, above the button with a sun and clouds).
Go to the '''EWS tab''' and click ''Reset'' followed by ''Save''. This will make sure you have a countermeasure program to use in game.
Then go to the '''MFD tab''' and do the same to. Later you can configure your DTC as you please, but if you don’t follow these steps you might not have any MFD pages or countermeasure programs when you play.

==Multiplayer==
===Connecting to a multiplayer game===
Connecting to a host in BMS is done in a older fashion than more modern games, to connect to someone hosting a BMS session you require the following pieces of information:
* '''The Server/Host external IP address''' (This can be acquired by accessing the UO main website and clicking "Server Info," or if privately hosting, searching for “What’s my I.P?” in Google).
* '''The Connection bandwidth'''. This is your allowed downstream and upstream to the host, normally this is recommended to be kept to '''1024 (kilobits)'''. This value may change depending on the host's total bandwidth allocated to the game, '''however it is important that ALL clients use the same connection bandwidth to avoid synchronization conflicts'''. If in doubt, ask the host.
* '''IVC IP address'''. This box can be left empty, or unchecked if not using IVC. An IP address needs only be entered if someone else is hosting the IVC server. (IVC is covered further on in this guide).

After getting this information, you can use the '''Comms''' button at the top of the main menu and create a bookmark with the information for the server you wish to connect to. Once completed, you may save the bookmark for future use.

{{Red|'''Forgetting to input a connection bandwidth value in the comms menu will break the multiplayer session for everyone. Double check that this value is entered.'''}}

Once connected to the host, you will return to the main screen. However the “Comms” button will now instead display a chat window for the main menu. This can be used for some pre-game chatter if IVC or Teamspeak is occupied. From here, you will now be able to proceed to either the Tactical Engagement or Campaign section and select the '''Online''' option. If the Host has a game running, their game will be displayed here and allow you to connect.
Please ensure that is is safe to join with the host first before connecting to a server, BMS can sometimes run into issues if someone joins whilst something is being changed.

* http://forums.unitedoperations.net/index.php/topic/15693-bms-advanced-joystick-bindings-shift-states-without-joystick-software/

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

File:Windowed mode part 2.png

2017-03-15T21:43:51Z

Gusy:

2017-03-01T22:36:51Z

Gusy:

''THIS IS A WIP''

=Learning Objectives"
1. Learn how to use VHF and UHF Communications in BMS.
2. Understand the Syntax used when Communicating between Fighter Aircraft.
3. Brevity Code Words.

=Learning Files=
*Video Outlining Communications in Combat.

=Basic Principles of Brevity=
* Know when to speak (and when to be silent).
* Know what to say.
* Accuracy and clarity.

==Responding to communications==
Within your flight (VHF), you may use your flight number as an alternative to the affirmative when given a directive (e.g. "Cowboy 1-1: Flight go trail. Cowboy 1-2: TWO Cowboy 1-3: THREE Cowboy 1-4: FOUR). This makes it '''clear''' for the flight lead to understand who has heard them and has intent to carry out the order.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

Between flights (UHF), the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that")

==Differences between directives and informatives==
Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "Lead checking left for steer 2"

=Do's and Don'ts=

DON'T use "message" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2)

=Brevity Code Masterlist=
ANGELS - Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)

ARIZONA - No ARM ordnance remaining. (HARMS for you BMS pilots)

BANDIT - Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.

BINGO - Fuel state needed for recovery (to RTB)

BLIND - No visual contact with friendly aircraft / ground position. Opposite of VISUAL.

BOGEY - Radar or visual contact whose identity is unknown.

BRAA - Bearing Range Altitude and Aspect. Aspect only required if other than HOT.

BREAK - Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).

BREVITY - Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.

BROKE LOCK - Advisory call regarding loss of radar/IR lock-on.

BUDDY LOCK - Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.

BUDDY SPIKE - Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.

BUSTER - Directive call to fly at max continuous speed (Mil power).

CHECK - (number, left/right) Turn (number) degrees left or right and maintain new heading.

CLEAN - No sensor information on non-friendly aircraft of interest / no visible battle damage.

CLEARED - Flight lead response: requested action is authorised.

CLEARED HOT - Flight lead response: release of ordinance is authorised.

COLD - Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"

COMMIT - Directive call to intercept.

DEFENSIVE - The speaker is under attack, moving defensively and unable to support others.

DELOUSE - Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.

DOLLY - LINK-4A/TADIL-C. Aka. "The data link" in BMS

FADED - Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.

FOX - A-A weapons employment (most should know this one already!)

FURBALL - Known bandits and friendlies in close proximity.

GATE - Directive/informative call to fly as quickly as possible, using afterburner/max power.

GORILLA - A large force of indeterminable numbers and formation i.e. a metric shit ton.

HOOK - (with direction) Directive call to perform an in-place 180-degree turn.

HOT - Meaning "turned towards"; the opposite of COLD.

JUDY - Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.

LOW - Below 10,000 feet MSL

MILLER TIME - Informative call indicating completion of A-G ordnance delivery. Generally used by
the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).

MUSIC - Electronic radar jamming. E.g. "Flight, music on"

NAILS - (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a
MiG-29 on my RWR, from my nose left, 10 o'clock)

NAKED - No RWR indications.

NO JOY - No visual contact with target/landmark, opposite of TALLY.

OUTLAW - Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying
from enemy airspace.

PITBULL - AIM-120 missile has reached MPRF active range (gone active). Also an ugly breed of dog.

PUSH - Go to designated frequency, no acknowledgement required.

PLAYTIME - Amount of time aircraft can remain on station.

RAYGUN - Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.

RIFLE - Friendly A-G missile launch.

ROGER - Indicates aircrew understands the radio transmission, DOES NOT INDICATED COMPLIANCE OR
REACTION.

ROLEX - Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.

SAM - Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.

SAUNTER - Fly at best endurance.

SINGER - Informative call of an RWR indication of SAM launch.

SORT - Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.

TALLY - Sighting of a target. Opposite of NO JOY.

TUMBLEWEED - Indicates limited situational awareness, NO JOY and BLIND. A request for information.

UNABLE - Cannot comply as requested or directed (preferably with reason if possible).

UNIFORM - UHF/AM radio.

VICTOR - VHF/AM radio.

VISUAL - Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.

WHAT LUCK - Request for results of mission or tasks.

WHAT STATE - Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.

WILCO - Will comply (with received instructions).

WINCHESTER - No ordinance remaining.