Series 7 wiped every PR Stunt leaderboard in the game. Playground called it a clean sheet. The thing worth reading twice is the support post that went up three days earlier.

TL;DR

  • Series 7 “City Life” landed November 2 at 6:00 PM UTC (Xbox/Windows 3.479.874.0, Steam 1.479.874.0). The Playlist opened November 5 at 2:30 PM UTC and runs to December 3.
  • Within days, Forza Support confirmed Drift Zone scoring was being reduced in certain corners and by a player’s FPS — and told players to cap the game at 60 FPS or below as a workaround.
  • Read that direction carefully: more frames made your score worse. The high-refresh PC rig was the penalty, not the advantage.
  • Hotfix 1 shipped November 5 (3.483.970.0 / Steam 1.483.970.0) and fixed the corner and FPS scoring issues.
  • The same update wiped the PR Stunts leaderboards entirely — Danger Signs, Drift Zones, Speed Zones, Trailblazers and Speed Traps. That’s the third major leaderboard reset of the year.
  • Unconfirmed and worth asking about: Drift Attack at Shimanoyama was not named in either the bug or the wipe.

What Playground actually admitted

Most coverage of Series 7 led with Tokyo routes and IKEA furniture. The sentence that matters came from Forza Support on X:

“We’re aware of an issue affecting Drift Zones after the Series 7 update whereby scoring is reduced in certain corners and by a player’s FPS. Players can reduce the chances of this from happening by temporarily playing the game at 60FPS or below.”

Sit with the second half of that. The official, studio-issued mitigation for a scoring bug was turn your frame rate down.

That is not a normal thing to ask of a racing game audience. Frame rate is the one setting the entire PC side of this hobby optimizes upward — it’s the reason people buy the monitor, the GPU, the whole rig. For a window after Series 7, every one of those frames was working against the score.

The part people get wrong: the instinct is to assume a frame-rate bug means PC players were cheating their way up the board. It’s the opposite. Scoring was reduced by FPS, so the player on a locked 60 console was in a better position than the player running 144. If you looked at the Drift Zone board after November 2 and wondered why your times felt uncompetitive on a machine that should have been quick — you weren’t imagining it.

Forza Support confirmed the hotfix rollout on November 5, and Hotfix 1 (3.483.970.0, Steam 1.483.970.0) lists fixes for both the corner scoring and the FPS scaling, along with a repair to the Saleen S7 front bumper.

Why the mechanism probably looks like this — labeled as the guess it is

Epistemic status: this is our reading, not Playground’s explanation. The studio described the symptom and shipped the fix without publishing a cause. What follows is inference from how the game is built.

FH6 does not run on one physics tick per drawn frame. As we covered in the 8-point tire model explainer, the game resolves tire load across 8 contact points at 360 Hz — deliberately decoupled from whatever your display is doing. That decoupling is the whole reason FH6 feels different to drive from FH5.

A scoring bug that scales with FPS is what you get when one piece of logic didn’t get that treatment — when drift points accumulate per rendered frame, or per-frame with a delta that doesn’t normalize, instead of on the physics clock. Draw more frames, slice the same slide thinner, score less of it.

This also explains a complaint that looked like user error at the time. Drift scoring already punishes a broken chain — the multiplier resets the moment the slide breaks, which is why one long sustained drift beats three short ones and why our drift cars for beginners and tandem guide argues for a car you can hold an angle in rather than one that snaps. Stack an FPS-dependent accumulator on top of that and a clean, long slide can still come back light.

Community testing lines up with that shape. Players on r/ForzaHorizon reported that running at 30 FPS, or certain frame-generation setups, returned higher scores — the same inverse relationship, from the opposite end. That’s a consistent signal across independent reports, not a proven mechanism, and we’d rather say so than dress a hypothesis up as a teardown.

The genuinely awkward part: the wipe and the bug are in the same update

Here’s where the timeline gets uncomfortable.

The Series 7 notes announce a complete wipe of the PR Stunts Leaderboards — Danger Signs, Drift Zones, Speed Zones, Trailblazers and Speed Traps — on the grounds that the update fixes glitches that allowed unrealistic scores. Collection Journal items earned from those records stay unlocked. Playground acknowledged the wipe takes legitimate scores with it, and framed the result as a clean sheet.

We have no quarrel with wiping a board after patching the exploits that poisoned it. Clearing and restarting genuinely is cleaner than adjudicating thousands of entries by hand.

The catch: the update that wiped the boards is the same update that broke Drift Zone scoring. So for roughly three days, the freshly reset Drift Zone leaderboard was being populated with scores produced under a bug Playground had not yet fixed — scores partly determined by hardware rather than driving. The clean sheet got written on before the ink was dry.

Hotfix 1 corrects the scoring going forward. It does not, as far as anything published says, clear the entries set between November 2 and the hotfix. If you are chasing a Drift Zone board right now, the names above you may include runs set at 30 FPS during the window. That is not an accusation of cheating — those players were using the game as it shipped. It’s a reason to treat early-Series-7 Drift Zone entries as a different dataset from everything set after November 5.

The pattern nobody is naming: this is the third reset

Worth putting in sequence, because “leaderboard wipe” has stopped being an event at this game and started being a maintenance cycle.

WhenWhat was resetTrigger
Series 3 (July)Rivals leaderboardsExploits, incl. drag tire abuse
July 13 notes— (PR Stunts wipe flagged as coming)Pending fixes
Series 7 (November)All PR Stunts boardsGlitches enabling unrealistic scores

We wrote about the Rivals wipe when it landed in the Italian Exotics update — and used the phrase “a clean sheet for racers” at the time, which Playground has now arrived at independently. The drag tire abuse that forced the first one is the same saga we worked through in the post-drag-tire-nerf touge guide.

Notice the pattern. Each wipe follows the same arc: an exploit runs long enough to distort a board, a fix ships, the board is cleared. Three times in roughly five months is not a scandal — it’s a live game with competitive scoring and a studio willing to use the reset button. But it does mean a leaderboard position in this game is a perishable good, and anyone grinding one should price that in.

The open question: what happened to Drift Attack?

Here’s what nobody has answered, and we think it’s the most useful thing to ask.

Drift Attack at Shimanoyama is not on the wipe list. The reset covers PR Stunts — Danger Signs, Drift Zones, Speed Zones, Trailblazers, Speed Traps. Drift Attack is a separate shared-world activity with its own in-world and Convoy leaderboards, which we covered when it arrived in September.

But Drift Attack scores on Horizon Drift mechanics. If the FPS scaling lived in shared drift-scoring code rather than in the Drift Zone activity specifically, Drift Attack would have inherited it — and its board was neither reset nor mentioned.

We don’t know, and we’re not going to pretend otherwise. Playground named Drift Zones and only Drift Zones. The possibilities are that the bug was scoped to the Drift Zone activity, or that it touched the shared path and the Drift Attack board quietly carries the same artifacts. That’s a question for the next release notes, and a reasonable thing to ask support about if you have a Shimanoyama run you care about.

It’s also the second time Drift Attack’s leaderboard has had an integrity problem in two months — Series 6 closed a fast-travel and rewind farming exploit on that same mode, which we noted in the Series 6 engine swap breakdown.

Also in this update, and genuinely good

Not everything here is a cleanup. Two changes are straightforward wins:

  • Playlist cars got cheaper — by exactly 25%. Playground cut the PTS needed to unlock new cars starting with City Life, citing community feedback, and published no figures alongside it. The cut is a flat 25% across all four reward slots: 20 → 15, 40 → 30, 80 → 60, and the Series car from 160 → 120. We broke the whole Series down separately in our City Life playlist guide.
  • Two permanent Tokyo routes — Edo Circuit Road Race and Shuto Charge Street Race — plus the Edamame Time Attack Circuit back at Horizon Stadium.

Also worth knowing if you build: the Ginetta G40 Junior was toned down after overperforming across several PI classes, map discovery now actually reaches 100% per region, and there are retroactive points waiting in the Playlist History tab for two challenges people couldn’t complete in Series 5 and 6.

The Bottom Line

The leaderboard wipe is the headline and the frame-rate bug is the story. A drift score that moves with your GPU isn’t a scoring problem, it’s a measurement problem — for three days the Drift Zone board was ranking hardware alongside driving, and the official advice was to handicap your own machine to get a fair number.

Playground fixed it in three days, which is fast, and the fix is in Hotfix 1. The unresolved part is that the wipe and the bug shipped together, so the reset board’s first entries were set under the broken scoring and nothing published says those were cleared.

If you set a Drift Zone score between November 2 and the hotfix, re-run it — the number you have isn’t comparable to the one you’d set today. If you’re rebuilding the run anyway, your drift tire compound and tire pressure setup is where the cheap points are, and that part didn’t change. And if you have a Shimanoyama run you’re proud of, it’s worth asking Playground directly whether Drift Attack shares the scoring path. Nobody has put that question to them in public yet.


Related on ApexSpeedCraft: Drift Attack at Shimanoyama | Why FH6 Feels Different to Drive: The 8-Point Tire Model | FH6 Drift Tires & Tire Pressure: What Actually Works | FH6 Drift Cars for Beginners & Tandem | FH6 Touge Guide (Post-Drag Tire Nerf) | The Series 6 Engine Swaps Nobody Documented

Sources: Forza.net — Embrace the City Life | Forza Support on X — Drift Zone FPS scoring | Forza Support on X — hotfix rollout | SteamDB — Series 7 patch notes | Unplayed.gg — Series 7 patch notes and HF1 versions | Mixed News — leaderboard wipe | Athlon Sports — leaderboard reset | Timesaver.gg — community frame-rate reports

Fediverse reactions

4 responses to “For Three Days, Forza Horizon 6 Scored Your Drifts by Frame Rate — and More FPS Made It Worse”

  1. […] you’re setting Drift Zone scores for points, the frame-rate scoring bug that made high-FPS runs score lower was fixed in Hotfix 1 on November 5. Anything you set now is […]

    Like

  2. […] FH6 Series 7 Autumn Week Breakdown | FH6 Series 7 City Life Guide | The Mascot Party Backlash | Drift Scoring Was Tied to Frame Rate | Horizon CoLab and […]

    Like

  3. […] the studio side, Playground’s November 5 Hotfix 1 (3.483.970.0 / Steam 1.483.970.0) patched Series 7’s FPS-dependent Drift Zone scoring bug and left PC memory allocation untouched. Waiting on 26.11.1 leaves you on the exact same broken […]

    Like

  4. […] zones are harder to tag cleanly, and reward higher multipliers when you hit them. Coming right off Series 7’s FPS-dependent Drift Zone scoring bug, shifting Drift Attack’s scoring gap toward line precision (and adding a permanent […]

    Like

Leave a Reply

Trending