paceboss learn
open the app →
navigate

Learn

PaceBoss surfaces sector splits, consistency, and pace gaps from your ACC race results. The articles here are organised in three zones: understanding what those numbers mean, turning a reading into a practice goal, and improving the technique a slow sector points at. A standalone section covers championship management, and one article explains how to get a CSV in the first place.

Understanding what you're looking at

The data vocabulary and what PaceBoss can and cannot tell you from a SimResults CSV.

  • ACC timing primer: what the numbers mean — What S1, S2, S3 sector splits mean in ACC, what a SimResults CSV export contains, and what PaceBoss reads from it.
  • What PaceBoss can and can't tell you — The exact scope of PaceBoss's analysis: what a SimResults CSV contains, what it does not contain, and how to bridge the gap with replay and hotlap video.
  • Pace bands explained: excellent to terrible — The five PaceBoss pace bands and their thresholds — excellent through terrible — what each means in a race, and why cohort-relative comparison matters in multi-class sessions.
  • Consistency explained — What the consistency percentage actually measures, what 99.5% versus 97% feels like across a race, and how to use sector variance to find which part of the lap is losing you time.
  • Theoretical best lap, explained — What theoretical best lap means in ACC and SimResults, how PaceBoss computes it, when it lies, and what the gap to your actual best lap tells you.

Doing something with the data

Using a PaceBoss reading as the starting point for deliberate practice.

  • How to find your pace deficit — A step-by-step workflow for finding where your lap time is bleeding in an ACC session, using sector thermometers, the pace-trend chart, and the laps table to isolate which sector to attack first.
  • Why your pace plateaus — Three reasons ACC drivers stop improving — a slow specific sector, a consistency floor, or a genuine pace ceiling — with a PaceBoss diagnostic decision tree.
  • Improve at a specific track — How to read PaceBoss's /me career view to triage which tracks need work and turn that into a one-track training plan grounded in your own data.
  • How to learn a new track — A 5-stage protocol for learning a new ACC track, with PaceBoss chip-tint progression as the tracking metric.
  • Practice session protocol — A structured 4-block sim racing practice session grounded in deliberate-practice research, with a 5-minute PaceBoss post-session review to connect each session's goal to a measurable result.
  • Bracket-relative learning — Why studying a driver 2 seconds per lap faster produces more improvement than studying the world record, and how to find that driver in PaceBoss's classification table.

Going faster (after PaceBoss points you at a sector)

Technique-level guidance for the corner type your sector loss is in.

  • Trail braking explained — Trail braking in ACC: why carrying brake pressure past turn-in rotates the car, which corner types it helps, and how to verify in the replay when entry braking is the issue.
  • Threshold braking — Maximum deceleration, when ABS-on is faster than ABS-off for most drivers, and the PaceBoss sector-variance signature that shows inconsistent braking zones.
  • Throttle modulation — Why rolling onto the throttle proportionally beats stabbing it at corner exit, and the sector-variance signature PaceBoss shows when exit modulation is the issue.
  • The grip envelope — The friction circle applied to ACC: why a tyre's grip budget is finite and shared between braking, cornering, and acceleration, and how exceeding it explains slow-sector signatures.
  • Looking ahead — How vision technique drives consistency before peak pace in sim racing, why it shows up in PaceBoss consistency data first, and how to train it in ACC.
  • Get faster from hotlap videos — Why copying inputs from alien ACC hotlap videos does not work, and what to extract instead: braking references, throttle pickup positions, racing lines.

Standalone

  • Run a championship — How to build a sim racing league championship in PaceBoss: create a championship, attach CSV imports as rounds, set a points scheme, handle drop-rounds, and export the standings table.

Start here if you don't have a CSV yet

  • Get your CSV — How to export a SimResults CSV from an ACC result file so you have the data source PaceBoss needs.

ACC race data

Lap time benchmarks, sector distributions, and car adoption stats drawn from the PaceBoss corpus — 3,902 drivers, 25 circuits, 51 cars, 470,618 race laps.

  • ACC race data — Per-circuit sector envelopes, per-car median lap benchmarks, and class adoption breakdowns sourced from publicly available ACC multiplayer results.