Which Three Telemetry Channels to Check First

4 min read
sim racing telemetry
telemetry channels
driving diagnostics
Empty braking zone at dawn, with dark tyre marks on the asphalt representing the brake and steering channels analysed in telemetry

Brake, throttle, and steering: the three channels that show the driver's gesture, not the car's behaviour — and that's why they're the first thing to open when comparing against a reference lap.

The three channels that reveal most about where you lose time are brake, throttle, and steering angle, overlaid with a reference lap faster than yours. They show the driver's gesture, not the car's behaviour — and gesture is what you can actually train tomorrow.

Suspension, tyre temperature, aero load: all of that matters, but it depends on setup and car. The three input channels are universal. They work on the Mazda MX-5 and the GT3, in iRacing and in GT7.

Why start with the inputs, not the car

Suspension and tyre channels need setup context to make sense. Two cars with different springs will show completely different travel curves for the same track behaviour.

Brake, throttle, and steering don't have that problem. They are exactly what your hand and foot did, period. Comparing your trace to a reference lap isolates precisely where the gesture diverges.

Channel 1: brake pressure

Don't just look at the braking point. Look at the shape of the entire pressure curve: peak, plateau, release.

  • Late or soft peak: indicates hesitation on entry, usually a sign of insecurity about the grip available in that specific corner.
  • Plateau too long: the driver holds constant pressure when they should already be releasing, which delays the car's rotation.
  • Stepped release: the brake drops all at once instead of tapering off gradually, which destabilises the front axle mid-corner.

This channel alone already explains a good portion of the cases where the driver thinks they're slow on the straight but are actually losing time under braking. To separate the two symptoms, it's worth revisiting how to check whether trail braking is slowing you down directly from the data.

Channel 2: throttle

The throttle exposes what the braking hid. If the brake came off too early or in a step, the return to throttle comes locked up.

  • Delay on first touch: the driver waits for the car to settle before returning to throttle, a sign they still don't trust the rear at that point.
  • Stepped ramp: throttle application in jumps instead of a smooth curve usually generates exit oversteer in more powerful cars.
  • Premature plateau: full throttle before the car is aligned with the track, which works in some front-wheel-drive cars and sabotages others with rear-wheel drive.

This channel is where most time is lost without noticing, because the mistake doesn't hurt on the wheel — it only shows up on the stopwatch. It's the same reasoning behind why you lose time in the rotation phase, not under braking.

Channel 3: steering angle

The steering wheel shows whether the trajectory is repeatable. Irregular steering peaks indicate correction, not driving.

Symptom in the traceWhat it usually indicates
Double peak on entryCorrection of under or oversteer, unplanned trajectory
Unstable plateau at the apexDriver adjusting the radius in real time, with no fixed turn-in point
Asymmetry between mirrored cornersDifference in confidence, not car, between left and right

When steering and brake appear out of proportion — a lot of angle with still-high brake pressure — the front axle is overloaded. That's exactly the point covered in how to release the brake in proportion to the steering.

Brake pressure: stepped release versus ramped releasebrake pressuredistance in the braking zone
Stepped releaseRamped release
Brake pressure: stepped release versus ramped releaseIllustrative shape: it shows the form of the input, not a measurement.

How to read the three together

  1. Open all three overlaid with your best lap and the reference lap, on the same corner, at the same distance segment.
  2. Mark where the brake diverges first, because that's the origin point of the delay — everything after is a consequence.
  3. Check whether the steering compensated for the brake difference with more angle or with correction.
  4. See when the throttle reacted to the earlier divergence, to know whether the cost was on entry, mid-corner, or on exit.

This exercise points to the exact phase of the corner where the time disappears. If you're unsure which corner of the whole lap deserves this analysis first, it's worth the method in how to know exactly which corner is costing you the most time in your lap.

Common mistake when comparing the channels

Comparing against the fastest lap of the entire day, instead of a clean and representative lap. An isolated record lap usually has a one-off setup that doesn't repeat — it becomes noise, not a reference.

Another mistake is judging the channel outside the corner's context. A late brake peak on a straight-line braking corner means one thing; the same pattern on a trail-braking corner means another, because the front tyre is already loaded laterally.

The three channels don't tell you what to do with the wheel. They tell you where your gesture diverges from the fast lap — the training starts after that.

Where Laptics fits in

Laptics records telemetry automatically while you drive and compares laps phase by phase through each corner, showing how much time each gesture cost in brake, throttle, and steering. The Driver DNA gathers these patterns that repeat across sessions, so you know whether the problem is the corner or you, on any track.

Practical summary

Start with the three input channels, not the car's channels. Brake reveals where hesitation begins, throttle reveals the cost of that hesitation, steering reveals whether the trajectory was planned or corrected. Overlay with a clean reference lap and look at where the divergence appears first — that's where tomorrow's training should aim.

Frequently asked questions

Why not look at the speed channel first?

The speed channel shows the result, not the cause. Brake, throttle, and steering show the gesture that produced that speed, and gesture is what you can correct.

Do these three channels work for any simulator?

Yes. They are driver input channels, available in iRacing, ACC, Assetto Corsa, GT7, and F1 25, regardless of car or setup.

Which lap should I use as a reference for comparison?

A clean lap that's representative of your consistent pace, not the single fastest lap of the day, which usually has a one-off setup that won't repeat.

What should I do when all three channels look normal but the time is still bad?

Check whether the comparison is being made segment by segment on the same corner, not over the whole lap. Small divergences in one channel only show up when we isolate the right phase.

Shouldn't suspension and tyre temperature be part of this first analysis?

They come afterwards. They depend on setup and car, and without isolating the driver's gesture first, it's easy to confuse a setup effect with a driving effect.

How does Laptics help with this analysis?

Laptics records telemetry automatically and compares your laps phase by phase through the corner across these channels, showing how much time each gesture cost against a reference.

Want to see this in your own telemetry?

Discover Laptics