Setup & first run
Getting video, telemetry, and overlays flowing into the headset.
Data the app expects
SK-FPV listens for several independent streams. Each is configured in its own file (editable later through the config web server). Defaults are shown below.
| Stream | Default endpoint | Purpose |
|---|---|---|
| Video (per camera) | UDP 5600, 5601, 5602 | One port per camera surface. |
| MAVLink | udp://0.0.0.0:14551 | Telemetry, mission download, command uplink. |
| Detections (ZMQ) | tcp://0.0.0.0:6600 | Object-detection overlay feed. |
| Geo targets (ZMQ) | tcp://0.0.0.0:6601 | External geographic targets. |
| Map tiles | HTTPS tile URL | Satellite imagery for the minimap. |
Video
Each camera in cameras.json binds to a UDP port and receives an H.264/H.265 stream. Point your aircraft's video transmitter (or your ground link, e.g. a WFB/RTP feed) at the headset's IP on the matching port. The first camera defined draws furthest back; later cameras layer on top. See Cameras & video for surface types and fisheye setup.
MAVLink
The flight controller connection is set in connections.json:
{
"mavlink": "udp://0.0.0.0:14551"
}
Route your autopilot's MAVLink stream to that port (typically through a router such as mavlink-router or MAVProxy). On connect, the app sends a heartbeat as a ground station, begins reading telemetry, and automatically downloads the mission. Waypoints then appear as targets.
set streamrate 30.
Map tiles
map.json holds the tile URL, the ground area covered, and the on-screen size. The default uses a satellite imagery tile service. Tiles are cached to disk (cache_size_mb) and memory (mem_cache_mb).
tile_url for a source you are licensed to use.
First run checklist
- Launch the app from the headset library. You start in Flight mode (
FLIGHTshown on the HUD). - Confirm video appears on the camera surfaces. If not, check the source is sending to the right IP/port.
- Confirm the HUD shows live values (airspeed, altitude,
SATS). If everything reads zero, MAVLink isn't connected. - Press Right stick click to recenter the camera surfaces in front of you.
- Press Menu to open settings and explore. The right hand still flies while the menu is open.
System requirements
- Meta Quest 3 (or compatible OpenXR Quest device), running at 90 Hz.
- A network path from your video/telemetry source to the headset (same Wi-Fi or wired bridge).
- Network permissions are granted by the app for receiving streams.