Race Engineer reads iRacing's telemetry SDK and turns it into decisions: how much fuel to put in, when the pit window opens, and whether your pace can hold. It never touches your inputs and never sends chat messages you didn't configure.
Race Engineer recalculates fuel-to-end from your actual burn rate, not a fixed average — so the number you see accounts for fuel-saving, traffic, and changing stint length as the race unfolds. It also cross-checks the car's fuel sensor against measured consumption, so a bad reading gets caught instead of trusted blindly.
In Automatic Mode, Race Engineer sets exactly how much fuel to add at your next stop, so you don't do the math at 300 km/h. It only ever adjusts the fuel service amount — never your inputs, never a chat message — and every change is gated so it can't fire outside a pit stop.
Fuel, tire wear, and your current pace are tracked together to flag when the pit window opens — and when staying out starts costing more time than it saves.
Race Engineer only speaks up when iRacing itself hasn't already told you: a track declared wet, a fuel-save target you're missing, an over-rev on downshift. If iRacing already shows it on screen, Race Engineer stays quiet.
Lap times, fuel used, pit stops, and cautions are logged per car and track, so you can come back to a previous race and see exactly how the strategy played out. Nothing leaves your machine — it's a local database, not an account.
The full interface — dashboard, history, alerts — is available in English and Portuguese today, and you can switch languages from settings without restarting.
iRacing's SDK allows firing a chat macro slot you've already set up in-sim. Race Engineer can trigger one of those on an event you choose — it can never type a free-form message on your behalf.
Every update is downloaded and SHA-256 verified before anything installs, and it will never install while you're connected to iRacing. If a new version fails to start, it rolls back automatically.