Sim and real, one progression.

One session format

Same shape, both halves.

Every session — sim or real — captures the same shape: corners, brake points, throttle traces, where time was lost and where it was found. The bridge is what lets a Tuesday night iRacing stint and a Saturday track day be compared on equal terms instead of treated as two different sports.

Shape vs intensity

Lap times do not transfer. Weakness shapes do.

A 1:34 on sim and a 1:34 at the real circuit are not the same number. Different reference lap, different setup, different sensor fidelity — the absolute intensity of the time does not transfer. What does transfer is the shape of a weakness: the corner where you brake too late, the apex you over-rotate, the trail-brake you release too early. Those shapes are platform-agnostic, and the bridge is what surfaces them as one weakness instead of two unrelated ones.

Sim to real

The work you put in on iRacing shows up at Spa.

You drive Spa on iRacing for two weeks of evenings. The bridge flags trail-braking-too-late at La Source as your top weakness; you attack the prescription drills. Two months later you are at the actual Spa for a track day and the mobile app captures the session. The bridge maps it back: progress on La Source trail-braking up 61%, retreated weakness now ranked 4th, new weakness flagged at the entry to Eau Rouge that the sim physics had not exposed. Four months of work, one report.

Real to sim

And the other way round, on the same logic.

The track day surfaces a weakness the sim never showed — say, mid-corner stability on long left-handers. The bridge translates the shape into a sim-equivalent drill on the best-matching iRacing session for the same circuit, and you get the prescription before the next track day. The work you do between events stays on-target instead of generic fast-lap chasing.

How it works

The pipeline, in three steps.

The bridge is not a black box. The shape of the algorithm is straightforward enough to describe; the work is in getting each step right.

1. Normalize. Every session — sim or real — gets reduced to the same canonical shape: the same traces (brake, throttle, steering, speed, time delta) sampled the same way along the same track-aligned reference, regardless of which platform produced it.
2. Detect weaknesses. The detector runs on the canonical shape, not on the absolute lap time. A weakness is a pattern — late on the brakes into T1, off-throttle too early at the apex, oversteer on exit — and patterns are platform-agnostic. The output is a ranked list of weakness episodes per session.
3. Match across platforms. When a session lands on the other platform, the matcher compares its weakness episodes to the most similar episodes on the previous platform. Matched pairs become a progression line on your driver profile; unmatched real-world episodes become new entries the sim physics had not exposed. The transfer report is the rendering of that comparison.