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.
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.
PaceBoss's role 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 stages, the chip changes colour. That's the closest thing to a "have I learned this track?" 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.
- 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.
- 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 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.
PaceBoss check: Open the session, look at SectorsChip. The sector(s) containing your "scary" corners are usually slowest. That tells you where to focus next.
Stage 4: Race-pace simulation
Drive a 30-minute stint at race pace with race-relevant context — fuel load, tyre wear, traffic if you can simulate it.
- 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.
- Try gear-selection alternatives. If a corner feels rushed in 4th, try 3rd.
PaceBoss check: 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.
Once race-pace stints are stable, the session history on /me will show the chip trending upward. That's the learning signal.
Common ACC examples
- 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 Nordschleife. 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 + chicane + 130R. Stage 4 race-pace stints reveal 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.
Further reading
- Skip Barber Racing School — multi-stage track learning as core methodology.
- 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 — PaceBoss 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.
questions
- How many sessions does it take to learn a new ACC track?
- Depends on the track. Most tracks stabilise in 5–10 sessions following a structured protocol. The PaceBoss per-track chip progressing from red to green over those sessions is the closest thing to a quantified 'I have learned this track' signal.
- What is the biggest mistake when learning a new track?
- Driving 100 laps at race pace on day one. This bakes in the wrong line through corners you found accidentally. A slow walk-through phase — 5–10 laps at deliberate pace — builds the correct geometry before pace.