The hard part of building a useful sim-racing spotter is not making it talk. The hard part is teaching it when the driver actually needs to hear something.
Most race-radio systems begin with the same obvious idea: an event happens, so the software says something about it. A car appears on the left. A flag changes. A lap completes. A gap moves. The tires change temperature. The driver misses an apex.
Every one of those facts can be useful. Stack them together at the wrong moment and they become noise.
That is the problem we are working on now inside Lynx-Vector. Radar and GripSense are already the public Open Beta tools. The next major capability in development is a coordinated iRacing race-radio system with Spotter, Crew Chief, Engineer, and Race Official roles.
A Spotter Is a Scheduling Problem Disguised as a Voice Problem
Making speech is easy compared with deciding which message deserves the radio. A driver entering a braking zone does not need three useful facts at the same time. They need the one fact that matters most right now.
We have been treating the radio as three competing information planes: Safety, Coaching, and Narrative. They all matter, but they do not have equal priority.
Plane One: Safety
Safety calls win. Nearby traffic, overlap, left/right/clear, and fast-arriving threats are the kind of information that can change the driver's next input immediately.
That means a side call has to be able to interrupt lower-priority chatter. If the Crew Chief is talking about a gap and another car reaches the driver's door, the race story can wait.
It also means timing matters. A technically correct call that arrives half a corner late is not useful just because the underlying data was accurate.
Plane Two: Coaching
Coaching is useful only when the driver has enough bandwidth to do something with it. Braking, entry, exit, grip, and vehicle-balance feedback can help build consistency, but a coaching line should not compete with immediate traffic or arrive at the exact moment the driver is committing to turn-in.
The Engineer role is being designed around those useful windows. The goal is not to pretend telemetry can see everything a real race engineer can see. The goal is to use the signals that are actually available, make conservative inferences, and deliver the feedback when it can still help.
Plane Three: Narrative
A race has a story. Position changes, gaps, clear track, traffic, a repeated battle with the same car, a late charge, or the final laps all change what the driver cares about.
That is where the Crew Chief comes in. The Crew Chief should help the driver understand the race without turning every straight into a podcast. Narrative belongs in the quiet spaces, and it should disappear the moment Safety needs the channel.
Four Roles, One Radio
We are separating responsibilities because it makes the decision-making clearer.
- Spotter: immediate nearby-car and traffic safety.
- Crew Chief: battles, gaps, position changes, objectives, and race narrative.
- Engineer: driver coaching and telemetry-derived vehicle feedback.
- Race Official: flags, start/finish state, and race-control context.
The driver should not have to care which internal role generated a call. The point of the separation is to make priority and timing better, not to add another configuration chore.
More Chattiness Should Not Mean More Bad Timing
There is an important difference between a talkative radio and an undisciplined radio. A driver may want a lot of information on a long straight and almost none of it at corner entry. Those are not contradictory preferences.
The system therefore has to think about attention, not just message count. Higher chattiness can fill quiet periods with useful context while still protecting the moments where the driver's eyes, hands, and brain are already busy.
Truth Matters More Than Personality
A race-radio system can sound convincing long before it becomes trustworthy. That is a dangerous trap. We would rather omit a clever call than invent certainty the telemetry does not support.
The same rule applies to damage, tire state, grip, and strategy. If the available data supports a conservative statement, make it. If it does not, do not dress a guess up as a fact because it sounds like something a real crew chief might say.
Coming to Lynx-Vector
The advanced race radio is still in active development. Radar and GripSense remain the current Lynx-Vector Open Beta experience, and we are not labeling unfinished radio behavior as a released feature.
But the direction is now clear: a race-aware system that can watch the traffic, coach the driver, understand the developing race, and know when silence is the most useful call it can make.
Follow the current Lynx-Vector build at: signallynx.com/racing/sim-racing/driver-awareness