Session charts, lap tables, and stats come from Le Mans Ultimate's session result XML. MyLMU can only show what the game exports — when fields are missing, it is usually an LMU export limit, not a MyLMU bug.
Two common situations cause incomplete data:
- Data gaps — LMU does not write tyre wear, fuel, virtual energy, or other per-lap fields for the full session (common in multiplayer, or when you leave the server early)
- Driver swaps — multiple drivers share one car; each upload typically includes resource data only for laps that driver was in the car
Lap times and sectors are often still present when resource fields are missing.
Understanding data gaps
Per-lap fields can be missing or cut off for several reasons unrelated to driver swaps.
Multiplayer export limits
In some multiplayer sessions, LMU exports lap times and sectors but omits tyre wear, fuel, and virtual energy for the entire race. When those fields are missing, Overview KPI cards, Charts series, and Lap Data columns for those metrics are hidden.
Early exit (DNF, DQ, None)
If you leave the server before the session ends — finish status DNF, DQ, or None — LMU stops streaming per-lap data when you disconnect. You may see:
- Lap times and sectors only up to your last completed lap
- Tyre wear, fuel, or energy missing from your exit onward — or entirely, if you left early
- Gaps that look like import errors but reflect missing game export after you left
This applies to solo and driver swap sessions alike.
How missing fields appear
When tyre wear, fuel, or virtual energy is missing from the imported laps, MyLMU hides that metric instead of showing empty values:
- Overview — average fuel/VE and most-worn tyre KPI cards appear only when that data exists
- Charts — fuel, virtual energy, and tyre wear charts appear only when that data exists
- Lap Data — fuel, VE, and tyre wear columns appear only when that data exists
If all three are missing, a short note on Overview explains that LMU currently omits them from some multiplayer exports. On Lap Data, the same explanation is on an info icon next to the table title.
Lap times and sectors may still be present.
| Situation | What happens |
|---|---|
| Multiplayer, no driver swap | All three fields often missing for the whole session — those KPIs, charts, and columns are omitted |
| Driver swap | Resource data usually exists only for laps you drove; co-driver stints are empty in your file. Metrics still appear if your stints include that data |
| DNF, DQ, or None | LMU stops streaming when you leave the server; resource fields may be missing from your exit onward, or entirely if you left early |
There is no separate “data gaps” tab.
Driver swap sessions
In endurance races, multiple drivers can share one car entry. LMU records:
- Which driver was in the car for each stint (start/end lap)
- Team-level results (one row per car in standings)
- Per-lap data attributed to the car, not always cleanly split per driver
MyLMU detects driver swaps from the XML and shows a Driver Swap Session notice in the session header on Overview.
What may be incomplete in driver swaps
| Field | Typical issue |
|---|---|
| Tyre wear | Missing or only present for laps you drove |
| Fuel | Missing or only present for laps you drove |
| Virtual energy | Missing or only present for laps you drove |
| Top speed | May be missing per lap, especially on co-driver stints |
| Position charts | Plotted per car/team rather than individual driver |
| Gap to class leader | Hidden for driver swap race sessions |
| Some stint stats | Aggregated at car level; individual driver breakdown limited |
Each co-driver imports their own XML. Your file includes resource data for your stints; your teammate's file covers theirs. Position and chart labels use car/team names so you can follow the shared entry across the race.
Co-driver linking
If you and a teammate both use MyLMU, you can link co-driver sessions to merge stint schedules across separate uploads:
- Open your driver swap session
- Accept or send a link request to your co-driver's matching session
- MyLMU merges the most complete stint schedule from both files
Linking improves stint accuracy but does not guarantee complete per-lap tyre wear, fuel, or speed data for the full race — each XML still only contains what LMU exported while that driver was in the car (and only until they left the server, if they disconnected early).
If stint ranges look wrong after linking, contact support.
What still works
Sessions with data gaps or driver swaps are still fully imported. Most features work normally:
- Standings — full results grid (team/car entries in driver swap races)
- Lap times and sectors — when present in the XML
- Race Director — events, pits, penalties, and stint ranges
- Driver swap stints — who drove which laps (driver swap sessions)
- Notes, sharing, favorites — unchanged
- Session history — filter with the Driver Swap toggle
Rankings and Analytics
Driver swap sessions are handled differently in aggregate features:
| Feature | Behavior |
|---|---|
| Rankings | Driver swap races are excluded from skill and discipline calculations |
| Deeper Analytics | Laps from driver swap sessions are excluded from tyre wear, fuel, and lap benchmarks |
| Milestones | Count normally if the session is a valid multiplayer import |
This keeps career stats statistically consistent — a shared car entry is not treated the same as a solo drive. General data gaps in non–driver-swap sessions do not exclude a session from rankings unless other eligibility rules apply.
Getting complete driving data
Result XML is a session summary. For full per-lap inputs, traces, and GPS:
- Record telemetry in LMU (
.duckdbfile) - Upload to MyLMU Telemetry
- Link telemetry to the session
Telemetry is recorded per driving stint and includes throttle, brake, steering, speed, and tyre data at high frequency — independent of XML export limits and driver swap gaps.