Difference between revisions of "UOAF Event Checklist"

From UOAF Codex
Jump to navigation Jump to search
Line 57: Line 57:
 
#All pilots should switch the clock to x16. (Don't forget to do this on your client if you're the admin.)
 
#All pilots should switch the clock to x16. (Don't forget to do this on your client if you're the admin.)
 
#Double-click your flight and your seat and save your data cartridge.
 
#Double-click your flight and your seat and save your data cartridge.
#Commit the server to 3D to '''Ramp'''.
+
#Commit the server to 3D to '''Taxi'''.
#Before T-00:06:00, switch the server to '''Taxi'''.
+
#Before T-00:06:00, switch the server to '''Ramp'''.
 
#Order all pilots to commit to 3D.
 
#Order all pilots to commit to 3D.
 
#Mute Discord
 
#Mute Discord
  
 
[[Category:SOPs]]
 
[[Category:SOPs]]

Revision as of 05:02, 31 July 2019

Event Start

  1. 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)
  2. For new comers
    1. Share SOPs link - tell them to review it
    2. Every flight should have an experienced UOAF member in it to avoid jankiness
    3. Upload/BW for connection
  3. Bring up dedicated server/IVC
  4. Share IVC/server IP in #saturday-events
  5. Fill Reserved Slots
  6. Introduce Moderator/s
  7. Introduce Event
  8. Introduce Package Leader
  9. Handoff control to Package Leader

Package Leader Briefing

  1. Explain the Plan
  2. Cover datalink procedures
  3. Comms if different from BMS briefing
  4. Answer Flight Leader questions
  5. IVC checks in flight order, as per briefing (F1)
  6. Final check on new comers: an experienced UOAF member should be in each flight.

Flight Briefing

  1. Players move to Individual flight channels for briefing
  2. Flight leader explains the plan
  3. Answer questions

Pre-Flight Procedures

  1. Players return to Briefing Room
  2. Package Leader or Moderator/s answer any final questions
  3. Take 3 minute break and sort out any issues.

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. We are only allowing one reconnect attempt per event. So make sure you verify everything works if you need to reconnect.
  5. GO over landing procedures
    1. Overhead break or...
    2. Visual Approach
  6. After you land and exit BMS or if you get knocked out, jump down into the debrief channel to chat with others.
  7. We will commit as Taxi
    1. If you have previously flown Ramp, safely commit while paused and switch to Taxi
    2. Be sure to cancel back to 2D
  8. Recon a target in 2D to pre-load your cache and speed your load-in time

Commit to 3D

  1. Save the Campaign
  2. All pilots should switch the clock to x16. (Don't forget to do this on your client if you're the admin.)
  3. Double-click your flight and your seat and save your data cartridge.
  4. Commit the server to 3D to Taxi.
  5. Before T-00:06:00, switch the server to Ramp.
  6. Order all pilots to commit to 3D.
  7. Mute Discord