← Back to blog /Blog

How I reached top 100 Rivals in Forza Horizon 6 — 5 tuning lessons

· 8 min read

Tags: rivals · tuning · FH6 · competitive · lessons

Six months ago I was a casual S1 player struggling to crack the top 5000 in Rivals. Today I am inside the top 100 on three different leaderboards, and I run an A-class personal best that sits inside the top 50 on the route I race most often. What changed was not my talent. It was my tuning approach, and specifically five lessons I had to unlearn from forum meta-builds and YouTube tune videos.

This is what actually worked. Take it as a guide if your goal is climbing the leaderboard rather than building “objectively the best” tune sheet.

Lesson 1 — Symptoms beat theory every single time

For my first 200 hours in FH6 I tuned by theory. I would read that a heavier front anti-roll bar increases front grip, so I would crank it on every car. I would read that more caster stabilises the chassis, so I would max it. The result was a car that did weird things in different corners and I could never figure out why, because I was changing 8 variables at once based on what was supposed to work.

The breakthrough came when I started doing the opposite. Instead of starting from theory, I started from symptoms. I would do a baseline lap, write down — literally write down — what the car did wrong. “Pushes wide on the second-to-last hairpin.” “Snaps on the high-speed left after the bridge.” “Cannot put power down out of the chicane.”

Then I would change one thing aimed specifically at that symptom, and only that symptom. The car pushes wide on a slow hairpin? Soften the front ARB by 2. The car snaps on the high-speed left? Stiffen rear damper rebound by 1. The car cannot put power down? Lower rear tire pressure by 1 psi.

Each change targets exactly one observed behaviour. After three or four iterations the laundry list of complaints shrinks to one or two, and you can fine-tune from there.

The thing that made EasyTune work as a product is exactly this principle. Verbalising the symptom forces you to be precise about what is wrong. “The car feels bad” is not actionable. “The rear loses grip when I trail-brake into corner six” is one tuning lever away from solved.

Lesson 2 — Iterate in small steps, not big leaps

The second thing I had to unlearn was the urge to make big changes. Stock front ARB at 25, target value 35? I would jump straight to 35. Then the car would feel completely different and I had no idea whether the change improved it or just changed it.

The competitive tuners I learned from all do the opposite. They change one variable by the smallest meaningful step, test it, decide if it is better or worse, and only then change again. Front ARB from 25 to 27. Test 3 laps. Better? Go to 29. Worse? Go back to 25, try a different variable.

This is slow. It feels slow. The first time you spend 90 minutes adjusting one setup, you will think this is a waste of time. But the cars that ended up on Rivals leaderboards came from this approach, and the cars I built in 15 minutes of bold changes never beat them.

A practical heuristic: if you cannot articulate why your change should help based on the previous lap’s symptom, you are guessing, not tuning.

Lesson 3 — Test in Rivals mode, not Free Roam

For months I tuned in Free Roam because it is convenient. Drive to a stretch of road, do a few laps, tweak the tune. The problem is Free Roam is unrepresentative. The road surface changes, traffic appears, there is no consistent measurement of laptime, and the AI drivatars affect your line.

The shift that helped most was tuning exclusively in Rivals mode. Every test session is on the exact same road surface, exact same starting conditions, with a timed lap output. Two laps in Rivals tells you more about a tune than 20 laps in Free Roam.

The other benefit is psychological. The leaderboard ghost in front of you sets a target. You can immediately see whether your change is moving you closer to or further from a known reference time. Free Roam has no reference; you are always tuning blind.

If your goal is laptime, tune in the mode that measures laptime.

Lesson 4 — Tire pressure first, anti-roll bar last

This is the lesson I wish I had learned in month one. The tuning hierarchy that worked for me, in priority order:

  1. Tire compound and pressure — Free contact-patch grip. Adjust first, always.
  2. Differential settings — Free rotation and traction. Adjust second.
  3. Camber and caster — Geometry. Adjust third.
  4. Spring rates — Suspension balance. Adjust fourth.
  5. Damping — Fine-tune the spring rate’s behaviour. Adjust fifth.
  6. Anti-roll bars — Final balance tweak. Adjust last.
  7. Aero — Class-permitting fine-tune. Adjust very last.

The reason ARBs come last is that they amplify whatever is already happening in the suspension. If your springs are wrong, the ARB will exaggerate the wrongness. Fix the underlying balance with springs and dampers first; use ARBs to dial in the last 5 percent.

The reason tire pressure comes first is that it is free. It costs nothing in setup time, makes no PI changes, and a 1-psi change can be worth a quarter-second per lap. Always start there.

I spent my first 100 hours tuning in roughly reverse order — aero and ARBs first, tires last — and wasted enormous amounts of time. Reversing the order saved more laptime than any other single change to my workflow.

Lesson 5 — Trust your feel, ignore meta builds blindly

The last lesson is the hardest. The FH6 community produces an enormous amount of meta-build content — YouTube videos titled “THE BEST S1 TUNE”, shared liveries with allegedly perfect setups, forum threads ranking the top 5 cars per class.

Some of this is good. Most of it is generic, optimised for a specific driving style or a specific track, and it will not work for you.

The cars that put me in top 100 were not the meta-build cars. They were cars I built around what I am good at — long sweepers, late trail-braking, smooth throttle modulation — and tuned to those strengths. A car that suits an aggressive corner-attack style will lose laptime in my hands and vice versa.

The metric that matters is your laptime in your hands on the track you actually race. Not the laptime someone else posted, not the theoretical optimum, not the build that wins forum debates. Trust the stopwatch and trust how the car feels through your specific input style.

This does not mean ignore community knowledge. The five fixes for understeer in our other guide are universal. The AWD center-diff bias starting points work for everyone. Use the community wisdom as a baseline, then deviate based on your data.

Bonus lesson — Save tunes, name them, version them

A small practical lesson: name your tunes with version numbers and what changed. “S1 GT3 — v3, soft front ARB”. “S1 GT3 — v4, soft front ARB + drop rear psi”. When you make a wrong change you can roll back in seconds. When you find a magic combination you remember what it was.

I lost a top-200 tune once because I overwrote it with experimental changes and could not reconstruct the original. Never again.

How EasyTune was born from these lessons

EasyTune exists because I got tired of spending 90 minutes per car re-deriving the same symptom-to-fix mapping. The engine encodes lesson 1 (symptoms beat theory), enforces lesson 2 (small iterations), works with your actual race time data, applies the priority order from lesson 4, and gives you a baseline you can then trust your feel on for lesson 5.

It is not magic. It is what an experienced tuner does mentally, written down and accelerated. If you are climbing leaderboards, you can choose to do this manually as I did for the first 200 hours, or you can let the diagnostic skip you to the bit where you are validating tunes on track instead of deriving them from scratch.

Closing thought

Top 100 is not about talent. It is about discipline: describe symptoms precisely, change one thing at a time, measure in the right environment, follow the priority order, and trust your own feel over generic advice. Do that across a few dozen cars and you will be there.

Tune your car. Trust your feel.

We use privacy-friendly analytics (Cloudflare, Microsoft Clarity, Vercel) — no cookies, no cross-site tracking. Learn more.