MyLMU Coach is powerful but not infallible. Understand what it can and cannot do.
Early access (beta)
Coach is in active early access (beta). Models, prompts, and data sources improve over time. Treat answers as coaching guidance — not absolute truth. The same notice appears in Coach → Help.
Always verify:
- Final positions and gaps on the session page
- Incident counts in session standings
- Lap times in the telemetry viewer
Wrong coaching mode
Symptom: Coach answers about career when you wanted session analysis (or vice versa).
Cause: Coach mode follows app context when you open or send a message.
Fix:
- Navigate to the session page or open the telemetry file first
- Start a New chat so old context does not confuse follow-ups
- Mention the session explicitly: "For this race at Spa, how was my final stint?"
Missing session data
Coach can only analyze data that exists in your account:
| Gap | Effect |
|---|---|
| Session not imported | Coach cannot see the race |
| No full XML | Limited stint, tyre, and fuel detail |
| Driver swap | Tyre wear, fuel, speed may be incomplete |
| No linked telemetry | Session mode cannot do trace-level analysis |
Coach should report missing data honestly rather than inventing values.
Telemetry limitations
- Requires a loaded
.duckdbfile and sufficient Coach Credits (works on Free with purchased packs) - Ghost comparison needs a reference lap loaded in the viewer
- Very large files may sample traces rather than every data point
- Not every channel in the recording is exposed to Coach
Setup suggestions
Setup change suggestions are recommendations to test, not proven optimal setups. Always validate in-game.
Hallucination risk
Like all AI systems, Coach may occasionally:
- Misstate a corner name or track detail
- Over-generalize from limited data
- Confuse similar sessions or drivers
If something sounds wrong, check the underlying session or telemetry data.
Privacy
Coach processes your MyLMU data to answer questions. See Privacy & Terms for how data is handled.