← Back to Apex Academia
APEX UNIVERSAL CONNECTIVITY BRIDGE

One bridge.
Every rig.

Coming soon · engineering scope

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.

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.

Console path

Use documented platform APIs, game exports, or approved capture hardware. Console support is gated by platform policy and game-specific adapters.

Wheel coverage

Normalize USB, Bluetooth, and approved wheel protocols without promising that every device exposes the same axes or telemetry fields.

Planned connection flow

01 · PAIR

Room code

Create a short-lived room code and approve the phone or desktop companion.

02 · CONSENT

Choose data

Select input axes and telemetry fields. No silent capture or MAC-address discovery.

03 · NORMALIZE

Map signals

Convert approved device events into a stable Apex input contract with quality flags.

04 · COACH

Use QI

Send bounded, explainable samples to Apex Academia without writing to the game or wheel.

PSVR2 path · local companion check

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 capabilityHTTPS, WebXR, and Gamepad APIsChecking…
Qurmmius companionLoopback OpenXR/SteamVR healthNot checked
Session gateExplicit consent before pose/inputConsent required

Browser capability check is running…

Start the native companion only when you are ready to test the physical headset.

What this avoids: no MAC-address discovery, console memory access, anti-cheat bypass, account automation, or game-file writes. If the companion is not running, use the normal WebXR-capable desktop browser path or the EraWeaver desktop preview.
Open EraWeaver VR scene →

The bridge verifies the runtime; enter the headset session from the EraWeaver scene in the launcher-created desktop Chrome window.