Aircraft or robot condition
Heading, position, link state, battery and other bounded platform information can be presented without moving command authority into the headset.
Meta Quest companion awareness
A spatial view of the mission. Not a second flight controller.
TacWing-X Quest Companion is designed to present authenticated platform state, localization integrity, tracks and shared world context in a separate awareness surface while the aircraft or robot remains controlled through its governed platform path.
TACWING XCompanion awareness
PlatformAircraft state
heading · battery · link
LocalizationIntegrity visible
valid · degraded · DR · lost
World stateTracks + geometry
source-aware shared context
AuthorityRead-only companion
no remote actuator path
What the companion can show
Bring the shared operational picture closer to the operator.
The companion layer is about awareness: platform condition, localization confidence, tracks and spatial relationships that are useful when the operator needs context beyond a flat telemetry list.
Know when position quality changes
The companion can surface whether localization is valid, degraded, dead-reckoning or lost rather than showing position as equally trustworthy at all times.
See persistent contacts and relationships
Visual tracks and federated world observations can be presented with source and freshness context instead of as anonymous markers.
Understand relative geometry
Home, aircraft and contact relationships can be displayed as bounded situational context for the operator.
Use more than one vantage point
ROS 2 or peer platforms can contribute authenticated observations to the shared picture while remaining authority-separated.
Keep important state visible
Selected mission events and integrity changes can be surfaced where the operator is already looking instead of being buried in another screen.
Authority boundary
Awareness can be distributed without distributing flight authority.
The Quest companion receives authenticated information. It is intentionally separated from the physical command path used by DJI, MAVLink or another platform adapter.
Read-only for physical actuation.
Opening the companion, pairing a headset or viewing a shared track does not grant the headset permission to command the aircraft or robot.
- Authenticated pairing and freshness checks protect the data plane.
- Stale companion state should stop being treated as current.
- Physical commands remain on the governed platform path.
- Native RC, autopilot and platform safety behavior remain authoritative.
Visual note: the diagram illustrates shared awareness across systems. It is not a claim that a Quest headset remotely controls every depicted platform.
Current boundary
Companion awareness is ahead of full immersive-product validation.
The architecture supports authenticated Quest companion state and cross-view awareness concepts. This page does not present unvalidated stereoscopic AR, world-registration accuracy or remote flight control as production capabilities.
What is deliberately not claimed: production-certified OpenXR flight control, autonomous engagement, remote actuator authority from Quest, or universal spatial registration across every platform and environment.
Connected system
Quest is one surface of the larger TacWing-X runtime.
Use the main product page for the edge C2 architecture or the ROS 2 page for the multi-platform observation federation model.