New Features

The tour of what just arrived in RaceVisor: an AI Chat you talk to from the driver's seat, and the Save It widget for drivers who steer with the back end.

What arrived in RaceVisor on 2026-11-03: an AI Chat you can talk to from the driver's seat, and a widget for drivers who steer with the back end. Every button and command word below is also in the Controls Reference; this page is the tour.

AI Chat widget#

A conversation with the model of your choice, inside the dash. It plays a race engineer on the radio: questions, problems, your laps, the car, the rig. Short answers, plain words, numbers.

  1. Add widget → AI Chat (under TIMING & TRACK). Add as many as you like.
  1. Click ⚙ and pick the model: a cloud service with your own key (Anthropic Claude, OpenAI, Google Gemini, xAI Grok, Mistral, DeepSeek, Groq, OpenRouter) or one on this PC with no key (Ollama, LM Studio) - with those, nothing leaves your PC. Ollama does not have to be running first: when it is the chosen service, RaceVisor starts it at launch, on a switch to it and before a question if it has stopped, and the session launchers start it before RaceVisor. For accurate answers and race advice, a cloud model is recommended: local models are free and private, but in testing they made things up, could not read screenshots and slowed the frame rate on track. Your mileage may vary.
  1. Type and press Enter, or talk (below). The answer shows in the panel.

Every widget keeps its own conversation. It is saved under Documents\RaceVisor\ai_chat\sessions and is there again after a restart. Give a widget a label and that is its name.

Shared. Turn Shared on in two or more panels and each one is told what the others have been discussing, and adds its own talk for them. Off = private. Every panel keeps its own conversation either way.

My laps. On, the model is handed this car + track's corner numbers - time lost, brake points, speeds, throttle points, the fastest car seen - the same numbers AI analysis sends. Ask "where am I losing time?" and it answers about your laps. Never the recording, your name or your iRacing ID.

A desktop window too. Right-click any Corner Pace or Brake-Gas Cue widget → AI analysis → Chat with the model, or a widget's own menu → Open in a window.

The menu works in the headset. Right-click the widget: Open in a window, My laps, Shared, Files, Speak, Open mic, Talk to THIS panel, Drop a capture into this chat, Undo, Stop, Clear, AI settings, Paths. It is the in-surface menu, drawn in the overlay, so it is there in VR.

Talk to it, hear it back#

Whisper (whisper.cpp with a model file on this PC) hears you; Windows voices or Piper talk back. Windows' own speech recognition is there as a fallback that needs no model file. Nothing leaves the PC for any of it. Pick the recogniser and the model in AI settings: a ggml model file in Documents\RaceVisor\models - base.en or small.en for a CPU, which is what the download runs on.

  1. Hotkey Editor → AI CHAT → bind Push-to-command (a wheel button is the natural choice). Hold it, speak, release: what you said appears in the panel as if typed and goes to the model.
  1. Or 🎤 Open mic: it listens all the time and sends after the quiet time (AI settings → seconds of quiet, 1.5 s by default). Open mic on when RaceVisor starts makes it the default.
  1. Microphone: a Quest headset plugged in when the voice is first used is the mic; otherwise Windows' default microphone.
  1. Spoken words go to the panel you last used; the listening panel shows 🎤 listening… and what it is hearing.
  1. Command words, said on their own: "disregard" throws away what was heard and cancels the answer; "undo" takes back the last question and answer; "stop" stops the answer being worked on and stops the voice. Stop also has a hotkey.
  1. 🔊 Speak on a panel reads replies aloud. AI settings picks the voice: a Windows voice (David, Zira, Mark) or a Piper neural voice on this PC - natural, seventeen English voices, women and men, US and UK, fetched with one button into Documents\RaceVisor\piper. The speaking speed slider (half steps; 0 = normal, 10 = about three times faster, RaceVisor starts at 3.5) applies to both. It comes out of the Quest's headphones when the headset was plugged in at start, otherwise Windows' default output. The text always shows; the voice is the option. While it talks the mic is ignored, so it never answers itself.

It draws#

Say or type "draw where I should brake for T3", "show me T5", "plot my time lost per corner", "diagram the braking phases". The answer comes with a drawing under the words.

Files: your games, your rig, RaceVisor's settings, any folder#

  1. AI settings → Paths: the folders the model may use, in four groups. Game - the sims' Documents folders (iRacing, Assetto Corsa, ACC, Automobilista 2, RaceRoom, rFactor 2 and Le Mans Ultimate UserData, Project CARS 2). Rig - Meta Quest Link, OpenKneeboard, SteamVR config, Virtual Desktop. Settings - RaceVisor's own folders. Global - anything you add. Detect fills in what is on this PC; Add folder takes any folder at all.
  1. Each row has may change (the model may write there) and on. Games and the rig start read-only; RaceVisor's own folders start writable.
  1. With 📁 Files on, the model can list, find and read in those folders - "what is my brake bias in the setup?", "find my app.ini", "why does my wheel profile keep resetting?" - and ask to change a file.
  1. Every write waits for you. The panel shows what it wants to write and Approve / Deny (also in the widget's menu, so it works in the headset). A .bak-<time> copy is made before any change, and Undo puts the file back.
  1. Never written: recordings, .ibt telemetry, videos, programs. Nothing outside the listed folders is readable, whatever the model asks.

Captures, straight into the chat - or out to share#

  1. Ask for it: "take a screenshot of monitor 2", "screenshot the headset", "record all monitors", "stop recording". Screenshots from the primary monitor, all monitors, monitor 1 / 2 / 3, or the headset (everything, sim only, or other overlays only). Screen video of the primary, all, or one monitor, MP4 to Documents\RaceVisor\videos. VR video is not available - it says so.
  1. FloDee's set, the same ways, through FloDee when it is installed: Capture Region (drag a box → PNG), Record Region (GIF), Record Video (drag a box → MP4), Capture Text (drag a box → the text comes into the chat as a message). Plus a webcam photo and webcam video (with a Webcam widget showing that camera).
  1. One click: the 📷 button next to the text box screenshots the primary monitor. It waits as a chip under the text box and goes with your next message; its path is put on the clipboard. The ▾ beside it picks all monitors, one monitor, the headset, webcam or FloDee's region / text captures. In the headset the widget's menu → Drop a capture into this chat has the same list. Vision models (Ollama llava / gemma / minicpm-v, GPT-4o, Gemini) look at it and tell you what they see.
  1. Share it: click a thumbnail to open it; right-click → Copy image (paste it into Discord, a message, anywhere), Copy file path, Open the folder.
  1. Bring your own: drop a picture file on the panel, press 📎, or Ctrl+V a copied image into the text box. It waits as a chip under the text box and goes with the next message.
  1. Copy a line out: every line in the log has a 📋 at its right end that puts that line on the clipboard, ready to paste into another chat, a message, anywhere. The text can also be swept with the mouse. The log has a scroll bar for long conversations.

It works the pit board, the car and the dash#

Say it the way you would to a crew chief; the model works out what you mean and does it, then confirms in one line what it did.

  1. Next pit stop: "only give me a splash of fuel", "five laps of fuel and raise the right front three pounds", "no tyres, fuel to full, tearoff off". RaceVisor sends the same commands the Pit Service widget sends, reads the pit board back from the sim, and the model confirms exactly what the crew will do: litres, which tyres, pressures, tearoff, fast repair. iRacing only.

Pit request (2026-11-05): "pit request", "box this lap", "I'm coming in" and the whole stop is done for you. RaceVisor tells the field you are pitting (the sim's chat macro), works out the fuel to the finish from the measured use plus the planner's reserve, marks the tyres worn past the limit, puts a fast repair on when the sim reports required repair, tearoff on, sends it all, reads the plan back to you, and messages the field again by itself when the car leaves pit road. "Fill her up" and "splash and go" change the fuel choice; "no tyres" or "fronts only" the tyres. Needs no key: it watches the sim, not the limiter. Put the two messages in the sim's chat macros 1 and 2 (Options → Text Chat), or change the numbers in AI settings.

  1. In-car adjustments: "go one round up on the track bar", "two clicks of wedge", "move the bias back", "spotter off". These are keys you bind in the sim's own options; put the same key under a plain name in AI settings → Rig controls once, and the chat presses it the right number of times. A control with no key is known but refused, and the chat tells you to set it.
  1. Your pit notes: "note that T3 is braking at the 2 board", "write that down", "read me my notes" - the Notes widget's note for this track, written live on the dash. A note is written only when the model sends the note command; if a model answers "added to your notes" without sending it (small local models do), RaceVisor tells it nothing was written and asks for the command, so the note lands on the second try. The crew log shows that as note-nag. A note command with a small typo in it (a stray bracket, a missing brace) is mended rather than dropped. With no session running there is no "this track" note: the widget shows General only and the track / General switch is hidden, so one note can no longer appear under two names.
  1. The web, and anything at all: the advisors are not limited to racing. "What's the weather at Daytona Saturday", "look up the Nordschleife lap record", "find a setup guide for the GT3 at Spa", "what's in the news", "write me a note to my landlord" - the chat searches the web and reads pages for you (its own web search and page fetch, no key), answers from what it found and says where it came from. With a Browser widget on the dash the page it reads appears there; "open <address> in the browser" shows a page without reading it; "what does this page say" reads what the Browser widget is showing. There is no off-topic: ask it anything.
  1. Race model (local models): a model on this PC runs on the graphics card, the same card that draws the headset - a 10 GB model answering mid-lap costs frames. In AI settings, Race model names a small local model (llama3.2, gemma3:1b) that takes the questions while the car is on track; in the pits, the garage or with no session the full model is back, automatically. The dash says which is answering when it switches. Blank = always the full model. Cloud services are unaffected (they cost nothing on the card).
  1. The wheel drives the chat. A wheel's hat switch can now be bound like any button (Hotkey Editor shows it as D-pad up / right / down / left), and new actions go with the face buttons: Say "Yes, please", Quiet (twice fast = quiet + stop thinking), Pit request (the chat's whole stop, no exit message), Screenshot into the chat, and four sim chat macros - pitting, exiting pits, thank you, sorry - straight to the field. On a G29: O talk, Triangle yes, X quiet, Square pit request; D-pad left pitting, right exiting, up thank you, down sorry.
  1. RaceVisor itself: "spotter off" / "radar on" switches the dash's own widgets; "raise the chat voice two clicks", "slow the voice down", "wait three seconds of quiet", "make the fuel widget half transparent" turn the matching settings.

"Use Amy's voice"#

Seventeen Piper voices and whatever Windows has, switched by name from the driver's seat: "use Amy's voice", "voice Ryan", "talk like Alan" - the new voice says hello. "List the voices" reads them out, "put the voices in a note" writes the list into the General note.

Show all, Tile, Default, and "AI chat full"#

Widgets over and under each other, and the one you want is the one you cannot grab. Three new toolbar buttons: Show all (every widget on), Tile (every widget on, in a grid, nothing overlapping) and Default (the layout as it loaded). By voice: "show all", "widgets tiled", "widgets default", "widgets restore". One widget big: "AI chat full", "timing full"; back with "AI chat restore". "Add a radar" puts a new widget on the dash, "remove the radar" takes it away, "save layout" saves under the current name and "save as oval night" under a new one. Ask the chat what to show for a job and it recommends widgets and adds them when you say yes. "Resize RaceVisor bigger" grows the whole overlay. And the kneeboard: "kneeboard closer", "kneeboard up a bit", "kneeboard bigger", "tilt the kneeboard back", "kneeboard off", "kneeboard recenter" - the Kneeboard Position sliders, spoken. RaceVisor does these itself, instantly, no model needed. All of them are on the new Voice Commands widget, grouped, for the dash, a VR quad or the kneeboard; "what can I say" reads the same list.

It keeps your record, in every sim#

Every session you drive is recorded on its own: sim, track, car, session type, laps, best and average lap, incidents, fuel, tyre pressures and setup items, the rating and licence the sim showed, start and finish position. "What did I run at Phoenix", "what pressures did I use last time here", "how is my rating going" are answered from it. Driver profiles by a name you choose: "driver Sam", "add driver Sam". And a career manager that asks what you want out of your racing before it plans anything, and keeps your answer.

It knows the manual, it has a crew, and it keeps the log#

Three things from 2026-11-05 that turn the chat into the team around the driver:

  1. The manual is inside it. Every page of this site's documentation rides inside the exe, and the passages that match your question go to the model with each call. Ask how a widget works and the answer comes from the manual.
  1. Specialists. For a real job the chat hands work to agents that run at the same time: crew chief, strategist, setup engineer, driver coach, spotter, data analyst, rig tech, career manager. "Plan my stops" goes to the strategist with the measured fuel use, the laps to go and the tyre wear; "get me ready for this race" puts three of them to work. You get one answer built from their reports. Same model for all of them, so each agent is one more call.
  1. The crew log. Every question, answer, action, agent report, pit request and pit exit is written to Documents\RaceVisor\ai_chat\crew_<month>.log, with the time. Ask "what did we do last time here" and the chat reads it back. Nothing leaves the PC.

Radio widgets#

The chat as TV radio chatter, under TIMING & TRACK: Radio (both sides - "RHEA: how many laps of fuel?" / "AI: five laps"), Radio - AI only and Radio - driver only. Just the words, newest at the bottom, named after the sim's driver name. Drawn on the dash, so they go in VR quads and on the kneeboard; the chat panel itself can stay on the monitor. The chat is also handed the live telemetry every turn - fuel, laps of fuel, laps and time left, temperatures, lap times, tyres - so "how many laps of fuel?" gets the real number.

Build your own widget#

The site's Widget Builder page: text, bars, gauges and lamps, each bound to a telemetry channel, laid out by dragging on a live preview. Download one small .json file, put it in Documents\RaceVisor\widgets (or Add widget → MY WIDGETS → Import), and it is a widget like any other: monitors, kneeboard, VR quads, accent colour, opacity. Edit the file on the page and save it over the old one; RaceVisor picks the change up on its own. Fifty-odd channels, from speed and gear to tyre temperatures and laps of fuel left.

Save It widget#

For driving with the back end: gas it, let the rear step out a set amount, and point the car with the throttle. One widget shows whether the rear is where you want it, shouts when it is going past saving, and lights a wheel that has locked or is spinning. Under PEDALS & STEERING.

  1. Rear slip gauge - the rear axle's slip angle on a bar: centre is straight, left / right is the tail out to that side. The green band each side is the slip you want; the red ends are where SAVE IT starts. The needle is white under the band, green in the band, orange past it, red at alert.
  1. Status line - IN THE BAND while you are in it; SAVE IT flashing red with a red frame when the rear is past the alert angle or is still stepping out fast beyond the band; LOCKING (red) when the brakes are hard on and the car has stopped slowing for it; SPINNING (orange) when the throttle is hard on and the car has stopped pulling.
  1. Two lamps - BRAKES and DRIVE, each with the g the pedal is making; red LOCKING / orange SPINNING when grip goes. iRacing's live feed has no per-wheel speeds, so these come from pedal versus the g it produced, the same test as the Brake vs g and Throttle vs g widgets. A sim that does publish wheel speeds gets four tiles, LF RF / LR RR, with each wheel's speed as a percent of the car's.
  1. Set the band for the car: right-click → Rear slip band → a preset (Tidy 2-4°, Lively 3-7°, Loose 5-10°, Sideways 8-15°) or Your own numbers: SLIDERS - three draggable sliders on the properties panel's THIS WIDGET tab, in the headset, that stay open while you drag. Each widget keeps its own numbers.

The numbers come from the chassis velocities and yaw rate iRacing publishes at 60 Hz, through a simple bicycle model. Other sims give the body slip angle only.

Token counter and cost#

Every panel's status line shows what it has spent: tokens in (everything sent - the conversation, the notes, what it read) and out (the answers), the last exchange in brackets, and the cost. Type the service's price per million tokens in AI settings → Price of this model and the cost is real money at that price; leave it blank for tokens only. A model on this PC is always $0. The widget's menu shows the same and resets the counter. The numbers are the service's own count, saved with the conversation.

Smaller things from the same night#

Where things are saved#

WhatWhere
ConversationsDocuments\RaceVisor\ai_chat\sessions\<id>.json
Shared logDocuments\RaceVisor\ai_chat\shared.json
Day log of everything saidDocuments\RaceVisor\ai_chat\<date>.txt
Model, key, voice settingsDocuments\RaceVisor\ai_settings.json (keys encrypted for your Windows user)
Folders the chat may useDocuments\RaceVisor\ai_paths.json
Screenshots and webcam photosDocuments\RaceVisor\screenshots
Screen and webcam videoDocuments\RaceVisor\videos
Backups before a file changenext to the file, name.bak-<date-time>