Race control that asks before it acts.
Auto Race Control watches the incidents and the race state, works out what race control would do, and shows you the exact call and the reason before anything is sent.
It types the same iRacing admin commands a steward would, so a person stays on the button: in Suggest it fires nothing, in Auto you can veto every call.
Auto Race Control is part of Pro. Try it free for 14 days from inside the app.
Suggest: every decision waits for you. Tap Fire to send it, or Dismiss.
Decision feed
Export: CSV or JSON- Full-course caution3 cars in an incident on lap 14Suggested
Audit log
Newest first- Race-control message to the admins
- Drive-through vetoed by the host
Suggest first, then Auto.
Nothing reaches the race until three switches line up, so the engine never surprises you. Run a whole race in Suggest, check the calls match the ones you would have made, then tune the rules before you arm Auto.
- Step 1: EnableIt is off by default and hidden until you enable it. Then its arm toggle joins the title bar.
- Step 2: ArmArming hands it the ability to act. Disarmed, it still watches and explains, and does nothing.
- Step 3: SuggestThe default. Every decision is listed with the exact call and a plain reason. You tap to fire or dismiss each one.
- Step 4: AutoDecisions fire on their own, still guarded: confirm each one, or set a veto window that counts down before a call is sent. A live-fire warning shows while it is armed.
Suggest
Auto
The same call on the sample race. Suggest waits for your tap; Auto sends it when the veto window runs out, unless you veto.
Cautions that a lone spin never throws.
An automatic caution needs a fresh cluster of incidents that is big or heavy enough: at least two cars by default, or one wreck past the severity you set. Tune the minimum cars, whether a stopped car counts as a hazard, the cluster window, the cooldown between cautions, the earliest lap, a no-caution window at the end and a cap per race.
Scheduled cautions
Independent of incidents, and sharing the same cooldown and cap, so a scheduled caution and an incident caution never double up.
- StageAt the lap numbers you set, or every N laps.
- TimedOn a caution clock, with optional jitter and a laps-to-go cutoff.
- RandomA capped number spread across a window of laps.
The caution, step by step.
iRacing ignores a restart, a pace-lap change or a wave-by until the pace car has picked up the field and crossed the line, so those calls are held and sent on the first completed pace lap.
- L12Green
- L1301CautionPits closed
- 02Pits open
- L1403Pace lap 1Wave-bys, then the line-up
- L1504One to goLate calls held
- L16Restart
05Every call on this strip fires and logs once.
- The cautionA caution flies for an incident cluster, a stopped car or the schedule.
- On the cautionThe pits close, then reopen a set number of seconds later.
- First pace lapWave-bys for the most-lapped cars, up to a cap per caution, then the pace laps and a single or double-file restart. Cars already waved around, on pit road or retired are skipped, and laps down count in class.
- One to goHold at one to go stops wave-bys and pace-lap changes that would arrive too late to count. The restart order still goes out.
- Every callEach call fires and logs once, so the engine never throws the same caution twice.
Penalties that only step one way.
A car’s incident points build over a window you set, and the ladder escalates one way: a warning, then a drive-through, then disqualification.
- Jumped startsOff by default. Flags a car that gained too many places off the line by the end of lap 1, with an end-of-line or drive-through penalty.
- Custom rulesYour own trigger and action: an incident cluster, a car’s points, every Nth incident, a first-lap incident, clean laps or a blue flag held too long. Scope each rule to classes, keep it off in the final laps, give it its own veto delay.
- Manual paletteDeploy a caution, set the restart, change pace laps, issue or clear an end-of-line, send a race-control message. Through the same checks, and in Suggest they queue so you can rehearse them.
The penalty ladder
- WarningFirst step
- Drive-throughMore points
- DisqualificationLast step
Each step fires once per car and never steps back.
Decision feed
The limits, stated plainly.
Auto Race Control is a tool for the person running race control, not a replacement for them.
- You need to be a session adminIt works by sending iRacing admin chat commands, and iRacing only accepts them from a session admin.
- Race sessions onlyOnly a race session is administered automatically. Practice and qualifying are left alone.
- It reads what iRacing sharesIncidents come from the same detection as the incident log, from the data iRacing makes available. Check the replay before you call a protest.
- Part of ProAuto Race Control, Race Admin and the stewards crawl come with Pro, League and Enterprise. Remote steward messages ride the cloud relay, so they need League.
- PracticeLeft alone
- QualifyingLeft alone
- RaceAdministered
- Session admin
- The host running EDR Broadcast
- Incidents
- From the incident log
- Plan
- Pro
On the sample race, with the host as session admin: only the race session is administered.
The same incident picture.
Incident detection feeds the caution rules, the Auto-Director’s incident cuts and the stewards. Remote stewards’ messages land in your veto cue before they reach air.
Incident log
0:41:02#23Sam VanceL132x
- Caution rulesFull-course caution 4 cars in an incident on lap 13
- Auto-DirectorIncident cut to #23
- Remote stewards#23 and #15, contact on lap 13: worth a look on the replayIn your veto cue
Sample data: one logged incident on lap 13 of the sample race, and where the same detection shows up.
Questions.
Does it work in any iRacing session?
Only where you are a session admin, because iRacing only takes admin commands from one, and only in a race session. That can be any race session you run as admin, hosted or league.
Will a single spin throw a caution?
Not with the defaults. An automatic caution needs at least two cars in a fresh incident cluster, unless one wreck passes the severity you set or you count a stopped car as a hazard.
What if a call is protested?
Export the decision feed as CSV or JSON. It lists every call the engine made or would have made, with its reason and what happened to it, for a stewards’ report.
Can remote stewards use it?
On League, remote stewards join a cloud room and their messages land in your veto cue. Urgent airs after a short catch window, Info after a longer one, and Official waits until you send it.
Which plan includes Auto Race Control?
Pro, and League and Enterprise above it. Every new install can try it on the 14-day Pro trial, with no card and no automatic charge.
Run your own show.
Auto Race Control is part of Pro, beside the Auto-Director, replay and incidents. Try every Pro feature for 14 days from inside the app: no card, no automatic charge.