airaceGP Docs

Customizing the engineer

Almost everything about how the engineer behaves is a setting. The new controls below include their defaults. Open Settings and look in the groups below. Games differ: items marked ACC only appear for Assetto Corsa Competizione.

How much it talks #

  • Chattiness (0 to 100): how readily it volunteers an unprompted call.
  • Verbosity: how much detail each call carries.
  • Call interval: how often the engineer considers speaking on its own.
  • Allow the engineer to stay quiet: lets it say nothing when there is nothing worth saying.
  • Quiet button (Settings → Audio, or Quiet on the home bar): a button on your wheel (or a key) that toggles quiet mode for the session. The engineer stops volunteering routine calls and says so; your questions are still answered and urgent calls still come through. Press again for the radio back.
  • Space between calls. Default: 0 (off). Range: 0 to 120 s; a routine call that would land sooner than this after the last one is dropped. Urgent calls and your questions always go out. Off at 0.
  • Longest routine call. Default: 0 (off). When enabled, 5 to 60 words; shortens a volunteered call, at a whole sentence where it can. Your questions are never shortened. Off at 0.
  • Hold calls through corners and Longest hold (ACC only): waits for the corner exit before speaking, never past the longest hold, and never for urgent calls.

What it talks about #

  • Fuel updates on or off, and the fuel plan to the flag.
  • Drink reminder (0 to 60 min): every this many minutes of driving the engineer reminds you to drink. The clock only runs while you are on track. Off at 0.
  • Say what's on the dash: read out dash warnings.
  • Warn about the mandatory pit stop and First reminder: when the first reminder comes.
  • Sector coaching is ACC only, beta and off by default. It compares sectors with your own best and stays quiet on invalid or incident laps.
  • Spin detection: handled in the app, with an option to hand it to the AI instead.
  • Custom instructions: a few lines of your own guidance, applied on top of the built-in prompt.

Space between calls drops routine calls that arrive too soon; Longest routine call shortens volunteered calls. Both are off by default and neither shortens your answers.

Voice and language #

  • Engineer language: nine languages, translated on your PC with no cloud service. A language pack downloads once, the first time you pick it.
  • Voices: the English default is Cori, a clear British voice; a male American English voice downloads from the same list. Choose an installed voice or download another from Settings → Voice, and set the volume.
  • Microphone and speech recognition: pick the input, the speech model size, and whether the mic is on.
  • Interrupt sensitivity: how loud you must be to cut the engineer off.
  • Wake word: optionally start a question by name instead of by voice activity.
  • Push to talk (Settings → Audio): talk with a detected controller button, a D-pad direction or a key. Press Bind button, then the button. Hold: the engineer hears you only while it is held, and letting go sends the question. Tap: tap once, then speak; the question ends when you stop. Pressing it while the engineer talks cuts him off. It works while the game has focus; if the wheel is unplugged, voice detection takes over and the app shows AIR-408. Off leaves voice detection on its own.
  • App language is separate from the engineer's language.

The AI behind it #

  • Model chain: one chain for unprompted calls and one for your questions, each an ordered list of providers and models. See The model chain.
  • Use fallbacks: if the first entry fails, ask the next. A failure shows its error code and the fix.
  • Smart routing: send simple questions to a small, fast model.
  • Custom endpoint: any OpenAI-compatible service. Its terms and data handling are between you and its operator.
  • Prompt override: replace the built-in system prompt entirely. For advanced use.

If every AI provider fails, a driver-question fallback uses the app's facts or says plainly that there is no answer.

Data and network #

  • Record sessions: keep a recording of each session for the Analysis page. Recordings stay on your PC.
  • ACC broadcasting: read rivals and gaps from ACC's Broadcasting API (read-only).
  • UDP format (F1 25): must match the game's telemetry settings. If packets do not match, the app skips them and shows AIR-308.
  • Forward UDP (F1 25): F1 sends telemetry to one address only. List up to four host:port targets, for example 127.0.0.1:20777, and the app re-sends every packet there unchanged, so SimHub, RaceLab or a motion rig keep working. Point those tools at the port you list.
  • LAN dashboard: show the dashboard to another device on your network. Keys and restart stay on the race PC.

Driver memory across sessions

Settings → AI → Remember me between sessions. Default: on.

Driver memory keeps the last 8 sessions per game, track and car in driver_memory.json on your PC. The file is never uploaded.

It remembers best and typical clean laps, fuel per lap, hot tyre pressures and temperatures, peak brake temperatures, pit stops and where the car stepped out as a percentage of the lap.

Remember me between sessions is on by default. Turning it off stops recording and recall; Forget everything clears saved driver memory.

Memory is ACC only for now: F1 frames have no track/car identity. The remembered summary can enter requests to your chosen AI provider; its spoken wording has not had a live-model check.

Strategy planner

Ask about stops or fuel in an ACC race: the strategy planner works out when to stop, how much to add and whether the fuel reaches the flag, in laps, never litres, with a 1-lap reserve.

Fuel saving is suggested only within a realistic limit. The planner does not model tyre wear, traffic, undercuts or safety cars; ACC pit-window units remain unverified, so that window is not used.

Setup advice

Setup advice compares measured hot tyre pressures with the dry or wet pressure window and gives the change in psi per corner, using recent sessions or the live frame when memory is off.

This is not a setup builder. Brakes, camber, toe, aero, ride height, dampers, bars and gearing are not measured for setup advice, so it gives no values for them and no target cold pressure.

Setup advice is offered when you ask about setup or pressure in ACC, not during routine calls. The newest remembered session decides the change. For an unmeasured topic, the current spoken answer may be the generic “No read on that yet”.

Spotter beta

Settings → AI → Spotter. Default: off.

The Spotter is ACC only, beta and off by default in Settings, AI, Spotter.

A dedicated fast rivals feed drives car left, car right, three wide and clear calls. A call cuts the engineer off; it can resume afterwards, although a routine line that waits too long is dropped.

Tested in simulation, not verified on a real PC: opponent updates, left/right in traffic and audio timing. Run the ACC update-rate test first, and do not enable the Spotter in a race until it shows the feed is good enough.

Developer page #

Developer mode. Default: off. Tap the app version five times to reveal the local Dev page. It shows detector states, what the AI is given and recent events, with Force tick and Radio check actions. Reset app is in About.

The Wheel and buttons card shows one light per detected button, D-pad direction and held key, lit while it is held, to check whether a button can be bound for push to talk. Hardware compatibility is unverified on a real PC; try your device in this view.

Run the ACC update-rate test during a race with moving opponents for two minutes and keep acc_cadence.json for review.

The LMU recorder is a tester tool: start recording, add notes while driving, then stop to write the report zip. It does not make Le Mans Ultimate supported.

The Spotter live view shows feed age, rivals and direction; the demo plays a call over a long engineer line so you can hear the cut and resume.

Developer tools are local only. Wheel lights and the ACC and LMU tools are not verified on a real PC; the game tools need Windows. Browser checks used a mocked backend.

Le Mans Ultimate is not supported yet. Its game integration is fixture-only and unverified on a real PC; the recorder exists for testers.