Manufacturer-neutral input
Fanatec, Logitech, Thrustmaster, Moza, Simagic, Asetek, PXN, Hori, and generic USB wheels use the same axis/button check when the platform exposes them.
Hardware + telemetry coverage
Bring your wheel and your racing game.
Apex Academia is designed around normalized inputs, not a single wheel brand or a single simulator. Use the manufacturer’s supported driver on PC or the console’s native wheel support, then connect a documented game data output through the local companion.
What “every wheel” means here: any wheel that the platform and game expose as a supported HID, DirectInput/XInput device, or console-native controller can follow the same Apex setup flow. Live telemetry still requires a documented output, official plugin, approved bridge, or session export from the title.
One normalized contract
Adapters map steering, throttle, brake, clutch, gear, speed, RPM, tire, and fuel fields into one bounded schema for coaching.
Graceful fallback
If a title offers no documented live data, players can still drive and import a supported session export for post-run coaching.
Wheel input paths
| Path | Where | Status in Apex Academia | What you do |
|---|---|---|---|
| USB HID / GamepadStandard axes and buttons | PC | Diagnostic-ready | Connect the wheel, press Check wheel input, and bind controls in the game. |
| DirectInput / XInputLocal driver or bridge | PC | Adapter route | Run a reviewed companion adapter that maps the device to the normalized contract. |
| Console-native wheelPlatform-approved connection | PlayStation / Xbox | Input-native | Select the correct console mode and verify steering/pedal bars inside the game. |
| Separate pedals / shifterIndependent USB devices | PC or console | Profile-dependent | Bind each device in the title, then confirm brake and throttle travel while stationary. |
Telemetry paths for any racing title
| Title exposes | Best route | Coverage meaning |
|---|---|---|
| Documented UDP / JSONLive packets | Live adapter | Companion can listen on the documented port and normalize bounded samples. |
| Shared memory / local SDKPC-only process data | PC companion | Use a local, reviewed adapter; the browser still receives only sanitized samples. |
| Official plugin or approved bridgePlatform-supported integration | Bridge route | Follow the title/platform owner’s integration and keep credentials out of the browser. |
| CSV, replay, or session exportPost-run file | Import route | Review the run in Performance lab when live telemetry is unavailable. |
| No documented outputNo supported data channel | Input-only | Wheel input can still work. Apex will not scrape memory or claim live telemetry. |
Check a game’s path
Pick the platform and the data channel the game documents. This gives the safe route to use; it does not guess ports or promise unsupported access.
Choose a channel to see the safe connection path.
Searchable game catalog
Find your title before connecting telemetry. A status describes the safest currently documented path; it never claims live data when a game does not publish it.
Can’t find your game? Add it below so it is saved to this device and queued for an adapter review. Until a supported data path is verified, new entries are marked input-only.
Add a game
Add a title that is not visible in the catalog. This creates a local profile only; it does not scrape game memory or promise telemetry support.
The universal setup loop
Verify platform support
Use the platform’s official wheel mode/driver. Confirm steering, throttle, and brake bars move in the game.
Calibrate once
Center the wheel, match rotation, and set pedal travel. Save a profile for that title.
Select a data path
Enable the documented output or choose an approved bridge/export. Never guess ports or read game memory.
Normalize locally
Start the companion, pair the room code, and map the title’s fields to Apex’s bounded telemetry contract.
Check before driving
Move one input while stationary and confirm a fresh timestamp, speed, throttle, and brake sample.
Coach across disciplines
Save a clean baseline, then compare braking, traction, consistency, and energy management in any supported racing genre.
Common questions
Will a wheel work if it is not listed?
Usually, if the platform and game expose it as a supported controller. Use the wheel’s official driver/console mode and run the generic input check. A new adapter may be needed for proprietary drivers or unusual axis layouts.
Can you provide telemetry for every PC and console racing game?
We can provide a common adapter contract and a title-by-title integration path, but no honest system can invent data a game does not publish. Where live output is unavailable, Apex uses an approved bridge or session export instead.
Does the console need a PC?
Driving input does not. A PC or local companion is only needed when the title’s supported telemetry route requires a bridge or when you want a second-screen HUD.
What is the next engineering milestone?
Prioritize a small certified adapter set: one generic PC HID adapter, one documented UDP adapter, one session-export importer, then add title profiles with a visible compatibility status and test fixture for each.
Build input telemetry for an unsupported game
When a title publishes no live data, Apex can still capture wheel/controller input locally for coaching. This records steering, pedal/button values, timestamps, and device identity; it does not invent speed, RPM, tire, or lap data.
Connect a browser-visible wheel/controller first. For a console wheel, capture must run through the local companion bridge.
No capture saved.