Guide - for league owners

Your racing is better than your broadcast

Most sim racing leagues put on genuinely good racing every week, and then stream it with no commentary, one camera, and nobody watching. Or they don't stream it at all. Here is why that happens, and what it takes to fix.

What a race broadcast actually needs

Watch any real motorsport coverage and count the jobs being done. There is someone deciding which car the audience should be looking at. Someone choosing whether that is an onboard shot or a trackside pan. Someone talking, constantly, explaining what the picture means. And someone running the production - overlays, replays, the stream itself.

A sim racing league needs the same four jobs covered. The difference is that a broadcaster has four people doing them, and your league has whoever answered the Discord message on Wednesday.

Why it doesn't happen

The problem is not that league owners don't care about production. It is that the job repeats. Every single race night, someone has to sit in a spectator seat for two hours doing nothing but watching other people race - and then do it again next week, and the week after.

Camera duty is boring. Commentary is worse, because it is boring and exposed - talking continuously for two hours is genuinely hard, and most people who try it once don't volunteer again. So the rota thins out, and eventually the stream goes out silent with a fixed camera on the leader, which is a worse advert for your league than not streaming at all.

What actually makes a broadcast exciting

It is worth being precise about this, because the instinct is usually wrong. A more exciting broadcast is not a matter of better overlays, a slicker intro, or a nicer camera path. Production polish is what people notice when the racing is already being covered well. It cannot rescue coverage that is pointed at the wrong car.

What makes a race watchable is being shown the thing that is about to happen. A gap that has been shrinking for three laps. Two cars going into a braking zone side by side. A driver who just went off and is rejoining into traffic. Those moments are what an audience remembers, and every one of them is a decision - somebody chose to be looking there at that second.

This is also why leader-cam is such a poor default. The leader is frequently the least interesting car on track, because being fastest often means driving alone. The race - the part with jeopardy in it - is usually somewhere in the middle of the field, involving drivers who will never appear on a highlights package unless someone deliberately points a camera at them.

So the job is not really camera operation. It is judgement, applied continuously, for two hours, across twenty cars at once. That is a genuinely hard thing to ask a volunteer to do well every week - and, as it turns out, a very well-suited job for something that can watch all twenty cars simultaneously and never gets bored.

What automatic cameras get you, and what they don't

There are automatic camera tools. rFactor 2 has a couple of plugins. iRacing has camera automation built in. If you are running Le Mans Ultimate, there is nothing at all.

The trouble with them is that they are a black box. The camera cuts somewhere, and you have no idea what it was reacting to or whether it considered the fight you wanted to see. When the coverage is wrong there is nothing to look at and nothing to learn from - you either accept it or go back to doing the job by hand.

And picking the camera is only part of the challenge. None of them say a word. Camera automation covers the easier half of the problem and leaves the half your audience actually notices.

Covering all four jobs automatically

BattleDirector is built to do the director's job rather than the camera operator's. It reads live telemetry and scores every car on track for how interesting it is right now - how close its battle is, where it sits in the order, whether it just had an incident, whether it is running side by side, and how long since the audience last saw it. It cuts to the best of them.

It also knows when not to cut. A tight battle is protected, so the broadcast doesn't walk away from the thing you tuned in for. Lead changes interrupt everything. A maximum time on any one car forces variety, so no driver gets forgotten and no broadcast goes stale.

Camera choice follows the situation rather than a rotation. Trackside for packs, because three cars side by side need the width. Onboard for a close duel. Under a tenth and a half of a second apart, it goes to the cockpit every time, because that is the shot that moment deserves.

Then it talks. Live commentary across 67 event types - lead changes, overtakes that stick and ones that don't, incidents, fastest laps, purple sectors, fuel, session timing, the podium. It is class-aware, so in a multi-class field it tells you someone took the lead in Hypercar rather than just taking the lead. If you run rFactor 2 Log Analyzer, it can pull your championship standings in and know when the pass it is describing matters to the title.

The parts of a race weekend that aren't the race

Coverage is not only the two hours of green flag running, and this is where league broadcasts usually fall down hardest. BattleDirector runs an F1-style grid walk on a manual formation lap, going through the field class by class and introducing each driver and car. It reads out qualifying results. After the flag it walks the finishers.

There is also a race control system - a Virtual Formation Lap, and Code XX, a safety car analogue that can trigger itself when it spots a cluster of incidents. Those announcements go out in a separate race control voice, and the Discord bot can read them to your drivers in a voice channel while your viewers hear them on the stream. Both of those are early preview and off by default - newer than the grid walk and ceremony, which are well tested.

What race night looks like

Your broadcast PC joins the server as a spectator, exactly as it would if a person were about to sit there. You start BattleDirector on that machine, and you leave.

It takes the formation lap, runs the race, tightens up its cutting on the last lap, and walks through the top three after the flag. If something big happens it rolls a replay - and if a good fight is running at that moment, it holds the replay until the action calms rather than cutting away from live racing.

Nothing about your existing setup changes. It drives the game's cameras, not your stream, so your streaming software captures the game window exactly as it does now and your overlays keep working untouched. Commentary plays to the system audio device as another source. And because it runs on the broadcast box rather than on anyone's racing rig, no driver's frame times are affected by it.

Where to start

With one race. Point it at a session you were going to stream anyway, leave it alone for two hours, and watch the result back. You will know within a few laps whether it is cutting to the things you would have cut to.

BattleDirector runs on Windows and works with rFactor 2 and Le Mans Ultimate today, with iRacing planned. It is in active beta, and preview access is handed out through the Discord ahead of Steam early access - so that is currently the way to get a copy and try exactly that.