On-screen touch
The Android game includes flight controls without an extra device.
Explore touch controlsThe input connection
Four commands. Familiar hands. A deliberate setup.
Start with touch on Android, or configure compatible physical input. A controller name alone is not a compatibility guarantee.

Choose the connection
The Android game includes flight controls without an extra device.
Explore touch controlsDetection, channel mapping and the platform all matter. Inspect every input before flying.
Follow the setup stepsUSB is a connection, not proof of joystick output. Named hardware validation remains pending.
Read the validation methodController field guides
Explore the Universal Controller update, including mapping, mode-aware throttle and explicit activation. Google Play publication of this update is not yet confirmed.
USB joystick, Bluetooth HID and compatible ExpressLRS Wi-Fi setups, with device and firmware requirements.
Choose your connectionMeasure travel, remove drift and distinguish manual collective from assisted and 3D throttle.
Calibrate your sticksKeep a saved baseline, inspect live input and resume deliberately after a disconnect.
Save and resume safelyEvidence reviewed 4 October 2026. Tested means a named device, connection and platform passed acceptance testing. Experimental means implemented with incomplete hardware validation. Planned means validation or implementation is still pending.
| Controller | Connection | Platform | Status |
|---|---|---|---|
| Xbox-style standard gamepad | USB / Bluetooth | Linux | ExperimentalHistorical Linux Bluetooth input test; current build hardware retest pending. |
| Standard PC / Android gamepads | USB / Bluetooth | Windows / Android | ExperimentalOS gamepad input implemented; each model and transport needs validation. |
| Generic HID gamepads & FPV radios | USB joystick / Bluetooth HID | Linux / Windows / Android | ExperimentalRequires joystick axes exposed by the OS. Manual mapping available. |
| RadioMaster / EdgeTX joystick radios | USB HID | Android / OS-exposed joystick input | ExperimentalRecognised by EdgeTX USB identity or joystick capabilities, not by name. Guided setup verified with a replayed Android event stream; physical model acceptance pending. |
| ExpressLRS joystick modules | Bluetooth HID / Wi-Fi joystick v1 | Android | ExperimentalRequires compatible module/firmware. Wi-Fi transport checked with mock firmware, not a physical transmitter; not every RadioMaster RF module supports it. |
| Custom input adapters | Wi-Fi (dh-controller v1 / paired v2) · USB serial (DHS1) | Android | ExperimentalFirmware examples compile; the UNO serial path passed a host protocol test. Paired v2 Wi-Fi boards are authenticated. No board has been flashed and flown yet. |
| Keyboard-style devices | OS-exposed USB / Bluetooth keys | Android / available key-input APIs | ExperimentalBindable key actions and paired digital directions implemented. Device-specific acceptance and accessible key events required. |
| PlayStation-style controllers | USB / Bluetooth | Supported gamepad APIs | ExperimentalOnly where the OS exposes a standard gamepad; model mapping varies. |
| MFi-compatible controllers | Bluetooth / supported wired | Supported Apple devices | PlannedApple build and hardware acceptance testing pending. |
| DJI FPV controller input | Device-specific USB | PC / device-dependent | PlannedNo DJI FPV model is certified in the current build. |
No current build device is labelled Tested without a completed physical acceptance run. A supported API is not a guarantee that every device using it will work.
Continue with controller guides, detection troubleshooting or the DJI compatibility explanation.
A useful distinction
The optional input lab can show commands received by your browser. It does not run the native physics model or certify a controller in the game.
Desktop builds remain in development. Android hardware still needs device-specific verification.
A browser illustration, not a hardware compatibility test. The interactive controls load when you open this panel.
Drag the sticks or connect a gamepad. See all four commands come alive. This lightweight illustration explains the controls; the simulator runs the full flight model.
Drag either stick with your mouse or touch. Focus a stick and use arrow keys.
Connect the device, press a button, then choose Gamepad or FPV Radio. Browsers may hide devices until you interact. Raw input stays on this device.
Detection starts when Gamepad or FPV Radio is selected.
Standard gamepads use a Mode 2 starting layout. Unmapped radios require explicit axis selection. Browser detection does not certify support in a native build.