As an Amazon Associate I earn from qualifying purchases. Some links on this page may earn RealIRacing a commission at no extra cost to you. Gear I personally race on is called out as such; other picks are researched recommendations.

MoTeC i2 Pro opens a wall of data. Twenty channels scroll past, each line a different color, and most of them look like noise if you have never been taught to read them. The good news: you don't need an engineering degree to spot the difference between a clean lap and a messy one, or to see where your setup is fighting you. You need to focus on five channels that tell a story about pace, control, and efficiency. Start there and the rest becomes optional.

A trace is a time-series plot. One axis is time (usually from 0 to maybe 2 minutes for a lap), the other is magnitude (speed, angle, pressure, whatever the channel measures). When lines spike or dip, something happened. Your job is to ask: does this make sense, or is it telling me I made a mistake or my setup is wrong?

The five channels you must learn first

Speed, throttle position, brake pressure, steering angle, and lateral acceleration tell almost everything about how fast and how cleanly you drove a lap. If you export a trace from iRacing telemetry or log one from a real-world sim, these five channels should be your first stop.

Reading the speed trace like a map

Start with speed because it tells you the most about your lap immediately. Overlay two of your fastest laps on top of each other (most telemetry tools let you compare). Find the places where one lap's speed line is consistently lower than the other.

If your speed is lower in a straight, you made an error (lock-up, off-track excursion, or poor exit from the prior corner) that cost momentum. If it's lower mid-corner, you ran out of grip or hit the apex too fast and had to slow down to recover. If it's lower on corner entry, you either braked too late (speed was too high) or backed out of the throttle too early on the prior straight.

Comparing laps

When comparing two laps, don't just look at the final delta in the display. Trace your finger along each line and watch where the gap opens and closes. That's where the real differences live.

Spotting mistakes in throttle and brake traces

A clean throttle trace looks like a square wave: full on, then off at the braking point, then back on at corner exit. If your throttle chart looks like a saw tooth with lots of small bumps, you're feathering (modulating throttle at partial position) during acceleration. This is always slower than full throttle or full off.

Brake pressure should be a clean ramp. At trail-braking corners (like a high-speed sweeper), a linear decay from peak brake to zero at the apex is ideal. Multiple peaks or a stepped decay (high, drop, high again) means you're reapplying brake after an initial release. That costs lap time. It's also a sign that your braking point is inconsistent or your reference is wrong.

If your throttle and brake are active at the same time (overlap), you're trail-braking deliberately. That's fine for a few high-speed corners. But if you see brake and throttle overlapped at a 90-degree corner, you're making a mistake. Either your brake point is too late or your throttle comes on too early.

Understanding steering and lateral G

Steering angle and lateral acceleration should rise together and fall together. A smooth, single-peak curve is fast. If your steering trace has two bumps (double apex), you're turning in too much, straightening, then turning again. That's either a line error or the car is pushing and making you correct. Compare it to a lap where the steering is one smooth input.

Lateral G should peak at the apex and should match the speed trace. If lateral G peaks before the speed minimum, you're entering the corner too fast and the car is fighting. If it peaks after the apex, you're carrying too much speed and the car is starting to wash wide. The ideal lap has both peaking at the same time.

Oscillation in steering (small up-and-down wiggles) is almost always a bad sign. It means you're making tiny corrections instead of committing to one input. This often points to either a setup problem (the car is twitchy or loose) or your own lack of confidence in the car's balance.

Using the trace to spot setup issues

Setup problems show up clearly on a telemetry trace. If your car is loose (rear sliding), lateral G will plateau or drop before you reach maximum steering angle. If it's tight (understeering), you'll reach maximum steering angle before lateral G peaks. A well-balanced car rises smoothly into the apex and holds it.

Brake traces reveal lockups instantly. A spike in brake pressure with a dip in speed (not smooth) is a lock-up. If you see this consistently at one corner, either adjust your reference point earlier or soften your brake balance. If it's erratic, it's a driver input problem.

Throttle wheelspin looks like a speed drop during acceleration with full throttle applied. The car is sliding, not gripping. If this happens coming out of a slow corner, your exit line is wrong or you need more rear grip. If you're on a straight, it's usually just over-enthusiasm.

The workflow: compare a good lap to a bad one

Export or log two laps. One should be your personal best in a session, the other a lap where you feel you made mistakes or were slower than expected. Load them both into your telemetry tool and overlay them. Now step through each sector (a corner, a set of corners, or a straight) and ask these questions:

  1. Where does the speed line diverge first? That's where the lap started to go wrong.
  2. Is the throttle on/off cleaner in the faster lap? Look for feathering in the slower lap.
  3. Does the faster lap brake later, or earlier? Note the braking point difference.
  4. Is steering smoother or wobblier in the faster lap? A single curve vs. bumps.
  5. Is lateral G higher and more consistent in the faster lap? That's confidence and grip.

This comparison is faster and more reliable than watching a replay, because the data doesn't lie and you won't miss small inputs. A replay might not show the nuance of a 2% throttle input, but the trace will.

Common beginner mistakes in reading traces

People often zoom too far in or out on the time axis. If you zoom all the way in on a single corner, you'll see noise and small corrections that look bigger than they are. If you zoom out and look at the whole lap at once, you'll miss the detail. Start with a single sector (one corner plus the straights around it) and work from there.

Another mistake is ignoring the scale. A lateral G trace that looks jagged might actually be a 0.1 G variation, which is nothing. But if the scale is 0.01 G per grid square, it looks huge. Always check the axis labels. A 0.2 G variation at the apex is not the same as a 0.02 G variation.

Finally, avoid the trap of chasing a single channel. If your speed is 1 mph lower than your best lap, that's worth investigating. But if every other channel looks identical, the 1 mph is probably just normal variation. Look for patterns. A good lap usually has multiple channels that align better, not just one channel that is exceptional.

Create a reference lap

Export your best lap from a practice session and keep it as a reference. When you jump into a new race or a new car, compare your first flying lap to that reference. You'll spot setup changes, driver errors, or track condition shifts immediately.

Next steps: dig deeper if you want

Once you're comfortable with these five channels, telemetry gets deeper. Brake temperature, front and rear lateral load transfer, engine RPM, suspension movement, tire slip ratio and tire slip angle all add nuance. But they're not necessary to drive faster. The fundamentals of reading a trace come from understanding speed, throttle, brake, steering, and lateral G. Everything else is refinement. Start there, and you'll catch most of your own mistakes before they cost you lap time in the race. For a deeper dive into how your setup affects the car's behavior on track, the principles in a structured rig setup feed directly into what you'll see in these traces.

From the RealiRacing shop

Before your next session, free up your rig. NWM PitStop is the clean-up + stream-priority script set we run before every session — our own product, not a third-party pick. See NWM PitStop →

The gear in this guide
PickWhy it made the listTested?
MOZA R9 Direct Drive Wheelbase9 N·m direct drive — the base bolted to my rig right nowRaced on
1440p 120 Hz+ G-SYNC Compatible Gaming Monitormy single-screen setup — high refresh matters more than sizeRaced on

As an Amazon Associate I earn from qualifying purchases. Some links are affiliate links — I may earn a commission at no cost to you.

Watch it, don't just read about it

I stream and upload iRacing races on my MOZA R9 rig — real laps, real force feedback, real mistakes. See the gear from this guide working before you spend a cent.

▶ Subscribe on YouTube

Skip the trial and error

The force-feedback, pedal and baseline settings I actually race, written up as setup packs for MOZA, iRacing, ACC and Le Mans Ultimate. The opening section of each pack is free to read.

See the setup packs →

Free FFB tuning checklist

The order I tune force feedback in, from rig to wheelbase software to iRacing, plus the clipping check. Enter your email and the checklist opens right here. No spam, unsubscribe anytime.

See the privacy notice.

FAQ

What telemetry tool should I use to read MoTeC traces?

iRacing exports telemetry that opens in MoTeC i2 Pro, which is free to download from the MoTeC website. You can also use Garage61, which is web-based and free, or RaceStudio which is what many real racers use. All three will show you the same five core channels. Start with whatever is easiest to access. The software doesn't matter as much as your ability to read the channels.

How do I compare two laps if the telemetry tool won't load them together?

If your tool doesn't have an overlay feature, export both laps as CSV or another data format and load them into a spreadsheet (Excel, Google Sheets). Plot speed vs. time for both laps on the same chart. You won't get the color-coded detail, but you'll see the differences. Most tools made for sim racing (MoTeC, Garage61, RaceStudio) do support overlay, so this is a fallback only.

Why does my speed trace look jagged even in a straight?

Straights should show smooth acceleration or coasting. Jagged lines usually come from two sources: your data log is recording at a low frequency (sampling rate too slow), or your game graphics are running at low frame rates (causing data points to be inconsistent). A data logging frequency of at least 60 Hz will smooth this out. If you're playing at 30 fps, upgrade your monitor or graphics settings first. A jagged straight trace almost never means you're doing something wrong.

What should I do if I see an obvious difference in one channel between two laps?

Trace through the entire sector to understand the cause. A lower speed at corner exit usually traces back to a weaker entry (more braking, later apex, or less commitment). Don't fix one channel in isolation. Read the story: brake trace, then steering trace, then speed trace together. If brake pressure is lower in the worse lap but steering and lateral G look the same, your brake application was inconsistent. If speed is lower but nothing else changed, you might be carrying too much steering angle or the car balance shifted.