One overlay, every sim: how Rillence normalizes telemetry
iRacing speaks IRSDK, ACC speaks shared memory, F1 speaks UDP. Here's how we turn them all into the same channels.
Every simracing title exposes telemetry differently. To give you a single, consistent view, Rillence normalizes them all into one channel model.
The wire formats
- iRacing publishes via the IRSDK shared-memory interface.
- Assetto Corsa / ACC expose physics and graphics structs over shared memory.
- F1 24 broadcasts UDP packets you subscribe to.
- rFactor 2 / Le Mans Ultimate use an internal shared-memory plugin.
Each has its own units, sign conventions and update rate. Raw, they're impossible to compare.
A common channel model
Rillence maps every source into one schema — speed, throttle, brake, steer, gear, rpm, plus per-wheel tyre data where the sim provides it. Units are normalized (km/h, 0–100% pedals, signed steering), and everything is resampled onto a single time base.
The payoff: a lap from iRacing and a lap from ACC line up on the same delta timeline. You can finally answer "am I braking later in this corner than I was last week — in a completely different sim?"
That common model is also what keeps your history portable. Because everything lands in one open format, your data outlives any single title.