MyLMU - Telemetry & Stats Tracker for LMU (New AI Update)

MyLMU Telemetry v0.7.5
  • New Telemetry Leaderboard tab with global, friends, and team scopes. Filter by track, car, class, car, time period, weather (Beta), and session type.
  • Podium, ranked table, and viewer summary card with rank, percentile, and gap to leader; See Lap and Compare from any entry.
  • Per-file leaderboard visibility: public, friends-only, or private.
  • Public share links (Pro): anyone with the link can view a telemetry file in the browser (no account needed), read-only.
  • Dedicated lap viewer page when opening a leaderboard entry.

Changelog | support@mylmu.app

MyLMU Telemetry Leaderboard

Leaderboard Lap Viewer
 
MyLMU App v0.96

Session details​

  • Standings now show a Gap column vs the class leader (time deltas and laps down in races; pace gaps in qualifying and practice).
  • Sort standings by Sector 1 / 2 / 3 in addition to position, grid, and best lap.
  • Clearer Finish Time handling for DNF, DQ, and other not normal results.
  • New Race / Qualifying / Practice Charts tab with field pace visuals: best-laptime gap, ideal vs best lap, lap times, and laptime distribution (outlier and invalid-lap toggles).
  • Your Charts: improved drag a lap range to zoom, PIT markers on pit-entry laps, and clearer invalid-lap indicators.
  • Practice sessions unlock full analysis (standings, stats, Practice Director, etc.).
  • Rival comparisons in Lap Data now show per-lap deltas across lap time, sectors, and related metrics.
  • More accurate pit-stop counts on driver-swap races. (Thanks Arthur!)

Teams​

  • Add Trophy Room results from a shared session: pick a session to prefill the result form, or add from the team Sessions table.
  • Linked Trophy Room results open the source session details.

Documentation​

  • New MyLMU Documentation at /docs covering the App, Telemetry, Sync Agent, Coach, Teams, Community, Rankings, and more.
  • Docs search (⌘K/CTRL+K), light/dark theme, table of contents, page feedback, and Summarize with AI via external assistants.
  • Docs links from the site footer, landing page, and relevant dashboard areas.

Driver profile​

  • Improved activity heatmap and consistency layout on mobile and desktop.
  • On your own profile, the driver name links to Settings to edit it.

Friends & messages​

  • Unread message badges on friends and in the Friends menu.
  • Clearer message sidebar timestamps and styling.

Misc​

  • Sign out from onboarding if you need to switch accounts.
  • Fixed reference lap times for some tracks used in session details overview. (Thanks Tim!)
  • Localized Contact, Cookies, Privacy, and Terms URLs for supported languages.
  • Other minor fixes.
Changelog | Documentation | support@mylmu.app

MyLMU Documentation - Getting Started

New Session Details Charts
 
MyLMU Telemetry v0.7.6
  • Timeline ping: bookmark a moment on the scrubber (P), jump back with Shift+P, and clear with Alt/⌥+P.
  • Racing line Line Style can color by speed, fuel use, virtual energy use, tyre wear rate, brake temps, and tyre temps along the lap (with per-corner wheel pick for wear/temps).
  • Clearer Pit Wall view-tab layout across Inspector, Laps, Strategy, Thermal, Driver, Car, and Events.
  • More Pit Wall Strategy and Thermal charts: fuel / VE trends, wear per fuel and wear per VE, thermal trends, and stint overlay comparisons; drag-to-zoom on channel charts.
  • Fixed Pit Wall lap detection / segmentation edge cases for flying-lap scope.
  • Fixed Overview tab scrolling so the pane follows content instead of empty scroll past the end.
Changelog | Documentation | support@mylmu.app

wearrateping.jpg
 
Sync Agent feedback:
It takes awfully slow to sync sessions as it starts from scratch every single time. It will identify and upload just the last few sessions but it takes it forever to arrive at the conclusion that out of the 800 result files scanned it only needs today's 3. Then it proceeds to upload and analyze. Multiple progression bars in and out, most with false time estimates.
 
Sync Agent feedback:
It takes awfully slow to sync sessions as it starts from scratch every single time. It will identify and upload just the last few sessions but it takes it forever to arrive at the conclusion that out of the 800 result files scanned it only needs today's 3. Then it proceeds to upload and analyze. Multiple progression bars in and out, most with false time estimates.
You’re right the “Sync Existing Files” can take a while and we’ll try to improve it, but that is a one time operation in the Sync Agent, the automatic uploads (Folder watching with “Start with Windows”) is what the Sync Agent is made for, the perfect flow should be setting up the results folder and then never needing to check the sync agent app again. If you want to upload manually everyday instead, I suggest just using the upload dropbox on the website. All the processing happens on our servers so you don’t even need to have the computer/browser running after the upload part. Please also understand this is a free service we provide for thousands of users every month and while we strive to have the best service possible something’s are far from perfect.
 
I will test it as background process, caged with ProcesLasso to E-cores to make sure it doesn't interfere with poorly optimised main LMU.

I do understand it's free and of mind bending scope at that! But maybe it could get improved in accordance with 80/20 rule :)
 
And it seems the agent left in the background works more fluidly. I exited LMU soon after a race and and least 2 files were already processed.

That's not good:
"Tyre wear, fuel & energy data unavailable

A recent Le Mans Ultimate update stopped writing tyre wear, fuel, and virtual energy data to some session result files. We're sorry for the inconvenience — some stats on this session may appear incomplete. We'll display this data here immediately once it's available in game exports again.

Learn more about data gaps"
Tyre wear I understand but fuel?

BTW, one of the sections in mylmu pitwall shows "tyre" values with percentages and single slider axis with "15% worse than community average." I assume it's tyre wear for the given track or session and the only interpretation is that I'm overdriving?
 
Hi,

Don’t really understand what you meant for the unavailable metrics, we can’t really parse values if they are not produced by the game 😅. This happens on multiplayer sessions only, you can try an offline session and those metrics will show because they are written to the file. (https://mylmu.app/docs/sessions/session-details/driver-swaps-and-data-gaps#data-gap-banner)

For the “Deeper Analytics” those values are just the average for the community for a specific filter, we can’t infer any type of driving conclusion from those very basic session files values.
 
Hi,

Don’t really understand what you meant for the unavailable metrics, we can’t really parse values if they are not produced by the game 😅. This happens on multiplayer sessions only, you can try an offline session and those metrics will show because they are written to the file. (https://mylmu.app/docs/sessions/session-details/driver-swaps-and-data-gaps#data-gap-banner)

For the “Deeper Analytics” those values are just the average for the community for a specific filter, we can’t infer any type of driving conclusion from those very basic session files values.
Seccaz! Seccaz... Always assume my admiration for your project! :D I obviously directed that concern at S397. When did they slimify the data?
 
Seccaz! Seccaz... Always assume my admiration for your project! :D I obviously directed that concern at S397. When did they slimify the data?
Hey, I'm pretty sure this started with v1.3.3. Also keep the feedback/questions coming, we've already shipped some of your feedback and will continue doing so.
 
Nice!

I am going to be focusing on in-real-use problems and initial impression walls.

1. IMO your biggest potential is in telemetry without the need of Motec i2. But with that it might well be that you overestimate the people's ability to freely test your telemetry module by the simple fact of file size limitations and upload count limitations. Even with races below 1 hr people would have to either use Qualy only recordings or setup their recording to manual to catch a small file size with a representative lap in hopes it turns out below the limit of 20 MB.
2. You need to revisit what is THE BASIC setup adjustment workflow, not just provide a high number of graphs. Check out the description of this video for the brakedown of THE BASIC flow, ammending with RIDE HEIGHT as it's hugely impractical to do 'by replay camera', and outright impossible at Daytona.
3. Quality pass. Revisit axes labels and units. I'mn going to try to provide some examples later but just wanted to give you a hint. One of your graphs contains a chassis parameter in meters :) In case of missing data - clearly state "LMU doesn't output the data" or "Needs more laps to calculate."
 
Telemetry more task oriented:
Let's take the Pitwall - Car (should be renamed to Chassis and Suspension?). The first thing to me is 'Great. But what should I do with it?'
Even having some knowledge on setups I do not know...
With my so-so level of knowledge there are two main tasks for me in the Chassis area:
A1. Maximize top speed on straight by lowest possible ride height.
A2. Assure positive aerodynamic balance (RAKE ANGLE) by lifting the back a little.

In my attached example from Fuji:
A1. I don't the means to achieve A1 because I don't have FRH/RRH mapped to distance (locations on the track); I need to know where the front bottoms out on the track and how severely because I might make the decision to ignore a section of bottoming out to keep my straight line max speed.
A2. You might say it's fine as rake and aero balance are kind of the same. Suggestion: provide a typical aero balance for front and mid-engine cars separately as a reference.
3. Damper Velocity: Most of my high speed dampers work "at 0.5%" on average, low speed 99+%. Does that mean I go into my in-game setup and take out all the high speed damper values to 0? Can I do any meaningful adjustment knowing "my slow speed damping is 99+%"?

Staying with the subject of maximum speed:
It's one of the basics and easy to understand by most (WILL BE USED BY USERS) so I suggest adding this task as well. And you can do it better than most. Most creators just slap a colorful RPM plot. You can provide an overlayed graph with:
a. RPM
b. Speed
c. LONGITUDINAL ACCELERATION
As laid out by the venerable Aris from Kunos .... Can't find his video, here's a short explanation on motec by a real driver.
 

Attachments

  • irfan_20260803_143811.jpg
    irfan_20260803_143811.jpg
    121.3 KB · Views: 5
On the ride height:
1. I FOUND something useful on the Track map page - and I strongly insist the 'Overlays' in the lower right corner has low discoverability.
2. Still, for the task graphs are better. In fact gizmos with momentary values are always that - gizmos. Graphs should always be preferred as they are better for the purpose, and importantly, are not 'harder for newcommers'. See my above post about task-oriented telemetry workspaces.
 
Hey, thanks for taking the time on this.

On file size / Free limits
Free is intentionally tight (3 uploads / month, 20 MB = +/-15 min of recording) because telemetry is the expensive part to develop, store and serve. Pro is what covers that. If we kept adding Free telemetry capacity (more files, bigger uploads), we’d have to charge for things that are free today across the rest of MyLMU. So the trade-off is deliberate, free gets you a real look at the viewer, Pro is for full race/practice logs, unlimited uploads, no 20 MB limit, and other benefits. Maybe, in the future, we'll do a free trial approach, alongside the free usage.

For a first proper look, a short practice or manual record of one clean flying lap is enough. We’ll also look at making that “record one flying lap” path clearer in the Telemetry onboarding so people don’t bounce on the limit before they’ve seen the value.



On setup workflow vs more graphs
I agree. Having lots of charts isn’t the same as a "basic setup loop". This is actually the foundation for one of our next "Setup/Telemetry" updates.



On ride height specifically
You’re right that the Car tab histogram alone doesn’t answer “where does it bottom and how hard?”. The distance-based view already exists in Pit Wall -> Inspector -> Suspension (FRH/RRH vs lap distance), and on Track Map via the "Susp" overlay. Discoverability can be a problem, and you are right about that. We’ll improve that and lean harder on graphs for these workflows. Live overlays stay useful for scrubbing/live replay purposes, but graphs should lead for setup work.



On aero balance
We already track front/rear ride-height ratio at peak speed each lap, and how that shifts as fuel burns off (Pit Wall -> Car -> Aero Balance Shift). That’s a useful trend signal, but it’s not the same as publishing rake in mm or an absolute “target %.” I’m cautious about a single target for front versus mid-engine cars, since the right number depends on car, track, and downforce level, and a wrong published target could send people chasing the wrong setup. What we can do more usefully is make the stint trend clearer (increasing/decreasing as fuel burns) so you can see direction of travel even without an absolute reference. Open to figuring out a safer starting-point framing, including clearer rake if that helps.



On damper velocity
(Important clarification) those %s are time spent in low-speed vs high-speed shaft motion (threshold +/-25 mm/s, in line with how most damper dyno sheets split the ranges). On a relatively smooth track, 99% low-speed is normal, not a sign anything's wrong. It does not mean you should pull high-speed dampers to zero in the setup menu. That would be the wrong takeaway, and the UI should make that clearer. We'll tighten the copy/interpretation there.



On units
Fair. Ride height showing in meters is not how people think about chassis. "mm" should be there.



On a top-speed workspace (RPM + speed + long G)
Liked this a lot, and the motec video makes it clear. To be precise about the check, some drop in long G right after an upshift is normal and expected, since RPM falls to a lower point on the torque curve. What you're actually looking for is whether that drop is small and momentary versus a big flat spot, a big dip usually means you shifted early relative to where the torque curve wants you to, or the ratio gap between those two gears is large. So it's less "flat line across the shift" and more "how much does it lower, and does it recover fast." Speed-over-distance alongside it lets you compare that against a different shift point or gearing choice. Those channels are already in the data, packaging them as a proper gearing/Vmax task is a strong candidate for the kind of guided workflow you're describing. Full "calculate optimal shift RPMs from a torque sheet" is a separate, much heavier job.



As always, I appreciate the concrete feedback. That’s what actually moves the product. Can't promise to implement all of this, but we'll try. Keep this coming.

Cheers!
 
MyLMU App v0.97

Race schedule​

  • New Race Schedule in the dashboard: official multiplayer series, championships, and special events with day and month views, filters, and session detail.
  • Upcoming races on the home dashboard.
  • Reminders via in-app notifications, email, and a personal Discord webhook.

Sessions​

  • Personal session tags: create, rename, and delete tags; assign them from the sessions table; filter the list by one or more tags.
  • Charts tab: race pace box plot and smoothed race-pace charts.
  • Improved Session stats tab.
  • Clearer driver colors on overall session charts and more filters for the charts.

Analytics​

  • Analytics can combine race, qualifying, and practice into an All Types view.
  • Lap Times Explorer now its own page with clearer Type and Mode filters.
  • Some UI improvements in the analytics page.

Teams​

  • Lap record seasons: owners and admins create named date windows in Settings; Lap Records can switch between All-Time and a season board (Discord alerts cover both).
  • Delete team events (after the event has ended/cancelled).
  • Sort team lap records by date (default) and lap time; new lap record history.
  • Clearer team invite join page.

Documentation​

  • Docs home redesigned around a Get started task list and clearer browse-by-product navigation.

Profile & notifications​

  • Pro status shown on avatars in driver profiles and the notification center.

Onboarding​

  • Draft progress is kept when you leave onboarding for Terms or Privacy, then restored when you return.
  • Other onboarding improvements.

Misc​

  • Dashboard search matches common track aliases (for example Imola).
  • Updated reference lap times for Paul Ricard, Daytona, and Laguna Seca.
  • Refreshed favicon and app icons.
  • Other minor fixes.
Changelog | Documentation | support@mylmu.app

raceschedule.jpg
schedulenotifications.jpg
 
MyLMU Sync Agent v1.2.3
  • Introducing new Setups folder watching and management for future (Pro only) setups features.
  • Added translations for four languages (Polski, 한국어, 日本語, Nederlands).
 
MyLMU App v0.98

Setup Stash​

  • New Pro Beta Setup Stash: personal .svm library organized by track, car, and intent, with favorites, personal reference, versions, notes, and best lap.
  • Import from Sync Agent or upload manually; compare versions; edit values; send setups back to your LMU Settings folder.
  • Team Setups now with promote / push / pull between Stash and the team library.

Teams​

  • Team Talk: announcements (optional in-app, email, and Discord for Pro owners), pinned posts, seen-by counts, multi-channel live chat, private and read-only channels, @mentions, and event-linked channels.
  • Share setups, sessions, telemetry, events, and lap records into Talk with contextual reactions.
  • Insights view on Lap Records: record holders, recent breaks, top tracks, and clearer standings.
  • Game version on lap records and history, with a Version filter.

Sessions & analytics​

  • Optional weekly sessions digest email summarizing your imported race, qualifying, and practice activity.
  • Clearer session list filters and a Clear filters control.
  • Track pages: personal sector PBs, relative pace map, and lap pace distribution.
  • Wins, podiums, and similar race metrics no longer count DNF results.

Milestones & profile​

  • New and expanded milestones (including Laps Led, Comeback Wins, Class Specialist, streaks, and more) plus a Completion tab.
  • Session Showcase on your public driver profile: add, remove, and reorder eligible online race and qualifying sessions (also from session detail).

Notifications​

  • Redesigned notification center with clearer unread treatment and smarter activity copy.
  • Better email unsubscribe flow that returns you to the right Settings toggle.

Localization​

  • Chinese, Russian, and Ukrainian Dashboard UI locales added.

Misc​

  • Small dashboard polish (sidebar scroll cues, cleaner sign-out, home feature card).
  • Other minor fixes.
Changelog | Documentation | support@mylmu.app

setupstash.jpg
 
Back
Top