Difference between revisions of "UOAF Event Checklist"
Jump to navigation
Jump to search
Line 22: | Line 22: | ||
#Answer Flight Leader questions | #Answer Flight Leader questions | ||
#IVC checks in flight order, as per briefing (F1) | #IVC checks in flight order, as per briefing (F1) | ||
+ | #Final check on new comers: an experienced UOAF member should be in each flight. | ||
==Flight Briefing== | ==Flight Briefing== |
Revision as of 17:13, 28 July 2019
Contents
Event Start
- HW Readiness
- Run an Instant Action to ensure that your controls and Track-IR are functioning properly
- Restart BMS.
- For new comers
- Share SOPs link - tell them to review it
- Every flight should have an experienced UOAF member in it to avoid jankiness
- Bring up dedicated server/IVC
- Share IVC/server IP in #saturday-events
- Fill Reserved Slots
- Introduce Moderator/s
- Introduce Event
- Introduce Package Leader
- Handoff control to Package Leader
Package Leader Briefing
- Explain the Plan
- Cover datalink procedures
- Comms if different from BMS briefing
- Answer Flight Leader questions
- IVC checks in flight order, as per briefing (F1)
- Final check on new comers: an experienced UOAF member should be in each flight.
Flight Briefing
- Players move to Individual flight channels for briefing
- Flight leader explains the plan
- Answer questions
Pre-Flight Procedures
- Players return to Briefing Room
- Package Leader or Moderator/s answer any final questions
- Take 3 minute break and sort out any issues.
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.
- We are only allowing one reconnect attempt per event. So make sure you verify everything works if you need to reconnect.
- GO over landing procedures
- Overhead break or...
- Visual approach rules
- After you land and exit BMS or if you get knocked out, jump down into the debrief channel to chat with others.
- We will commit as Taxi
- If you have previously flown Ramp, safely commit while paused and switch to Taxi and cancel back to 2D
- Recon a target in 2D to pre-load your cache and speed your load-in time
Commit to 3D
- Save the Campaign
- Commit the server to 3D
- Doubleclick your flight and your seat and save your data cartridge
- Commit taxi in flight order, as per briefing (F1)
- Mute Discord