How to Read Telemetry to Find Lost Tenths in FH6 Drag Racing
Stop Driving on Feel Alone
Every racer thinks they had a clean pass until the ET says otherwise. That gap between what you felt and what actually happened is where tenths live , and telemetry is how you go get them back. Forza Horizon 6's built-in data output, paired with the overlay and analysis tools here on 1320 Forza, gives you a frame-by-frame breakdown of exactly where your run fell apart. You just have to know what you're looking at.
This guide breaks down the three biggest killers , wheelspin, bog, and bad shift points , and shows you how to find them in the data before you ever make another pass.
Understanding the Speed Trace First
The speed trace is the backbone of your telemetry read. It's a simple line: time on the X-axis, vehicle speed on the Y-axis. A perfect drag pass looks like a smooth, steep curve that flattens only as you approach top speed. Any deviation from that curve is lost time.
What a clean trace looks like:
- Steep, unbroken climb off the line
- No dips, no plateaus, no hesitation bumps
- Smooth speed recovery after each shift
Every wobble, flat spot, or dip in that line is a story. Your job is to learn to read them.
Spotting Wheelspin in the Data
Wheelspin is the most common ET killer in FH6, especially on high-power builds running street or sport tires. The problem is it often feels fast , the revs are screaming, the car sounds angry, and you think you're moving. The trace tells the truth.
What Wheelspin Looks Like
On the speed trace, wheelspin shows up as a flat or barely-climbing line in the first 0-60 ft window despite full throttle input. Meanwhile, if you're logging RPM alongside speed, you'll see RPM surging while speed stalls. That delta between engine output and vehicle acceleration is your wheelspin signature.
In the 1320 Forza telemetry overlay, cross-reference the throttle channel with the lateral and longitudinal G-force traces. Excessive wheelspin will kill your forward G without killing your throttle input , a clear mismatch.
Fixes to test:
- Reduce launch RPM in 200-300 RPM increments
- Add rear downforce if the platform supports it
- Soften rear spring rate to improve squat and bite
- Move tire pressure down a tick (within class legal if racing ladder)
Diagnosing Bog Off the Line
Bog is the opposite problem , you've overcorrected for wheelspin, dumped clutch at too low an RPM, and the engine stumbles under the load. Where wheelspin looks like a flat speed trace with RPM climbing, bog looks like a speed trace that hesitates and then recovers, usually with a corresponding RPM dip visible in the engine channel.
The Bog Signature
Look for a brief pause or dip in speed in the first quarter-second of the run. RPM drops sharply at launch, then recovers as the engine finds traction. On 60-foot times, bog will cost you more than almost anything else because the entire run compounds off that opening interval.
If your 60-foot is soft relative to your top-end speed, you're losing the race at the tree, not the stripe. Bog is almost always the culprit.
Fixes to test:
- Raise launch RPM gradually
- Stiffen clutch tuning if the platform allows it
- Check that your launch control setting (if using one) isn't holding you below peak torque
Finding Shift Points in the Trace
Bad shift points are sneaky. A missed shift by 200 RPM might only cost you a couple hundredths in isolation , but across four or five gears, you're looking at real tenths stacked up. The speed trace is where you find them.
What to Look For
Every shift shows up as a brief speed plateau or micro-dip as the transmission moves between gears. That's normal. What's not normal is a long flat section or a significant speed drop at a shift point, which means you're either:
- Shifting too early and falling out of the powerband
- Shifting too late and running out of revs before the next gear loads up
- Catching a rev limiter and bouncing off it
Reading the Shift Table
Use the 1320 Forza telemetry tool to pull your RPM-at-shift data from each gear change and compare it to your dyno trace for that build. You're looking for shifts that happen inside the peak torque band for the next gear , not just before the rev limiter in the current one.
| Gear Change | RPM Too Low | RPM Too High | Target Zone |
|---|---|---|---|
| 1st → 2nd | Bogs on entry | Limiter bounce | Peak torque crossover |
| 2nd → 3rd | Power valley | Late shift cost | Powerband overlap |
| 3rd → 4th+ | Falls flat | Minimal loss | Match to top speed pull |
The goal is seamless powerband handoff from one gear to the next. When your shifts land in the right window, the speed trace looks nearly uninterrupted through each gear change.
Turning the Data Into Faster Passes
Reading telemetry is worthless without a system for testing changes. Make one adjustment per session, run a minimum of three passes per configuration, and compare the average ET , not the best single pass, which can mask inconsistency.
A clean workflow:
- Export your run data with the 1320 Forza telemetry tools after each session
- Overlay two runs on the speed trace to visually diff them
- Identify the earliest point where the traces diverge , that's your problem area
- Make one targeted adjustment, retest, repeat
Consistency in your process is what separates tuners from guessers. The car that wins grudge races and ladder rounds at 1320 Forza isn't always the fastest build on paper , it's the one that gets tuned off real data and hits the same number every single time.
Last Word
The tenths you're looking for are already in your data. Wheelspin, bog, and shift point drift are leaving time on the table every pass, and now you know how to see them. Pull your telemetry, read the trace honestly, and start making changes with purpose instead of gut feel. The strip doesn't lie , and neither does the data.