Tell us about one sim-racing session, your game, car, track, and one area you want to improve. The proposed review returns up to three observations and one practice drill. This first offer is human-delivered; the dashboard below is a product demo, not your personal analysis.
Ambience is off until you press Enable ambience.
Demo values are simulated. Apex CSV v1 is the first defined local import path; the separate EVO bridge is experimental. When real input is selected, unavailable fields are shown as unavailable and sample coaching/setup cards remain examples, not personal analysis. CSV files are processed in this tab and are not sent to QI.
See how sample telemetry could be turned into explainable coaching cues and setup recommendations.
Measured channels appear independently; unavailable inputs remain blank rather than being shown as zero.
Complete two clean laps to compare pace at matching lap positions.
Schematic lap-progress zones only — not the circuit’s physical layout. A captured track trace appears only when a clean lap includes sufficiently dense, valid world X/Z position samples. B marks the sampled brake crossing at 15%; T marks the sampled throttle crossing at 80%; outlined markers show a matched prior-lap crossing. Colors compare sampled speed, not time loss or safety.
Circuit outline: © OpenStreetMap contributors · ODbL.
Example only: rear-left is +5.4°C above the simulated sample baseline.
Example pattern: throttle is 11% earlier than the sample reference lap.
An example of how a smoother trail-brake release might be described.
Contextual lesson: Why earlier throttle can overheat a GT3 rear axle.