Back to blog
director-apparchitecturemcp

Director v3: the broadcast moved onto your own hardware

Why we rebuilt the Sim RaceCenter Director as a local Electron app with a deterministic core and MCP at every seam, and what happened to the Race Control cloud.

·Sim RaceCenter Team·3 min read
On this page

The first Sim RaceCenter Director was a desktop client of a cloud service. Race Control, a web app on Azure, held the drivers, rigs and sessions. A serverless API planned every camera sequence with a hosted model, and the desktop app polled for the next one. Telemetry went up to the cloud and decisions came back down.

It worked, but a live broadcast depended on a login, a network round trip and a model call for every cut. When any of those stalled, the broadcast stalled with it. The executor cascade post-mortem covers one of those afternoons.

Director v3 is the rebuild. It runs on a Windows broadcast host on the same network as OBS, and has no cloud dependency.

What Director is now

Director is a Windows desktop app built on Electron. Underneath, Director is a local hub:

  • It runs OBS control and communications (Discord voice, text to speech) as native services inside the app.
  • It receives race events from the publisher on each driving Rig over authenticated HTTPS. It drives cameras and replays through the simulator MCP server on a spectator host.
  • Its in-app agent uses the same brokered tools as the operator. An aggregate MCP endpoint for external agents is planned.

Nothing in the broadcast path needs an account, a login or an outbound API.

A deterministic core

The decision of what to show is no longer a model call. Every cycle, a TypeScript core in Electron main scores what is happening on track and picks a shot pack. Battles for position, overtakes, traffic trains, pit windows, incidents, restarts and leader gaps each have one. A shot pack is a versioned recipe of iRacing camera, OBS scene and dwell steps. The binder fills it with real cars and cameras, and the executor runs it through MCP.

Because the core is deterministic, the same race input always produces the same cut list. That is what lets us test it: hundreds of frozen golden cases replay through the core on every change.

On top of that core sit the features that make a broadcast watchable:

  • Focus drivers with a focus-weight control, from "follow the field" to "follow my drivers".
  • Replays of incidents, aired under cover of an onboard cut so the viewer never sees the replay seek.
  • A post-race highlight reel built from every incident that was a replay candidate.
  • Overlay graphics rendered by Director and composited in OBS.
  • Preflight checks, an ALL STOP that halts the run, Rig publishers and speech in one action, and a separate one-press safe scene.

The agent is advisory

AI is still part of the product, but in a different role. The optional Broadcast Agent plans, explains and helps with setup. Changes follow plan → confirm → apply → verify, dangerous actions stay operator-only, and nothing an agent does can lock up the broadcast. Every decision, whether it came from the operator, the core or the agent, lands in the activity stream and in the run's evidence bundle.

What happened to Race Control

The Race Control web app and API have been retired. This site is now a static product site. Older posts that describe the cloud architecture are kept in the archive for history.

The simulator side moved the other way: into the open. The simulator MCP servers that read iRacing and Le Mans Ultimate are GPL-3.0 and accept contributions.

You can watch a Director-produced broadcast on YouTube.