Track Limits

Track Limits compares a car’s position with the circuit boundaries published for that track and layout. When enabled and configured for an event, it can show a possible excursion, validate the outcome and report applied limits to race direction. The configuration matters: a circuit with no published limits cannot be judged the same way.

What the driver sees

A possible excursion first shows VALIDATING. This is provisional and does not yet add to the counter. The helper colors indicate how validation is progressing; the final text is what matters:

The HUD displays a TRACK LIMITS · N count for applied events in that session. A provisional or cancelled event does not increment it. In some practice or qualifying workflows, a lap may also be marked invalid when the integration can act on local ACSM results. That integration is separate from simply installing the event CSP block.

What to do after leaving the track

Return to the circuit safely, leave room for traffic and follow your event’s sporting rules. Do not brake abruptly or stop in a dangerous place to influence an automatic decision. The detector may consider how long you were outside, the available telemetry and whether any gained time was returned, but exact thresholds can vary with the published configuration. A color alone is not a final verdict.

If a boundary seems wrong, record the circuit, layout, lap and an image or replay, then report it to your organizer after it is safe. Race officials can review the event in the private Race direction console.

For organizers

Indy oval mode

In the Track Limits editor, select Indy oval · first tyre edge, then publish the configuration for the intended circuit/layout. Any measured part of one tyre crossing the published boundary starts validation immediately; touching the boundary without crossing is legal. The standard full-wheel mode remains the default. The existing validation and applied/cancelled outcomes still apply; this is not an automatic penalty.

Place and review the boundary on the legal edge of the event’s white line. Auto Lines may follow a kerb instead and does not establish the Indy sporting boundary. Test both sides and pit entry/exit before competition. Indy detection requires published world-space borders and valid tyre geometry; native AC wheels-out counts cannot establish a partial-tyre crossing.

Track boundaries are published per circuit and layout. The repository and editor let authorized officials review limits.json, sectors and the active revision. RaceControl delivers the matching published configuration to eligible sessions. Test a new track configuration before competition, including pit-lane exclusions and the route actually loaded by ACSM.

Mesh touch (bollards, cones, …)

A circuit configuration may also name track meshes that count as a track limit when touched. Each rule sets a mesh name pattern (for example bollard_*), a label and a touch radius in metres:

{
  "meshRules": [
    {"pattern": "bollard_*", "label": "Bolardo T3", "radiusM": 2.5}
  ]
}

Touching a configured mesh opens a VALIDATING event, exactly like a boundary exit: it is provisional until the usual time-loss validation decides APPLIED or CANCELLED. It is not an automatic penalty, and direction reviews it in the same console. Rules that match zero or several meshes stay disabled rather than guessing; the organizer’s in-game explorer shows the match count and live distance so patterns can be verified before publishing. New rules only apply after the configuration is published for that circuit and layout.

Changing a published boundary during a session can change subsequent judgments; communicate such a change under your event rules. The public documentation does not replace the circuit-specific limits file or the organizer’s regulations.