Plan: Pro

A logged incident is one click from its replay.

The incident log watches the whole field and flags contact, spins, offs and stopped cars as they happen. Click a row and the replay jumps to the moment.

Detection works from the data iRacing makes available, so check the footage before you call what happened on air.

Incident detection, replay control and race control are part of Pro. Try them free for 14 days.

The incident log docked beside the timing board during a sample race: recording live, a 15 second rewind, and four incidents on lap 13 for cars 12, 15, 23 and 11, each with its count and a Jump button
Jump#12 Liam Marsh, lap 13: the replay starts at 0:40:54, 15 s before the incident.

Never miss the replay.

Each row shows the car, what happened and when. Mode follows iRacing’s own incident feed where it can, infers from telemetry where it cannot, or shows raw events.

The incident log: recording live, four incidents on lap 13 for cars 12, 15, 23 and 11, each with its incident count and a Jump button
  • Jump to the momentClick a row and the replay goes straight to it. A rewind buffer lands the jump a few seconds before the contact.
  • Filter the noiseThe type filter narrows the log to the kinds of incident you care about.
  • Road and ovalRoad and oval tracks keep separate thresholds, so the log suits the event.
  • One picture for the crewThe same detections drive the stewards crawl, the Auto-Director’s incident cuts and, in a cloud room on League, the remote viewers.

Replay from the same screen.

The Director panel sits beside the timing board, so the shot, the replay and the race order are in front of the same operator.

The Director panel: camera buttons, replay transport, playback speeds from a quarter speed to four times with Live selected, and Replay
  • TransportPlay, pause, go live, rewind and fast-forward, scrub by 5 or 30 seconds, jump to a session time.
  • SpeedStep the playback speed down to slow motion, then back to live.
  • Clean captureToggle the iRacing interface off for a clean replay, and save a clip.
Plan: Pro

Race control, with a human on the button.

Auto Race Control is the automatic side of race admin: it can throw full-course cautions, run pit and restart procedure, wave lapped cars by and apply an escalating penalty ladder, from rules you tune. It is off until you enable it, and nothing reaches the race until you arm it.

See race control

The app’s top bar with Auto Race Control armed in Suggest mode: a suggested wave-by for lapped car 14 under caution, waiting on its Fire button
Suggest mode: the call waits in the top bar, with its reason, until you press Fire.
  • Suggest firstIn Suggest mode every decision is listed with the exact call and a plain reason, and nothing fires until you tap it.
  • Auto, still guardedIn Auto mode you can confirm each call, or set a veto window that counts down before an action is sent.
  • A record of every callExport the decision feed as CSV or JSON for a post-race stewards’ report.
  • Manual paletteDeploy a caution, set the restart, adjust pace laps, issue a penalty or send a race-control message, through the same checks.

Questions.

The Auto-Director uses the same detections to cut to an incident as it happens.

Is every detected incident certain?

No. The log works from the data iRacing makes available and flags likely moments so a human crew finds them faster. It is a broadcast aid, not a steward’s decision.

What can it flag?

Contact, spins, offs, stopped and mechanically slow cars, and full-course cautions.

Can I jump the replay to an incident?

Yes. Click an incident in the log and the replay jumps to that moment, a few seconds early, ready to frame a follow-up shot.

Which plan includes incident detection, replay and race control?

Pro, and League and Enterprise above it. Every new install can try them on the 14-day Pro trial, with no card and no automatic charge.

Run your own show.

Incidents, replay and race control are part of Pro. Try every Pro feature for 14 days from inside the app: no card, no automatic charge.