Lapmetry – Telemetry & 3D Analysis | AI Coach | Race Engineer | Spotter & Radar | Strategy | Fuel | Tyres | Overlays | Live Pit Wall

[Lapmetry]

Hi everyone,

I'm Alessandro, a solo developer from Germany, and Lapmetry is my telemetry, coaching and race-engineering platform for sim racing — for Le Mans Ultimate, ACC, Assetto Corsa and AC EVO. LMU is the sim where it can do the most, so this is where I post updates and read your feedback. This first post is kept up to date; the replies below carry the release notes.

https://lapmetry.com — a Windows app for capture, overlays and the race engineer; analysis in the app and in your browser.

Open beta: every new account gets full Pro for 90 days, all sims included. After the beta the core stays free permanently — all overlays, the Command Overlay, the race engineer, the full analysis of your own laps and the coach against your own best, on one sim of your choice. Pro adds the context: community references at your pace level, the training plan, the AI debrief, all sims at once. Free keeps detailed telemetry for 14 days (lap times and personal bests forever); Pro keeps everything.

In the sim​

• Command Overlay. One key (Ctrl+Shift+Space) opens Lapmetry over the running game — home, live, sessions, analysis, coach, race engineer, race widgets, community. Mouse, keyboard, wheel or controller. Run the game borderless or windowed.
• 26 race widgets as click-through windows: dash, delta & timing, sectors, stint history, inputs with TC/ABS lights, tyres & brakes, fuel & energy, session, G-force, radar, track map with the whole field, live coach, post-lap coach, the line, pit briefing, corner sheet, weather with forecast, race engineer — and the LMU-first set: relative, standings, traffic, duel, damage monitor, race control, rejoin & launch, pit monitor. Options and sizes per widget, "show in practice / quali / race", layouts saved per game and session type, presets to start with, and a sample view so you can set everything up before the game runs.
• Cockpit for a second monitor: the same readouts as a grid, several pages, seven templates from driver dashboard to pit wall.

Race engineer & spotter​

• The spotter calls cars alongside on the side it measured; in LMU it checks lap position, so no ghost calls on parallel sections at Le Mans or Daytona.
• The race engineer talks about fuel and energy, tyres against the car's real window, brake wear, damage and repair time, flags and penalties, gaps and trends, pit windows and undercuts, the one rival you are racing, and the weather. 64 kinds of calls in ten languages, four talk levels from off to chatty, every call switchable, a radio log of what he said and what he held back. He is silent in braking zones and when you are wheel to wheel.
• Co-driver: pace notes before every corner — braking force, gear, apex speed — finished before the brake point or not spoken at all.
• Voice is off by default; switch it on in the setup or under Settings → Audio, on any output device (headset, Sonar, VoiceMeeter).

Analysis​

• The 3D workbench: every session as a track model with camera flight, your lap against your best or a community reference as a replay with ghost, over 40 telemetry channels — speed, pedals, steering, gear, tyres (core and surface), brakes, suspension, ride height, wheel load, fuel and energy, hybrid, wind — the delta as a band under the track, a traction circle, and your onboard video in sync (the file stays on your PC).
• Corner workbench: 21 measurements per corner across braking, turn-in, apex and exit, against the reference.
• Your line on the real asphalt: LMU reports track edges and lateral position, so the line comparison draws the track at true width and shows the metres you left to the kerb.
• Race analysis: true pace in clear air vs. what traffic cost you, tyre degradation per stint, what each pit stop was worth, position story, final classification, a fact sheet (game version, aids, rules) and the setup you drove.
• Import old laps from ACC's and LMU's own recordings; unknown tracks are learned from your driving, corners included.
• Lapmetry AI answers questions about your own laps — fuel for a race distance, where you lose time — on Lapmetry's own server, not at an external AI provider.

Coach & training​

The coach tells you why you lose time, not just where: braked too early, let go of the brake after turn-in, coasted, waited for the throttle — 27 causes across every phase of a corner, each with your number against the reference, what it costs, and whether the fix is in your hands or in the car. For every corner: your line against the faster one, the telemetry, a replay of both laps in sync, the concrete instruction, the technique behind it and a drill with a target. The training plan gives you one focus per week, drills with hit rate and the trend over your last sessions. Free against your own best; with Pro against community references at your pace level (P50–P99, built from real captured laps).

Setups​

The library starts with your car and shows per track what you actually drove — with best lap and sessions. Import your files with a wizard, compare two to four setups (versions included) differences first, write a version straight into the game folder. The optimizer reads your sessions, shows what the car does in which corner, tells you whether that is the setup or your driving, and proposes one change plus alternatives — with the game's own values and the limits the game knows. Open for every account; the shop is not open yet.

Live pit wall & community​

• Pit wall on your phone or tablet: your telemetry live on lapmetry.com — delta, sectors, tyres, fuel, the engineer's calls. Broadcast a stint with one link; teammates and league watch without an account, and you can revoke it any time. Installable as an app, with optional push notifications.
• Leaderboards from captured laps only — nothing typed in, wet and traffic laps flagged, not hidden. Driver profile, friends, personal bests and monthly recaps as shareable cards for Discord.

The fine print​

• Windows app; analysis in the app and in the browser. Ten languages (EN, DE, ES, FR, IT, NL, PL, PT-BR, RU, UK).
• Your laps stay yours: everything stays on your PC unless you sync, the app's privacy page says what leaves your computer and when, no usage analytics. EU-hosted, GDPR.
• It's a beta — things will occasionally be rough, the changelog moves most days. Not affiliated with Studio 397 or MSG. Screenshots show the built-in demo data.

What I'm looking for​

LMU drivers who use it and tell me what's wrong, what's missing, and what an LMU racer needs that I haven't thought of — endurance racers especially. Thanks for reading; your feedback is the roadmap.

Alessandro

 

[Geperd]

Will try it out! Maybe it helps me finally gitting gud

 

[Lapmetry]

Update — five days on

Hi again,

Quick update on what's changed since Friday. Short version: 58 releases, twelve new overlays, and a couple of LMU bugs I'm not proud of. Starting with those, because if you tried it over the weekend you probably hit one.

What was broken (and is fixed)

• LMU lap times were off by one lap. Every lap was saved carrying the previous lap's time — which is why your last lap, usually the quick one, seemed to go missing. Fixed.
• The first laps of an LMU session weren't recorded at all. Lists started at lap 2 or 3. Fixed.
• LMU tracks were mirrored in the 3D view. The same circuit looked different depending on which sim it came from. Fixed — and the track surface is now drawn at its real width instead of assuming twelve metres everywhere, so your line no longer appears to run beside the asphalt.
• Also fixed: abandoned laps counting as personal bests, physically impossible times reaching the leaderboards, large sessions failing to upload, and importing old recordings filling your disk. Bad entries that already slipped through are cleaned up on update — including an 11-second Monza lap.

Sorry about those. Beta, but still.

Overlays: 13 → 25

The original post said thirteen widgets. There are 25 now, and LMU is the only sim that gets all of them — the others reach 15 to 22, and there's an honest matrix on the site saying exactly which widget gets data where.

New since Friday, LMU-first:

• Duel — the car ahead and your pursuer, with live gap, trend and sector comparison. You see exactly where you win and where you lose against that one car.
• Traffic — warns you before a faster class arrives, with class and time to contact. Silence is the normal state.
• Pit monitor — the approach with distance to pit entry, the stop as a running timer, and the stop estimate item by item, including the game's own recommendation.
• Standings — the whole field as a tower with class colours, gap to the leader, last lap, pit stops, tyre age and position arrows. Your row always stays in view.
• Damage monitor — your car as a silhouette with colour-coded zones, wheels and suspension, and the number that actually matters mid-race: repair time in seconds, before you reach the pits. While nothing has happened, the window stays calm.
• Race control — flags, penalties, pit limiter and track limits in one slim strip; colour only appears when there's something to report.
• Rejoin & launch — stopped off line it shows the gap to oncoming traffic; on the grid, the lights plus pedal targets for the start.

Plus: the input overlay got a rotating wheel with the real steering angle, the clutch, TC/ABS activity right in the trace and an FFB clipping bar. The track map shows the rest of the field. The weather widget has a real forecast timeline. And every widget can now be switched per session type (practice / quali / race) and have its modules turned on and off individually — what you switch off really disappears, and the window shrinks to match.

... and much more.

Where all that LMU data comes from

Beyond the shared memory, the app now also talks to LMU's own local REST API (localhost:6397). Nothing to install; it polls gated on game state, backs off when nothing changes, and never blocks the 100 Hz telemetry loop. That's what feeds the repair-time estimate, the pit-stop breakdown and the game's recommendation, brake wear, per-compound tyre stock and consumption, the lap history and the weather forecast — plus the field's energy levels, which LMU exposes for every car. That last one is off by default: gold for endurance strategy, a grey area sportingly, so it's your call.

Coaching

• The co-driver. If you want it, a voice calls each corner before you get there, read from the reference lap: how hard to brake, which gear, when to lift and coast, and on the highest setting apex speed and the power call on exit. Every call finishes before things get serious — nothing is said under braking, and it stays quiet in a battle. "Off" to "Full" in the settings.
• The Line — a ribbon that runs with you. Ahead lies the ideal line, coloured by what to do there: red brake, amber coast, green throttle. A bar across the track marks the braking point, and your own trail follows behind.
• The corner sheet — after a corner, that corner as a trace: speed, brake and throttle stacked, your run against the reference. It shows what a sentence can only claim.
• The pit briefing — while you're stopped: the session, how the car is doing, what to work on in the next stint.
• You now choose what you're measured against: automatic, your own best, a percentile step, or one particular driver's lap. And the live coach works on the free plan too — against your own best lap instead of staying empty.

The analysis got rebuilt

Honestly the biggest change: the session page is one connected workspace now.

• Your lap in 3D, scrubbable, with a freely orbiting camera, a chase view and top-down. Time loss, speed, throttle, brake, gear and steering can be painted straight onto the track — for time loss you see where you lose it, not just that you're behind.
• A ghost car running your reference on its own clock, so you watch the gap open instead of two cars driving glued together.
• Over 40 telemetry channels instead of three — steering, gear, tyres, brakes, suspension, fuel — with zoom into any part of the track, a readout bar under your cursor and a distance/time axis switch. LMU now also records clutch, tyre wear, suspension travel, ride height and wind.
• A corner workbench: 21 measurements per corner across four phases, with the spread over your laps and a clear verdict on where the time sits.
• A time-loss band across the whole lap where every section carries the same colour and number as on the map — click one, and map, chart and figures all point at the same place.
• Sector table with your best sectors and the theoretical lap, multi-lap overlay, CSV export, and career numbers from your race results (wins, podium rate, average finish, positions gained — plus per track).

Session sheets

Every session now carries a fact sheet (game version, driving aids, rules), for LMU a setup sheet — your car's setup as the game reports it — and for races the final classification with the whole field.

Import your old laps

You can now import laps from the recordings your sim writes itself, including sessions where Lapmetry was never running. In LMU you switch telemetry recording on once in the game; the app finds the files for you.

Try it without installing anything

New pages, all running live on demo telemetry in your browser:

• lapmetry.com/overlays — all 25 widgets over a real cockpit, with the sim matrix
• lapmetry.com/coaching — how the coach works, and what it deliberately never does
• lapmetry.com/faq — 40 questions, from sim setup to privacy

One thing I should be straight about

In my first post I said the free tier keeps "the full analysis of your own laps". I've since had to put a number on the storage side of that: on Free, a session's detailed telemetry is kept for 14 days (plus a few days' grace, with a warning in the cockpit before anything expires). Your lap times, sectors, validity and personal bests stay forever — what expires is the measurement curve, not the result. Everything else stands: all 25 overlays free, the full analysis and the coach against your own best, on one sim of your choice. And during the beta everyone has Pro anyway, so nothing expires for the next 90 days.

Still the same ask

LMU drivers who actually use this and tell me what's wrong. The race-craft overlays (duel, traffic, pit monitor, standings) and the race analysis are the newest and least-tested parts — I'd especially like to hear from people doing longer races whether the pit-stop and repair-time numbers match what actually happens in the box.

Alessandro

 

[Lapmetry]

Lapmetry v0.75.0 — Race Engineer & Spotter: an engineer who can stay quiet

Hi again,

Biggest single update since I opened this thread, and the one where LMU pulls furthest ahead of the other sims — so it gets its own post.

Lapmetry now has a spotter and a race engineer on the radio. The spotter calls a car alongside you before it is alongside you. The engineer keeps fuel, energy, tyres, brakes, damage, flags, gaps and strategy in view. And the part I spent most of the work on is the part you won't hear: he is built to shut up.

Desktop v0.75.0 / web v0.73.0. Runs locally from your own data — no account, no Pro, no cloud.

---

A spotter that reports is already too late

The call takes about a second to say, and the system's speech output needs ~145 ms before the first sound. By the time "car left" is out, the car is past your mirror.

So this one doesn't report — it predicts. The closing rate between two cars says when they will be side by side; if that is less than 0.9 seconds away, the call comes now. That doesn't optimise the latency away, it overtakes it. Lead time is adjustable, down to 0 for classic behaviour.

And on LMU it knows whether a car is even on your stretch of track.

At Le Mans, at Daytona and on the Nordschleife the circuit runs alongside itself. Anything measuring distance in space alone will call you a car that is a kilometre of track away, on the other side of a fence. Everyone who has used a spotter there knows the ghost calls.

LMU reports each opponent's lap position, so the parallel-stretch check is part of the geometry: not on your piece of track, not a neighbour — however close in metres. ACC and AC EVO report neither lap position nor per-opponent speed; there the prediction runs on my own derivation alone and ghost calls can't be ruled out. I'd rather write that than pretend the three sims are equal.

A side that has been called also stays called until it really is clear, and the all-clear waits a beat longer — otherwise one overtake becomes "car left", "clear", "car left", and a premature "clear" is the one call that steers you into someone.

---

The engineer: 64 kinds of call across 12 topics

Fifty rules in eleven families. Real examples from the product:

• Fuel and energy — "Three laps of fuel." · "We're 24 litres short to the end." · "Save 0.4 litres a lap — that costs you 2 tenths." · hypercars: "3 laps of energy." · "Save 2 percent energy a lap."
• Tyres — "Fronts: 9 degrees above the window." Against the window your car reports, not a generic GT3 scale.
• Brakes — "Pads at 11 millimetres — about 18 laps left."
• Car and damage — "Suspension: heavy damage, 28 seconds to repair." Before you reach the pits, not after.
• Race control — "Yellow in sector 2." · "Full Course Yellow. Slow down, no overtaking." · "Time penalty: 5 seconds."
• The field — "2.1 behind, he's taking 3 tenths a lap." Gaps with a rate, not a bare number.
• Strategy — "Box this lap — tyres." · "Pit window open — closes in 2 laps." · "Undercut works on Nakajima — worth 9 tenths."
• Session — "5 minutes to go." · "Last lap!"
• Pace — "1:43.2 — personal best."
• Weather — "Rain in about 12 minutes."

Every topic switches off on its own, and goes quiet by itself when your game doesn't provide the data behind it. Four talk levels; terse is the default — flags, penalties, fuel, pit stops. Off is genuinely off, and the spotter has its own switch.

Every kind of call has exactly one rank on one axis, so nothing has to be guessed in a conflict: spotter interrupts everything · critical ("wheel gone", "box this lap", "penalty") cuts into a sentence but never into the spotter · important (tyres, brakes, fuel, gaps) waits for a quiet moment and expires if it doesn't come · then answers, info, small talk. Discarded means gone — a call from two corners ago isn't information any more, it's a distraction.

---

The silence is the product



He holds his tongue in a braking zone — and those zones come from your own pedal work, not from a track map, so they work on a track nobody has mapped. Also when you're wheel to wheel (nobody in a fight is working on tyre temperatures), when the call is above your talk level, when it came too soon after the last one, when it's no longer true, or when the game doesn't provide the data.

And this is the part that matters: every one of those is written into the radio log with its reason. You read back the session — the calls he made, and beside them the ones he swallowed and why. You can see that on lap 12 he wanted to say something about your front tyres and let it go because you were running side by side.

The documented main complaint about tools like this isn't "it said the wrong thing", it's "I don't know whether it's still running". A silent tool and a broken tool look identical. This one shows you its silence.

---

"What this game provides" — measured, not claimed



No tool can know what a game delivers; it can only measure it. So there's no hand-maintained compatibility table deciding what you get — there's an observer watching what actually arrived in this session. Zeros don't count as measurements (an unwritten shared-memory field reads as 0, which looks exactly like data), a capability once confirmed survives torn reads and pit stops, and in the first seconds nothing is judged at all — that's the garage, not a poor sim.

If something is missing, the panel says "the game does not report it", and the rules needing it stay visibly quiet instead of silently.

Where LMU lands: of the eleven things the engineer works from, LMU delivers ten in full — spotter, parallel-stretch check, fuel, virtual energy, tyre temperature against the real window, brake temperature and pad wear, damage and repair time, flags/penalties/FCY, gaps with a trend, pit window and undercut. More than any other sim by a distance. The one it doesn't deliver is the rain forecast, which — genuinely unexpected — only ACC reports.

AC 1 and iRacing are deliberately absent: there the observer confirms so little he'd stay quiet more than he'd speak, and an empty window is worse than none.

---

Fine tuning

The defaults should mean you never open this. But there is: fuel reserve in laps (drivers think in laps, not litres), fuel maths safe / median / bold, minimum gap between calls, overall chattiness, braking-zone and wheel-to-wheel silence, spotter lead time and lateral range.

Engineer and co-driver share one voice now and no longer talk over each other. The radio-log overlay hides the spotter's calls by default — the spotter belongs in your ear, not your eye.

---

What I'm not claiming

• On ACC and AC EVO the spotter is structurally weaker than on LMU. Neither reports lap position or per-opponent speed.
• It doesn't get faster than ~145 ms. Most of that is the system's speech output. The compensation is the prediction, not shaving the delay.
• He doesn't know your opponents' strategy — he sees their gaps, stops and trend, not what's in their tank.
• Your own position in the spotter is up to 200 ms old on LMU, because it comes from the same data block as the opponent positions it's measured against. A fresher position of your own wouldn't be better geometry, it would be contradictory geometry.
• The history rules are built and stay quiet in this release. They need consolidated laps per combination, and I haven't built that consolidation yet. On me, not on your laps.

---

Hear him without installing anything



lapmetry.com/engineer

That page runs the real rule set on synthetic telemetry over a real LMU screenshot — same 50 rules, same queue, same sentences as in the game. Move the talk-level slider and watch the radio log change, including what gets held back. It is not a video.

You can also play the spotter calls in any of ten languages, spoken by the voice installed on your own machine — no voice actor, no audio files, no cloud. Calls carry keys, not sentences, which is why a new language is a translation rather than a studio booking. What you hear there is literally what you hear in the car.

---

What I'd like from you

Endurance drivers especially:

1. Does the spotter fire early enough at Le Mans and Daytona — and does the parallel-stretch check actually kill the ghost calls for you?
2. Is terse the right default? The radio log makes this easy to answer: read back a stint and tell me which calls you'd have wanted gone — or which ones in the "held back" column you'd have wanted to hear.
3. Do the strategy numbers hold up — pit window, undercut value, fuel to the flag? I'd like to know where they diverge from what actually happened in the box.

Full changelog: lapmetry.com/changelog

Alessandro

 

[Geperd]

Hi,
I've temporarily uninstalled it since it didn't save me disabling 'start with system'. If that is fixed I'll redownload it.
Also, I didn't have sector times shown in the app, just laptime.

 

[Lapmetry]

Hi,
I've temporarily uninstalled it since it didn't save me disabling 'start with system'. If that is fixed I'll redownload it.
Also, I didn't have sector times shown in the app, just laptime.

Thanks for taking the time to write this up instead of just walking away — that's genuinely helpful.

You were right about the autostart, and it was a daft mistake on my part: the app remembered that it had switched the setting on once, but not that you'd switched it off. So anything that wiped that little note — a reinstall, an update, a virus scanner — and it happily turned itself back on. Worse, if Windows refused the change, the switch still showed "off" while your PC kept launching it. No wonder you gave up on it. That's fixed in v0.75.1, which is out now.

The sector times puzzle me, though — they should be right there in the lap list next to the lap time. Were you looking at that, or at the overlay in-game? If it's the overlay: no widgets are switched on out of the box, you choose them in the Widgets gallery first, and that's not obvious enough. Either way I'd like to know which screen you were on.




Same update also takes some load off your CPU while you're driving. If you do give it another go and something's still off, just tell me — I'm one person here, and reports like yours are how this gets better.

 

[Geperd]

Downloaded again
It still instantly switches 'start with system' on again when switching out of the settings tab.
Any way to reimport telemetry and sessions again?
Edit: it also won't let me change the audio channel in Steelseries sonar - I like it on the 'chat' channel
Edit2: Race engineer/spotter etc not working in practice servers or not at all? I had not a single voiceline, all set to on and 'chatty'
Edit3: Sector times now show up properly!

 

[Lapmetry]

Lapmetry v0.76.0 — spotter now names the right side in corners, restore laps from the cloud, pick the voice output device​

Since v0.75.1 there have been three releases. Most of what is in them came straight out of this thread, so thank you — the reports were specific enough to find real bugs, including one I would not have gone looking for.

---

The spotter called the wrong side in corners​

This is the one worth reading about, because the cause was not obvious and it affected everyone.

The spotter measured where a car was in your car's frame of reference. In a corner that frame is the tangent, not the track. A car twenty-five metres behind you, on exactly the same line, therefore computes as being off to the inside:

Corner radius	15 m back	20 m back	25 m back
150 m	0.75 m	1.33 m	2.08 m
70 m	1.60 m	2.84 m	4.42 m
40 m	2.78 m	4.90 m	7.56 m

More than a lane width. So somebody genuinely 2.5 m to your left, closing in a right-hander, computed as +1.9 m — the wrong side of zero. The spotter called "right". Then as the car closed, the geometric error shrank quadratically, the sign flipped back, and one overtake produced the full sequence: car right → right clear → car left → left clear.

The other half of the same bug: a car sitting directly behind you in the tow was pushed sideways by the same maths and announced as a neighbour that was never beside you.

Fixed by measuring the bend of your own path and subtracting it, so the side is judged against the track rather than the tangent. The bend is measured through the exact same projection the opponent positions go through, which means the sign cannot drift apart between the two calculations — that mattered, because a mirrored radar was a real bug here once before.

Where the bend cannot be measured (session start, pit lane, walking pace) the call comes later rather than wrong. A wrong side is worse than a late one, because you act on it.

Worth noting for this forum specifically: LMU is the only sim that reports per-car lap distance, which is what lets the spotter throw out the "ghost" cars on parallel straights — Mulsanne, the Nordschleife, Daytona. On the others that check simply does not run, and the app says so in its capability panel rather than pretending otherwise.

---

Restore your laps from the cloud​

The sync only ever ran one way: up. Reinstall, swap a drive or move to a second PC, and your laps were on the web but the client knew none of them. This came up here as "Any way to reimport telemetry and sessions again?"

Settings → local storage → restore from the cloud. Two steps on purpose: first it tells you how many sessions and laps are missing, then you decide. Sessions already on disk are never touched — your local copy is the more complete one if they differ.

Two honest caveats:

• Telemetry can come back missing while lap times and sectors come back fine. Either the retention window has passed or it is outside your plan. The report tells you how many laps that affected instead of quietly leaving you to discover it.
• Sessions uploaded by very old client versions have no client-side identifier and are skipped, because without one they cannot be matched and would duplicate on every run.

---

Pick the device the voice speaks through​

Also from this thread: "it won't let me change the audio channel in SteelSeries Sonar — I like it on the 'chat' channel."

It could not, and the reason is structural. The app spoke through the browser speech API, which has no concept of an output device — no device selection, no stream to route. It goes wherever Windows sends the WebView process, which is not the app.

The voice now runs through the app itself and plays on a device you choose. Settings → Live Coach → output device. The list is whatever Windows reports, so virtual channels (Sonar, VoiceMeeter, VB-Cable) appear there like any other output — Windows treats them as outputs, so the app does too. Nothing is hard-coded for any particular product.

It applies to everything the app says: Race Engineer, spotter, co-driver and live coach. The app makes no other sound — no chimes, no alerts — so that really is all of it. The choice is stored by device identifier rather than name, so it survives reboots and replugging.

If the app cannot speak through the chosen device for any reason, it falls back to the system voice rather than going silent. A mute spotter is worse than one on the wrong channel.

---

Two smaller fixes​

"Start with system" showed on while it was off. Reported here twice, and the second report was the useful one, because the first fix only repaired half of it. Saving the choice worked; reading it back was blocked by a permission that had never been granted, the error was swallowed, and the switch fell back to its initial value every time you left and re-entered the settings tab. It now reads the real state, greys out while it does not know, and shows the reason if the read fails.

A damage call read out a placeholder word instead of a number. "Repair seconds seconds." The sentence always expected a repair estimate; the code only supplied one when the sim provided it. On LMU the estimate comes from the game's own web interface, so if that is not reachable you would have heard it too. There is now a separate sentence for the case without a time, in all ten languages.

That one turned into a wider sweep. Every one of the 64 things the engineer can say is now checked in all ten languages for two failure modes: a placeholder left standing, and — the quieter one — a word the catalogue does not know, which does not leave a visible marker but silently drops out of the sentence. That found a second latent case before anyone heard it.

---

Updating​

The app updates itself; Settings → version & updates checks on demand. Current version is v0.76.0.

Keep the reports coming, particularly the ones in the form "it said X and Y was true" — the spotter bug was found from exactly that kind of description, and it had been wrong in every corner since the feature shipped.

 

[Lapmetry]

It still instantly switches 'start with system' on again when switching out of the settings tab.

Fixed in v0.75.3. My first fix only repaired half of it: saving your choice worked, but reading it back was blocked by a permission the app had never granted itself. The error was swallowed, so the switch fell back to its default of "on" every time the settings tab was rebuilt. It now reads the real state, greys out while it does not know it yet, and shows you the reason if the read ever fails. Sorry for the second round on this one — your report is what caught it.

Any way to reimport telemetry and sessions again?

Yes, as of v0.76.0: Settings → local storage → restore from the cloud. It first tells you how many sessions and laps are missing locally, then you decide whether to pull them. Anything already on your disk is left untouched.

Two things to expect: lap times and sectors always come back, but telemetry may not if the retention window has passed or it is outside your plan — the report tells you how many laps that affected. And sessions uploaded by much older client versions are skipped, because they carry no identifier to match on and would otherwise duplicate on every run.

it also won't let me change the audio channel in Steelseries sonar - I like it on the 'chat' channel

It genuinely could not, and now it can — v0.76.0, Settings → Live Coach → output device.

The reason it was impossible: the app spoke through the browser speech API, which has no notion of an output device at all. No device selection, no stream to route. It just goes wherever Windows sends the WebView process, which is why Sonar could not get hold of it either. The voice now runs through the app itself and plays on a device you pick. Sonar's channels show up in that list like any other output, because that is what Windows reports them as — nothing is hard-coded for Sonar specifically.

It covers everything the app says: Race Engineer, spotter, co-driver and live coach.

Race engineer/spotter etc not working in practice servers or not at all? I had not a single voiceline, all set to on and 'chatty'

That should not happen, and practice is not the reason — nothing in the engineer looks at the session type, so a practice server is treated exactly like a race.

There is a built-in answer for this, which is faster than guessing: open the Race Engineer page and look at the radio log at the bottom, with the filter set to "Held back". Every call that was not spoken is listed there with the reason in plain words — "game does not provide the data", "session warm-up", "above your level", "in the pits", "braking zone", and so on. Whatever it says there tells us immediately where this is stuck.

If the log is completely empty, that is a different and more useful symptom: it means no calls were generated at all, rather than generated and held back.

One thing I would like you to try, because the answer is informative either way: switch the level from "Chatty" down to "Terse" or "Normal" and drive a few laps. It should not matter — "Chatty" lets more through than the other two, not less — so if the lower settings do produce calls and "Chatty" does not, that points at something specific I would want to chase down. I can test it tomorrow.

Also worth confirming: "Read aloud" switched on (below the level), and the capture actually running while you drive.

Sector times now show up properly!

Good to hear — that was the v0.75.1 fix. A lap with no sector clock used to record [0,0,0], which then poisoned the theoretical best time. Ungauged sectors are now skipped rather than counted as zero, and the lap lists show a dash instead of "0.00".

Thanks for reporting!

 

[Geperd]

Tried it in practice - I don't know if it's intended but seems to just throw all the voicelines at me at the finish line every lap. TTS is a bit hard to understand at times, I'll try another system voice.

 

[Lapmetry]

Lapmetry v0.79.0 — the LMU crash on entering a race, a spotter rebuilt against measured data, a cockpit for the second monitor​

Six days, 18 releases: desktop v0.79.0, web v0.80.2. Starting with the one that cost people a session.

---

The spotter says the side it measured, not the side it expected​

Continues the v0.76.0 post. All of it measured in real LMU sessions — Daytona, Porsche 963.

The pre-warning had never fired. It builds the closing rate from the previous tick and discards any span under 20 ms as noise; the capture loop ticks every 16 ms. Both numbers right on their own — together, the prediction was thrown away in every tick since the feature shipped. It now measures against the last real measuring point: first call moved from 5.4 m before overlap to 23.4 m. LMU-specific half: opponent positions sit in the 5 Hz scoring block, so in a 60 Hz loop the rate was zero eleven times and twelvefold on the twelfth.

Then, driving it, the prediction turned out to guess the side. It never looked at the lateral offset — only at how fast the longitudinal gap shrank — and took the side from the bare sign, skipping the doubt window a measured call must pass:

Prediction 17 warnings median 8.3 m arc error ±1.4 m
Measured 21 warnings median 3.8 m arc error ±0.3 m

A car is two metres wide: at eight metres that error is enough for the wrong side, at four it is not. 44 % of all warnings came from that branch. The lead-in for new cars is therefore gone — which walks back part of what v0.78.1 promised here, deliberately: a warning with a guessed side is worse than one half a second later, because it makes you pull into the car it warned about. The prediction stays for a car already announced, where it prevents a premature all-clear.

The side flipped on a doubt the spotter already knew. The window granted a car at 20 m up to 1.4 m of lateral offset as mere arc residue; the side check flipped at 1.1 m. Half the wrong calls lived between those two numbers — a car sitting quietly behind you on the left computes as moving right in a left-hander, so the spotter cleared left and warned right for a car that had not moved. Measured: 34 calls in 120 s, 10 of 17 warnings contradicting the previous side within four seconds. One doubt value now serves both. Same recording: 90 calls → 58, 18.2 → 11.8 per minute, side flips under four seconds from 12 to 7.

A warning that revoked itself after 263 ms — shorter than speaking both lines takes; 28 of 50 warn/clear pairs were under 900 ms. The clear only measured how long a side had been empty (200 ms), never how long the warning had been standing; plus the 250 ms minimum gap, that is exactly the 263 ms measured. A warning is no longer revoked while it still stands.

And the curvature estimate was blind: 171 samples of own path curvature, 152 of them (88.9 %) null, the rest sitting at the clamp. The support points came from the 5 Hz scoring — 12–16 m apart at 60 m/s, while the measuring window is 9–32 m wide, so no point ever fell inside. The path is now observed from telemetry (~90 Hz, 1.5 m apart), the origin still from scoring, so both run against the same clock. And a clamped value no longer counts as a measurement: a false "known" turns silence into a wrong call.

All of that is measured on recordings. The on-track half is what I would like from this thread.

---

The engineer talked without a pause on a fresh install​

@Geperd — "it seems to just throw all the voicelines at me at the finish line every lap" was a real bug, not the design. On a fresh install every numeric engineer setting read back as 0 instead of its default (Number(null) is 0, and 0 passes a finite-check). One of them is the cooldown factor, which multiplies every repeat interval — times zero. So there was no spacing between calls at all, and the finish line is where most of them come due at once.

Eight further confirmed findings in the radio path went with it: every call carried a four-second expiry regardless of its own rule (a pit call is valid twelve seconds — discarded after four, and since an unheard call keeps its lock, it then stayed silent for two minutes); the radio only pre-empted on a higher band, so one spotter call queued behind another and expired after 900 ms; and one Windows clock correction (NTP) could silence the spotter for the rest of the session.

On TTS: the app speaks through Windows' own engine, so the quality is whatever voice Windows has installed (Windows Settings → Time & language → Speech). Lapmetry lets you pick the output device, not yet the voice — say if a voice picker would help, and post here if you find a Windows voice that reads the calls well.

---

The cockpit is now a window of its own​

For the second monitor: a grid of the same readouts you know as overlays, freely arranged across several pages, seven templates from driver dashboard to pit wall, twelve saved layouts — one for the sprint, one for endurance. You pick the screen, full screen or not, and whether it opens with the game; capture starts and stops from there too. Two new performance settings came with it, the measured result printed underneath: 58.5 % → 18.6 % of one core on the test machine. The big item is not the frame rate, it is shadows and blurs.

---

Eight channels that lay in shared memory and never arrived​

Tread temperature, slip, wheel load, wear, clutch, DRS, hybrid/battery, and engine speed as a number. What that means for LMU:

• Tread temperature next to the core — the signed difference between them is the diagnosis. Hot surface with a cold core means you are overdriving them and patience helps; the other way round means cooked, and nothing helps.
• Wheel load in newtons is LMU-only. ACC's field is an AC1 leftover and is not filled — four zeros would be an invented measurement.
• Slip stays empty in LMU on purpose — memory holds patch and ground speeds you could derive one from, and a derivation standing next to a measurement without saying so is quiet invention.
• Hybrid, battery and regeneration are in the fuel calculator.
• The clutch was inverted between games — that hit ACC and EVO, not LMU (LMU reports pedal position, ACC engagement). If you drive both, you did not imagine it.

---

Shorter​

• The engineer talks about the car you are actually racing (v0.78.0): the rival's tyre age and fuel, whether he still owes a stop, which sector he takes out of you, and the moment he makes a mistake. Plus: stopped off track, is traffic coming or are you clear. "Am I catching him?" now works in every sim — that used to be LMU-only. Quiet by default, all of it switchable; live demo at lapmetry.com/engineer
• Setups, in beta: the app imports your setup files into a library, every value in plain language, two versions side by side, plus a diagnosis that says whether the cause is the setup or the driving — and tells you to leave the setup alone when it is the driving. LMU is the best case, structurally: the rF2 .svm writes KeySetting=<index>//<Label>, and behind the // is what the game itself shows ("−1.8 deg", "52.0:48.0"), so nothing has to be guessed. 49 real LMU files gave 88 proven scales — Corvette Z06 brake bias at −0.2507 % per step, R² 0.99994.
• Lapmetry AI on the site now works numbers out of your own laps — fuel for a race distance, where you lose time, a single corner — as cards, not prose. It runs on my own machine, not at an external AI provider, and the deterministic coach engine stays the authority.
• Settings in fourteen sections with a search that finds the setting, not just the section; assignable shortcuts; the telemetry rate visible at any time.

---

Updating​

The app updates itself; Settings → version & updates checks on demand. Current versions are desktop v0.79.0 and web v0.80.2, full list at lapmetry.com/changelog

Keep the reports coming — the whole spotter section above exists because people described what they heard against what they saw.

Alessandro

 

[Lapmetry]

Lapmetry v0.84.0 — Lapmetry over the game, a coach that tells you why, setups rebuilt​

Five days, ten releases: desktop v0.84.0, web v0.82.0. Most of the desktop app is new, so here is what changed for you — with pictures. (They show the built-in demo data, which is why they say "ACC" where yours will say "LMU".)

First: if 0.81.2 locked you out​

If you updated on Monday and saw "Licence invalid (expired)" with a start button that did nothing: that was a bug in 0.81.2, not your account. 0.81.3 fixed it the same day — update and you are back. Sorry for that one. Since then, whenever recording is locked for whatever reason, the app says so right where you are looking — status bar, start button, home screen, inside the overlays — together with the way out.

Lapmetry over the game​

One key (Ctrl+Shift+Space, changeable) opens Lapmetry on top of the running game: home, live, sessions, analysis, coach, race engineer, race widgets, community and the few settings you change mid-session. Works with mouse, keyboard, wheel or controller — map your buttons by pressing them. The game stays visible; run it in borderless or windowed mode, same as for the overlays.

While you are driving, the overlay shows only what counts in a race, and the home pane adapts: driving, in the pits, session over, no game. The race widgets pane is where you switch displays on and off, pick a preset (Minimal, Balanced, Engineer, Endurance) or arrange the widgets at true size — drag the box, the real overlay moves with it.

The coach tells you why — and what to do about it​

The old coach told you that you lose time in T7. The new one tells you why: braked too early, let go of the brake too soon after turn-in, coasted, waited too long for the throttle — 27 causes across every phase of a corner. Each one comes with your number against the reference, what it costs you in that corner, and whether the fix is in your hands or in the car. It also connects the dots: "late on the throttle because you braked too deep."

For every corner you get your line against the faster one with brake point, apex and full throttle, the telemetry, a replay of both laps in sync — and underneath, the concrete instruction with numbers, the technique behind it and a drill with a target for your next session. All of this works without an account or internet, against your own best laps.

Daytona drivers: the banking used to count as a corner, so the coach complained about your throttle in the tri-oval. Fixed — flat-out sections only get line and consistency feedback now.

The training plan replaces the to-do list: one focus per week, drills with a target and hit rate, your trend over the last five sessions, and what actually got better — with the number.

Overlays: set them up without the game running​

• Every widget now shows sample data while no telemetry is coming in — size, font and options can be set up before you launch the game.
• Widgets never shrink below their content any more, and the presets come in fitting sizes.
• Zoom, opacity, title bar, "show in practice / quali / race" and the content modules can be changed in the gallery, in the Command Overlay and while arranging.
• Second or ultrawide monitor? Pick it under Settings → Command Overlay → Monitor — overlays, layout editor and presets then all use that screen.

Setups, rebuilt — open for every account​

The setup area is out of the per-account beta: everyone has it now. The shop stays closed a while longer.

The library starts with your car: your setups per track, best lap and sessions, and every card tells you which setup you actually drove with. Importing is a wizard — car, track, files — with "only cars I drive" and "hide unnamed" (ACC's basic, basic_2, … saves). Compare puts two to four setups side by side, versions of the same setup included, differences first. The optimizer walks you through it: which sessions it read, what the car does in which corners — and whether that is the setup or your driving —, then one recommendation plus two alternatives, each with the value as the game shows it, what to expect and what it costs, and what it rejected and why.

Two fixes for everyone who tried it before: the optimizer no longer proposes steps the game does not have (the "ABS 9 → 10" case), and Lapmetry now reliably recognises which setup you drove in a session — also for sessions from before the import — and shows what it recognised it by.

Also new​

• New home screen, new look: darker, calmer, easier to read, with fixed colours for gain, loss, warning and reference. Font size, contrast, colour-vision modes and reduced motion under Settings → General.
• The 3D workbench from lapmetry.com is in the app: Analysis → Workbench for synced sessions, Analysis → Local for your own laps without an account or internet.
• Voice is off by default now, with one switch for all voices under Settings → Audio. If you use the radio and updated, switch it back on there once — and "off" actually stays off now.
• Ctrl+Shift+O works again.
• Spotter calls can be muted one by one; the radio log is sorted into critical, strategy and spotter.
• Sessions with search, favourites and tags; settings in nineteen sections with a search box and a privacy page that says plainly what leaves your computer and when; live pit wall, training and community inside the app.

Updating​

The app updates itself; Settings → Updates checks on demand. Current versions: desktop v0.84.0, web v0.82.0 — full list at lapmetry.com/changelog

Alessandro

 

[Doc]

This is an amazing resource! The only issue is the lack of community references to compare lap times to. It would be great to either be able to upload our own reference times or connect with other places that have them, such as Ohne Speed's LMU Laptimes

 

[mpracer]

Hello, I recently downloaded version 0.86.0. The app is nice and demanding, I'll need a few days to understand all its features, which seem, on a first analysis, very interesting, and being able to use them well could really raise the level of driving.

I noticed one particular thing: while driving around a track, the engineer tells me that the pressure of one of the tires is at 1.6 PSI and warns me that it's too high, but 1.6 PSI equals 11.0 kPa, whereas normally tire pressures are above 136 kPa that rorrispond to 19.7 PSI

I'd like to let you know that I'm using the Italian language.

 

[Lapmetry]

Lapmetry v0.87.0 — laps that went missing, references that finally compare, and an app that updates itself​

Eleven days, eight releases: desktop v0.87.0, web v0.85.0. This one is mostly repair work, and two of the repairs are ones I owe you an apology for.

Interlagos laps were never recorded — at all​

If you drove São Paulo and found nothing in Lapmetry afterwards: that was not your setup, your account or a failed upload. The game reports the track as "Autódromo José Carlos Pace", Lapmetry was looking for "Interlagos" — and when it cannot name a track, it does not create a session. Every lap there was dropped silently, with no error anywhere.

That has been broken since August and is fixed in v0.87.0. Interlagos records normally now. Sorry — laps already lost cannot be recovered, and this one was entirely on me.

Related, and the reason it stayed hidden so long: when Lapmetry meets a car or track it cannot identify, it now says so in the log instead of quietly recording nothing. If that message ever shows up for you, send me the line — it tells me exactly what to add.

Assetto Corsa and ACC: every lap lost its telemetry​

Lap times were listed, but corner analysis, the line and the telemetry stayed empty. A check inside the recorder treated every ordinary finish-line crossing as a broken recording and threw the measurements away. LMU was not affected — this hit AC and ACC only.

Fixed in v0.87.0. If you also drive those sims, your laps there are usable again from now on.

"There are no community references" — about that​

@Doc raised this a while back, and it deserves a straight answer.

Two things were happening. The first was a genuine bug: with Pro, corner findings were being compared against your own best lap while the screen said "community". If you uploaded a good lap, you saw zeros everywhere. That is fixed since v0.86.0 — the numbers there are other drivers' laps now, and they are real.

The second is simply how it is built, and I want to be honest about it: references are made only from laps people actually drove and captured. Nothing is typed in, nothing is imported from lap-time sites. That is the whole point — a reference you can open, replay and compare telemetry against, at your own pace level (P50–P99), not a number in a table. The cost is that a car/track combination needs drivers before it has references. On the popular LMU combos they exist; on rare ones they do not yet.

So no upload of your own reference times, and no connection to external lap-time lists — not out of stubbornness, but because neither can be replayed or analysed. What does help is simply driving with capture on: every clean lap becomes part of the pool for everyone at that pace.

The app keeps itself up to date now​

This is the one new feature in this batch, and it exists because the version spread got out of hand — people were driving with bugs I had fixed weeks earlier and had no idea.

From v0.87.0, Lapmetry installs updates itself. The rule is deliberately narrow:

• Only when the Lapmetry window is in front. If it is not, the app does nothing at all — it cannot see what else is on your screen, so it will not touch anything. A racing sim, a shooter, anything: if it is in the foreground, no update happens.
• Never during a recording, and never while a game is running. Not even for an urgent fix.
• When it does go ahead, you get twenty seconds' notice in the corner with a "Not now" button next to it.

So it should never interrupt you mid-session. If it ever does, tell me — that would be a bug, not the design.

Your account, your language​

• Account handling moved into the app (v0.86.0): sign up, sign in, forgotten password, change password — no more switching to the browser and back. Password reset sends you six digits to type in where you are.
• The app language now follows you. You can pick it during first-run setup (top right), and it applies on every other machine you install on, plus your emails. Until now it only applied to that one installation — and worse, every new account was created in German regardless of where you signed up. If your app has been stubbornly German, set the language once in the app and it will stick everywhere. Fixed in v0.87.0 / web v0.85.0.

Beta runs until 1 December 2026​

The beta is now one fixed date for everyone instead of "90 days from signup". Until then every account has full Pro with all four sims. Registration is open — no waiting list, no invite — and you can download and use Lapmetry without an account at all: recording, overlays and analysis of your own laps need no server.

Also fixed​

• Overlays behave again: switching them on and off works immediately, they stay visible after a race, the G-force widget draws, and the start lights show the right way round.
• Recording runs through: no more silent stop after long sessions, no lost final lap when quitting from the tray.
• The coach is more concrete: six findings now give you their actual number instead of a general sentence, and brake point, lap delta and your driven line are correct.
• The race engineer says the right thing: no invented pit stop in the first stint, fuel warnings only in races, and the open refuelling window is reported in every sim.
• The pit wall link has a QR code — scan once with your phone and it is open.
• Everything about sound is in one place (Settings → Audio): voice, volume, and which of them talks at all — engineer, co-driver, live coach, spotter.
• A shortcut Windows refuses now tells you. If another program already holds the same combination, the shortcut used to sit in the list looking fine and do nothing.
• Uploads the server rejects for good no longer clog the queue. They sit in settings with a reason, stay complete on your PC, and can be resent after an update.
• A single stray data point no longer costs a whole session — a pedal value a thousandth outside the allowed range could previously fail an entire upload.
• Setups and the setup area are open for every account; the widget gallery and engineer topics are sorted into families instead of one long list.

@mpracer — your tyre pressure report​

Thank you for this one, it is exactly the kind of report I need. You saw the engineer call a pressure of 1.6 PSI and warn that it was too high, which is obviously nonsense — real pressures are around 20–28 PSI.

I have not been able to reproduce it yet and I do not want to guess in public. Could you tell me:

• Which car and track, and was it a race, qualifying or practice?
• Did the tyres & brakes widget show the same 1.6, or a sensible number?
• Was it one wheel or all four?

If it is easier, send a diagnostics report from Settings → Updates → Send diagnostics right after it happens and mention it here — that gives me the session and I can look directly. Same for anyone else seeing odd pressures.

​

Updating​

The app now updates itself when the window is in front and nothing is running; Settings → Updates still checks on demand. Current versions: desktop v0.87.0, web v0.85.0 — full list at lapmetry.com/changelog

Alessandro

 

[mpracer]

Alessandro, I tried a pratice session in Algrave, after 5 laps the Engineer tells me that the right left tyre pressure is 1.6 PSI too high.

• Which car and track, and was it a race, qualifying or practice?
  • Algrave, Practice
• Did the tyres & brakes widget show the same 1.6, or a sensible number?
  • in the picture attached you can see the tyre & Brake overlay after 5 laps
  • 
• Was it one wheel or all four?
  • in 5 laps just the FL tyre

In the setting menu I tried to share with you the data, but I don't know if it's what you asked since, as I told you my app ims in Italian

 

[Blue_Monkey]

Please consider shortening your title, it takes tons of space on the forum page ... thanks

 

[mpracer]

The Turn 1 in Portimao is on the right, in the picture it seems on the right, my be it is wrong orinetation

 

[Lapmetry]

Lapmetry v0.94.0 — official corner numbers, your line where you drove it, and a new look​

Eight days, sixteen releases: desktop v0.94.0, web v0.93.0. First the three replies from last time, then what changed.

@mpracer — you were right, twice​

The tyre pressure call. Your screenshot solved it, thank you. The 1.6 was never the pressure itself: the engineer compares each tyre with its own warm pressure from early in the stint, and your front left had climbed 1.6 psi since then. The sentence said "pressure 1.6 psi too high" — which reads exactly the way you read it. Since v0.88.0 it says "pressure up 1.6 psi", in all ten languages.
Turn 1 at Portimão. Also right: the flat track maps — like the corner view in your screenshot — were drawn mirrored, so a right-hander showed as a left. Fixed in v0.88.0; the maps now match the real circuit. The 3D view was not affected.

Official corner numbers on 25 tracks​

Until now, Lapmetry numbered corners the way it detected them in the laps, and that rarely matched the circuit — its "T7" could be the track guide's "T9". On 25 tracks, Le Mans, Monza, Portimão and Interlagos among them, corners now carry their official numbers and names, as the circuit uses them. Your corner values line up with other drivers', and the coach talks about the corner you know from the track guide.
On tracks without an official list, newly learnt maps now split chicanes properly and get every corner's direction right.

Track variants are tracks of their own​

Monza Curva Grande, Le Mans Mulsanne, the Bahrain and Silverstone variants, the Paul Ricard layouts, Sebring School, COTA National, Lusail Short and Fuji Classic used to end up under the main track, mixing their laps and records with it. Since v0.93.0 the app recognises which layout you drive, and each variant has its own records and comparisons. Sessions recorded before stay where they were.

No more lost laps on an unknown car or track​

Last time I apologised for Interlagos, where the game's track name didn't match and nothing was recorded. Since v0.94.0 that can't happen anymore: if Lapmetry doesn't know a car or track yet, it keeps the laps anyway and lists the session as "Waiting for an update (stays local)". Once an update knows the content, the session is sorted in and uploaded.
Two LMU cases I found along the way, both fixed in v0.93.0: laps at Long Beach weren't recorded, and the Aston Martin Vantage LMGT3 was filed as the GTE car. Sorry to everyone who drove those. Aston sessions from before 0.93.0 still show under the GTE for now.

Your line, where you actually drove​

• Your car in the analysis could sit exactly on the reference line, or run down the middle of the track while the reference visibly took the corner. Your driving was never the problem; it was drawn in the wrong place. Fixed.
• Opening your best lap no longer compares it with itself (zero everywhere). Lapmetry takes your next-fastest lap and says which one.
• The 3D map opens from straight above, so the camera angle no longer squashes the gap between two lines.
• Sessions stored only on your PC now show the time-loss trace, line coach, lap comparison, corner trend, race review and coach sheet, offline too. They used to stay empty there.
• If telemetry was thinned out on your PC to save space, opening the session fetches it back from the cloud.
• The AI debrief and questions about a session now work when you open it from your PC.

A new look​

• The app has six areas in one header: Home · Drive · Sessions · Coach · Overlays · Setups. Settings and the guide are in the account menu and behind Ctrl + K. One session list instead of three, and "Open analysis" is a proper button.
• Purple means one thing: your fastest lap, like on a timing screen. Everything you click is azure — new logo included.
• Overlays stay readable over anything. Every character has a dark outline, so you can take a widget's background all the way down to 0 % and choose slate or black for it in the widget's options.
• The website is new, and the FAQ and pricing page are in all ten languages.

Setups​

• One sortable table: read a row, open a row, tick two to four to compare.
• You decide which setup you drove. Lapmetry's guess is now a suggestion in the session: take it, pick another, or say none fits.
• The optimiser asks one thing instead of four; your telemetry decides the rest unless you say otherwise.
• "Compared to what's usual" now draws on setups from the whole community for 46 cars — as ranges, never anyone's setup file.

References and your account​

@Doc, a follow-up to last time: a community reference line is now the middle of several drivers' laps instead of one person's recording.
You can delete your account yourself under Settings → Account, with 30 days to change your mind. What goes and what stays anonymously is stated before you click.

Also fixed​

• Race engineer: calls with numbers are grammatically right in all ten languages.
• Coach: no more false "throttle too early" before flat-out corners or "braked too late" after a quick dab of the brake in a chicane.
• Sector times: incomplete laps show none instead of estimates.
• Quitting or shutting down waits until the last laps are saved.
• Sign-in: other people's failed attempts on a shared connection no longer lock you out.
• Switching accounts takes settings, voice, language and widgets with it, and new sessions land in the right account.
• Race review: start and finish positions are right in long races, and pit laps count as a stop.
• Consistency in your stats counts clean laps only.

Tell me​

• Do the official corner numbers match what you know from your tracks?
• Anything in your session list "Waiting for an update"? Tell me the car and track and I'll add them.
• @mpracer — does the Italian engineer read naturally now?

Updating​

The app updates itself when its window is in front and nothing is running; Settings → Updates checks on demand. Current versions: desktop v0.94.0, web v0.93.0 — full list at lapmetry.com/changelog
Alessandro

 

[mpracer]

Ok, I understood that the 1.6 PSI is just the increment of pressure that means about 11 KPa that is the unit in LMU fopr the pressure.

I noted something I don't understand in the telemetry. In Road Atlanta your app consider just 7 corner and the coach too he talk me about 7 corners


but the page of the coach tells me that I have to correct my driving style in T11, is there something wrong? (The corners in Road Atlanta are 11 as you can see hereRacingcircuits.info



and still I noticed that the track is reversed

the corner T11 is righthander and not lefthander

Thanks for your app very interesting to learn better how to modify your driving style