Live timing and the stream overlay
Follow a race weekend live, session by session, and put what happens in it on a stream with the casters' overlay.
Every server bdr's agents run has a live timing page: the running order of the session under way, built from the sector lines the cars cross, as the server reports them. Next to it is a stream overlay for casters: a page for OBS that calls out overtakes, best laps, contacts and damage as they happen.
Opening live timing
- An open lobby: on the lobby's page, select Live timing under what it is doing now. It shows while the server reports a session.
- A race: on the race page, under Splits, select Live timing in a split's live row. It shows while the split's server runs a session.
The address is /timing/<server>. Anyone with it can watch; it needs no sign-in.
The board
One row per car, the leader first:
| Column | What it shows |
|---|---|
| Pos | The place. In a race, by how far each car has come, timing point by timing point. In practice and qualifying, by best lap. |
| Gap | In a race, the time to the leader, taken where the car is now, or the laps it is down. In practice and qualifying, To best: the time to the fastest lap. |
| Last, Best | The last lap and the car's best. Purple is the fastest of the session, green the car's own best, struck through a lap that was cut. |
| S1–S3 | The sectors of the lap under way, or of the last lap at the line. |
Pit next to a name means the car came in at the end of its lap. What changes lights up first, then the rows move, so you see who passed whom.
The board is Provisional: it comes from the sector lines, not from the result. The result is the server's own file, which arrives when the session ends.
A weekend, one tab per session
When a server's weekend has more than one session, each gets a tab: Practice, Qualifying, Race, numbered when there are several of a kind (Race 1, Race 2). The running session has a red dot.
- The page follows the running session. When qualifying ends and the race starts, it moves to the race by itself, and qualifying stays as its own tab.
- Select a finished session's tab to see how it ended. The page then stays there; the running session's tab pulses when the next session starts.
- Once the server's result file for a finished session has arrived, its tab gets a check mark and Official result leads to its results page.
A weekend is one pass through the sessions the server was given: a race's practice, qualifying and race, or the sessions you set for a lobby, several of one kind included. A lobby loops its weekend, so when it starts again from its first session, or when the server goes back to practice because everyone left, the tabs start over too.
Note
Live timing is kept while it happens, not stored for later: three hours after the last lap the tabs are gone, and the results stay, on the session's page.
When the timing stops
Nothing driven is lost when the platform or the agent restarts in the middle of a session. The agent on the server keeps every timing point until the platform has it, and sends again whatever the platform missed.
- Reconnecting: when we update the platform, the page loses its connection for a few seconds and says Reconnecting. It comes back by itself, and the laps driven meanwhile follow.
- Catching up: after such a gap, the server sends what it kept. The page says how many timing points are still to come; until then the board may be a few laps behind.
- Lost contact with the server: the server's agent stopped reporting while cars were on track. Usually it is back within a minute or two, and the timing carries on by itself. After ten minutes the note changes to No word from the server: the server may be down.
An agent that restarts while the server runs goes on reading the server where it left off, so the session, the drivers and the timing carry on too.
The stream overlay
Note
The overlay is a preview: it is new and still being tested. If you run a test race or stream with it, tell us how it went on our Discord.
The overlay is a transparent page for an OBS Browser source, made to sit next to ACC's own broadcast HUD. It shows nothing but the moments it calls out, one card each, in the look of ACC's HUD:
| Card | When |
|---|---|
| Overtake | In a race, a car is now ahead of a car that was ahead of it. It is seen at the next timing point, so up to a sector late. A car going into the pits is not passed. |
| Fastest lap | A valid lap faster than every lap before it in the session. |
| Personal best | A valid lap faster than the car's own best, from its third lap on. |
| Contact | The server reports two cars touching. The same two again within five seconds count once. Not shown since 19 October 2026 (see For platform admins below). |
| Damage | The server reports a car's damage grew. Not shown since 19 October 2026 (see For platform admins below). |
Each card slides in, stays a few seconds and slides out. When many happen at once, a few show and the rest wait their turn; when too many wait, the oldest go.
Getting the link
- Select Stream overlay on the live timing page.
- On a race page, each split has Stream overlay next to its server's name as soon as it has a server, so you can set OBS up before the start.
The address is /timing/<server>/overlay. It shows the session that is running, and follows the weekend into the next one by itself.
Setting it up in OBS
- Add a Browser source and paste the overlay's address as its URL.
- Set the width and height to your canvas, such as 1920 × 1080.
- Leave the background transparent. Place the source over the game.
Change what it shows by adding these to the address, joined with & after a ?:
| Option | Does | Default |
|---|---|---|
corner= |
Where the cards stack: top-left, top-right, bottom-left, bottom-right. |
bottom-left |
hold= |
How many seconds a card stays, 3 to 30. | 7 |
stack= |
How many cards show at once, 1 to 6. | 3 |
show= |
Which cards, separated by commas: overtake, fastest_lap, personal_best, contact, damage. |
all |
For example, only overtakes and the fastest lap, at the top right:
/timing/<server>/overlay?corner=top-right&show=overtake,fastest_lap
The demo
Platform admins can watch a made-up weekend: Live timing demo on the platform overview, at /timing/demo. It plays a short qualifying and then a race, with overtakes, pit stops, cut laps and contacts, at 1, 5, 20 or 60 times the pace. The overlay of the demo is at /timing/demo/overlay; it takes speed= as well as the options above:
/timing/demo/overlay?speed=20
Each time the page opens, the demo starts again with a new field.
For platform admins
Below the board, platform admins see Server contacts · admins: what the server itself reported for the open tab's session, as our spectator heard it until 19 October 2026. Every contact with another car or with a wall, its impact value, and every change of a car's damage, newest first. The same list is on the session's page once its result is in. It was recorded to learn what the server's numbers mean, and it is not rated.
Note
Contacts have not been recorded since 19 October 2026. The server only reports them to a client connected to it, and a client that stays on the server made ACC's lobby list show our servers with one driver, however many were on them. Sessions from before keep their list.