RaceControl · Organizers
Race direction console
Use the live map, flags, messages, incidents and decisions.
Race direction is the private, live workspace for a licensed organization. It shows one selected server session at a time so actions go to the intended race. It is a control surface for officials, not a public spectator page.
Before you issue an action
Check the server name, circuit, session type and LIVE state at the top of the console. When several sessions are available, choose the correct one first. The live map shows the circuit and car positions when current telemetry is available; a missing map position is not proof that a car has left the event.
The top status bar shows whether the rolling-start feature is enabled. Its toggle changes the feature state and should be used deliberately. Synchronize refreshes the console data; the normal live updates continue without it.
Control the track
The Track status panel issues flags and procedures such as GREEN, YELLOW, double yellow, Safety Car, FCY, RED, BLUE, WHITE, pit closed and formation. Some flags can apply to a selected area of the circuit. The map and configuration dialog help define that area. BLUE requires a target car. Confirm the active state shown after an action; color and icon alone are not a substitute for checking its text.
Communicate and decide
- Communications: send a text instruction to all drivers or a target, choose its severity and duration, or send a short voice message to an eligible radio client.
- Decision: select a driver, choose a warning or penalty type, provide any required value and a reason, then issue the decision.
- Operational register: open incidents, penalties, the timeline or Track Limits to review what has happened and update a case.
- Instant replays: view detected replay candidates when a broadcast client is connected. Replay availability depends on that client.
The history page is available from the console. The public board is separate and only appears when the organization publishes it.
Live actions can affect drivers. Verify the selected session, car and command before sending; use your event’s sporting rules for decisions.
If the console has no session
Check that the correct ACSM event is enabled in Settings, the server is linked in /account, the connector has synced and the game server is running. A client with the HUD may need to join before the console has useful live data. The history page can still show earlier activity.