UOAF Codex - User contributions [en]

Fragteam

2023-02-21T20:59:46Z

Streak: /* Fragging checklist */

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

 

==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
 
|}

==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.
 

===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.
 

===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)

 

==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

 

==Fragging checklist==

*For BMS refer to checklist at https://drive.google.com/file/d/1tsl-62ee1PFaK-0hCwd3OsNWwXBWhZlI/view?usp=share_link
*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?

 

==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."'''

 
==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__

UOAF Event Checklist

2021-01-11T21:15:09Z

Streak:

==Pre-Event Start==

#Bring up dedicated server/IVC [https://docs.google.com/document/d/1SFc83qfpqaHfD12ON8zRmH8EhCNq-42t8EX5kizQ8uc/edit# using instructions here]
##Verify or load the correct xxxpre file on server
##Start IVC Server
##Launch BMS
##Select Comm and host: “self” or “Host BMS Event”
##Navigate to Campaign/Saved and select xxxpre file
##Check max player setting equal or more than 30
##Select server location. Normally a transport ac on a remote location of the theatre as a training flight and in briefing status!
##Stop server by halting clock!
#Ensure [https://drive.google.com/drive/folders/1tdt4thujx8FQiXR8qefyIObfqOjwZVCB copy of event google form survey is made]
##Rename copy of previous event by changing filename and content header
##Click on Send, select link icon, select URL shorten and copy this link for later distribution.

==Event Start==

#Introduce event #
#Introduce Moderator/s
#Introduce Package Leader
#HW Readiness
##Run an Instant Action to ensure that your controls and Track-IR are functioning properly
##Restart BMS. You MUST restart BMS (since BMS 4.34)
#Look for new people, if so:
##[[General SOPs|Share SOPs link]] and [[SOPs/Minimum Competencies|minimum competencies]] into #saturday-bms-events - tell them to review it
##Upload/BW for connection
###'''Determine Upload Speed''' (<nowiki>http://www.speedtest.net</nowiki>), note megabits
###'''Convert upload speed to kilobits''', 1 mbps = 1000 kilobits, eg. 2 mbps = 2000 kilobits
#[https://docs.google.com/spreadsheets/d/183fqu-FcyYtvMTRD8Ohwxb4Zz_DkNK8--BI6hawyD7o/edit#gid=0 Share IVC/server IP and alternative IP] in #saturday-bms-events
##Copy the server up message from "Dog the Server Monitor" in #roster and share it in #saturday-bms-events
##'''Tell folks: If you encounter blue text or latency issues in the past or if they have a questionable connection to use the alternative IP''' [note to moderator: it's using Amazon Global Accelerator, the regular IP is not]
#Slots
##Fill Reserved Slots
##Make sure everyone is slotted, flight leads and package lead are happy
#Make sure the slot list in the signup sheet matches what's in game so that you can use this to tally attendance later OR use windows snipping tool to capture who is in the briefing room for a count of attendance.
#Handoff control to Package Leader

==Package Leader Briefing==

#Explain the Plan
#Answer Flight Leader questions
#GO over landing procedures
##[[Airport operations#Overhead break|Overhead break or...]]
##[[ATC Vector Visual#Normal Procedure|Visual Approach]]
#Final check on new comers: an experienced UOAF member should be in each flight.
#[[Radios#IVC Check|IVC checks]] in flight order, as per briefing (F1)

==Flight Briefing==

#Players move to Individual flight channels for briefing
#Flight leader explains the plan: motherhood, threats, weapons, tactics, contracts
#Answer questions

==Pre-Flight Procedures==

#Players return to Briefing Room
#Package Leader or Moderator/s answer any final questions
#Take 4 minute break and sort out any issues, "well be turning at X of the hour" where X is the minute

==After break: Moderator read SOPs==

#Please mute but do not deafen discord 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, use Instant action to check flight controls, then relaunch BMS and reconnect. '''Every time you enter 3D, you must restart BMS entirely.'''
#After you land and exit BMS or if you get knocked out, jump down into the debrief channel to chat with others.
#Recon a target in 2D to pre-load your cache and speed your load-in time
#"Double-click your flight and your seat and save your data cartridge."
#We will commit as Taxi, everyone click takeoff then taxi right now

==Moderator: Commit to 3D==

#'''Save the Campaign with the same file name'''
#Goal is to have the server in 3d 1 minute before the first player flight loads into 3d on a taxi star
#Put the server into taxi
##It will load the server flight into taxi 1 minute before the 1st player flight begins their taxi take off (T-7)
##'''Note that it goes off of the take off times of all the player slots.''' For those with early take off times it's not enough to x64 speed while sitting in the slot. They need to leave the slot and wait until an appropriate take off time
##Once the server enters 3D, it should automatically stop rendering, turning the BMS window a solid color (probably black).

==Post-game==

#Exit the game
##Press escape, count down from 5 seconds
##Press E, count down from 5 seconds
##wait for sound to indicate you are outside of the cockpit view, then wait for 2d
##If stuck, alt tab out and select "Force Rendering Enabled" on the D3D11 disabler. Now you should be able to see the menu, and correct accordingly.
##'''Save Campaign/mission to xxxpost'''
##Close BMS
##Download xxxpost.zip to UOAF drive in designated folder (xxx+1)
##Exit remote desktop (RDP)
##Shut down Instance, verify server stopped, sign out
#direct message each event attendee (using screenshot from before) with a link to the survey and a greeting like this: "thanks for attending UOAF xxx today! If you have a moment we'd love to hear your feedback on the event in this very short survey: LINK HERE it will help us improve our events, processes and cater them to your interests better. Thanks for your involvement in our community and please come again."
#Update [https://docs.google.com/spreadsheets/d/1P8MJnSn1SJuFYkH-hryECPAuh7ANcqJexjlmn8iHz_E/edit#gid=0 metrics here] after 24 hours or so
##Share summary of metrics and highlights to the #metrics-and-event-performance channel

==Debrief==

#Use windows snipping tool to capture count of people in the debrief room, this will feed into the metrics for debrief attendance.
#Verbal debrief: for each flight lead
##4-5 minute time box per flight.
##High level beats of the flight plan and outcome
##What went well, by callsign
##What we can do better next time, by callsign
#Tacview
##Thank people who attended, let them know the formal debrief is over now and they can leave if they want or stick around for fun times
##No timebox - optional part for those who want to stick around and shoot the shit.
##Unstructured "lets look at cool shit" part

[[Category:SOPs]]

UOAF Event Checklist

2021-01-11T21:06:56Z

Streak:

==Pre-Event Start==

#Bring up dedicated server/IVC [https://docs.google.com/document/d/1SFc83qfpqaHfD12ON8zRmH8EhCNq-42t8EX5kizQ8uc/edit# using instructions here]
##Verify or load the correct xxxpre file on server
##Start IVC Server
##Launch BMS
##Select Comm and host: “self” or “Host BMS Event”
##Navigate to Campaign/Saved and select xxxpre file
##Check max player setting equal or more than 30
##Select server location. Normally a transport ac on a remote location of the theatre as a training flight and in briefing status!
##Stop server by halting clock!
#Ensure [https://drive.google.com/drive/folders/1tdt4thujx8FQiXR8qefyIObfqOjwZVCB copy of event google form survey is made]
##Rename copy of previous event by changing filename and content header
## Click on Send, select link icon, select URL shorten and copy this link for later distribution.

==Event Start==

#Introduce event #
#Introduce Moderator/s
#Introduce Package Leader
#HW Readiness
##Run an Instant Action to ensure that your controls and Track-IR are functioning properly
##Restart BMS. You MUST restart BMS (since BMS 4.34)
#Look for new people, if so:
##[[General SOPs|Share SOPs link]] and [[SOPs/Minimum Competencies|minimum competencies]] into #saturday-bms-events - tell them to review it
##Upload/BW for connection
###2. '''Determine Upload Speed''' (<nowiki>http://www.speedtest.net</nowiki>), note megabits 3. '''Convert upload speed to kilobits''', 1 mbps = 1000 kilobits, eg. 2 mbps = 2000 kilobits
#[https://docs.google.com/spreadsheets/d/183fqu-FcyYtvMTRD8Ohwxb4Zz_DkNK8--BI6hawyD7o/edit#gid=0 Share IVC/server IP and alternative IP] in #saturday-bms-events
##Copy the server up message from "Dog the Server Monitor" in #roster and share it in #saturday-bms-events
##'''Tell folks: If you encounter blue text or latency issues in the past or if they have a questionable connection to use the alternative IP''' [note to moderator: it's using Amazon Global Accelerator, the regular IP is not]
#Slots
##Fill Reserved Slots
##Make sure everyone is slotted, flight leads and package lead are happy
#Make sure the slot list in the signup sheet matches what's in game so that you can use this to tally attendance later OR use windows snipping tool to capture who is in the briefing room for a count of attendance.
#Handoff control to Package Leader

==Package Leader Briefing==

#Explain the Plan
#Answer Flight Leader questions
#GO over landing procedures
##[[Airport operations#Overhead break|Overhead break or...]]
##[[ATC Vector Visual#Normal Procedure|Visual Approach]]
#Final check on new comers: an experienced UOAF member should be in each flight.
#[[Radios#IVC Check|IVC checks]] in flight order, as per briefing (F1)

==Flight Briefing==

#Players move to Individual flight channels for briefing
#Flight leader explains the plan: motherhood, threats, weapons, tactics, contracts
#Answer questions

==Pre-Flight Procedures==

#Players return to Briefing Room
#Package Leader or Moderator/s answer any final questions
#Take 4 minute break and sort out any issues, "well be turning at X of the hour" where X is the minute

==After break: Moderator read SOPs==

#Please mute but do not deafen discord 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, use Instant action to check flight controls, then relaunch BMS and reconnect. '''Every time you enter 3D, you must restart BMS entirely.'''
#After you land and exit BMS or if you get knocked out, jump down into the debrief channel to chat with others.
#Recon a target in 2D to pre-load your cache and speed your load-in time
#"Double-click your flight and your seat and save your data cartridge."
#We will commit as Taxi, everyone click takeoff then taxi right now

==Moderator: Commit to 3D==

#'''Save the Campaign with the same file name'''
#Goal is to have the server in 3d 1 minute before the first player flight loads into 3d on a taxi star
#Put the server into taxi
##It will load the server flight into taxi 1 minute before the 1st player flight begins their taxi take off (T-7)
##'''Note that it goes off of the take off times of all the player slots.''' For those with early take off times it's not enough to x64 speed while sitting in the slot. They need to leave the slot and wait until an appropriate take off time
##Once the server enters 3D, it should automatically stop rendering, turning the BMS window a solid color (probably black).

==Post-game==

#Exit the game
##Press escape, count down from 5 seconds
##Press E, count down from 5 seconds
##wait for sound to indicate you are outside of the cockpit view, then wait for 2d
##If stuck, alt tab out and select "Force Rendering Enabled" on the D3D11 disabler. Now you should be able to see the menu, and correct accordingly.
###'''Save Campaign/mission to xxxpost'''
###Close BMS
###Download xxxpost.zip to UOAF drive in designated folder (xxx+1)
#direct message each event attendee (using screenshot from before) with a link to the survey and a greeting like this: "thanks for attending UOAF xxx today! If you have a moment we'd love to hear your feedback on the event in this very short survey: LINK HERE it will help us improve our events, processes and cater them to your interests better. Thanks for your involvement in our community and please come again."
#Update [https://docs.google.com/spreadsheets/d/1P8MJnSn1SJuFYkH-hryECPAuh7ANcqJexjlmn8iHz_E/edit#gid=0 metrics here] after 24 hours or so
##Share summary of metrics and highlights to the #metrics-and-event-performance channel

==Debrief==

#Use windows snipping tool to capture count of people in the debrief room, this will feed into the metrics for debrief attendance.
#Verbal debrief: for each flight lead
##4-5 minute time box per flight.
##High level beats of the flight plan and outcome
##What went well, by callsign
##What we can do better next time, by callsign
#Tacview
##Thank people who attended, let them know the formal debrief is over now and they can leave if they want or stick around for fun times
##No timebox - optional part for those who want to stick around and shoot the shit.
##Unstructured "lets look at cool shit" part

[[Category:SOPs]]