UOAF Codex - User contributions [en]

SOPs/Basic Requirements

2020-08-21T13:30:21Z

Starfury: /* General */ Minor reformat

==BMS==
'''''The following are general competencies expected of new and experienced players joining our community events.'''''

'''''If you have any doubts about being ready to fly, please reach out to any Roster member on our Discord server'''''
<br />

==='''''<big>BROAD STROKES</big>'''''===

*<big>Have you connected to a BMS server and verified that hardware and IVC work correctly?</big>
*<big>Can you take off, fly, pickle the chosen ordnance, and land afterward?</big>
*<big>Can you talk to us while you’re doing it?</big>
*<big>Can you follow directions and generally be a mature human being?</big>
*<big>Can you keep your lead in sight?</big>
*<big>If so, you’re probably good. Read below for specifics.</big>

<br />

===''GENERAL''===

*Basic English Language skills - enough to understand commands and be able to call out threats, report status/location, etc.

===''HARDWARE''===

*'''Stable''' internet connection with >2MBps up/down. BMS is sensitive to connections with poor stability; one client with an unstable connection can ruin an event.
*Working speakers/headphones and microphone

===''SOFTWARE''===

*BMS 4.34 installed and verified as working
*IVC verified as working prior to the event
*Discord installed, voice communication verified as functioning

===''BMS UI KNOWLEDGE''===

*Comms menu (connect to a server)
*Basic 2D Map interface functions
**Find packages/flights in the ATO
**Select flight and seat in a package
**Set PPTs
**Set STP Lines
**Recon targets, assign Precision Steer Points
**Basic DTC setup, including Comms Plan and IFF Plan
*IVC use (F1/ F2/F3)
*Commit Ramp/Taxi/Runway selection

===''PILOT SKILLS''===

*Taxi and take off
*Basic navigation using HUD/DED/HSD and Nav STPs
*Landing (visual) - overhead break pattern recommended
*Maintain loose formation (keep Flight/Element Lead in visual range)
*Follow Flight/Element Lead instructions

===''AVIONICS KNOWLEDGE''===

*Read RWR
*Read airspeed, mach, altitude and time to waypoint/target on HUD
*Read/understand HSD
*Locate, lock, attack air targets with the FCR and both AIM-9 and AIM-120 missiles
*Locate, lock, attack ground targets with the FCR and TGP
*Change weapons using MFDs
*UHF/VHF radio usage

===''EVENT-SPECIFIC SKILLS''===

*Specific events may have additional technical proficiency requirements, to be outlined in the briefing document for that event

[[Category:SOPs]]

SOPs/Basic Requirements

2020-08-21T13:29:43Z

Starfury: Updated and reformatted Broad Strokes

==BMS==
'''''The following are general competencies expected of new and experienced players joining our community events.'''''

'''''If you have any doubts about being ready to fly, please reach out to any Roster member on our Discord server'''''
<br />

==='''''<big>BROAD STROKES</big>'''''===

*<big>Have you connected to a BMS server and verified that hardware and IVC work correctly?</big>
*<big>Can you take off, fly, pickle the chosen ordnance, and land afterward?</big>
*<big>Can you talk to us while you’re doing it?</big>
*<big>Can you follow directions and generally be a mature human being?</big>
*<big>Can you keep your lead in sight?</big>
*<big>If so, you’re probably good. Read below for specifics.</big>

<br />

===''General''===

*Basic English Language skills - enough to understand commands and be able to call out threats, report status/location, etc.

===''HARDWARE''===

*'''Stable''' internet connection with >2MBps up/down. BMS is sensitive to connections with poor stability; one client with an unstable connection can ruin an event.
*Working speakers/headphones and microphone

===''SOFTWARE''===

*BMS 4.34 installed and verified as working
*IVC verified as working prior to the event
*Discord installed, voice communication verified as functioning

===''BMS UI KNOWLEDGE''===

*Comms menu (connect to a server)
*Basic 2D Map interface functions
**Find packages/flights in the ATO
**Select flight and seat in a package
**Set PPTs
**Set STP Lines
**Recon targets, assign Precision Steer Points
**Basic DTC setup, including Comms Plan and IFF Plan
*IVC use (F1/ F2/F3)
*Commit Ramp/Taxi/Runway selection

===''PILOT SKILLS''===

*Taxi and take off
*Basic navigation using HUD/DED/HSD and Nav STPs
*Landing (visual) - overhead break pattern recommended
*Maintain loose formation (keep Flight/Element Lead in visual range)
*Follow Flight/Element Lead instructions

===''AVIONICS KNOWLEDGE''===

*Read RWR
*Read airspeed, mach, altitude and time to waypoint/target on HUD
*Read/understand HSD
*Locate, lock, attack air targets with the FCR and both AIM-9 and AIM-120 missiles
*Locate, lock, attack ground targets with the FCR and TGP
*Change weapons using MFDs
*UHF/VHF radio usage

===''EVENT-SPECIFIC SKILLS''===

*Specific events may have additional technical proficiency requirements, to be outlined in the briefing document for that event

[[Category:SOPs]]

Fragteam

2020-05-08T02:13:41Z

Starfury: /* Fragging checklist */ Added STP altitude check

This page contains the description, role and responsibilities, SOPs and process documentation for the UOAF fragteam.

<br />

==Current members==
{| class="wikitable mw-collapsible mw-collapsed"
!BMS
!DCS
|-
|Bibleclinger

DarkFib3r

Domestos

DrSlaughterRex

Foxy

Fumes

GasMan

Gusy

Krause

Nighthawk

Oirien

Wh1t3b0Y
|Abelian
Darkfiber

Domestos

DrSlaughterRex

Eagle

HellHound

Krause

Nighthawk

Oirien

Woody
<br />
|}

==Role and responsibilities==
The UOAF fragteam is a group of players, not necessarily Roster members, responsible for the creation and publication of the weekly BMS events. They also maintain documentation relative to best fragging practices, checklists, and other procedure necessary to maintain the quality of the generated events.
<br />

===Joining the fragteam===
Anyone can apply to be part of the fragteam; current members of the team assess the request, if necessary arrange training/instruction to ensure the applicant can frag events independently and with the required quality standard. This is not supposed to be a heavy, technical process, but simply a way to ensure quality.
<br />

===Competences===
Players intending to create missions/events at UOAF should:

*Be experts at using the mission editor and generating missions that are technically sound (meaning among other items, that waypoints, timings, takeoff order, server flight, etc are taken care of to minimize delays and headaches on game day)
*Be knowledgeable in the various missions, munitions, profiles, and airframes
*Constantly review the process and document best practices and The Fragging Checklist
*Be able to independently assemble products for briefing and planning (including maps, comms plans - as “standardized”)
*Try to spread the workload in the best way to avoid burnout
*Be capable of getting people up to speed on all of the above to expand the squadron’s fragging manpower (depending on how we decide to arrange things, this can be a requirement for fragging official events)

<br />

==Fragging workflow==

*During planning meetings, some time is set aside to discuss the two upcoming events, allocating as many people as possible to the two events (coordinator, package lead, server host/backup, and a fragger)
*The overall situation in the campaign should be addressed briefly to give some background and input to the fragging process
*After the meeting, the event coordinator ensures work proceeds on the event, and is responsible for finding replacements for key figures if need be
*The fragger and package lead can collaborate to hatch and refine a plan
*The fragger creates the mission and products according to sop/other resources established by the frag team, and finally posts event to discord (format TBD)
*This can be done individually or as a team effort (group fragging is encouraged for less experienced people)
*The frag can also be double checked by other fraggers, spontaneously or on request of the fragger
*Players RSVP indicating preferred slot, and are expected to read and process the briefing, in order to expedite briefing
*On game night, Package commander should be already aware of the tactical situation, possibly having planned with fragger ahead of time; package brief is kept to a minimum and flight briefs/question time can take most of the briefing time
*Mission is played, everyone has a good time
*Debriefing of event, feedback to fragger/pl/fl; keep track of issues and over time propose changes to fragging SOPs if necessary

<br />

==Fragging checklist==

*Does each steerpoint for each flight have a cruise air speed > 300 knots?
*Is the altitude for each steerpoint appropriate?
*Will the SEAD and/or escort be in front of the strikers in time to deal with threats?
*Is there at least 1 minute between each take off time?
*Does the escort and SEAD have enough time to work their steer points before strikers arrive?
*Is there at least 1 minute between each flight TOT on a co-located target?
*Are all co-located flight plan steer points deconflicted by either time on steer or altitude?
*Does every flight have an abort airfield that is safe and close to the FLOT?
*Are navigation steerpoints separated by a minimum of 20-30nm (Med Alt Only) + logical?
*Does the package have the means (weapons, terrain) to deal with every threat within range of the flight plan?
*Is there an AWACS fragged?
*Is the server flight fragged in a location to maximize the server's FPS performance?

<br />

==Cross-post to other communities==
We have been given permission to cross-post our event announcements into the following communities:

#<nowiki>#bms_flights in Falcon Lounge</nowiki>
#<nowiki>#mission-schedule on F4BMS Ready Room</nowiki>
##Note, we agreed to not use any notification groups or @ pings in posting here
##As there is rarely any posting in this channel, it's easy to see historical invites from other UOAF members

Simply re-post the Discord post from #announcements on our Discord into these channels above. It should be appended with a general note to include:

#Reminder to download 3rd party theaters, if applicable
#Entry criteria, typically "'''If you can take off, navigate, follow basic orders, communicate, and drop bombs, feel free to join us. Nobody needs to be perfect. Discord link can be found in the RSVP page above."'''

<br />
==To do:==
A few items have to be clarified for SOP inclusion:

*Weather: dynamic or not, i didn’t completely follow the discussion but i saw there are issues with jolts when the map changes
*Editing REDFOR: yay or nay?

[[Category:SOPs]]
__FORCETOC__

Squadron Process

2020-05-08T02:08:13Z

Starfury: Minor grammar fixes

=Team Charter=
[[File:UOAF_Roundel_clean2.png|frameless]]
{| class="wikitable"
|'''Squadron Vision'''
|'''<big>We aspire to be the most fun, accessible, humble, and passionate flight simulation squadron in the world</big>'''
|-
|'''Mission'''
|
*Hosting detailed, well thought-out, epic, seriously fun, and consistent BMS events
*Consider engagement with other sims
*Host training events and wiki
*Community outreach
**Open door
**Creating good relationships with community leaders, content creators
**Being the example which sim communities should aspire to
*Re-evaluation and re-assessment - data driven and collection
*Frequent involvement of the squadron in squadron direction and decision making
|-
|'''Roles + responsibilities'''
|'''Lead (Krause)'''
*Wringable neck for the squadron
*Prioritizes backlog of work
*Leads planning and squadron process as a servant leader
*Veto power
*Delegates powers to other patch members, and mentors/coaches them on execution
*Expert-level flight sim guy

“Fellowship of the wing” (DF, Gus, Force)

*Emeritus officers, serve as stakeholders for the squadron leadership
*Advise current leadership but not decide anything

'''Roster (“patched members”):'''

*Day to day moderators of the events/operations
**Discord
*Training
*Flight leading
*Package leading
*Responsible for supporting and improving SOPs
*Face of the squadron
*Meet minimum competencies
**Sharing resources to help people get to min competencies
*Giving input and voting on what we should do next
*Fragging/supporting events
*Event coordination (See below)

'''Frag team:'''

*Owns standards for the frag
**Improving and teaching those standards
*Generating the frags
|-
|'''Scope'''
|'''In:'''
*BMS events
*Open to other types of gaming (e.g. DCS, IL2, Steelbeasts etc)
**Our values should apply to those games
*Cross-community events
*Content creation
**Mod development
**Videos
*Creating/supporting a wiki (resurrect codex)
*Everything on Discord
*Surveying and collecting metrics
*Server maintenance/expansion
*Website

'''Out:'''

*TeamSpeak (We can use it, but we want to move toward discord)
|-
|'''Values'''
|
*Mutual learning
*Being respectful
*Be an example to others
*Serious fun
*Team work
*Should accept/give feedback
*Expertise
*Continuous improvement
*Punctuality
|-
|'''Success criteria'''
|''How do we know if we are being successful?''
*We have a set of KPIs here which are collected after every event. We use this data to steer improvements in the squadron.
|-
|'''Risks/weaknesses'''
|
*
|-
|'''Motto'''
|''Sordida Unguibus'' “Dirty fingernails” - TBD for an alternative
|}

=Communication=
We use [https://discord.gg/jAyjpz2 Discord (click to join)] to communicate over voice, post and share events. We can also use TeamSpeak on demand at 74.91.123.42 pw: grits.

=Documents=
Please store all documents (including ACMI) on the [https://drive.google.com/drive/u/3/folders/0B01Wjtmo89sBb1J5Y2pKd2o2TWM UOAF google drive here]. '''Note that this is a public folder''', but can only be edited by the UOAF members google group which includes all patched members. IF you want to restrict access (e.g. confidential info), be sure to click the “share” button on the top right and tweak it so that only uoaf-members@googlegroups.com OR a specific subset of members can see it.

=Planning=

*We use [https://trello.com/b/tH9G6FFs/uoaf-team-board a Trello Kanban board] to manage our team work
*Each task (card) on the board represents a week of work or less
**Bigger tasks can be broken down into multiple cards
*Patch members can add tasks they want to happen in the backlog
**Patch members vote for the priority tasks
**Patch members should get others to vote for their tasks and generally get consensus
**Lead officers considers the squadron’s feedback and metrics, pulls tasks into the backlog
***Items at the top should be worked on first
**Patch members can/should work on tasks on their own initiative outside of the backlog if they want - we’re all volunteers here and no one is the boss :)
*Work happens continuously, and we meet every 2 weeks before the Saturday event to reassess our backlog, progress and what we can improve ([https://docs.google.com/document/d/1nPy_mjRFKDwJWMOmcScJXfQqwf6BZgyHvaEh7u4BrvU/edit See bi-weekly agenda and process])
*We discuss ongoing plans/work in #planning-and-strategy on Discord

==Event Planning==
Identify on a Trello card:

*Package commander: The guy who will lead the package.
*Mission fragger: Make the mission, test it, upload it to drive. Collaborate with others (especially package commander) to ensure quality. Make briefing and posting it.
*Event team
**Event Coordinator: Responsible for making sure the entire event is executed on time, with quality and overall delivery of the event.
***Making sure software and dependencies are up to date on the server
**Moderator: Responsible for running the event from a logistics point of view
***Remote desktop, putting server in, saving mission etc
***[[UOAF Event Checklist|Running checklists, pre and post]]
***Responsible [https://drive.google.com/drive/folders/1tdt4thujx8FQiXR8qefyIObfqOjwZVCB for collecting metrics afterwards]. Can be collected by backup moderator, but moderator ultimately responsible.
**Assistant moderator: Also present, and will fill in for the host if he’s not there. If he is there, will assist however possible.

=Groups=

==Google==

*Administered by groups.google.com
*Used for calendar invites, document on google
*UOAF-leadership can manage all groups

[https://groups.google.com/forum/#!forum/uoaf-members Uoaf-members] aka uoaf-members@googlegroups.com

*Who: All patch members.
*Have edit access to the google drive location (all can view)
*Includes “UOAF-leadership” (see below)

[https://groups.google.com/forum/#!forum/uoaf-leadership UOAF-leadership]

*Who: Officers/leadership team

==Trello==

*Trello participation is included [https://trello.com/uoaf/members in this team membership here]

=Funding=
UOAF uses a paypal business account under the email '''uoafdonations@gmail.com'''

The paypal [https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=SDFJRDJEYEDHG&source=url link for recurring monthly is here]. Members and stakeholders are suggested to donate to ensure continued operation of the squadron.

The paypal account is currently owned by Chris Krause. Any balance is held in reserve for voting by the squadron, any deficit is currently paid for out of pocket by Chris Krause.

Financial records of the paypal are to be shared with the community whenever requested.

=Voting in Patched Members=
Anyone can initiate a vote for someone to become a patched member. The goal of voting is to gain consensus on whether or not the person in question exemplifies the values of UOAF (see above) and also is taking on the list of responsibilities of a patched member on his/her own initiative (See above), with promise to expand those responsibilities.

We bias toward saying "No" than "Yes" and hold a very high personal conduct bar. Anyone who we can't say no to should have been a patch member already!

The squadron leader has veto power as with all things.

====Initiating a Vote====
Make a post in #roster-voting, following the template:
@Roster I'd like to nominate [@name] for roster!
[optional reason for nomination]
<nowiki>Respond to this with :goodvibes: if you think [he/she] should be one and :Disappointed: if not. </nowiki><br />
Then send an email to uoaf-members@googlegroups.com letting everyone know a nomination is starting. This is to give members who are not monitoring discord a chance to see the notification, and to make sure it doesn't get buried.

After 72 hours if complete consensus is made, the squadron leader or a designated 2nd will reach out to the individual and invite them to the roster - if they accept, we add them to the Discord @roster tag and make a hype post in #roster with mad emoticons.

Remember that they will need to be added to the Google group (Can be done by any leadership), and should also review and understand this page here on the Codex.

=Servers=

**Server database [https://docs.google.com/spreadsheets/d/10fiOLWnDxkIkypYJ02Ayl0EXV2-JpM8YW2UK5J2fvXE/edit#gid=0 is maintained here]
**There is also a link with credentials/RDP information in it, ask leadership for a link.

General SOPs

2020-04-25T20:37:11Z

Starfury: Minor formatting and grammatical changes

==Gameplay==
{| class="wikitable" style="margin-left:5px; float:right; width:45%; font-size:10px;"
!<u>Rules</u>
!<u>Explanation</u>
|-
|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.
|-
|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.
|-
|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.
|-
|3.2
|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.
|-
|3.3
|Sometimes element lead speaks for the flight, such as when he is leading the "hot" element during a grinder.
|-
|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.
|-
|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.
|}

#Each pilot should follow the directives of his lead, whether element, flight, or package.
#Wingmen should try their best to fly visually with their lead unless he says otherwise.
#Communication:
##Wingmen should communicate with flight leads as required.
##Wingmen should stay off the radio unless it's absolutely necessary/required.
##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.
<div style="clear:both;"></div>
==UOAF Events==
{| class="wikitable" style="margin-left:5px; float:right; width:45%; font-size:10px;"
|+
!<u>Rules</u>
!<u>Explanation</u>
|-
|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.
|-
|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.
|-
|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.
|-
|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.
|-
|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!
|}

#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.
#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.
<div style="clear:both;"></div>
==BMS-Specific==
{| class="wikitable" style="margin-left:5px; float:right; width:45%; font-size:10px;"
!<u>Rules</u>
!Explanation
|-
|1.
|Loadouts are crucial to mission planning. Also, BMS doesn't play nicely with multiple people editing the loadout of a flight at the same time. Leave this to Flight Leads to manage their flight's loadouts.
|-
|2
|Flight plans are crucial to mission planning. Leave this to Flight Leads to manage.
|-
|3
|This has a tendency to make BMS unstable.
|-
|4
|This is set by the mission planner, and should NOT be moved. Moving Bullseye while someone is in 3D can crash BMS.
|-
|5.1
| 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
|}

#Wingmen shouldn't touch loadouts.
#Wingmen shouldn't touch the flight plans.
#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.
#*Upload Bandwidth should be set no lower than 2048.
<div style="clear:both;"></div>

==UOAF Pickup==

*Guests are welcome to create and run pickup flights outside of main events.
*Guests can join or create a pickup flight by asking in Discord.
*Guests are expected to follow flight standards laid out in Gameplay SOPs.

==UOAF Roster==

*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.
*Roster members are expected to take flight leader and element leader positions during flights as required.

==UOAF Fragging / Mission Planning==

*Mission Planners who are creating event missions will be subject to DCS and BMS frag guidelines for mission quality purposes.

[[Category:SOPs]]