Why simulator at all.
The standard objection: simulators aren't realistic, real flying is what matters, why waste training hours on a video game? The standard reply: real flying produces crashes, crashes produce wrecked drones, and wrecked drones halt training. The simulator's job isn't to be realistic — it's to be the place where the irreversible mistakes become reversible.
Three reasons the cohort program uses simulators, ranked by impact:
The objection that doesn't hold
"Simulators aren't realistic, so they're not useful." This is true on the first half and false on the second.
Modern simulators (Velocidrone, Liftoff) approximate flight physics well enough that the stick-to-response mapping transfers. They don't perfectly model wind, GPS noise, or specific motor characteristics — and they don't need to. What transfers is the muscle memory of "stick movement → drone response", and that transfers because it's mostly a function of FC firmware logic, which the sims model accurately.
What doesn't transfer well: spatial perception at distance, real wind handling, the visceral attention level of flying real hardware. These need real-world flying. The simulator builds the foundation; real-world flying refines it.
For partner orgs considering whether to include simulator time in their training: yes. Even modest amounts (~5-8 hours) measurably improve early-flight outcomes. The cost is one laptop, one simulator license per trainee (~₱1,500), and the time. Less than one wrecked drone's repair bill.
Picking a simulator.
Five flight simulators are realistic options for cohort training in 2026. They're not equivalent. Velocidrone is the cohort recommendation for specific reasons; alternatives serve specific contexts. The single most important consideration is whether the simulator supports your real radio as a USB controller — without that, the muscle memory doesn't transfer.
The five worth considering:
− Graphics are dated; community is smaller than Liftoff's.
− Optimised for racing/freestyle, not survey-style flying. FC behavior is "FPV-feeling" rather than INAV-accurate.
− Limited tracks; physics simpler than Velocidrone/Liftoff; radio support varies.
− Pure racing focus; not aligned with survey training. Cohort doesn't recommend.
− Same as DRL — racing-only focus. Not for cohort training.
The cohort recommendation: Velocidrone. Three specific reasons:
- FC behavior closest to INAV. Velocidrone's flight model includes Position Hold, Angle, and RTH-style modes that match what trainees will use on the real cohort default drone. Liftoff's modes are more racing-oriented.
- Cohort exercise tracks available. The downloadable simulator pack includes Velocidrone-format tracks for the 14-exercise cohort library. Liftoff would require recreating these.
- Multiplayer mode tested for group sessions. Section 5 covers running cohort instructor sessions; Velocidrone's multiplayer has been tested with 12 trainees on a single network.
When to deviate from the cohort default:
- Use Liftoff if you have alumni who specifically want to develop racing/freestyle skills (small minority of alumni). The skills transfer back to survey work, but the sim emphasis is different.
- Use FPV.SkyDive if the trainee can't afford even ₱1,500 for the cohort license. Free is better than nothing — they'll get most of the basic stick-skill benefit, just with rougher physics.
- Don't use DRL or DCL for cohort training. Race-focused sims teach the wrong reflexes for survey work.
Hardware setup.
Connecting the radio to the laptop, installing the simulator, and verifying everything talks. The single biggest setup pitfall is using a gamepad or game controller instead of the actual radio — the muscle memory doesn't transfer. Use the radio you'll fly the real drone with, even if connecting it is annoying.
What you need:
- The radio you'll use with your real drone. EdgeTX or OpenTX radios (RadioMaster TX16S, BetaFPV LiteRadio, RadioMaster Boxer, etc.) all work as USB sim controllers.
- A laptop or PC. Windows 10/11 works best for cohort defaults; Mac (Intel and Apple Silicon) works with most sims; Linux works with some sims and not others.
- A USB cable matching your radio's port (most modern radios use USB-C; some older ones use micro-USB). Data cable, not charging-only — same as the FC connection issue from fc-setup.html Section 02.
- Modest hardware: 8GB RAM, integrated graphics from any chip newer than 2019, 5GB free disk space. These aren't graphics-demanding games.
Setup procedure (Velocidrone, Windows):
- Install Velocidrone from
velocidrone.com. The free demo is sufficient for verifying the setup; upgrade to full version once verified. - Plug the radio into the laptop via USB. Power the radio on.
- On the radio, select "USB Joystick" or "USB-Joy" mode (location varies by radio model — check your radio's manual). The radio's screen should indicate it's now in joystick mode.
- Open Velocidrone. In Settings → Controls, click "New Profile" and follow the calibration prompts. Move each stick to extremes when prompted.
- Test by entering a track. Sticks should respond as expected: throttle (left stick up/down), yaw (left stick left/right), pitch (right stick up/down), roll (right stick left/right) for Mode 2 radios.
When the radio doesn't connect
Three common causes, in order of frequency:
- Radio not in USB Joystick mode. Most radios default to USB Storage when plugged in (for SD card access). Switch the mode in the radio's USB menu. This is the #1 problem and the easiest to miss.
- USB cable is charge-only. Try another cable. The same issue from fc-setup.html Section 02 — many cables that came with phones don't carry data.
- Driver missing on Windows. Most radios use HID joystick drivers built into Windows; rare cases need a manual driver install. EdgeTX's documentation walks through this. macOS and Linux generally don't need extra drivers.
If the radio shows up in the OS as a "USB Joystick" or similar (Windows: Game Controllers panel; macOS: System Information → USB) but Velocidrone can't see it, the issue is in the simulator's controller settings — re-do the calibration in Velocidrone Settings → Controls.
Gamepad fallback. For trainees who don't yet have a radio (early in the program, before the build is complete), a gamepad can be used temporarily. Xbox One, PS4/PS5, and most generic USB gamepads work with all the sims listed. This is acceptable only for the first 1-2 hours of simulator time — pure stick familiarity. Once the trainee has a radio, switch to it. The muscle memory of stick precision and ergonomics differs significantly between gamepad and radio, and gamepad practice doesn't fully transfer.
Multi-platform notes:
- Windows: Best supported. All five sims run natively. Cohort default platform.
- macOS Intel: Velocidrone and Liftoff run natively. Some performance penalty vs Windows but workable.
- macOS Apple Silicon (M1/M2/M3): Velocidrone runs natively (recent Universal Binary releases); Liftoff via Rosetta 2 with minor stutters. FPV.SkyDive works in browser regardless.
- Linux: Velocidrone runs via Steam/Proton (works well). Liftoff has limited support. FPV.SkyDive works in browser.
- Tablets/phones: FPV.SkyDive only. Real radios connecting to mobile devices via OTG cables is hit-or-miss; not recommended for cohort use.
The exercise library.
flight-training.html lists six basic exercises for Stage 1. The full cohort library is fourteen, expanding into emergency recovery, advanced maneuvering, and survey-specific patterns. Trainees complete the first six during Stage 1; instructors layer in additional exercises based on observed weaknesses or to introduce specific scenarios.
The fourteen-exercise library, organised by category:
How to use the library:
- Stage 1 trainees complete A1-A6 in order, ~10 hours total. This is the cohort default.
- Stage 2-3 trainees who've moved to real flight return to the simulator for B1-B4 when those scenarios become relevant. Cohort instructors typically introduce these in week 4.
- Advanced alumni use C1-C4 for survey-specific practice and mission rehearsal. C4 is particularly useful before unfamiliar AOIs.
The downloadable simulator pack includes Velocidrone-format track files for each exercise. They're labeled with the exercise codes above so trainees can find them quickly.
Group sessions.
Cohort training runs simulator sessions for 8-12 trainees simultaneously. Coordinating that many people on one network requires structure: shared schedules, radio rotations if not everyone has their own yet, multiplayer Velocidrone setup, and observation rotations between flying and watching. Done well, group sessions are higher-yield than individual practice because trainees learn from observing each other.
Equipment for a 12-trainee group session:
- 12 laptops, OR one laptop per pair of trainees (rotation between flying and observing).
- 12 radios. One per trainee for best results; if not available, 6-8 radios with rotation works.
- One local network (WiFi or Ethernet) supporting Velocidrone multiplayer for shared tracks.
- One large display or projector at the front of the room showing the instructor's screen — useful for demonstrations and error-correction.
- Spare USB cables. Always more than you think — they fail at the worst moments.
Cohort default group session structure (60 minutes):
Pair-flying as a teaching tool
The cohort cell's pair-flying structure (introduced in flight-training.html) starts in simulator sessions. Trainees in the same cell sit at adjacent laptops, take turns flying and observing. The observer's role:
- Watch the flying trainee's screen, not just their hands.
- Note specific things the flying trainee does well.
- Note specific things they do less well.
- Switch roles every 10-15 minutes.
The observation role is itself useful for the observer's own flying. Watching another pilot makes their own habits visible to themselves, which they wouldn't notice while flying.
Cohort cells stick together in this rotation. Even outside formal sessions, alumni report that simulator practice with cell members is the most useful kind of practice — the social dimension keeps motivation up during the rote-practice exercises.
Common pitfalls in group sessions:
- Instructor flies most of the time. Tempting to demonstrate constantly, but the trainees need stick time, not more watching. Demonstrate the minimum needed, then step back.
- Trainees sitting silent. If a trainee is struggling but not asking for help, the instructor needs to notice. Cohort cells help here; cell members notice when one of them is stuck.
- Trying too many exercises in one session. One exercise per session works well. Two is sometimes acceptable. Three is too many — trainees feel rushed and don't develop competence in any of them.
- Skipping the closing reflection. Sessions feel "done" once practice ends, but the 5-minute reflection is where trainees consolidate the day's learning. Don't skip it.
Beyond Stage 1.
Most pages about flight simulators focus on the beginner case. The cohort experience is that simulators continue to be useful well past Stage 1 — for skill maintenance, mission rehearsal, equipment testing, and emergency-response refresher practice. Alumni who use simulators throughout their working life have measurably better outcomes than those who treat the sim as a Stage 1-only tool.
Four ways alumni use simulators after graduation:
Cohort 02 alumni patterns at the 12-month mark:
- Alumni reporting regular sim use (weekly during no-fly seasons): higher mission completion rates, fewer reported "rusty" returns to flying season, more comfort with new mission types.
- Alumni reporting no sim use after graduation: more "rusty" returns; one alumna who'd had no sim time in 10 months crashed during her first post-monsoon mission (recovered drone, but the lesson stuck).
The cohort 02 data isn't a controlled study — sim users may differ from non-users in other ways. But the pattern is consistent enough that the recommendation is real: keep the simulator installed; use it regularly; treat it as a tool, not a phase.
One specific recommendation for partner orgs running fleets: include simulator practice in the operations rhythm. A weekly 30-minute sim session with the team becomes part of the work cycle, not an extra burden. The cumulative effect on team flying skills is significant.