TL;DR

  • F1 simulators don’t “prefer” certain tracks. They amplify circuits where small pace differences convert into big points swings, and compress circuits where they don’t.
  • Two archetypes cover most of the variance: track-position circuits (qualifying and first-lap matter disproportionately) and raceable tracks (race pace and tyre management win out).
  • Overtaking difficulty and degradation sensitivity are the biggest hidden multipliers. They decide whether a pace advantage pays out cleanly or gets trapped behind traffic.
  • Run the same season across two or three calendar/worldview variants in the Season Simulator and compare distributions. If your conclusion survives all of them, it’s real.

Some tracks make a season feel stable. The quickest car qualifies well, controls the race, banks the points, and Sunday finishes more or less the way Saturday suggested it would. Other tracks feel chaotic. Traffic matters. Pit timing becomes everything. One small error flips a weekend from P4 to P11, and the points table doesn’t care what the underlying pace picture looked like.

Simulators are sensitive to that difference because they aren’t only modelling pace. They’re modelling how pace turns into track position, and how track position turns into points. That’s the real reason the same team can look dominant in one simulation run and merely good in another — even when you haven’t touched the baseline pace numbers. You didn’t change the car. You changed the environment: track type, passing friction, tyre falloff.

The useful version of this isn’t chasing a single predicted standings table. It’s understanding which tracks reward a team’s strengths and which ones punish their weaknesses. The cleanest way to do that is to stress the season in the Season Simulator across a couple of calendar worldviews and compare distributions.

Track archetypes: the pace-to-points exchange rate

A season simulator is essentially a translation layer. It takes performance assumptions — pace, qualifying execution, strategy efficiency, reliability — and translates them into points. Track archetypes control the exchange rate.

On some circuits, a tenth of underlying pace reliably buys you grid position, clean air, and tyre life, which then buys you points. On others, the same tenth gets stuck behind a slower car, trapped in dirty air, and turned into nothing.

Track-position tracks. Narrow racing lines, awkward DRS zones, high penalty for running off-line, large gaps between “can follow” and “can pass.” Monaco is the archetype. Hungary and Singapore are in the same family. Qualifying and the first lap are disproportionately valuable, and strategy often goes defensive — cover the undercut, avoid rejoining in traffic, protect track position even when the tyre curve says a longer first stint is slightly quicker on paper.

Raceable tracks. Multiple viable lines, strong passing tools, lower friction when a faster car catches a slower one. Spa, Austin, Interlagos. The simulator rewards underlying race pace and tyre management more than peak one-lap pace. Losing two places early is recoverable. Wrong strategy calls can be mitigated by overtakes.

Think of each round in the Season Simulator as a different conversion environment. If your inputs assume Driver A is +0.15s on average, you should expect that advantage to pay out very differently across the calendar. The point of simulation isn’t to pretend every circuit behaves the same. It’s to quantify the uneven payout.

Overtaking difficulty — the multiplier no one names

Overtaking difficulty is one of the most important levers in season modelling, and one of the most misunderstood. People treat it as a narrative variable — “hard to pass here” — but in a simulator it acts like a multiplier on everything that creates track position.

When passing is difficult, qualifying execution compounds. P3 instead of P6 isn’t just three positions. It’s cleaner air, better tyre temperatures, more freedom on pit windows, and less exposure to being held behind a car that’s slower in clean-air pace but fast enough on the straights to defend. The simulator will usually show tighter point distributions for the front runners on these tracks (fewer recoveries from mistakes) and harsher penalties for small errors (grid penalty, scruffy lap, slow stop).

When passing is easier, the same qualifying gap matters less. The faster car converts pace into position. Strategy errors get fixed on track. Even a mediocre grid slot can produce a high points finish if the race pace is there.

Don’t treat overtaking difficulty as a single truth. Run two worlds in the Season Simulator — one where passing is slightly harder than your baseline, one where it’s slightly easier. If the championship outcome flips between them, you haven’t found a prediction. You’ve found a dependency. That’s actually useful: it tells you which weekends are must-execute qualifying events and which are ones where race pace can rescue you.

Degradation sensitivity — why tyre tracks widen the distribution

Tyre degradation isn’t just about how many seconds a stint loses. It changes the shape of the decision tree: which strategies are viable, how punishing traffic becomes, how quickly a race can diverge into separate mini-races based on tyre life.

On high-deg circuits, tyre management creates larger performance spreads within a race. A car that protects its rears might only be modestly quicker over one lap but dramatically more consistent over a full stint. That consistency makes the undercut sharper (fresh tyres bite immediately), makes the overcut situational (track position might be worth a few worn laps), and raises the payoff for clean air. It also raises the cost of getting stuck — following closely overheats tyres, overheating accelerates degradation, and a small track-position problem turns into a full strategy collapse.

From the simulator’s perspective, high-deg tracks widen the distribution of outcomes. Bigger swings from Safety Car timing. Bigger pit-stop delta effects. More variance from traffic placement. Low-deg tracks compress strategy space: fewer viable stop-count differences, more direct pace conversion, fewer ways for a slower car to “out-strategise” a faster one.

Practical point: if your model assumes Team B is slightly kinder on tyres than Team A, don’t assume that advantage pays out evenly. It pays out most on high-deg, high-traffic-sensitive events — and barely matters on low-deg, easy-pass circuits. Stress it in the Season Simulator by nudging degradation sensitivity up and down and watching which drivers’ downside risk changes, not just their average points.

What “simulator love” actually is

When people say a simulator “loves” a track for a specific car, they’re usually seeing compounding, not favouritism.

A rough example. Car X has a small advantage in medium-speed corners and qualifies well. Car Y is slightly faster in race trim and easier on tyres. On a track-position circuit with low degradation, Car X’s advantage compounds. The simulator converts it into more poles, more time in clean air, fewer traffic losses, and a higher probability of leading early — which is disproportionately valuable when passing is hard and strategy options are limited.

On a high-deg, raceable circuit, Car Y’s traits compound instead. Tyre life becomes flexible pit windows, consistent late-stint pace, and a higher probability of making an offset strategy work. When passing is easier, that advantage cashes in as positions rather than getting trapped behind slower cars.

The track doesn’t create pace. It determines whether your pace can be realised as points. That’s why simulator outputs have to be read as conditional: “given this track type and these passing and degradation assumptions, this is how often each driver wins.” Making that conditionality visible is the whole point of the Season Simulator.

A workflow: compare worlds, not single runs

The most common mistake with simulators is treating one run as the answer. The better approach is to treat each run as a world with explicit assumptions.

Start with a baseline in the Season Simulator using your best estimate for relative pace and reliability. Then build two variations that isolate the track-side drivers.

Variation 1 — overtaking worldview. A slightly more track-position-heavy season vs a slightly more raceable one. You’re not trying to pick which is correct for every circuit. You’re bounding the reality. If a driver’s title probability is stable across both, they’re robust. If it swings hard, you’ve learned what kind of calendar (and what kind of weekends) they actually need to win.

Variation 2 — degradation sensitivity. A tyre-limited season vs a low-deg one. This is often where you discover that a small assumed tyre advantage is either quietly irrelevant or the biggest lever in your entire model, depending on how much of the calendar behaves like a tyre track.

Read the outputs like an analyst. Look at ranges and downside risk, not just the most likely finishing order. And remember the 2025 rules: no fastest-lap bonus. Marginal pace now has to pay out through positions and race outcomes, not through a late-race soft-tyre flyer — so your simulation logic should reflect that when you evaluate close points battles.

Reading the results without overclaiming

A season simulation is a decision tool, not a prophecy. If the simulator says Driver A wins 58% of the time, that’s not a prediction of the championship. It’s a statement about how often the modelled season produces that outcome under the assumptions you set.

The disciplined question is: what assumption is doing the work?

  • Is it that Driver A qualifies better on track-position circuits?
  • Is it that Driver B’s tyre curve dominates high-deg rounds?
  • Is it reliability?
  • Is it simply calendar mix — the distribution of track archetypes still to come?

The moment you can name the lever, you can test it. If you can’t name the lever, don’t trust the number. Change one thing in the Season Simulator, rerun, compare. Consistency across plausible worlds is worth more than a single run that produces the “right” answer for reasons you can’t explain.

The takeaway

Simulators “love” some tracks because those tracks amplify specific strengths — qualifying execution when passing is hard, tyre management when degradation is high, clean-air control when traffic is costly. The value isn’t declaring a winner. It’s discovering which parts of performance actually decide points under different track archetypes.

If you want a grounded way to test that, run two or three calendar/assumption worlds in the Season Simulator and compare the distributions. When the conclusion survives those changes, you’ve found something real enough to base decisions on.