Safe connection wizard
Connect the console, wheel, and telemetry companion.
The console and game verify the wheel. The local companion receives only supported telemetry and forwards normalized samples to Apex. The web app never reads console memory.
Important: a wheel can work in the game even when the title does not publish live telemetry. In that case, use input-only coaching or a supported session export.
1 · Choose your route
Start by selecting the title and enabling its documented telemetry output.
2 · Complete the stationary check
Verify wheel input in the gameOpen the game’s controller page and confirm steering, throttle, and brake bars move. Calibrate and save the profile.
Enable the documented data pathUse the title’s UDP, data-output, official bridge, or session-export option. Do not guess ports or use memory readers.
Pair the roomStart the companion on the bridge computer, generate its room code, enter it above, then open the paired HUD.
Confirm fresh samplesWith the car stopped, move one input at a time. Drive only after the HUD shows a recent sample.
3 · If no telemetry arrives
Recheck the game’s documented output setting, companion gateway address, and room code. If the title has no supported output, Apex will keep the result as input-only or let you import a supported session after the run.