How to learn a new track in ACC

The wrong way to learn a track: load it up, drive 100 laps at 90% pace, hope for the best. You'll end up faster than you started but with bad habits baked in — the wrong line through one corner because you found it once and never re-evaluated, the wrong gear because you never tried the alternative, an apex that's "fine" instead of optimal because your reference for "optimal" is yourself an hour ago.

The right way: a structured progression that builds knowledge before pace. Real-world racing schools use a 4–5 stage protocol; sim racing should adopt the same shape. The pacing is faster (no expensive crashes), the principle is identical.

PaceBoss's role here is the verification step. The per-track chip on /me tints by your gap to the field's fastest recorded lap at that track — green when you're at the front, red when you're far off. As you progress through the learning stages, the chip changes colour. That's the closest thing to a "have I learned this track yet?" diagnostic the data permits.

Stage 1: Look up

Before driving, before even loading the track, gather information.

• Track map. A diagram with corner numbers and approximate gear suggestions. ACC's in-game telemetry HUD or a community resource (RaceDepartment, official Kunos manual) provides this.
• Onboard videos. A clean lap from a fast driver. Watch full speed once, then segments (the hotlap-video methodology applies here).
• Track-walk video. Many F1 drivers and racing schools publish track-walk videos. They cover elevation changes, kerb usage, corner naming, line decisions. Worth 10 minutes before any driving.
• Reference braking points. Note where the alien starts braking — boards, lines, kerbs, gaps in the fence. You'll use these as anchors.

Time investment: 15–30 minutes. No driving yet.

Stage 2: Walk-through (slow laps)

Load the track, slow car (or your car at minimum pace). Drive 5–10 laps focused entirely on geometry, not time. Goals:

• Find the visual references for braking from your earlier video study.
• Drive the racing line deliberately — even if it costs you 5 seconds a lap. The line you build now will be the line you race; reinforcing the wrong line here costs you sessions later.
• Notice elevation changes, kerb usage, blind crests. You'll need to know what's over each crest before you reach it at race pace.
• Identify the "scary" corners — the ones you don't trust yet. Note them.

Time investment: 15–20 minutes. PaceBoss won't show useful data yet (your pace is intentionally slow).

Stage 3: Build pace deliberately

Now you can press. But not flat-out — the goal is to build comfortable pace incrementally, evaluating each corner as you increase commitment.

A useful pacing strategy: pick one corner per lap to push at race pace; drive the rest at 95%. The next lap, push the next corner. After 12–15 laps you've evaluated each corner individually at the limit. Then start chaining them.

This is where the grip envelope discipline matters most — you're discovering each corner's grip ceiling, not assuming it. Push one corner past the envelope, lift, learn, push less hard next time.

PaceBoss check at the end of this stage: open the session, look at SectorsChip. The sector(s) containing your "scary" corners are usually slowest. That tells you where to focus the next stage.

Stage 4: Race-pace simulation

Now drive a 30-minute stint at race pace with race-relevant context — fuel load, tyre wear, traffic if you can simulate it. Goals:

• Hold race pace, not qualifying pace.
• Build consistency. The pace-trend chart's spread should tighten lap-by-lap.
• Notice where you're inconsistent. Those are the corners that still need study — your race pace varies through them because you don't have the muscle memory yet.
• Try gear-selection alternatives. If a corner feels rushed in 4th, try 3rd. If the rear gets light in 2nd, try 3rd. You're testing technique decisions you couldn't evaluate at slower pace.

PaceBoss check at the end of this stage: consistency percentage and theoretical-best gap. If consistency is below 99% on a track you should know, you're still in the learning phase. If theoretical-best gap is large, you have potential you haven't combined yet — see why your pace plateaus.

Stage 5: Race-craft simulation (optional but recommended)

Once you're comfortable at race pace, simulate race scenarios: traffic (public lobby or AI), defensive driving, and a long enough stint to feel tyre wear. This stage is less about pace and more about turning solo pace into race results. PaceBoss won't track the race-craft elements directly, but the consistency metric will reflect whether you can hold pace under pressure.

What PaceBoss can show you across the stages

• Stage 1–2: nothing yet (you haven't generated meaningful data).
• Stage 3: SectorsChip shows which sectors contain your weakest corners. The cohort comparison (if you're racing against AI or in a session) tells you whether you're in the wrong gear, on the wrong line, or just slow.
• Stage 4: consistency percentage + theoretical-best gap together tell you whether you've stabilised at this track. Stable consistency below your usual benchmark means you've adapted to the track; stable consistency at your usual benchmark means you've fully absorbed it.
• Across multiple sessions on /me: the per-track chip's tint and sparkline shape track your progress over time. A chip that's red and flat means the track is unlearnt; orange and trending up means you're making progress; green and stable means you've largely solved the track.

The chip-tint progression (red → orange → yellow → green) over 5–10 sessions at a new track is the canonical "I've learned this track" signal.

Common ACC examples

A few tracks where the protocol pays off most:

• Bathurst (Mount Panorama). Single-lane Mountain section, blind crests, severe consequences. Skipping Stage 2 (walk-through laps) at Bathurst is a guaranteed expensive lesson. The track demands respect at every commitment level.
• The Nordschleife. ACC's longest track. There is no learning the Nordschleife in one session — it's a 3-month project of incremental discovery. Stage 3 (one corner at a time) maps cleanly to a track this long.
• Suzuka. Combination corners through the Esses + the chicane + 130R. High-speed direction changes that punish bad lines. Stage 4 (race-pace stints) reveals which Esses combination actually works for you, not just which one feels right at slow pace.
• Spa. Eau Rouge–Raidillon needs Stage 2 commitment-building before any race-pace work. The visual cues and the elevation change interact in ways you can't pre-script.

For each of these, the PaceBoss workflow is: drive Stage 3, check the per-track chip on /me, drive Stage 4, check it again. The chip's progression — both colour and sparkline shape — is your tracking metric.

Console caveat

The protocol is fully platform-agnostic. Two small console notes:

• In-game replay use. Without telemetry, console drivers rely more heavily on the in-game replay for learning. The protocol's Stage 1 (look up) should include watching your own previous laps in the replay, paying attention to your line and brake points. This is essentially free coaching.
• Hotlap-video selection. If you can find hotlaps from controller drivers (search "ACC PS5 hotlap [track]" or "ACC Xbox [track]"), prefer those over wheel-driver hotlaps for the technique segments. The lines transfer; the inputs don't.

Further reading

• Skip Barber Racing School — multi-stage track-learning is core to their methodology.
• Bondurant School — similar staged approach, focus on commitment-building.
• Ross Bentley, Speed Secrets — the chapter on track learning.
• Driver61's track guides — track-by-track breakdowns with commentary.

Related reading

• Improve at a specific track — the PaceBoss-side workflow once you've reached Stage 4 and want to triage which tracks need more work.
• Get faster from hotlap videos — the Stage 1 study methodology.
• The grip envelope — the discipline behind Stage 3 incremental commitment.
• Why your pace plateaus — what to do when Stage 4 stops yielding pace.