UOAF Event Checklist

From UOAF Codex
Jump to navigation Jump to search

(optional) fix weather on frag if using custom weather maps

  1. Install weathermaps locally, download here https://drive.google.com/file/d/1Tv1gQQlAAoNRp5vVEXZcc7P3FJZQVnW5/view?usp=sharing and extract to `C:\Falcon BMS 4.35\Data\Add-On NTO Polar Vortex\Campaign` OR download this folder from the server: `C:\Falcon BMS 4.35\Data\Add-On NTO Polar Vortex\Campaign\WeatherMapsUpdates`
  2. Copy the nearest time weather fmap file from `C:\Falcon BMS 4.35\Data\Add-On NTO Polar Vortex\Campaign\WeatherMapsUpdates` to `C:\Falcon BMS 4.35\Data\Add-On NTO Polar Vortex\Campaign` For example, we fixed your frag on the server today by copying 11600.fmap to C:\Falcon BMS 4.35\Data\Add-On NTO Polar Vortex\Campaign because the campaign time is 1625.
  3. In weather, switch `weather model` to `Map Model`, select the fmap file in step 2, then make sure `"maps auto update" `is checked
  4. Save wth
  5. Confirm it worked by looking at the briefing text for weather forecast

Pre-Event Start

  1. Bring up dedicated server/IVC using instructions here
    1. Verify or load the correct xxxpre file on server
    2. Start IVC Server
    3. Launch BMS
    4. Select Comm and host: “self” or “Host BMS Event”
    5. Navigate to Campaign/Saved and select xxxpre file
    6. Check max player setting equal or more than 30
    7. Select server location. Normally a transport ac on a remote location of the theatre as a training flight and in briefing status!
    8. Stop server by halting clock!
  2. Ensure copy of event google form survey is made
    1. Rename copy of previous event by changing filename and content header
    2. Click on Send, select link icon, select URL shorten and copy this link for later distribution.

Event Start

  1. Introduce event #
  2. Introduce Moderator/s
  3. Introduce Package Leader
  4. HW Readiness
    1. Run an Instant Action to ensure that your controls and Track-IR are functioning properly
    2. Restart BMS. You MUST restart BMS (since BMS 4.34)
  5. Look for new people, if so:
    1. Share SOPs link and minimum competencies into #saturday-bms-events - tell them to review it
    2. Upload/BW for connection
      1. Determine Upload Speed (http://www.speedtest.net), note megabits
      2. Convert upload speed to kilobits, 1 mbps = 1000 kilobits, eg. 2 mbps = 2000 kilobits
  6. Share IVC/server IP and alternative IP in #saturday-bms-events
    1. Copy the server up message from "Dog the Server Monitor" in #alerts and share it in #saturday-bms-events
    2. 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]
  7. Slots
    1. Fill Reserved Slots
    2. Make sure everyone is slotted, flight leads and package lead are happy
  8. 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.
  9. Handoff control to Package Leader

Package Leader Briefing

  1. Explain the Plan
  2. Answer Flight Leader questions
  3. GO over landing procedures
    1. Overhead break or...
    2. Visual Approach
  4. Final check on new comers: an experienced UOAF member should be in each flight.
  5. IVC checks in flight order, as per briefing (F1)

Flight Briefing

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

Pre-Flight Procedures

  1. Players return to Briefing Room
  2. Package Leader or Moderator/s answer any final questions
  3. 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

  1. Please mute but do not deafen discord during the flight
  2. Use Shift-T to chat in game if you have technical issues
  3. 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.
  4. After you land and exit BMS or if you get knocked out, jump down into the debrief channel to chat with others.
  5. "Double-click your flight and your seat and save your data cartridge."
  6. We will commit as Taxi, everyone click takeoff then taxi right now

Moderator: Commit to 3D

  1. Save the Campaign with the same file name
  2. Goal is to have the server in 3d 1 minute before the first player flight loads into 3d on a taxi star
  3. Put the server into taxi
    1. It will load the server flight into taxi 1 minute before the 1st player flight begins their taxi take off (T-7)
    2. 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
    3. Once the server enters 3D, it should automatically stop rendering, turning the BMS window a solid color (probably black).
  4. DO NOT MINIMIZE THE RDP SESSION OR GAME INSIDE THE RDP SESSION. Keep RDP window open in windowed mode and in the background. Do not minimize it or a memory leak in BMS 4.35 will crash the server.
    1. You can look at task manager memory utilization to make sure the memory leak issue is not happening. IF you see it steadily increasing past like 35-40% the issue is happening and you need to make sure BMS is not minimized and RDP is not minimized.

Post-game

  1. Exit the game
    1. Press escape, count down from 5 seconds
    2. Press E, count down from 5 seconds
    3. wait for sound to indicate you are outside of the cockpit view, then wait for 2d
    4. 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.
    5. Save Campaign/mission to xxxpost
    6. Close BMS
    7. Download xxxpost.zip to UOAF drive in designated folder (xxx+1)
    8. Exit remote desktop (RDP)
    9. Shut down Instance, verify server stopped, sign out
  2. 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."
  3. Update metrics here after 24 hours or so
    1. Share summary of metrics and highlights to the #metrics-and-event-performance channel

Debrief

  1. Use windows snipping tool to capture count of people in the debrief room, this will feed into the metrics for debrief attendance.
  2. Verbal debrief: for each flight lead
  3. Flight leads: please update the claims tab on the signup sheet so we can track campaign metrics.
  4. 4-5 minute time box per flight.
    1. High level beats of the flight plan and outcome
    2. What went well, by callsign
    3. What we can do better next time, by callsign
    4. Update CLAIMS on signup sheet
  5. Tacview
    1. 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
    2. No timebox - optional part for those who want to stick around and shoot the shit.
    3. Unstructured "lets look at cool shit" part