Difference between revisions of "UOAF Event Checklist"

From UOAF Codex
Jump to navigation Jump to search
(add and rearrange SOP)
Line 13: Line 13:
 
#* ''Procession of Command''
 
#* ''Procession of Command''
 
#* ''Who to add when in 3D''
 
#* ''Who to add when in 3D''
#Run a Quick Engagement to ensure that your controls and Track-IR are functioning properly
+
#Run an Instant Action to ensure that your controls and Track-IR are functioning properly
 
#IVC checks in flight order, as per briefing (F1)
 
#IVC checks in flight order, as per briefing (F1)
 
==Flight Briefing==
 
==Flight Briefing==
Line 27: Line 27:
 
#Use Shift-T to chat in game if you have technical issues
 
#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, reconnect, verify that your issues are sorted and rejoin. Use Instant action to check flight controls.
 
#If you have an issue close BMS and IVC. Get your issues sorted out, reconnect, verify that your issues are sorted and rejoin. Use Instant action to check flight controls.
 +
#We are only allowing one reconnect attempt per event. So make sure you verify everything works if you need to reconnect.
 
#Landings at airbases follow the overhead break.
 
#Landings at airbases follow the overhead break.
 
#After you land and exit BMS or if you get knocked out, jump down into an open channel to chat with others.
 
#After you land and exit BMS or if you get knocked out, jump down into an open channel to chat with others.

Revision as of 20:25, 12 January 2018

Event Start

  1. Bring up dedicated server
  2. Fill Reserved Slots
  3. Introduce Moderator/s
  4. Introduce Event
  5. Introduce Package Leader
  6. Handoff control to Package Leader

Package Leader Briefing

  1. Explain the Plan
  2. Answer Flight Leader questions
  3. Cover datalink
    • Hosting
    • Procession of Command
    • Who to add when in 3D
  4. Run an Instant Action to ensure that your controls and Track-IR are functioning properly
  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
  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. TeamSpeak will be muted 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, reconnect, verify that your issues are sorted and rejoin. Use Instant action to check flight controls.
  4. We are only allowing one reconnect attempt per event. So make sure you verify everything works if you need to reconnect.
  5. Landings at airbases follow the overhead break.
  6. After you land and exit BMS or if you get knocked out, jump down into an open channel to chat with others.
  7. We will commit as Taxi
  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. Commit the server to 3D
  3. Doubleclick your flight and your seat and save your data cartridge
  4. Commit taxi in flight order, as per briefing (F1)
  5. Mute Teamspeak