MyLMU identifies which sessions belong to you by matching the driver name in the XML file to your Driver Name in Settings.
Driver swap sessions: Each co-driver imports their own XML file. Per-lap fields like tyre wear, fuel, and speed are typically exported only for laps while that driver was in the car — not for co-driver stints in the same file. See Driver Swaps & Data Gaps.
Exact match required
The name must match exactly — including:
- Case —
John Doeis different fromjohn doe - Spacing — extra spaces matter
- Suffix — if your in-game name includes
#1234, include it in Settings
No matching driver
If files are skipped with "no matching driver":
- Open Settings and check your current driver name
- Open the XML in a text editor and find your name in the
<Driver>section — look for<Name>Your Name Here</Name> - Set Settings → Driver name to match that
<Name>value exactly (case, spacing, and#1234suffix if present) - Import again
Special characters
MyLMU normalizes some apostrophe types (e.g. ' vs ') and ignores apostrophes when comparing names. Not all special characters are supported — accents, symbols, or unusual punctuation in your in-game name may prevent a match even when the name looks correct.
If your name uses special characters:
- Compare Settings and the XML
<Name>character by character - Try simplifying or adjusting the name in Settings to match the XML as closely as possible
- If imports still fail, contact support with your driver name and the exact characters from the
<Name>tag so we can help
Changed your in-game name?
If you renamed yourself in LMU but want to import older files:
- Temporarily update your driver name in Settings to match the old XML files
- Import the files
- Change your driver name back in Settings
This only affects how new imports are matched. Already-imported sessions keep their original association.
Multiple names over time
Import each batch with the matching Settings name. There is no way to import another driver's sessions into your account — only your own results are matched.
Related
- FAQs — detailed driver mismatch troubleshooting
- Duplicates & Troubleshooting