Phone companion
Pair the phone to the desktop bridge with a one-time room code. The phone shows connection state, consent, and the last received sample.
A planned user-paired phone and desktop bridge for reading approved wheel and controller input, forwarding permitted telemetry, and giving Apex Academia one consistent connectivity path across PC and console ecosystems.
Pair the phone to the desktop bridge with a one-time room code. The phone shows connection state, consent, and the last received sample.
Use documented platform APIs, game exports, or approved capture hardware. Console support is gated by platform policy and game-specific adapters.
Normalize USB, Bluetooth, and approved wheel protocols without promising that every device exposes the same axes or telemetry fields.
Create a short-lived room code and approve the phone or desktop companion.
Select input axes and telemetry fields. No silent capture or MAC-address discovery.
Convert approved device events into a stable Apex input contract with quality flags.
Send bounded, explainable samples to Apex Academia without writing to the game or wheel.
Use this check on the Windows PC that has the official PSVR2 adapter and SteamVR. It confirms what the browser and a future native companion report; it does not emulate a headset.
Browser capability check is running…
Start the native companion only when you are ready to test the physical headset.
The bridge verifies the runtime; enter the headset session from the EraWeaver scene in the launcher-created desktop Chrome window.