General SOPs - Revision history

Bs1: /* BMS-Specific */

2021-02-15T21:23:43Z

BMS-Specific

Bs1: /* UOAF Events */

2021-02-15T21:18:26Z

UOAF Events

Bs1: /* BMS-Specific */

2021-02-15T02:52:40Z

BMS-Specific

Starfury: Minor formatting and grammatical changes

2020-04-25T20:37:11Z

Minor formatting and grammatical changes

BibleClinger: /* BMS-Specific */

2020-04-23T19:09:17Z

BMS-Specific

BibleClinger: /* BMS-Specific */

2020-04-23T18:44:57Z

BMS-Specific

BibleClinger at 18:44, 23 April 2020

2020-04-23T18:44:36Z

BibleClinger at 18:41, 23 April 2020

2020-04-23T18:41:42Z

BibleClinger: /* UOAF Events */

2020-04-23T18:27:43Z

UOAF Events

BibleClinger at 18:25, 23 April 2020

2020-04-23T18:25:30Z

@@ Line 89: / Line 89: @@
 |}
-#Wingmen shouldn't touch loadouts.
+#Wingmen shouldn't touch loadouts.  View your stores load via the mission briefing.
 #Wingmen shouldn't touch the flight plans.
 #Wingmen shouldn't change anything to do with ground troops.

@@ Line 58: / Line 58: @@
 #Each participant should listen to, understand, and follow the directives from the Event Moderator.
-#UOAF events are generally open to all members of the community who consider themselves ready, however, some restrictions may apply.
+#UOAF events are generally open to all members of the community who consider themselves ready, however, some restrictions may apply. Check out the UOAF Event [[SOPs/Minimum Competencies]].
-#All pilots who wish to attend an event should sign up on the event-specific RSVP sheet. Players can request slots or flights, but these will ultimately be decided on by the mission commanders.
+#All pilots who wish to attend an event should sign up on the event-specific RSVP sheet found in the [https://discord.com/channels/582602200619024406/603106314947919882 #Announcements] channel on UOAF Discord. Players can request slots or flights, but these will ultimately be decided on by the mission commanders.
 #Marshal and Briefing times must be respected.
 #All participants will show up on time with all hardware and installations ready to go at or before event time.

@@ Line 80: / Line 80: @@
 |This is set by the mission planner, and should NOT be moved. Moving Bullseye while someone is in 3D can crash BMS.
 |-
-|5.1
+|5
 | rowspan="2" |Bandwidth settings for BMS is a complex topic. Clients should enter bandwidth values that reflect 70% of their download and upload rates. Clients need to enter a minimum of 4mb. If you don't enter the correct values, you will be asked to reconnect with the correct values. Please be courteous and get your Bandwidth values set correctly prior to Event Time.
 |-
-|5.2
+|6.2
 |}
@@ Line 90: / Line 93: @@
 #Wingmen shouldn't change anything to do with ground troops.
 #Bullseye shouldn't be changed.
 #Bandwidth
 #*Download Bandwidth should be set no lower than 4096.

@@ Line 1: / Line 1: @@
 ==Gameplay==
 {| class="wikitable" style="margin-left:5px; float:right; width:45%; font-size:10px;"
-!Rules
+!<u>Rules</u>
-!Explanation
+!<u>Explanation</u>
 |-
 |1
@@ Line 31: / Line 31: @@
 ##Wingmen should communicate with flight leads as required.
 ##Wingmen should stay off the radio unless it's absolutely necessary/required.
-##Package comms communication should be mostly limited to flight leads. (Some exceptions apply.)
+##Package communication should be mostly limited to flight leads. (Some exceptions apply.)
 #Going solo and doing your own thing, or directly trying to contradict the lead's plans and perform a mutiny, can result in you being uninvited from future events.
 #Flights should follow their assigned tasks, and not arbitrarily choose new missions for themselves.
@@ Line 38: / Line 38: @@
 {| class="wikitable" style="margin-left:5px; float:right; width:45%; font-size:10px;"
 |+
-!Rules
+!<u>Rules</u>
-!Explanation
+!<u>Explanation</u>
 |-
 |1
@@ Line 61: / Line 61: @@
 #All pilots who wish to attend an event should sign up on the event-specific RSVP sheet. Players can request slots or flights, but these will ultimately be decided on by the mission commanders.
 #Marshal and Briefing times must be respected.
-#All participants will show up on time with all hardware and installations ready to go at, or before, event time.
+#All participants will show up on time with all hardware and installations ready to go at or before event time.
 <div style="clear:both;"></div>
 ==BMS-Specific==
 {| class="wikitable" style="margin-left:5px; float:right; width:45%; font-size:10px;"
-!Rules
+!<u>Rules</u>
 !Explanation
 |-
@@ Line 91: / Line 91: @@
 #Bullseye shouldn't be changed.
 #Bandwidth
-##Download Bandwidth should be set no lower than 4096.
+#*Download Bandwidth should be set no lower than 4096.
-##Upload Bandwidth should be set no lower than 2048.
+#*Upload Bandwidth should be set no lower than 2048.
 <div style="clear:both;"></div>

@@ Line 72: / Line 72: @@
 |-
 |2
-|Flight plans are crucial to mission planning. Leave this to Flight Leads to manage their flight's loadouts.
+|Flight plans are crucial to mission planning. Leave this to Flight Leads to manage.
 |-
 |3
@@ Line 85: / Line 85: @@
 |5.2
 |}
 # Wingmen shouldn't touch loadouts.
-# Wingmen shouldn't touch the flight plans.
+#Wingmen shouldn't touch loadouts.
-# Wingmen shouldn't change anything to do with ground troops.
+#Wingmen shouldn't touch the flight plans.
-# Bullseye shouldn't be changed.
+#Wingmen shouldn't change anything to do with ground troops.
-# Bandwidth
+#Bullseye shouldn't be changed.
-## Download Bandwidth should be set no lower than 4096.
+#Bandwidth
-## Upload Bandwidth should be set no lower than 2048.
+##Download Bandwidth should be set no lower than 4096.
-<div style = "clear:both;"></div>
+##Upload Bandwidth should be set no lower than 2048.
 ==UOAF Pickup==

@@ Line 36: / Line 36: @@
 ==UOAF Events==
 {| class="wikitable"
 |+
@@ Line 41: / Line 48: @@
 !Explanation
 |-
-|Each participant should listen to, understand, and follow the directives from the Event Moderator.
+|1
 |It can take a very long time to get everyone into the server. The moderator has a plan to get everyone into the server and into the sim as fast as possible, but he needs your help.
 |-
-|UOAF events are generally open to all members of the community who consider themselves ready, however, some restrictions may apply.
+|2
 |Some sims can be complicated to operate for newbies, and there are many pitfalls. Usually for DCS and BMS, we require that people can take off, navigate, employ some weapons, fly something resembling a formation, communicate with lead, and land. If you can do this, and if you've flown in MP before, you should be good to attend an event. Nevertheless, UOAF reserves the right to request a checkride for any new attendant.
 |-
-|All pilots who wish to attend an event should sign up on the event-specific RSVP sheet. Players can request slots or flights, but these will ultimately be decided on by the mission commanders.
+|3
 |This sheet helps UOAF determine the amount of participants planning on attending a given event. We can't always secure people's wishes for which flights and slots they want, but we try our best to accommodate people. RSVP priority will be for Roster Members first and guests second with conflicts resolved by the Event Moderator.
 |-
-|Marshal and Briefing times must be respected.
+|4
 |The official event time is usually the briefing time. This is when the briefing needs to start in order for us to be on time. No one wants an unnecessarily long briefing. To that end, we have Marshal time, which is when everyone should begin gathering. You should be able to get into the server at Marshal time.
 |-
-|All participants will show up on time with all hardware and installations ready to go at, or before, event time.
+|5
 |It is crucial that we start the event at event time. If that is briefing time, then we need to begin briefing right at that point. All participants are expected to be ready. While we wish to be helpful, our official events are not tech sessions; we cannot be expected to solve people's tech issues with large events. Be respectful of the time other people are investing in this. Please test your hardware and setup prior to event time, preferably before event day. If you need assistance, ask before event day!
 |}

@@ Line 1: / Line 1: @@
 ==Gameplay==
+{| class="wikitable" style="margin-left:5px; float:right; width:45%"
 !Rules
 !Explanation
 |-
-|Each pilot should follow the directives of his lead, whether element, flight, or package.
+|1
 |Our events are large, and we need order so that we can accomplish our objectives in a timely fashion so everything doesn't descend into chaos.
 |-
-|Wingmen should try their best to fly visually with their lead unless he says otherwise.
+|2
 |A flight can't be effective if they are not coordinating. If you're doing your own thing, you aren't operating as a cohesive unit, and your flight lead can't use his flight's full potential to accomplish his task. If flights fall apart, the package will fall apart. Learn the basic formations. Leads will often be happy with Wedge or Finger Four formations if they don't specify.
 |-
-|Communication:
+|3.1
+|Depending on the situation, flight leads need to hear from their wingmen in order to understand what their wingmen are doing. If a wingman receives a launch warning from his RWR, for example, the wingman should immediately announce the launch using proper brevity if able. Even a simple, "2 Defensive SAM!" in the heat of the moment is better than nothing.
-*Wingmen should communicate with flight leads as required.
+|-
-*Wingmen should stay off the radio unless it's absolutely necessary/required.
+|3.2
-*Package comms communication should be mostly limited to flight leads. (Some exceptions apply.)
+|Radios in the F-16, and often other aircraft, operate in half-duplex. If you are transmitting, you can't hear. Also, multiple transmissions on the same frequency effectively jam that frequency, making no transmission clearly heard. It's very easy to lose transmissions or tie up the radio if you're communicating useless information. It's more important for leads to communicate than wingmen to give non-essential status information.
-|Radios in the F-16, and often other aircraft, operate in half-duplex. If you are transmitting, you can't hear. Also, multiple transmissions on the same frequency effectively jam that frequency, making no transmission clearly heard. It's very easy to lose transmissions or tie up the radio if you're communicating useless information. It's more important for leads to communicate than wingmen to give non-essential status information. Sometimes element lead speaks for the flight, such as when he is leading the "hot" element during a grinder.
+|-
 |-
-|Going solo and doing your own thing, or directly trying to contradict the lead's plans and perform a mutiny, can result in you being uninvited from future events.
+|4
 |If everyone is a leader, no one is a leader, and we descend into chaos. Leaders lead. Wingmen are extensions of their leads. This doesn't mean you can't question the lead if he gives an impossible order, or respond with "unable" to a directive that is clearly going to get you killed; just don't try to mutiny and hijack a flight for your own purposes.
 |-
-|Flights should follow their assigned tasks, and not arbitrarily choose new missions for themselves.
+|5
 |Roles within a package are often very important dependent upon one another. It's a team effort. A flight needs to focus on its objective and do it well. If your mission's task is ESCORT, don't fly off to strafe ground targets. Others are depending upon you.
 |}
 ==UOAF Events==