MyLMU Logo
Documentation
Sign inGet Started
Getting StartedSessions Overview
Getting Started
Product Overview
MyLMU App
MyLMU Telemetry
MyLMU Coach (AI)
MyLMU Sync Agent
Sessions
Getting Started
Sessions OverviewImporting SessionsDesktop Sync Agent for SessionsLinking Telemetry to Sessions
Session History
Session Details
Import
Sync Agent
Analytics
Milestones
MyLMU Telemetry
Getting Started
File Library
Telemetry Viewer
Leaderboard
Teams
Plans & Limits
AI Coach
Troubleshooting
MyLMU Sync Agent
Getting Started
Sessions Sync
Telemetry Sync
Daily Usage
Troubleshooting
Privacy & Security
MyLMU Coach (AI)
Getting Started
Coaching Modes
Coach Features
Troubleshooting
Privacy & Terms
Teams
Getting Started
Team Dashboard
Sharing with Your Team
Discord & Alerts
Team Calendar
Profile
Plans & Limits
Rankings
Getting Started
Skill & Discipline
Placement & Tiers
Community Leaderboard
Driver Profiles
Sessions & Imports
Notifications
Plans & Limits
Troubleshooting
Community
Getting Started
Activity
Leaderboards
Friends
Friend Groups
Lap Records
Track & Car Stats
Weekly Meta
Overall Community Stats
Feature Requests
Privacy
Troubleshooting
Misc
Opening Settings
Account & Data Lifecycle
Profile
Notifications
Appearance
Feedback
Using the Documentation
DocsSessionsGetting StartedSessions Overview

Sessions Overview

How MyLMU Sessions works — from XML import to session detail pages, analytics, and milestones. Official MyLMU guide.

Last updated July 11, 2026

Summarize this page with AI

MyLMU Sessions turns Le Mans Ultimate session result XML files into a searchable race history with detailed per-session analysis.

What happens after import

  1. Validation — MyLMU checks file format, size, driver name match, and duplicates
  2. Parsing — standings, lap times, sectors, pits, and metadata are extracted
  3. Storage — the session is added to your history in Dashboard → Sessions
  4. Ready — open the session for full detail, or view aggregated stats in Analytics and Milestones

Main areas

In the dashboard you will find:

AreaPathPurpose
SessionsDashboard → SessionsYour full race history — browse, filter, and open sessions
Session detailClick any session rowStandings, charts, lap data, rivals, and notes
AnalyticsDashboard → AnalyticsCareer-wide performance trends
MilestonesDashboard → MilestonesLong-term achievement progress

XML vs telemetry

Sessions are powered by .xml result files — the official session summary LMU writes after every race, qualifying, or practice.

For high-frequency driving data (throttle, brake, GPS traces), you need separate .duckdb telemetry files. MyLMU can link them to a session so you can jump from results to the Telemetry Viewer.

See Getting Started with MyLMU for a full comparison of both file formats.

Next steps

  • Importing sessions
  • Session History — browse and filter your list
  • Session Details — what you see on a session page

Was this page helpful?

PreviousGetting StartedNextImporting Sessions

On this page

  • What happens after import
  • Main areas
  • XML vs telemetry
  • Next steps

Was this page helpful?

Documentation

  • Getting started
  • Product overview
  • Sessions
  • MyLMU Telemetry
  • MyLMU Sync Agent
  • MyLMU Coach (AI)
  • Teams
  • Rankings
  • Community
  • Misc

Product

  • Open dashboard
  • Sync Agent
  • Contact
  • Pricing
  • Changelog
  • FAQs
  • Branding

Community

  • Instagram
  • Community forum
  • YouTube
  • X

© 2026 MyLMU

•Privacy Policy•Terms of Service•Cookie Policy