- iRacing
- .ibt
.ibt · iRacing
Analyse iRacing .ibt telemetry files
An iRacing .ibt file stores fixed-size records behind a header and a YAML session description. Wild Telemetry decodes it directly, with nothing to install, and uses the simulator's own lap counter, which is exact because it increments precisely at the start/finish line.
- Format at a glance
Format at a glance
| Extension | .ibt |
|---|---|
| Source | iRacing (disk telemetry) |
| Magic | None: detection is structural |
| Dependencies | No additional ones |
| Lap boundaries | Exact, from the sim's own lap counter |
| Distance accuracy | +0.10% and +0.08% against declared length |
| Units | Declared and converted: m/s, radians, m/s2, kPa |
How accurate is the lap distance?
Measured against the length iRacing itself declares: 3653.7 m against 3650 at Okayama, a 0.10% difference, and 4283.5 m against 4280 at the Red Bull Ring, 0.08%.
It is not free. The LapDist channel is discontinuous in three separate ways, and all three must be treated alike: the start/finish crossing itself, 60 Hz jitter stepping backwards by centimetres, and a one-off initialisation jump. The Red Bull Ring file contains 421 negative steps of which only 2 are real crossings; crediting a lap to each would turn a 12.8 km session into 1376 km. Any step the speed trace cannot justify is replaced by the speed-integrated one.
- The product
- FUJI
What you get when you open a session.
What it does not do
- An .ibt has no magic number, so the structure is checked instead. A live shared-memory dump carries the same header and would read as 1,852,796,192 records of noise: there is a dedicated fixture whose whole job is to be rejected.
- Other simulators go through the CSV export route, and it is worth checking case by case before promising anything.
Have .ibt files?
Tell us which logger you run and we will say whether we can open your files before you install anything. Answered by hand.