Telemetry Coaching

Telemetry mode activates when a .duckdb file is open in the Telemetry viewer.

Coach reads high-frequency trace data from the lap you are viewing — speed, inputs, tyres, G-force, and more sampled along distance.

What you can ask

Corners and segments

• Analyze a turn by name, number, or distance range
• Summarize deltas vs your ghost, personal best, or external reference
• Compare braking points, apex speed, and throttle application

Line and inputs

• Racing line deviation vs reference lap
• Steering profile and wheel slip
• Braking and throttle traces through a sector

Ghost and reference comparison

Works when you have loaded:

• Community ghost — fastest community lap for track/car
• Personal best — your best lap in the file
• External ghost — another Your files recording on the same track

Ask Coach to compare your current lap to the loaded reference for any segment.

Setup from recording

Coach can read setup values embedded in the telemetry file.

For change suggestions, attach a baseline .svm in chat — see Setup attachments.

Segment comparison modal

Coach can open an in-viewer Segment Comparison modal summarizing:

• Time, speed, throttle, and brake deltas
• Optional tyre and brake temperature context
• A written summary aligned with the trace and track map

See Segment comparison.

Example prompts

• "Compare Lesmo 2 to my ghost lap"
• "Am I braking too early into T1?"
• "Show steering and slip through the final sector"
• "Where am I losing time vs the community ghost?"
• "Explain my setup and suggest one change for understeer"

Requirements

Tips

• Telemetry traces are the most expensive mode (typically 55–130 CC)
• Name the corner or segment — "Analyze T3 braking" beats "How was my lap?"
• Reserve telemetry coaching for corners where you need technical detail; use Session mode for race-level trends

Related

• Telemetry documentation
• Telemetry: AI Coach
• Track map and replay