PitCrew v0.11.0 — test build 1

A test build of v0.11.0, from dev. It is offered
only to installs with Get test versions turned on. What is below is queued for
v0.11.0 and may still change before it ships.

---

Added

Changed

Fixed

• The debrief keeps your last lap when the leader finishes first. The race now waits until you
  cross the line, leave the car or the session cools down, so the last lap has its time and fuel.
• A race that ends on lap 1 has a debrief. After a crash, a tow or a disconnect on the opening
  lap, the Debrief screen shows the race, says why it has no lap times, and lists what iRacing
  reported.
• The Conduct tab no longer says your last lap did not finish when you did. If a lap is still
  open after the checkered flag, it says the race was filed while that lap was still open. A new race
  with points but no report no longer reads as an old one.
• A race briefing at a pit stop no longer says the pre-race lines. If your first garage briefing
  of a race comes after the green, the engineer leaves out "the race is coming", the start type and
  the Rookie mode lines, and gives the conditions and pressures only.
• Record this session says when telemetry has stopped. It used to say that a recording was
  already running.
• Changing the engineer mode by voice and in the window at the same moment no longer disagrees.
  The later choice wins, and if a voice change cannot be saved, the engineer no longer confirms it.
• Two German lines say "Incident", as the rest of the German catalog does.
• The Record this session card no longer says the file is for a bug report, and the reporting
  guide says what the decision log holds more exactly.

Removed

---

Install: download the -setup.exe below and run it. Windows 10 or 11, 64-bit.
No administrator rights, no .NET, no Python, nothing else to install.

The installer is unsigned, so Windows shows a SmartScreen warning —
More info → Run anyway. The first run downloads the voice model (~310 MB);
after that PitCrew works offline. See the
install guide.

Built from ed1d5f25a0664dd3a1e2baf1f5bf98ca03784239.

PitCrew v0.10.0 — beta

Added

• The engineer tells you who just came close. In a race, when a car of your class comes
  within about a second and a half under green, you hear one line about that driver: their
  licence and whether their lap times are getting quicker, steady or slower. When one of you has
  pitted and the other has not, the line says that too. Each driver gets this line once per race,
  in the Normal and Coach modes.
• The engineer remembers your opponents. After each race you finish, the engineer keeps the
  drivers of your class and how the race against each one ended. When one of them is near you in a
  later race, you hear it, for example "Bruno Silva de novo. Na última corrida juntos, terminou na
  sua frente." The memory stays on this PC. To delete it, open Settings → Data → Opponents and
  press Forget opponents.
• Rookie mode adds a short word to the race briefing. Before the race, the engineer tells you
  the incident limit and how the race starts, and reminds you that the goal on lap one is a clean
  turn one. Turn on Rookie mode to hear it.
• You can see when the engineer is muted. The title bar shows "Engineer muted" while the
  engineer is muted, by Alt+M or by voice. With the in-game overlay on, it shows the same note
  on track. Press Alt+M to unmute.
• The engineer praises a clean pass. When you pass a car of your class with no incident in
  the seconds before, you hear a short word of praise with the driver's name and your new
  position, for example "Boa, sem incidente! Passou Lima e subiu pra segundo."
• Rookie mode helps you after a spin. If you spin and stop on track while a car is coming,
  the engineer tells you to hold the brakes, then tells you when the cars have passed. Turn on
  Rookie mode to hear it.
• Rookie mode keeps the radio quiet until you are through the first corner. On the first
  lap of a race, only the spotter, flags and urgent warnings speak until you are past turn one.
  On the formation lap you hear one reminder, and if you get through turn one with no incident
  the engineer tells you so. Turn on Rookie mode to hear it.
• Rookie mode tells you when it is safe to rejoin. If you stop off track while a car is
  coming, the engineer tells you to wait and how many seconds away the car is, then tells you when
  you can go. Turn on Rookie mode to hear it.
• The engineer says who you passed and who passed you. When you gain or lose a place to a
  car of your class, you hear the driver's name, for example "Costa passou. Agora você tá em
  terceiro." When the engineer cannot tell which car it was, you hear the same call as before,
  without a name.
• The engineer tells you when a car of your class is pressing you or is within reach. In a
  race, when a car of your class stays within one second behind you for a few seconds, the
  engineer warns you and tells you to defend. When you are within one second of a car of your class
  ahead, the engineer tells you that you can attack. Each car is called once until it drops back.
  The calls wait for the spotter, and they play in the Normal and Coach modes.
• In Coach mode the engineer tells you the gap ahead and behind during a race. Every three
  laps, the engineer names the car ahead and the car behind and the gap to each, when that car is
  within three seconds. The call waits until no car is alongside, so it never talks over the
  spotter. When the engineer has just told you that a gap is closing, the report leaves that car
  out.
• You choose how much the race engineer says. Pick Short, Normal or Coach in Pit
  strategy → Engineer, or say "modo curto", "modo normal" or "modo treinador" on the radio. On
  track the engineer confirms it. Short keeps the spotter, flags, penalties, car health, fuel, your
  own pit calls and the race start, and leaves out the routine gap reports, positions, lap times,
  briefings and the guesses about a rival's pit stop. Normal is what the
  engineer says today. Coach is Normal plus coaching lines: the practice goal and the gap report
  below.
  Answers to your questions play in every mode. The bottom bar of the window shows the
  current mode, and a click on it opens the setting.
• Rookie mode, for new drivers. Turn it on in Pit strategy → Engineer, with any engineer mode.
  It adds short calls about how to behave on track: when to rejoin after an off, what to do after a
  spin, a calm first lap. These calls always wait for the spotter and never say whose fault a
  contact was. If your iRacing licence in the session is R or D, the window offers it to you once.
  The calls themselves arrive in later updates, so for now the switch changes nothing you hear. The
  bottom bar shows "Rookie" while it is on.
• You can set a goal for practice and hear how it goes. In Pit strategy → Engineer, pick
  Clean laps, Consistency (laps within a band of your median lap) or Fuel (laps under a
  fuel figure per lap, in your sim's units, with your average as a hint), and how many laps must
  count. In a practice session the engineer says the goal when you start, your progress every few
  laps and when you reach the goal, in Coach mode. The Debrief keeps each
  practice session that had a goal, with the result and the laps that counted.
• PitCrew keeps a log of every call in each session. For each session, the engine writes one
  file in %APPDATA%\race-engineer\decision-logs\ with every call it said and every call it
  held back, with the reason, such as a cooldown, a car alongside or the wrong moment in the race.
  When you think a call was missing, the log shows why. Old logs are removed on their own, and
  decisionLog in tuning.json sets the size limits or turns the log off.
• You can record a session from the window. Turn on Record this session in Sims → iRacing.
  The window shows where the file is and how big it is. The recording stops by
  itself when you leave the session or a new event starts. The file lets the session be replayed
  call by call. It holds the name and iRacing ID of every driver in the session, so do not attach it
  to a public issue.
• The debrief has a conduct report. A new Conduct tab lists every incident iRacing reported in
  the race, in order: what happened (car contact, contact with a wall, off track or loss of control),
  the lap and the session time. Incidents on lap 1 are marked as the start, and a count per kind
  sits on top. Click a lap to open it in the lap sheet. Races recorded before this version show the
  kinds without a session time.

Changed

• The guides now say to run iRacing in borderless or windowed mode for the overlay. They used
  to say exclusive fullscreen works. It does not: the game covers the overlay. The voice works in
  every mode.
• The sims have their own screen. Sims in the rail (Alt+9) holds iRacing's settings editor,
  Display (field of view and the curved-monitor correction) and Assetto Corsa. Settings now holds only
  the app: General, Data & storage, and Phone & tablet, where the dash's connection and its frame rate
  now sit together.
• Pit stop and briefing switches moved to Pit strategy. "Arm the next stop automatically", "Let
  the live plan act" and "Brief me before each session" are on the new Engineer tab of Pit
  strategy.
• Field of view uses the curve correction's screen while it is on. The diagonal, aspect, distance,
  screens and curve radius come from Curved monitor and are shown read only, so the two sections can
  no longer disagree about your rig. The note that Field of view writes nothing to iRacing while the
  correction is on is now at the top.
• Settings is shorter. Hotkeys shows the four keys that work on track and keeps the screen keys
  behind a link. Startup, Window zoom and the dash rate say less, and Storage counts every model you
  downloaded rather than naming only Kokoro.

Fixed

• The live plan no longer waits for an answer that was lost. If you answer a proposal, on the
  desktop or on the phone, or change the profile on the phone, and the engineer's confirmation
  never reaches the screen, the screen now sees that the live plan has changed and says that it
  shows what is saved, instead of "result unknown".
• The window follows the sim again. The title bar's sim status and the overlay's automatic
  show and hide in a session updated only when the window opened. They now follow the sim
  while the app runs.
• The engineer tells you that you are closing on a car even when another car passes you.
  Before, a car that passed you, or came near for one lap, made the engineer start counting again.
  So in a race with position changes you often heard no "closing" or "car behind is closing" call.
  Now the engineer follows each car on its own and makes the call after three laps of closing.
• Small wording fixes on the Sims and Settings screens. "1 sessions" and "1 value differ" read
  correctly, the correction's dates are in English, and a few labels say "center" instead of "centre".
• A live-plan answer with no reply no longer says that nothing changed. When you accept or decline
  a proposal, or change the profile on the phone, and the race engineer does not reply within four
  seconds, PitCrew and the PIT screen now say the result is unknown and point you to the live plan.
  The change may have been applied. If the reply comes later, the screen shows it.
• The voice-command guide no longer says your engineer cannot command the car. Its limits now
  match the pit-stop commands: you can set fuel, tyres, fast repair and the tear-off by voice, but
  you cannot call yourself in, pick a tyre compound or change your pit plan.
• The troubleshooting guide no longer tells you to post a decision log or a session recording in a
  public issue. Both files can name other drivers, and a recording also holds their iRacing IDs.
  "Reporting a problem" now lists these files and says to k...

PitCrew v0.9.0 — beta

Added

• The engine can run plugins. A plugin adds something PitCrew does not do itself, such as a
  flag display on an LED matrix. It runs apart from the engineer: a plugin that crashes, hangs or
  uses too much memory is stopped and started again, and after three failures in ten minutes it stays
  off. The engineer keeps talking in every case. For plugin authors,
  pitcrew-engine --headless --plugin-dev <folder> runs a plugin and reloads it when it changes, and
  --safe-mode starts with no plugins.
• Plugins can use USB serial devices. A plugin opens only the port you pick in its settings, and
  two plugins never share one. PitCrew closes the port when the plugin stops or fails, so a
  device such as an LED matrix goes dark instead of freezing on the last frame.
• Plugins remember their own choices. A plugin can read back the files it saved, so the Flags
  plugin keeps your finished device setup and the flags you turned off between restarts.
• Plugin settings are easier to undo and to pick. Empty a number field to put the setting back
  to its default (for the Flags plugin, the board's own pin). An animation pack is now picked from
  a list of the installed packs, by name, so a pack you saved yourself can be chosen.
• A device plugged in late shows up. A plugin's port list looks again when you come back to the
  window, and has a button to look again now. With no device plugged in, it says so.
• Plugin settings use sliders and button rows. A plugin can ask for a slider, a percent slider or
  a row of buttons, add a unit and a one-line description, and offer a pin field for a board's
  GPIO pins.
• A plugin's pixel editor has a palette. Pick a color and paint with it, drag across cells,
  right-click to turn a cell off, fill or clear the frame, and change a color or add one with the
  system picker or a hex code.
• A plugin's pixel editor works from the keyboard. Tab into it, move with the arrow keys and
  paint with Enter or Space; a screen reader names each cell's row, column and color by name.
• Plugin screens keep your place with the keyboard. A button a plugin turns off while it works
  keeps keyboard focus, and the next step's heading takes focus when a setup moves on. The step
  forward always sits at the right of its row, a success reads as a success, and a progress bar
  tells a screen reader only each step and quarter instead of every update.
• A plugin's pixel editor announces the brush. The colors are one group you move through with
  the arrow keys, the eraser is called the eraser, and a read-only grid names its corner colors.
• A firmware upload survives a plugin restart. If a plugin restarts while PitCrew writes a
  board for it, the plugin finds the upload still running and shows its progress again, instead
  of losing track of it while the port stays busy.
• A plugin's screen shows which button moves you on. Its main action is drawn in the app's own
  accent, so a setup's Next or Upload stands out from Back; a step that is not open yet stays plain. A
  message's heading sits on its own line. A screen reader hears a plugin's progress
  and messages as they change, and a read-only pixel grid says what it shows.
• A Plugins screen. The new Plugins item in the rail lists the plugins on this PC. Turn each one
  on or off and change its settings there; the port setting lists the USB devices plugged in. A
  plugin that is on and has a screen of its own gets an item in the rail under Plugins, with a dot
  when it needs your attention. Plugins still arrive by hand for now: the catalogue comes later.
• PitCrew uploads firmware to Arduino and ESP32 boards for a plugin. A plugin that drives a
  device, such as the Flags plugin, can ask PitCrew to find out which board is on the port and to
  write the plugin's firmware to it. PitCrew restarts the board into its bootloader by itself, so
  there is no button to hold and no Arduino IDE to install. It works with the ESP32-C3, the ESP32,
  the Arduino Uno and Nano, and the Leonardo and Micro. While it writes, it holds the port, and the
  plugin gets it back when the upload ends.
• A plugin is no longer stopped for being slow when Windows only paused it to run something else.
  Only the time the plugin really computes counts against its limit.
• A field-of-view calculator for iRacing, Assetto Corsa and Assetto Corsa EVO. Settings › Display
  › Field of view works out the correct field of view from your screen size, the distance from your
  eyes and, on triple screens, the side angle and bezels. Curved screens count their real curve.
  iRacing gets the horizontal view across all your screens, and PitCrew can write it with the
  matching monitor values, after you review them and with a backup of each file. Both Assetto Corsa
  games get the vertical view of one screen, to enter in the game. It also suggests the side angle
  at which your side screens face you, and draws your rig from above.
• A new PitCrew is announced in a window of its own. When a new version of PitCrew is ready and
  you are not driving, a dialog shows the version, the download size and a link to what changed.
  Download, then Restart to update, are still two separate answers, and "Later" puts it back in the
  corner panel until you next open PitCrew. It never appears while iRacing is running. New
  engineers, phrases and screens still arrive in the corner panel.
• ire-replay decide --language. The replay tool can now speak a recording in any catalog
  language, numbers included, instead of only in Portuguese. The parity corpus keeps an English
  record of one race, which the website's radio log reads.

Changed

• Plugins are built for plugin API 2. A plugin made for the first plugin API does not load until
  its author rebuilds it; the Plugins screen says why. The Flags plugin is already rebuilt.
• Plugin screens hold up when something goes wrong. A plugin screen PitCrew can't draw no
  longer blanks the window: it says so and keeps the plugin's settings usable. A screen that never
  arrives gets a Try again button instead of waiting forever, and a plugin restarting after an error
  counts down to the restart. A double click on a plugin's button or action sends it once, and the
  port list picks up a device as soon as you plug it in.
• Plugin screens are easier to scan. A plugin's tabs sit under its title, its buttons line up in
  rows, its status lines and switch lists group together, and its tables are denser. On the Plugins
  screen the status, Open and the switch line up from row to row, and a long plugin name keeps its
  place at narrow window sizes.
• Clearer messages on the Plugins screen and on plugin screens. Errors say what failed and what
  to do next, a port in use names the plugin that holds it, and the Plugins screen drops its
  one-tab bar. It now mentions the rail only when more plugins have a screen than the rail can show.
• The curved-monitor correction moved to Settings › Display. It sits next to the new
  field-of-view calculator. It works as before; only the place changed.
• PitCrew installs for your Windows user, and updates without asking for administrator rights.
  The download is now a -setup.exe instead of an .msi, and it installs into your own user folder.
  When you accept a new PitCrew from the update panel, it closes, shows a small progress window and
  opens again. The first time, if your PitCrew came from the old .msi, Windows asks your permission
  once to remove it. Your settings, profiles and voices stay where they are.
• Plugins are published next to PitCrew. The releases page now also lists plugin releases, named
  "Plugin · …". The app's installer is in the newest release named "PitCrew v…". The plugin source and
  the guide for plugin authors are in the plugins/ folder of the public repository.

Fixed

• A plugin with damaged files now says it can't start, instead of saying it isn't installed.
  When no serial port is found, the settings now say to plug the device in, and the list picks it up
  on its own.
• Plugin screens work better with a keyboard and a screen reader. A plugin's button keeps focus
  after you press it, and the color editor puts focus back on the color you edited. A screen reader
  now says when a plugin fails, restarts or comes back, and reads a setting's error with that
  setting. Error text in plugin settings is easier to read, unlit pixels on a matrix show their
  outline, and with no device plugged in the port row says so in a place the keyboard reaches.
• The phone and tablet show the Companion and PIT screens of the version you installed. An
  installer could carry the screens from an earlier build, so the race screen on the phone kept its
  old layout after an update.
• PitCrew opens again after it updates itself. When you accepted a new PitCrew from the update
  panel, the window closed for the installer and did not come back. It now reopens when the install
  is done.

---

Install: download the -setup.exe below and run it. Windows 10 or 11, 64-bit.
No administrator rights, no .NET, no Python, nothing else to install.

The installer is unsigned, so Windows shows a SmartScreen warning —
More info → Run anyway. The first run downloads the voice model (~310 MB);
after that PitCrew works offline. See the
install guide.

Built from a8a03e61585451d632b6764c389acba0d78d6af6.

Plugin · Flags 1.0.0

Changed

• The Live tab leads with the matrix. Beside it are what the sim shows, what the matrix plays and
  the flag player. The Device card stays under it, whether the board is fine, missing or needs an
  update, so it no longer jumps. The header says only Connected; the card names the chip and the
  firmware.
• The Animations tab puts playback and the flags you allow on the left, and the pack and the editor
  on the right. The animation editor groups its controls: painting, frames and speed, then save.
• Detect board only says which chip the board has. A matching chip no longer counts as a yes
  for the upload, because a button box can carry the same chip: the Upload step asks with a
  Yes, COM… is my matrix board button, and says that Detect board restarts the board.
• A matrix test that paused after two minutes goes on from the screen it was on.
• The Test step says in one line what it is for. Live names the sim PitCrew reads instead of always
  saying iRacing.

Added

• A safer upload. When nothing on the port answers as PitFlag, the Upload step asks whether that
  port is your matrix board before it writes, so a button box or wheel on the wrong port is not
  overwritten. Detect board answers it too. While it writes, the Upload button stays, as
  Uploading…, under a notice to keep the board plugged in, with how long it takes.
• The animation editor takes PitCrew's palette: pick a color and paint with it, drag to paint,
  right-click to turn a cell off, fill or clear the frame, and change a color or add one (up to 16).
  These changes count as unsaved edits and come back after a restart like the others.
• Built for plugin API 2 (pitcrew:plugin@2).
• When Windows gives the matrix a new COM port and PitFlag answers there on the board you set up,
  the setup offers Use COM… to take the port in one click. A set-up matrix can always leave the
  setup with Cancel, and only a new port opens the setup again.
• Fill, Clear and Delete frame in the editor can be undone once. Discard changes asks before it
  throws the changes away. Play on the matrix says why it is off when the board is not
  connected.
• An upload that is still running when the plugin restarts comes back on the Upload step with its
  progress, and the port stays PitCrew's until it ends. Changing the port mid-upload no longer
  takes the old port back early, and the Board step locks the port and board while PitCrew looks at
  the board.
• When the board does not answer 20 seconds after a good upload, the Upload step says so and tells
  you to unplug and replug it, or upload again, instead of waiting without end. A port that just
  took PitFlag is not asked about again.
• After a failed upload, the board's own tip (such as the double reset on a Leonardo) shows again.
• The setup step and the editor's unsaved changes come back after PitCrew restarts.
• Test the matrix from the device card is a test of its own, with Done, not the setup's last
  step. Changing a setting restarts the test's two-minute timer.
• Finishing the setup plays green, then checkered, on the matrix.
• The Matrix step asks only for the matrix, its pins and the current limit. Color order, LED
  correction and rotation are in Test, where you can see them.
• Brightness is on the device card. After a save to My pack, the pack picker is right under the
  message. Live names the flag and the animation in plain words, and keeps drawing the preview when
  the board is unplugged.
• The Flags screen. Until a device is set up, it shows only the setup: Board (port and board type),
  Matrix (type, pins, current limit), Upload (checks the
  settings, then writes the firmware) and Test (the matrix test). Finish setup unlocks only on
  the last test screen, with the board connected.
• After the setup, the screen shows the device's connection, with Test the matrix and Set up
  again, and two tabs: Live and Animations. A new port opens the setup again.
• The setup blocks a pin the board cannot use (a flash pin on an ESP32, a pin the board does not
  have) and two MAX7219 lines on one pin, and warns above 500 mA on USB power.
• The Live tab is one card: the matrix as it is now, the flag the sim shows and the flag the matrix
  plays. The device card shows the connection only when it needs attention; the screen's header
  shows it the rest of the time.
• Turn each flag on or off on the Animations tab, in four groups: Start, Caution, Race, and Stop and
  penalties. While a flag that is off is out, the matrix stays dark. A test still plays it.
• The animation editor can delete a frame and discard unsaved changes. Buttons that cannot act are
  off: Previous and Next on one frame, Duplicate at 120 frames, Play with no board connected. A save
  note goes away at the next edit, and an animation whose id is not a plain file name is not saved.
• The Animations tab names each animation the way the flag switches do ("Yellow, waving", not
  yellow-waving), in the table, the editor and its messages, and lists them in that order.
• The Live matrix refreshes the screen only while the Live tab is open.
• The animation editor, which saves to My pack. A save keeps the animations saved before, the
  matrix picks up the change at once when My pack is in use, and the editor says how to switch to it
  when it is not.
• Picking another animation while the editor holds unsaved changes asks first: save and open, discard,
  or keep editing.
• A failed firmware upload offers Try the upload again and says the board is not damaged. After a
  good upload, the step says it waits for the board to restart.
• The Live tab shows a warning when the board is not connected.
• Settings use the right control: brightness, current limit and green time are sliders (brightness in
  percent), matrix type, color order and rotation are button rows, and pins are pin fields that
  fall back to the board's default pin when left empty. Each setup field says what it is for.
• Simpler screens: the orientation test has the Zigzag and Mirror switches, so the whole setup stays
  on the Flags screen; old firmware gets an Update to PitFlag button that opens only the upload;
  the upload step shows one line when your settings check out; Live plays a flag from a list with
  one Play button; the animation table drops its On/Off column, which the switches already show.
• Setup reads at a glance: a progress bar with the step you are on, Back and the next step always in
  the same place, a clear "PitFlag is running" message after the upload, and no greyed-out button on
  the last test screen.
• The Now card on Live reads as two plain lines instead of a table with empty headers.
• The PitFlag 2.2.0 firmware for WS2812B and MAX7219 matrices: one prebuilt image each for the
  ATmega328P, ATmega168, ATmega32U4, ESP32 and ESP32-C3. It shows a boot animation until PitCrew
  talks, and redraws only when the serial line is quiet.
• ESP32-C3 boards, on the chip's own USB port. The default data pin is GPIO 4.
• Firmware upload in the setup for every board: ESP32-C3, ESP32, Arduino Uno and Nano
  (ATmega328P and ATmega168) and Leonardo or Micro (ATmega32U4). Pick the board and press Upload.
  PitCrew restarts the board into its bootloader, writes the firmware the plugin carries and checks
  it. No button to hold, no Arduino IDE.
• Detect board in the setup asks the board which chip it is, and says which Board to pick.
  The step also names the port's USB adapter.

Includes 1.0.0-beta.1:

Added

• The flag on an 8×8 matrix over PitFlag wire v2, for every sim PitCrew reads.
• Matrix settings (type, pins, color order, zigzag, mirror, rotate, current limit). The board keeps
  them, so a turned image is fixed without a new upload.
• The matrix test on the Device tab: six fixed screens that show if the color order, the wiring and
  the brightness are right, and which setting to change.
• LED color correction (on by default): the colors sent to a WS2812B lose some green and blue, so the
  yellow flag is not lime. The screen keeps the pack's colors.
• The standby screen: outside a race (no sim, or not in the car) the matrix plays the pack's
  standby animation. "Animate outside a race" turns it off.
• The link sends the whole state again every second, and writes one burst per tick, so a lost
  packet heals.
• A board with PitFlag 1.x firmware is named, with its version, and asks for the new firmware.
• The Classic pack: 15 animations and the flag mapping.
• The Flags screen with the Live, Animations and Device tabs.
• The animation editor, which saves to My pack.
• The PitFlag 2.1.0 firmware for WS2812B and MAX7219 matrices: one prebuilt image each for the
  ATmega328P, ATmega168, ATmega32U4 and ESP32. It shows a boot animation until PitCrew talks, and
  redraws only when the serial line is quiet.

Firmware

PitFlag firmware 2.2.0
for the ATmega328P, ATmega168, ATmega32U4 and ESP32. See plugins/plugins/flags/firmware/README.md.

This is a plugin release. The PitCrew app is in the releases named "PitCrew v…".

PitCrew v0.8.6 — beta

Added

• A briefing before you get in the car. With a session loaded and you out of the car, the
  Companion shows the weekend's sessions and which one is running, the weather and track
  temperature, the grid from qualifying (or the field by iRating before there is one) around your
  slot, your car and setup, your best lap there and your saved pit plan. It works for practice and
  qualifying too, not only races. With the sim closed it shows your last race and the ones before it.
  The waiting-screen options in the Companion's settings are now the clock, how many recent races to
  list and how much of the grid to show.

• Assetto Corsa EVO. Open Assetto Corsa EVO and the engineer is listening, with nothing to
  install or set up: fuel, laps and lap times, your position, flags, pit lane, the session clock,
  and tyre temperatures and pressures. The spotter calls cars alongside from where every car is on
  track. After your first clean lap at a track, which PitCrew remembers for next time, the gaps to the
  cars ahead and behind are heard too. EVO does not share the other cars' names, positions or lap
  times, so calls that need those stay silent. Settings → Connections has an Assetto Corsa EVO card
  that says whether the game was found and is coming through, and whether the clean lap is still
  needed. With iRacing and both Assetto Corsas on one rig, PitCrew follows whichever one you are
  driving.

• The other cars on Assetto Corsa. PitCrew now puts a small app in Assetto Corsa's folder and
  switches it on, so the engineer hears the rest of the field: gaps, traffic, rivals and the
  undercut, as on iRacing. Settings → Connections has an Assetto Corsa card that says whether the
  app is installed, switched on and sending, and what to do when it is not, such as updating it or
  restarting the session. An Assetto Corsa started before the app was installed needs one restart.

• Visual checks of the desktop app through the agent MCP. A remote development agent can
  inspect the real PitCrew window, operate its controls through Orca, and receive screenshots
  directly to help verify interface changes.

• Live pit plan (beta). Your saved pit plan now follows the race. Every lap it works out again,
  from the fuel you are actually using, how many stops you need, where they fall and how much fuel
  each one takes. Each plan keeps a strategy profile, conservative, balanced or aggressive, that you
  pick on the PIT page or on the phone. The fuel of a stop that follows the plan adjusts on its own.
  Anything bigger is only proposed, on the PIT page and on the phone, and nothing changes until you
  accept it: one stop more, one stop less, a stop that moves, or a stop you can drop by saving a
  little fuel each lap. The plan also warns when a fuel amount you set by hand is no longer enough.
  It recovers the stops already made if PitCrew restarts mid-race. Settings → Pit stops → Let the
  live plan act is off by default. Turned on, the radio, the PIT page and the phone all read the
  same fuel figure, a stop that follows the plan is armed with the litres worked out at that moment,
  and the strategist tells you when the plan changes or an accepted fuel saving is not happening.
  Settings → Data shows how much of your driving history is kept for each car and track, and
  deletes it.

• The Debrief reads like a timing sheet. Pick a race at the top and step to the one before or
  after. A summary gives where you started and finished, your best and ideal lap, how many laps were
  within half a second of your best, your incidents and your time on pit road. A strip under it
  shows your lap times and your position through the race, with the stops and the cautions marked;
  click it to jump to that lap. The lap table colours each sector against your best and, in races
  recorded from now on, shows the gap to the car ahead, the car behind and the leader, and marks the
  caution laps. Stops lists the stops where the car stood in its box, each with the laps before it,
  the places won or lost and the time it cost; a drive-through, or leaving the pits before the
  start, is named for what it is. Sectors, Fuel and At this track complete it. Older debriefs still
  open, without the columns they never recorded.

• Pit strategy is one sheet per plan. The fuel calculator and the planner are now one set of
  race figures: race length, lap time, fuel per lap, starting fuel, tank, reserve, tyre life and the
  series' rules. Each says where its number came from, and what the race needs is highlighted. Under
  them are a chart of the fuel in the tank lap by lap and the plan as a table, with a row per stint
  (laps, fuel in, fuel used, fuel left, tyre age against tyre life) and a row per stop. Adding or
  editing a stop opens one window. You pick the tyres on a drawing of the car seen from above, see
  the tread left at your last stop at that track, and see how the stint splits and what the stop
  does to the fuel. Your saved plans sit in a column on the right, and pit presets have their own
  tab. When iRacing runs that car and track, the live plan sits above the sheet.

• Generic plans. A plan can now fit any car and track, such as "fuel only, tyres kept, 60
  minutes". Generic plans are listed under each car and track's own plans. Use for this car and
  track copies one there, sized to that race, and makes the copy the active plan, so the engineer
  arms its stops as usual. A stop with no window is called when the fuel runs short. Changing the
  generic plan later leaves the copies alone; using it again updates the copy.

• Curved monitor correction (beta). Settings → iRacing → Curved monitor works out iRacing's
  monitor values from your monitor's size, curve, eye distance and bezel gap. Your rig is on the
  left, with a status list right under it that says whether the correction is in this build,
  installed in the iRacing folder, blocked by another program's dxgi.dll (ReShade, for example),
  when it last ran in iRacing and with which values, and whether iRacing's settings match. On the
  right are the numbers iRacing needs, a view from above of your screens next to the ones iRacing
  is set up for now, the picture the correction sends to the screens, and iRacing's monitor
  values. If iRacing is set up for a different monitor, a warning next to those values gives both
  fields of view, because lines cannot line up until they match. One button, Apply to iRacing,
  saves the settings, installs or updates the small add-on in the iRacing install folder, and
  opens iRacing's monitor values for the usual review and backup; what it saved and installed is
  still shown while you review. The on/off switch, the install folder and Uninstall sit in a
  folded Install section under that button. Test mode covers all your monitors with two patterns.
  Horizon lines every 5° show the curve: when they look straight, the radius is right. A 3D room
  shows the seams: when its lines carry on across the gaps, the bezel gap is right. A small panel
  in the middle shows the radius, the eye distance and what to look for; H opens the full panel
  with buttons. The arrow keys adjust the radius and eye distance, Tab switches the pattern, and
  Ctrl+Shift+F10 compares with and without the correction, in test mode and while driving. If another program's dxgi.dll was there, it is kept as a backup and put back
  when you uninstall. The add-on is unsigned and has not been cleared for iRacing's anti-cheat, so
  use it in offline sessions until that is confirmed.

• The garage briefing suggests your cold tyre pressures. Once you have at least three similar
  runs in a car at a track, the briefing suggests a cold pressure for the front and rear, or for each
  tyre when the sides differ, and says how many runs it is based on. A similar run has the same
  compound, the same wet or dry track, and a track temperature close to today's. The suggestion
  aims for the hot pressures of your fastest of those runs. A run with a yellow, a reconnect or a
  missing lap is not counted. With too few runs, or on a fixed setup, no number is given. Nothing
  is changed in the car. The thresholds are in tuning.json's pressureEstimate section.

• Follow a rival from the Companion. Tap a driver on the Companion's leaderboard and the engineer
  confirms it, then calls that car's lap times and the gap to it each lap, and tells you when it
  enters and leaves the pits. Tap the same row again to stop. The followed row is marked on every
  connected screen, and the choice carries over from practice to the race at the same event. Set
  rivals.watchLapEvery in tuning.json to hear the lap calls less often.

• Gap calls say whether the rival has pitted. Once the stops begin, the lines about the car ahead
  and behind end with "esse carro já parou" or "esse carro ainda tem parada pra fazer" when
  that car has made a different number of stops than you.

• Who you'll come out behind. When your stop is called for the next lap and the time you lose in
  the pits is known from a previous stop, the engineer estimates which car in your class you will
  rejoin behind, and by how much. With no measured pit loss it says nothing.
  rivals.rejoinMaxGapS in tuning.json sets how far back a car may be and still be named.

• The engineer learns where to stay quiet. After a complete clean lap in a car at a track,
  routine calls wait through braking and corners for the next straight. Spotter calls and urgent
  alerts still come through immediately. The learned zones are kept between sessions, and the
  waiting time and straight length are adjustable in tuning.json.

• Tyre warnings compare with your own runs. A fresh reading after a run is compared with your
  earlier readings in that car at that track, per tyre, compound and wet or dry conditions. The
  engineer says when temperatures are unusually high or low, or a hot pressure is ...

Plugin · Flags 1.0.0-beta.1

Added

• The flag on an 8×8 matrix over PitFlag wire v2, for every sim PitCrew reads.
• Matrix settings (type, pins, color order, zigzag, mirror, rotate, current limit). The board keeps
  them, so a turned image is fixed without a new upload.
• The matrix test on the Device tab: six fixed screens that show if the color order, the wiring and
  the brightness are right, and which setting to change.
• LED color correction (on by default): the colors sent to a WS2812B lose some green and blue, so the
  yellow flag is not lime. The screen keeps the pack's colors.
• The standby screen: outside a race (no sim, or not in the car) the matrix plays the pack's
  standby animation. "Animate outside a race" turns it off.
• The link sends the whole state again every second, and writes one burst per tick, so a lost
  packet heals.
• A board with PitFlag 1.x firmware is named, with its version, and asks for the new firmware.
• The Classic pack: 15 animations and the flag mapping.
• The Flags screen with the Live, Animations and Device tabs.
• The animation editor, which saves to My pack.
• The PitFlag 2.1.0 firmware for WS2812B and MAX7219 matrices: one prebuilt image each for the
  ATmega328P, ATmega168, ATmega32U4 and ESP32. It shows a boot animation until PitCrew talks, and
  redraws only when the serial line is quiet.

Firmware

PitFlag firmware 2.1.0
for the ATmega328P, ATmega168, ATmega32U4 and ESP32. See plugins/plugins/flags/firmware/README.md.

This is a plugin release. The PitCrew app is in the releases named "PitCrew v…".

PitCrew v0.7.1 — test build 2

A test build of v0.7.1, from dev. It is offered
only to installs with Get test versions turned on. What is below is queued for
v0.7.1 and may still change before it ships.

---

Added

• Follow a rival from the Companion. Tap a driver on the Companion's leaderboard and the engineer
  confirms it, then calls that car's lap times and the gap to it each lap, and tells you when it
  enters and leaves the pits. Tap the same row again to stop. The followed row is marked on every
  connected screen, and the choice carries over from practice to the race at the same event. Set
  rivals.watchLapEvery in tuning.json to hear the lap calls less often.
• Gap calls say whether the rival has pitted. Once the stops begin, the lines about the car ahead
  and behind end with "ele já parou" or "ele ainda não parou" when that car has made a different
  number of stops than you.
• Who you'll come out behind. When your stop is called for the next lap and the time you lose in
  the pits is known from a previous stop, the engineer estimates which car in your class you will
  rejoin behind, and by how much. With no measured pit loss it says nothing.
  rivals.rejoinMaxGapS in tuning.json sets how far back a car may be and still be named.
• The engineer learns where to stay quiet. After a complete clean lap in a car at a track,
  routine calls wait through braking and corners for the next straight. Spotter calls and urgent
  alerts still come through immediately. The learned zones are kept between sessions, and the
  waiting time and straight length are adjustable in tuning.json.
• Tyre warnings compare with your own runs. A fresh reading after a run is compared with your
  earlier readings in that car at that track, per tyre, compound and wet or dry conditions. The
  engineer says when temperatures are unusually high or low, or a hot pressure is low against your
  history, and stays silent until enough runs are recorded. These calls describe the last run,
  because iRacing does not continuously report hot tyre readings on track.
• The engineer tells you where your lap time is going. In practice and in a race, when one sector
  of a lap cost you clearly more than the others against your own best lap in that car at that
  track, you hear which sector and by how much ("setor dois, cinco décimos mais lento que a sua
  referência"). It waits for a straight with nobody alongside, never speaks on consecutive laps, and
  stays quiet about a sector you spent behind another car, a lap with a yellow or a pit stop in it,
  and a best lap that is old, on another setup or in the other weather. Your best clean lap is kept
  between sessions, so from the second session at a track it can speak from the first lap. The
  thresholds are in tuning.json's sectorCoaching section.
• Prepare your iRacing settings before entering the simulator. Settings → iRacing edits the
  values in your existing INI files, loads selected values from an imported INI or from your own
  named presets, and shows every change for review before saving. A complete backup of each file is
  kept before it is replaced, and History restores selected values or a whole file. Editing is
  blocked while iRacing is running, and starting iRacing discards unsaved changes.
• The spotter tells you a car is still there. A car that stays alongside is called again every
  three seconds ("ainda na esquerda") until it clears, so you are never left wondering whether it
  has gone. Set spotter.stillIntervalMs in tuning.json to change how often, or to 0 to turn it
  off.
• Inside and outside on ovals. On an oval the spotter says "carro por dentro" and "carro por
  fora" instead of left and right. Road courses keep left and right.
• Three wide tells you where you are. With a car on each side you hear "você no meio", and with
  two cars on one side you hear which side you are on, instead of where the two other cars are.
• Change your pit stop by voice. Say "coloca vinte litros", "abastece até o fim", "troca os
  quatro pneus", "só os dianteiros", "sem pneus", "reparo rápido" or "tear off" and the engineer
  sets it in the car, then tells you what the car now shows. If iRacing caps the fuel to what fits
  in the tank, you hear the capped amount. Each command changes only what you asked for, and an
  automatic arm from your pit plan never overwrites it: the plan waits until you have made the stop.
  A command is only obeyed when it is heard in full, and never when you said "não" in the middle.
• Fifteen more questions you can ask by voice. Ask for the gap to the leader, the last lap of the
  car ahead, the car behind or the leader, your best lap, the time left, how much fuel you need to
  finish, how many laps you have done since your stop, your tyres, your repair time, your incidents
  and how many are left before the limit, your iRating, your licence and safety rating, the strength
  of field, and the track and air temperature. Tyre wear is the reading from your last stop, because
  iRacing only reports it in the pit box. "Quem está na frente?" and "quem tá atrás?" now
  work too, and answer with the name and the gap. The questions you could already ask are understood
  exactly as before.
• A briefing before every session. When you sit in the garage, or in your pit box before you pull
  away, the engineer goes over the track and air temperature and whether the track is wet. From the
  second session on, you hear only what changed: a warmer or cooler track, more rubber down, a wetter
  or drier surface, and which way to move your starting pressures. If nothing changed, the engineer
  says so in one line. The briefing stops as soon as the car moves, and it is never repeated for the
  same session, even after a restart. Turn it off under Settings → Race engineer.
• The weather is followed over time. The engineer now tells you when the rain is getting heavier,
  when the track is getting wetter, when race control declares the track wet, and when the track has
  warmed or cooled by several degrees since the start of the race, which changes your tyre pressures.
• Every run's tyre pressures are kept. After each run PitCrew saves the cold and hot pressures,
  tyre temperatures and tread with the track conditions, next to your lap history. This is the data
  a future pressure recommendation will learn from. Nothing is sent anywhere.
• High oil temperature is called. When the car's oil temperature warning comes on, the engineer
  now tells you, the same way it already did for the water temperature.
• An early warning when the engine runs hot. The engineer learns what water and oil temperature
  are normal for your car in the current session, then tells you when either climbs well above that,
  before iRacing's own warning light comes on. The classic case is a long stint in another car's
  tow: you hear the call in time to pull out and let the engine breathe. It stays quiet for the first
  15 minutes in the car while the engine warms up and it learns your normal running.
• Ask "how is the engine?" Press push-to-talk and ask about the engine, the water or the oil, and
  the engineer answers with the water and oil temperatures and the oil pressure, in your sim's units.
• Where you line up behind the pace car. On the formation lap and when a caution forms, the
  engineer tells you whether it is single or double file and where you are: your place in the line,
  or your row and which side of the grid. At one lap to green, that call includes your current row.
  You also hear when you get the free pass, when you are waved around, and when you are sent to the
  end of the line. Races only.
• Telemetry health on the Companion. The Companion's settings drawer now shows how many
  telemetry frames were thrown away, how many times PitCrew lost and found the sim again, and how many
  times it re-read the session details. If a session sounded wrong, include these numbers when you
  report it.
• "Are you OK?" after a big hit. When the car takes a heavy impact, the engineer checks on you
  straight away, then tells you about any damage once the car reports it. Kerbs and hard braking do
  not set it off.
• DRS and push-to-pass calls. In a race, on cars that have them, the engineer tells you when DRS
  is enabled for the next zone, and after each push-to-pass how many you have left. Cars without
  them hear nothing new.

Changed

• The spotter now watches every frame iRacing sends, not one in three, so a car is called as soon as
  it has really been alongside long enough, and a car that only brushed alongside for an instant is
  no longer mistaken for one that stayed.
• Temperatures and pressures are spoken in the units your sim is set to, and numbers above 99 are
  now spoken as words in every language.
• The engineer can now be tested against the .ibt telemetry files iRacing saves for your own
  sessions, not only against PitCrew's own recordings, so a problem you report can be checked on the
  session where it happened. No visible change in the app.
• The garage briefing can now be checked against a recorded session like every other call, and
  checking the same recording twice gives the same result. No visible change in the app.
• Every change to what the engineer says is now checked against a set of recorded race situations
  (a formation lap, a caution, a multiclass race, a driver disconnecting, a timed finish and a reset
  practice) before it ships. No visible change in the app.

Fixed

• PitCrew now logs a warning once per connection when iRacing's telemetry layout differs from the
  expected version or Assetto Corsa's layout is unverified, helping diagnose incompatible game updates.
• "Track drying" is said once while the track dries, instead of at every step of the drying.
• A stalled engine is called once, as a stall, instead of also as an oil-pressure and a...

PitCrew v0.5.0 — beta

You can talk back: press a key — or a button on your wheel — and ask your engineer about fuel, position, gaps or laps left, and it answers in its own voice. Hold it while you speak, or tap it once to start and once to stop, whichever suits where the button is. It listens only while you have it open, recognises Portuguese and English on your own PC after a one-time model download, and says “não entendi” rather than guessing at a question it does not know. One screen sets the whole thing up: pick your microphone, watch the level move as you speak, hear yourself back on it, choose which language's recordings to edit without changing how your engineer answers, and record the way you actually phrase each question.

Your engineer has three or four ways to say every call instead of one or two, knows the difference between qualifying and a race, and no longer calls a personal best a session record.

Qualifying has its own engineer for the first time — including the one-minute call that decides whether your last lap counts at all.

Pit strategy built from your own laps: pick a car and track, tell PitCrew the race length, and it proposes the fewest stops the race needs with a lap window for each. Keep several plans side by side, and in the race your engineer calls the stop, arms it in the car’s black box and reads back what iRacing has set. A fuel calculator sits beside it, and pit presets — “autofuel, no tyres”, “fronts only” — step from a button on your wheel.

Spanish, French and German are ready to speak, alongside Portuguese and English. German needs Piper, Supertonic, Azure or ElevenLabs, because the voice that ships with PitCrew has no German speaker.

PitCrew now listens to Assetto Corsa too — a beta that covers your own car: fuel, laps, position, pit lane and flags. It notices which sim is running and moves between the two by itself.

A fresh install opens on a short welcome that downloads the voice model in front of you and takes you to the audio setup.

Two more voices for your own PC, both free and both off until you pick one. Piper has fifteen voices across the five languages and is the quickest of them to speak a line — each voice downloads on its own, about 63 MB, so you fetch the one your engineer will use rather than the whole set; Supertonic has ten voices that come with the download, in two versions — one steadier, one closer to Brazilian Portuguese.

Every voice that runs on your own PC now has a play button beside it, so you can hear one read a line in your engineer's language and at their speed before you choose it.

The studio voice now uses ElevenLabs' cheap model by default — half the cost per character — and you can pick which of three models reads your engineer's lines.

A second online voice: Azure AI Speech, with Brazilian Portuguese voices of its own. A beta, off until you pick it — paste a key and a region and each engineer can have their own voice from it.

PitCrew no longer generates phrases in bulk on its own: it happens when you press a button, the strip along the foot of the window tells you when something is missing, and a bar above it shows what each voice is doing while it works.

The relative table on your phone now shows every class, in track order — so you can see the faster car arriving before you are shown a blue flag for it.

Your phone keeps the easy way to find your rig: scanning its code, choosing a remembered rig or typing an address still happens in the phone app. Once it is paired, the Companion and PIT panels come from the rig itself, so the same pages also open in any browser on your home network.

The Companion and PIT are one panel with two routes. Move between live telemetry and pit strategy without pairing again, whether you opened it from the phone app or a browser.

Your Companion layout, colours and font stay with the browser or phone WebView you use. The rig still supplies the race facts; each screen stays your own.

The banner over the sim has been redrawn in PitCrew's own green: a flat near-black panel with a thin edge, a green light when your engineer is on the radio, and a sound meter whose bars stand on a line so you can read it out of the corner of your eye. All four shapes changed together, and the low-profile strip — one line the height of a caption — is now the one you get if you have never picked a shape yourself.

The spotter is now its own voice, split off from the race strategist, with its own card, engine and voice picker on the Voices screen.

Every engineer can have their own voice, not just their own engine — so the race engineer, the strategist and the spotter no longer all sound like one person on a local engine.

PitCrew no longer overwrites your settings when it starts, and no longer tells you an installed voice model is missing while the engineer is still coming up.

Added

• Your tyres at every pit stop, in the race debrief.
• A fuel calculator beside your pit strategy.
• Pit stop presets you switch between from the wheel.
• A pit strategy planner built from your own laps.
• Several plans for each car and track.
• Your engineer arms the next stop for you.
• PitCrew now keeps a history of every lap you run, per car and track.
• Your strategist now calls a planned pit stop in three beats.
• A welcome screen for your first launch.
• PitCrew now listens to Assetto Corsa too.
• Your phone can show the lap you can still find.
• Your pit plan comes with you on the phone.
• The phone dash is going on the Play Store.
• The iPhone gets its own road in, through TestFlight.
• Spanish, French and German are ready to speak.
• Settings has a Models section.
• Clicking a race on Home opens it.
• The whole crew checks in when you get to the track.
• Your engineer tells you when you are in the tow.
• A single word as you cross the line, and then quiet.
• The Voice screen shows the last call you heard.
• Reload voices
• Home has a Radio check button.
• Test versions are now actually published, and they arrive on their own.
• You can ask for test versions, in Settings.
• PitCrew's screens can now update on their own, without reinstalling anything.
• PitCrew can now update itself.
• Each voice engine can now generate its own audio, and you choose which model to pay for.
• Bind your push-to-talk key by pressing it.
• The screen now tells you which key is actually working.
• Your microphone's Windows level, on the same screen as everything else about it.
• A test that tells you whether your microphone and your key actually work.
• You can now talk to your engineer with a button on your wheel.
• A debrief screen, so PitCrew is worth opening after the race and not only during it.
• Your engineer now calls the undercut and the overcut.
• You can teach your engineer how you ask for things.
• You can now see your microphone working, and hear yourself on it, before you record anything.
• You can now ask in one language and be answered in another.
• You can talk back.
• The button tells you it is listening.
• You can hear a voice before you choose it.
• A fourth voice engine you can try, Piper, and it is the quickest of the lot to speak a new line.
• A new voice you can run on your own PC: Supertonic, with ten voices and no key.
• A second online voice you can put an engineer on: Azure AI Speech.
• Picking an engine now starts with one question: on this PC, or online.
• Everything about an engine is inside the engineer who uses it.
• A control that is shared between your engineers now says so.
• Each of your engineers can now speak their own language, and there are five to choose from.
• Everything about an engineer is now behind their own name.
• Each engineer has their own cache warm.
• The wait between qualifying and the race is now a screen worth looking at.
• Your phone's dash now works out your pit stop.
• The dash on your phone now switches between practice, qualifying and race by itself.
• Qualifying now gets a screen built for one lap.
• You can reorder the cards down the side of the race dash by dragging them.
• The leaderboard now has a switch, like every other block.
• Each of your engineers can now have their own voice.
• PitCrew now tells you when there is a new engineer or new phrases, and never installs either on its own.
• Your phone's dash is now yours to shape.
• Practice, qualifying and the race each get their own dash.
• A preview, so you can set all of this up with iRacing closed.
• Five accent colours and three font pairs.
• The idle screen can be your own.
• PitCrew now states plainly what it collects and the terms it's free to use under, in the app and in the installer.
• Your engineer has three or four ways to say every call now, instead of one or two.
• Qualifying finally has an engineer.
• A red flag is now called on the radio.
• The engineer talks in the window before the green, where a real one talks most.
• You can now choose which ElevenLabs model reads your engineer's lines
• PitCrew now checks what your ElevenLabs key is allowed to do, not just that it works.
• The spotter is its own voice now, separate from the race strategist.
• A warning in the header of every screen when phrases are missing from the cache
• The relative table on your phone now shows every class.
• The interval column follows the track, not the standings.
• Your phone has its own dash settings.
• The board's compact size really lists nineteen cars now.
• Your phone shows your last race on the screen you meet before the next one.
• What your iRating and safety rating did is not shown, and the screen does not pretend otherwise.
• **Your engineer now warns you about a car...

PitCrew v0.4.0 — beta 1

PitCrew v0.4.0-beta.1

Beta de teste. Instalador não assinado — o Windows pode mostrar aviso SmartScreen; use More info → Run anyway.

Added

• Test versions are now actually published, and they arrive on their own. Turning Get test
  versions on used to buy you the same builds as everybody else, a little earlier at best ΓÇö nothing
  was ever released to that channel by itself. Now a change to PitCrew's screens reaches you within
  minutes of it being written, and the bigger changes are published to you ahead of everyone as they
  are ready.

Fixed

• An interface update no longer leaves people on test versions without one. Publishing a fix to
  PitCrew's screens removed the test channel's list of what was available, so anyone with Get test
  versions on stopped being offered anything at all ΓÇö quietly, since PitCrew read it as "nothing new"
  ΓÇö until the next full release put it back.

Added

• You can ask for test versions, in Settings. Off by default. Turn it on under Startup and
  PitCrew starts offering you new things before everyone else gets them ΓÇö they are less tested, and
  something may not work, which is the deal. Turn it off and you are back to released versions at the
  next check.

• PitCrew's screens can now update on their own, without reinstalling anything. When only the
  interface has changed, the panel offers it like any other update ΓÇö usually a few hundred kilobytes,
  because PitCrew reuses everything that did not change. Installing it redraws the window and your
  engineer keeps talking through it. If the new screens do not come up, PitCrew notices and puts the
  ones you had back by itself; there is also a Use the original interface item in the tray menu if
  you ever want to go back to the screens your PitCrew was installed with.

• PitCrew can now update itself. When a new version is out, the panel in the corner offers it the
  same way it already offers a new race engineer: it tells you the size, you decide whether to
  download it, and then ΓÇö separately ΓÇö whether to install it. Installing closes PitCrew and hands
  over to the Windows installer, which the panel says before you press. Nothing is ever downloaded or
  installed without you pressing, and never while iRacing is running. Beta versions are not offered
  this way.

• Each voice engine can now generate its own audio, and you choose which model to pay for. Open
  any engine on the Voices screen and there is a Generated audio section at the bottom: one press
  fills that engine's cache with every fixed line the engineers on it say, all of them in one run.
  On ElevenLabs each of the three models gets its own button with its price beside it, so you can
  stock the expensive model for a race weekend while your engineers keep speaking on the cheap one ΓÇö
  the audio is waiting the moment you switch. Nothing is generated until you press, and the button
  says when it is billed.

Fixed

• The radio banner came back on its own once a session started. Turning Radio messages off ΓÇö on
  the Overlay screen or with Alt+H ΓÇö held only until you got in the car: PitCrew put the banner back
  up the moment the session went live, and the switch quietly moved itself back on to match. The
  switch is now the one thing that decides. With it off the banner stays off whatever iRacing is
  doing; with it on the banner comes and goes with the session as before. It starts off every time
  you open PitCrew.

• While recording a phrasing, PitCrew told you to hold the wrong key. If you had changed your
  push-to-talk key, the recorder still said "Hold Alt+V and say it" ΓÇö the key PitCrew ships with
  rather than yours ΓÇö at the one moment it was asking you to press something. It now names your own
  key, and so does the microphone test.

• The microphone level bar was invisible when nothing was arriving. It was drawn in the same
  colour as the panel behind it, so a silent microphone showed no bar at all ΓÇö on the screen you open
  precisely because your microphone is silent. The empty bar is now visible, and a level loud enough
  to clip still shows red.

• A dead Play it back button on a take with no sound. When a test take came back without
  playable audio the button stayed on screen greyed out, which reads as a broken player. It is simply
  not there now.

Changed

• PitCrew now remembers which installation it is beside your settings, instead of inside the
  window. Nothing looks different, and nothing new is collected ΓÇö this is the same anonymous
  install id and the same "which races have already been counted" note as before, moved somewhere
  that survives the interface being replaced. It is the first step towards updating PitCrew's
  screens without reinstalling the whole app. Your existing id and race history are carried over, so
  no race is counted twice.

• Every box you type in, pick from or press is now the same height across the whole app. Text
  fields, dropdowns, search boxes and buttons each used to work out their own size, so a row that
  should have read as one line ΓÇö a field with a button beside it ΓÇö was three slightly different
  heights. They all measure the same now, and nothing in the app is taller than that.

• One corner, everywhere. The cards on the screens and the ones in dialogs were rounded by
  different amounts, which showed the moment a dialog opened over a screen. They are drawn with the
  same corner as each other and as the window itself, which is a touch rounder than before.

• The window's corners no longer show a seam against the desktop. PitCrew draws its own frame,
  and Windows was rounding the same window a second time a few pixels tighter ΓÇö so at each corner
  there was a sliver of Windows' shadow and border sitting outside PitCrew's own edge. The window's
  corner is now PitCrew's alone. The trade is that the main window no longer casts the Windows drop
  shadow: there is no way to have the system draw a shadow around a corner it is not drawing.

• A long device name no longer breaks a dropdown onto two lines. Microphone (2- Realtek(R)
  Audio) and names like it now end in an ellipsis inside the closed dropdown, which stays one line
  tall. The full name is still there in the list when you open it.

• The Voice commands screen is now two tabs instead of three columns. Setting the microphone up
  and teaching PitCrew how you ask are two different jobs, and they were sharing one screen ΓÇö with
  everything about your microphone squeezed into a narrow strip down the right-hand side. Push to
  talk now has the whole width for your key, your wheel button, the test and the microphone itself,
  side by side; Input catalog has the whole width for the list of what you can ask and how you
  phrase it. The switch that turns the whole thing on stays at the top of both, and the screen opens
  on Push to talk ΓÇö because if you came here in a hurry, that is usually why.

• The buttons on the Voice commands screen now match the rest of PitCrew. That screen had kept
  square, uppercase buttons from an older part of the app while every other screen moved to the
  rounded sentence-case ones ΓÇö so RECORD A PHRASING sat next to Start the test and neither looked
  like it belonged. They are all one shape now.

• The push-to-talk panel is grouped instead of being one list of six rows. What you press ΓÇö the
  key and the wheel button ΓÇö is now separated from what happens once you have: hold or tap, and the
  sound when the microphone opens.

• The Voice commands screen reads properly with a screen reader or with Voice Control. Several
  rows were captioned one way on screen and named another way to assistive technology ΓÇö the field
  under Key announced itself as "push-to-talk binding", so saying "click Key" to Windows Voice
  Control reached nothing ΓÇö and the sentence under each caption, including the one explaining that
  the sound when the microphone opens is what stops your first word being cut off, was never read out
  at all. Each control is now called what the screen calls it, and its explanation is announced with
  it.

• The microphone panel no longer leaves a gap below it. It was still sized as though it were the
  whole right-hand column, which stretched it to the full height of the window and could put a second
  scrollbar inside the first.

• Groundwork for better speech recognition. PitCrew can now be pointed at a second, higher
  precision copy of the recogniser, so the two can be measured against the same recordings rather
  than against an impression. Nothing changes for you yet ΓÇö same model, same download size, same
  everything a driver sees. It is how the next improvement to "não entendi" gets chosen on
  evidence.

Added

• Bind your push-to-talk key by pressing it. The key was the one thing on that screen you still
  had to spell ΓÇö and PitCrew's spelling, at that, with the modifiers first, no spaces, and
  NumpadAdd for the numpad plus. Press Press the keys on the Voice commands screen, hold the
  combination you want, and it is bound. Your wheel button has always worked this way; the key does
  now too. You can still type one in, and that is deliberate rather than left over: a chord Windows
  hands to something else before it reaches PitCrew never arrives at that screen to be captured, so
  typing is how you reach one you cannot press there.

• The screen now tells you which key is actually working. Changing the key takes a restart ΓÇö
  PitCrew asks Windows for it once, when it starts ΓÇö and until now nothing said so at the moment it
  mattered. Rebind the key and the screen names the one still in use until you restart, and the
  microphone test names t...

PitCrew v0.1.0 — beta

The first public beta. PitCrew talks to you during a race — the spotter, your fuel, your gaps and your position — in Brazilian Portuguese or English.

Added

• The first public beta. PitCrew speaks to you during an iRacing session: the spotter (a car
  alongside, which side, and when you are clear), fuel (consumption per lap, whether it reaches the
  end, and warnings as the tank runs down), gaps and position (filtered by class, so another class's
  leader is not reported as if it were your race), your lap times and personal bests, session flags
  and pit and penalty calls, and a memory of your best known lap for each car/track combination.
• Brazilian Portuguese or English, chosen independently of the interface, which is English.
  Spanish, German and French are written but not released yet.
• A local voice that needs no account and no network. Speech is synthesized on your own machine;
  an ElevenLabs API key is an optional upgrade to the studio voice, never a requirement, and an
  install without one gives up no information at all.
• An overlay over the sim — proximity bars and the last message as text — transparent,
  always-on-top and click-through, so it cannot steal a click mid-race. It keeps working with
  iRacing in exclusive fullscreen.
• Three global shortcuts: Alt+H shows or hides the overlay, Alt+R repeats the last thing
  said, Alt+M mutes the engineer.
• Timing you can tune yourself without waiting for a release — spotter debounce, fuel warning
  thresholds, the gap window and the opening silence, all in an optional tuning.json.
• Windows installer builds and GitHub releases are now produced by CI, and published here together
  with these notes.
• The website uses Google Analytics to count visits and how many people click through to download.
• PitCrew now measures how the app itself is used, and there is a page listing exactly what that
  means — what PitCrew sends. The short version: it reports what
  happens in the app, never who you are or how you drive. Whether the first-run voice download
  succeeded or failed, whether setup finished, whether PitCrew found iRacing, that a race was logged
  and how much the engineer said in it. Never your name, your engineers' names, your API key, your lap
  times or your telemetry, and nothing you typed. An earlier version of these notes said the app made
  no analytics requests at all; that is no longer true, and this replaces it rather than sitting next
  to it. There is no switch in the app — the page explains how to block it at the network, and PitCrew
  is built so that blocking it cannot break anything.
• A way to support PitCrew, at the bottom of the home screen. There is no paid version and
  donating unlocks nothing — every feature is already yours. It is there because the app has no paid
  tier, no ads and no account, and is written and tested by one person after work. Pick $5, $10, $25
  or your own amount; the button opens PayPal in your own browser, where you confirm before anything
  is charged. Your card details never reach PitCrew.
• The same way to support PitCrew, on the website, under the download button rather than in front
  of it. It offers the same $5, $10 and $25 as the app, or an amount you choose, and it says plainly
  what the money is for: the installer is not code-signed, so Windows warns you twice, and a signing
  certificate is the next thing that fixes for everyone who installs. Donating still unlocks nothing.

Changed

• The website now says what the first launch actually does: PitCrew downloads a 310 MB voice model
  the first time you open it, and runs offline from then on. It previously promised that a clean
  install worked offline, which was never true — and a driver on a metered connection would have
  found that out after installing.
• The website lists the two languages PitCrew speaks today, Brazilian Portuguese and English, rather
  than the five it has phrases written for. Spanish, German and French still need a voice before they
  can be spoken, and the site now says so instead of counting them.
• Every quoted radio call on the website is shown in Portuguese and English. The page's own
  interface is English and its readers are not only Portuguese speakers, so a column of untranslated
  quotes was decoration where it was meant to be the evidence.
• The website's "who speaks what" table can now be read in any of the five languages PitCrew has
  phrases written for, and the lines in it are the real ones out of the phrase catalog rather than
  examples written for the page. Picking Spanish, German or French says plainly that the words exist
  but the voice does not yet.
• The website's sections have more room to breathe, and the closing invitation to download gets some
  runway before the ask.
• The website no longer assumes your engineer is a man. It says "them" where it said "him", and the
  two example engineers now carry voice names that match the names they are given — the local one was
  labelled with a female voice under a man's name.
• The website's links and buttons are big enough to hit with a thumb. On a phone the four section
  links at the top were about a third of the size they should have been, and they are the only way to
  skip a section on a page that runs to some nine thousand pixels.
• The website is served with a strict content-security policy and the usual browser protection
  headers, so nothing it did not ship can run on it, and it cannot be framed by another site.

Fixed

• The website's download button now downloads PitCrew. Every link on the page pointed back into
  the page itself, so the button at the bottom — the one every other button leads to — did nothing at
  all when clicked. It, and the two above it, now go to the latest release.
• The website's footer links go where they say: the install guide, getting started, voices and
  languages, troubleshooting, the release notes and the issue tracker. All twelve previously scrolled
  back to the top of the page.
• The four numbered items in the website's header now scroll to the sections they name, and the
  header's own menu lists them in the order the page presents them. Section 03 was missing from the
  menu entirely, and the menu disappeared completely on a phone.
• Picking a voice in the website's voice-designer panel no longer has the panel change it back a few
  seconds later.
• The website no longer renders as a blank page when the browser is not running animations — a
  restored background tab, low-power mode, or an in-app browser. All of its text was hidden until an
  animation revealed it.
• Sharing a link to the website now produces a preview card with an image, instead of an empty one.

Removed

• The website's hero is much quieter: eight things were moving continuously behind the headline, and
  now two are.

---

Install: download the .msi below and run it. Windows 10 or 11, 64-bit.
No .NET, no Python, nothing else to install.

The installer is unsigned, so Windows shows a SmartScreen warning —
More info → Run anyway. The first run downloads the voice model (~310 MB);
after that PitCrew works offline. See the
install guide.

Built from 5ed589866c5de583c2127f77661d0ebe941eb406.