Help

The site can’t see your game. The companion is a small Windows program that reads Le Mans Ultimate’s telemetry and sends it to your room. It’s optional, and you can type every number by hand, but most of what StintLab does well comes from having it running.

Installing it

1. Download the companion, then run it. There’s nothing to install. It isn’t code-signed yet: if Windows warns, choose More info › Run anyway. Earlier versions are on the same page.
2. Paste your room code into it, or open it from a room and it will offer the code.
3. It needs one game plugin — TheIronWolf’s rFactor 2 shared-memory plugin, which is what LMU actually publishes telemetry through. The companion checks for it, and offers to download and enable it for you.

It asks before touching anything in your game folder, refuses to write while the game is running (Windows holds the file open and the write would fail silently), and backs up the plugin settings file before editing it, since that file is shared with every other plugin you have.

The desktop app

The companion window has six tabs: Home shows its status, the room code and the live telemetry, Planner opens the plan inside the app, and Data, Engineer, Overlays and Settings hold the rest. The Auto pit menu toggle lets it fill in the game’s pit menu for the next stop from the plan: VE, fuel, fuel ratio, tires, brake ducts and repair. It also has color themes, and a Show in Discord status option.

With damage, Price repairs automatically briefly asks the game for the exact repair time and puts the pit menu back, so the plan shows the game’s own number.

Overlays and stream overlays

The Overlays tab has a switch for each in-game widget, a live preview, All off and a hotkey that hides or shows them all. Besides the relative, standings, tires and radar there are fuel, yellow flag spotter, blue flag, rejoin, cuts counter and driver badge widgets. The standings and relative can use a Timing layout.

Stream overlays (OBS) shows each widget as its own page. In OBS add a Browser source and paste the widget’s address. Only the PC running the companion can open them. For widgets driven by the room, use Stream overlays on the site.

Two companions at once

If two teammates both have the companion running in the same room, nothing gets mixed up. In practice everyone’s data is kept, per driver, and a driver switcher picks whose you are looking at. In the race the PC actually in control of the car is the one used; the others are shown as spectating.

Practice and qualifying

Leave it running. The companion works out which session you’re in and changes what it does:

• Race — everything. The clock anchors to the green flag, stops close stints, the schedule re-times around what actually happened, and Discord gets told.
• Anything else — measuring only. Fuel, energy, tire wear and lap times are collected and saved; nothing touches the race plan, no stints close, and there are no strategy calls.

This is why “drive a few laps in practice” works. It is also why a Thursday practice run can’t rewrite Saturday’s plan. Switching from qualifying into the race clears whatever the earlier session left behind, so the race starts from zero.

Nothing is arriving

• The companion must run on the same PC you drive on. Telemetry is read from shared memory; it can’t come over the network.
• Enable Plugins has to be on in the game’s settings, and the game restarted after turning it on.
• You must be in a session — on track or in the garage. A game sitting in the menus publishes nothing.
• Check the room code in the companion matches the one in the top bar here.
• The Race tab’s Before the race: get connected checklist says which of these is missing.

The planner has three tabs: Drivers, Plan and Race. The tabs and the race ticker stay at the top while you scroll. Plan is split into sections, one on screen at a time: Event · Rates · Strategy · Stints · Tires. Saved data has its own page, Saved data in the top bar. Room setup, My settings, My availability, Download and Open plan file, Discord, Split view, the time zone, the theme and What’s new are in the … menu at the top right.

The Next line

One line above the plan says the next thing to do, and the tabs show a check when they’re done or ! when they need you. It reads the room, so a teammate who joins late sees the same thing.

Event

• Race duration — hours and minutes, e.g. 6:00.
• Race start — when the flag drops. It follows the UTC / Local switch in the top bar, and clicking the clock beside it switches between 12- and 24-hour times. The plan itself runs on UTC on purpose: it’s the one clock a team spread over five time zones can all say out loud without arithmetic.
• Checkered flag — race start plus duration.
• Dry tire allocation — individual dry tires for the race, not sets, including the grid set. Strategy needs it to judge the tire strategies.
• Track and Car — pick them and any empty Rates fill from your Saved data for that car and track. A banner says what was filled, with Undo.

Wet tires never count against the dry allocation. Wets are unlimited in LMU.

Rates

What the car uses each lap, in three rows, because a stint driven flat out, a stint saving fuel and a wet stint are three different cars:

• Standard — racing pace. This is the one that matters.
• Fuel saving — lifting and coasting.
• Wet — on wet tires.

All three rows are always shown. An empty row uses Standard. Recalculate from standard fills the Fuel saving row with the smallest saving that gets one more lap out of each stint. Fill from saved data fills the rows from any car and track you have saved.

Each row wants a lap time, VE per lap (%) and fuel per lap (liters). Whichever of fuel and VE runs out first sets the stint length, so both matter. The fuel ratio beside each row is the garage setting those two numbers imply. Fuel tank is in Event › More options, liters at full.

Tire wear is a rate too, so it is set here: Dry wear % / lap and Wet wear % / lap, each with an Avg / Per corner switch. Avg is one number for all four tires; Per corner is four, for a car that eats one axle. Left empty, wet stints wear at the dry rate.

You shouldn’t be typing these. Drive a few laps with the companion running and it offers what it measured. Press Use what we measured. Everything measured, wet running included, is saved per car and track for next time.

Final stint, under the rates, shows what the last stop must carry. Average a tenth quicker than planned and the flag falls with you a lap further on, so Spare laps (Stints › Pit stop) can carry fuel for laps beyond the plan.

Stints

The stint plan, built once you have picked a fuel and a tire strategy (see Strategy). At the top is a timeline of the race, green to flag:

• Each stint is a block in its driver’s color.
• ✓ marks a stint that is done. The stint on track now is outlined.
• Dots at each stop show how many tires are changed there.
• A blue top edge marks a wet stint; a dashed bottom edge marks a fuel-saving stint.

A one-line summary of the plan sits above the timeline, and a key below it.

Driver share · fair share

Driver share · fair share shows how much of the race each driver drives. The tick on each bar is an even split, so you can see at a glance who is over or under it. It also flags too many stints in a row and stints a driver isn’t available for. It opens by itself when something needs a look.

The stint table

• # — stint number. Type is STD (standard), FS (fuel saving) or WET; click it to change.
• Tires — how many tires are changed at the stop before this stint.
• UTC start / end — both editable; type an end time to force a stop.
• Laps — editable. A dot beside it means the number came from the race rather than the plan.
• Energy to load — VE needed for the stint, with a small margin. Over 100% is flagged: the stint can’t be done.
• Driver — click to assign, or press Auto-assign drivers.
• Status — Final for the last stint, Locked once the race has fixed it, Done once completed, and Early · done when it was cut short.

Fuel per stint switches how fuel is shared. Fill every stint fills each stint as full as it can and leaves the rest for the last one: fastest, but full stints have no spare. Even fuel gives every stint the same fuel and the same spare, for a few seconds more in the pits.

Everything you type is kept; the plan re-times around your edits. More holds Clear manual end times, Clear assignments and a full reset. Copy image copies the schedule as a picture for Discord.

Pit stop, below the table, holds the pit duration (the drive-through only, pit entry to exit), refuel rate, tire change time, minimum tire life, spare laps and how much tire wear fuel saving saves. Most races can keep the defaults, but set the pit duration for your track. Each stop costs the drive-through plus the longer of refueling and changing tires, because those happen at the same time.

Tires

Which tires go on at each stop. At the top, a life chart shows each tire’s life across the race against a lap axis, so you can see where it runs low. Below it:

• Allocation — a read-out of the dry tires set in Event (change it there). Fill minimum enters the fewest dry tires that get this plan to the flag without going under the minimum tire life.
• Fresh and Scrubs — new tires still unused in the plan, and used ones with enough life for another stint.
• Wear — a read-out of the wear rates, with Edit wear in Rates.
• More tire settings — the life each tire starts the race on.

The tire plan follows the tire strategy you picked. Each stint shows each tire’s life from start to end and what happens at the stop: fresh (a new set), scrub (a used set going back on) or keep (stay out on what is there). On a wet stint after another wet stint it reads fresh wets or keep wets. Wets are free, so that only changes the stop time.

Click any tire to override it. Your choice is pinned (📌) and the rest of the plan re-solves around it, telling you what else moved, how many dry tires the plan now uses, its lowest life and whether it still fits. Plan tires plans the tires again and keeps your pins; Clear manual changes (shown once you have a pin) removes every pin.

Wet stints run on wets, which are free in LMU, so they cost no dry tires and the slicks that came off wait in the garage at the life they had. When the plan only fits your allocation because of the forecast rain, the summary above the table says so and what happens if it stays dry: how many tires that needs, which stints would double-stint and the lowest life.

Forecast, multipliers and where numbers come from

• Plan for the forecast (Event) — on, rain in the forecast can switch stints to wets and move stops. Off, the plan ignores the forecast for everyone in the room; the live wets call still shows.
• Fuel use multiplier and Tire wear multiplier (Event) — enter the server’s values and the plan scales to match. Keep your rates at normal use. Laps you practice with a multiplier still count for pace and tires; their fuel is left out.
• Each number is labeled with where it came from: measured, saved, teammate, typed, community (other drivers at your pace) or official races estimate (a rough guess from official results). With no data of your own the planner fills from community, then official numbers. Your own data replaces them as soon as you have it.
• With no wet numbers yet, the planner uses a labeled wet estimate. Wet laps then fill the Wet row on their own, and tire wear is saved by compound and track temperature.

Discord

The Discord webhook and race alerts are in the … menu at the top right. See Sharing it with the team below.

The top line is your plan as it stands: stops, tire changes, laps and when you finish. During a race it counts from where you are now. Below it, two groups of cards: fuel strategies and tire strategies. Each card has one verdict line and compares itself with yours (“vs yours”), and the best one is marked.

Pick a fuel and a tire strategy first

In a new room no plan is built until you pick both: press Use this on one fuel strategy and one tire strategy. Until then Stints and Tires stay empty and the Next line says what’s missing. The tire strategies need the dry tire allocation set in Plan › Event first.

You can pick any card, not only the best one. If it’s slower than what you have, you are asked to confirm. Change your mind later the same way.

Fuel & stops

• Push every stint — every stint runs until fuel or VE runs out.
• Even fuel — spread the fuel evenly so every stint is about the same length.
• Save fuel to skip a stop — saves fuel on the fewest stints needed to drop one stop. It says per stint what to hold (L/lap or % VE/lap), for how many laps, and roughly how much slower a lap that costs. The cost is your Fuel saving row’s lap-time gap, scaled by how much of that save you need. The verdict says whether it’s worth it, and the break-even cost a lap.

Tire changes

• New tires every stop — new tires at every stop.
• Fewer tire changes — keep the same tires for more than one stint and only refuel in between. Named by how long each set lasts: Double-stint tires, Triple-stint tires, Tires every 5 stints, or a range such as 4–5 stints a set. Needs tire wear in Rates.
• Your tire plan (custom) — shown when your tire table matches neither.

Each card shows tire changes, tire time, the lowest life and the finish, and warns when tires would go under the minimum or need more dry tires than your allocation.

What if…

Open What if… to test the plan without changing it: we’re slower (s/lap), fuel or VE use is higher (%), pit stops take longer, it rains (from and until), or a driver can’t drive from a given time. Quick picks: +2% fuel, +0.5 s/lap, Rain at half distance. Each answer shows under its question and the cards update. Update my plan to this applies it; Reset clears it.

Below the cards, Fuel saving shows what it takes to drop a stop, and Realtime deltas compares the plan with the race clock.

To record practice, sign in and drive any practice session with the companion on your room code. After three clean laps, pit or stop and the run saves to Saved data (top bar). The room’s plan is untouched: only the race drives it, and qualifying is not recorded.

Fuel per lap, energy per lap, tire wear and lap time belong to one car at one track. They don’t change between races, so StintLab keeps them.

Anything the companion measures is saved on the Saved data page (top bar), per car and track. Use the Track and Car pickers to narrow the list. Each row shows lap, fuel, energy and wear per lap, pit lane time and how many laps it was measured over, with Use, Forget and Rename.

Wet running is kept per LMU condition (Dry, Damp, Slightly Wet, Wet, Very Wet, Extremely Wet), on slicks and on wets apart. Hover a condition to see its wetness range.

Each car and track shows with its icon and country flag. Next time you pick that track and car in Plan › Event, any empty Rates fill from them, with Undo. Rates › Fill from saved data fills them from any other pair. Signed in, they follow you to any machine; signed out they stay in that browser and move to your account the first time you sign in.

The Fuel analysis link on that page shows where your fuel goes: flow by RPM and throttle, fuel per gear, and totals from your clean laps. It needs companion 2.7.3 or newer.

The longest sample wins rather than the newest. A 30-lap stint knows more than the three laps you did before pitting for a setup change.

Roster

• Time zone — hours from UTC, e.g. −5 for New York in winter. New drivers get yours from the browser.
• Lap time — what this driver typically runs.
• Max in a row — how many stints they will drive back to back before handing over. Not a total for the race. Blank means no limit.
• Account — see below.
• ↑ ↓ — reorder. Cosmetic: availability and assignments are keyed by name, so moving a row can’t detach anyone from anything.

Reuse a roster pulls the drivers in from one of your other races, or from a room code. Names, colors, time zones, lap times and stint limits come across. Account links don’t: a claim means “this row is me, in this race”. Use a team is covered under Teams.

Availability

Press Add when you can drive on the banner above the roster to mark your own hours (also in the … menu, My availability). It shows once per room until you save.

The full grid is right under the roster. Click a cell to toggle a driver for that hour; Shift+click another cell to fill the range, or use All day on a day’s row. Each driver’s column is in their own local time, night is shaded, and the Stints column shows which stints fall in each hour. A stint counts as covered only if the driver is free for every hour it touches.

Auto-assign drivers (Plan › Stints) fills the schedule from availability and each driver’s max in a row, spreading stints evenly.

Invites — linking an account

+ Add driver, type the name, then Copy invite link in the Account column and send it. The driver shows as Invited and is ready for planning at once. The link opens a page to sign in with Discord and accept; the row is then Linked, and everything planned for it stays. Each link works once and expires after 30 days; Revoke invite stops it. One row per account.

Once linked, whatever that driver has measured for this car and track appears in Measured driver numbers under the roster. A paired companion sets the account’s in-game name, shown under the account name.

Each linked driver is shown against the team rates: lap, fuel, energy and wear, each as a difference. Press Use and that driver’s stints are timed, fueled and worn on their own numbers; everyone else is unchanged. Nothing is applied until somebody chooses it, and the choice is shared with the room.

Fuel-saving and wet stints always stay on the team rates. Those are defined by how a stint is driven, not by who is driving it.

A room is one race. A team is the people, and it outlives any one race, so teams live on their own page at stintlab.io/teams rather than inside a race. A team needs an account, because a team is a list of people.

The page has four sections: Members, Compare, Races and Settings.

Getting one going

Open Teams → New team. You get an invite code and an invite link, under Settings. There’s no adding people by name: they join with the code or the link. Two ways in:

• They join straight away — anyone with the code is in immediately.
• I approve each person — the code files a request and you let people in. Same code, different setting.

The code is owner-only, and Replace the invite code replaces it immediately for anyone still holding the old one. Only the owner sees who is waiting to join, and only the owner can remove people or hand the team over.

Compare

Pick a car and a track and every member’s measured numbers for it sit side by side. The track list follows the car, so you can only choose a pair somebody has actually run. Lap, fuel per lap, energy per lap and wear per lap, with the quickest and the lightest marked in each column, and how many laps each figure rests on. A number from four laps isn’t the same claim as one from thirty.

Joining a team means your numbers for a car and track are visible to its members. That’s the whole feature.

Nothing about a team touches a plan on its own. The only place the two meet is Use a team below: a race uses a team, a team knows nothing about any race.

Races

Every room this team has been pulled into, newest first, with how far through each one got. It’s the answer to “where is the plan we made for Spa” without a pinned message full of room codes.

Using a team in a race

Drivers → Add from team. Add members one at a time, or use the whole team as the roster. Every row arrives already linked to its account, with no invite, so each driver’s own numbers are offered for their stints straight away.

That’s safe here and not in From another race: joining the team was each member’s OK, granted by an owner or a code on the server.

Rosters also link themselves: the room owner and any driver with a signed-in companion are linked automatically, and you get a warning when a driver’s companion is not signed in.

What the team has on file travels in with them, so the offers exist even when none of them are online. Pick the car and track this race is running and their numbers appear, marked team. Anything published live by that driver’s own browser overrides it, since that one is first-hand and current.

With the companion running, the Race tab shows fuel and VE remaining, estimated laps left, tire life, position and the field around you. It also closes each stint into the plan as it happens, so the schedule ahead re-times off what really happened.

The Race tab has one bar of section tabs: Dashboard (the default, see below), Schedule, Tires, Damage, Pace, Weather, Rivals and Telemetry. Each one shows on its own, full width, so you can watch only the live stint plan, only the weather or only the tires. Telemetry also holds the call in detail: the call word, fuel and VE, undercut and overcut, “How the call was made” and the raw numbers. The tab you pick is remembered on this device, and a link can open one directly (add ?tab=weather). On the right of the bar are the connection pill, Engineer, Pop out (this tab full screen in a new tab, for a second monitor), TV, Fullscreen, Debrief and New race.

Before the race: get connected

The status pill at the top (“Ready · 0s ago”) opens a checklist: companion connected (with its version), LMU in a session, in the car (or spectating), and sending to this room. Until data arrives it stays open on the page and says what to fix for each row that isn’t ticked. Click the pill to hide it.

Measured from the car

Once the car has done 3 clean laps on a stint type (no pit or out laps), the measured fuel, VE and tire wear are used for race calculations by themselves. A line says so: “Race calculations are using the car’s measured rates (3.43 L/lap, 6.91% VE). Your plan says 3.42 L/lap, 6.90% VE.” Switch to plan rates goes back to Plan › Rates, and Switch to measured rates returns. The choice is shared by everyone in the room and changes the race calls only; your Rates stay as they are.

To change the rates themselves, two buttons, and they do different things:

• Set as the team default — writes what the car is doing into the team rates. The right move when the plan’s assumption is wrong for everybody: a setup change, rain, a BoP tweak. It confirms first, because it re-times everyone’s stints.
• Use for my stints — saves the same numbers to your account and applies them to the stints you’re down to drive, leaving everyone else alone. Only appears once your roster row is linked.

Strategy calls

Box, stay out or undercut, worked out from your fuel and VE against the cars around you. How the call was made shows the reasoning.

The engineer

🎧 Engineer is a spoken race engineer. Its button is in the planner’s top bar, and on the Race tab’s bar next to the connection pill. It speaks on every tab while a race is live, so you can work on Plan or Drivers and still hear it. It’s off until you tick Speak race calls (or press M). The same panel sets the voice and volume, and Test voice checks you can hear it.

What the engineer says has a switch per message type:

• Pit calls — pit window open, undercut on, save to finish.
• Next stop — filling to full, a small fuel save for one more lap, brake duct clicks. Said about 5 laps before the stop; the fuel call again when the pit window opens.
• Tire calls — slicks or wets at the next stop, and box this lap when a tire gamble goes wrong.
• Damage — what the damage costs a lap, whether to fix it now, at your stop or not at all, and top speed down.
• Stint brief — while you sit in the box: the stint ahead, the box lap, a save if one is needed, the tires when conditions matter and damage left unfixed. Trimmed to fit the stop; it stops when you drive off. Not in Quiet.
• Pace — now and then, what the tires are costing you a lap (Normal and Chatty).
• Encouragement — good stint on the way in, no worries after a lap that went wrong (Normal and Chatty).
• Strategy updates — the engineer briefs you like a real race engineer: a stint check-in (laps to the stop, fuel or VE on target, pace against the plan), plan changes, the stop ahead at 5 and 2 laps (tires, fuel, who takes over), the fuel-save target, tires near their limit or out of their window, the race situation, and your stop time on the out-lap. How much it talks sets how often: Quiet checks in every 10 laps, Normal every 5 and Chatty every 3; Normal and Chatty add the race situation about every 10 laps. Nothing is said before the green flag, in practice or qualifying, or after the white flag. Driver names are read by the browser’s voice.
• Fuel & energy — five and three laps of fuel or VE left, short start fuel.
• Tires & weather — wrong tires for the track, rain coming, track drying.
• Position & gaps — position changes, gaps, cars next to you pitting.
• Clock & last lap — a race brief on the grid, 30, 10 and 5 minutes left, white flag.
• Pit wall messages — what the pit wall sends with Message driver on the dashboard, read out on every screen with the engineer on.
• Personal bests — a new best lap.
• Lap delta — every lap against your best or the save target. Off by default, since a call every lap is a lot of radio.

All on and Essentials only (pit calls, next stop, tire calls, damage, strategy updates, and fuel & energy) set them in one go. Box this lap calls speak whatever is switched off, once the green flag is out (nothing about pitting is said on the grid), and each box call says which tires go on. The settings are saved on that device.

How much it talks: Quiet — key calls only; Normal — adds pace, the stint brief and encouragement; Chatty — everything, more often. Use this PC to voice pit wall messages makes the message voice on this PC; turn it off on the driver’s PC if the game stutters.

The engineer talks like one: a few ways of saying each call, your name now and then, gaps and losses in round numbers (“about a second and a half”). It is brief when you are within a second of another car and never starts a line under braking. Chatty is the default, built for driving solo; pick Normal or Quiet for less.

Weather, damage, rivals and warnings

• Weather tab — the game’s forecast up to two hours ahead, counted in laps. Across the top: air, track, wetness (how wet the racing line is, 0–100%) and rain now. Wetness carries LMU’s condition name: Dry, Damp, Slightly Wet, Wet, Very Wet or Extremely Wet. Slightly Wet or worse (over 7.5%) calls for wets; Dry and Damp run on slicks. Then the call in plain words, such as Box for wets in 3 laps, Fit wets at your planned stop, Stay on slicks or Dry ahead, with a short outlook. The chart shows wetness with its Likely range, the Too wet for slicks (7.5%) line, rain chance, your planned stops and, when a tire change pays, the Switch window. Hover or tap it to read any lap. A table below gives the tires for each stint ahead. Try a forecast previews the rain earlier, later, lighter or heavier without changing anything; Use this for the plan applies it. When the track turns wet, the stints ahead switch to WET by themselves.
• Damage tab — the car from above with what is hurt, how hard the last hit was (Light, Medium or Heavy), the call (Fix body only at your stop, Not worth fixing…) and what it costs, e.g. 0.8 s/lap slower. Details list the repair options, Body only and Body + suspension.
• Rivals tab — the Pit exit card shows where you would come out if you boxed now, and the Pit feed lists rivals as they pit and the tires they came out on.
• Warnings — a banner if you are on the wrong tires for the track (slicks in the wet, wets on a dry line), and before the start if there is not enough fuel or VE on board for stint one.

Two screens without two screens

• Split view puts any tab beside any other. Wide screens only.
• Pop out opens the race in its own tab for a second monitor.
• On a phone the Race tab becomes a stripped-back card view: who is on track, when they box, and the stints after that. Built for checking the plan away from the PC, not for running a race from.

Dashboard

The Race tab opens on the Dashboard tab, a grid of live panels that always fits the screen. Pick a preset for who is watching:

• Driver — big and simple: handover, gear, speed, the call, lap delta, laps of fuel and VE, position, next stop and time left.
• Engineer — track map, timing, handover, stint vs plan, fuel and VE, tires, alerts, weather and Message driver.
• Strategist — track map, timing, handover, a larger stint vs plan, fuel and VE, alerts and Message driver.
• Spectator — position, last lap, delta, time left, track map, timing and weather.

Edit layout shows, hides, moves and resizes panels; the layout is kept per preset on that device, and Reset this layout puts it back. TV hides the page chrome and Fullscreen fills the screen. Pop out opens it in a new tab for a second monitor.

The Track map places every car on the circuit (Expand for full screen). Monza, Spa, Bahrain, COTA, Interlagos and Silverstone are drawn straight away; other tracks are learned from a lap of your own driving.

Track outlines: TUMFTM racetrack-database (LGPL-3.0), based on OpenStreetMap data. Road Atlanta, Le Mans, Fuji, Sebring, Portimão, Imola, Lusail, Paul Ricard, Daytona, Long Beach and Laguna Seca: © OpenStreetMap contributors (ODbL).

Message driver sends a short call from the pit wall (Push, Box this lap, Fuel save, or your own text). On the Driver preset it shows until the driver acknowledges it, and the sender sees the tick. The Handover card shows who drives next and when, with a note the current driver can leave for them (Note).

Debrief

Race tab → Debrief (opens in a new tab) compares the plan with what happened, stint by stint: laps, start and end, length, average lap, fuel and VE per lap and stop time, each against the plan. A short What to look at list says where the biggest differences were, and a Drivers table sums each driver’s stints. It works during the race too (“So far”).

Share makes a summary image and copies it, ready to paste into Discord (or downloads it if your browser can’t copy images).

The room

The code in the top bar is the whole thing. Copy link (just Copy on a phone) gives a link that opens straight into the plan, with no account needed for anyone. Click the room name to rename it for everybody.

Signed in, rooms you create are saved to your account. Forget removes one from your list and leaves it running for everyone else; Delete this room destroys it, for everybody, and only the owner can.

Discord

In the planner, open the … menu at the top right › Discord. Paste a channel webhook (Edit Channel → Integrations → Webhooks → New Webhook → Copy Webhook URL), press Send a test message to check it, and the room posts a card every time a stint closes: laps, stint time, average and best lap, position and what it did to it, consistency, how far off the plan the stop was, who is out now and when they box.

The next-stop line gives the time in UTC, again in your local time, and as a live countdown, so one message reads correctly for everyone whatever zone they’re in.

Tick Post race alerts to Discord and it also posts wrong tires, fuel or VE critical, rain within 15 minutes and short start fuel, while the Race tab is open and the companion is sending.

Press Sign in in the companion. Your browser opens, you confirm, and the companion is linked to your account. There are no codes to copy.

• Companions that were already paired sign in automatically.
• If you are signed in on the companion’s Planner tab, it links automatically.
• Sign out in the companion unlinks it from your account on that PC.

Tip: a linked companion is how StintLab recognizes you as the driver (see Driver swaps).

A signed-in companion chooses a room by itself, in this order:

1. The room you chose with Use for my companion.
2. Otherwise, a room you are a member of that matches the track, car and time.
3. Otherwise, it creates a room for your race.

To change it, use the companion’s Room card. Room codes still work if you prefer them.

Tip: if the wrong room keeps being picked, set the right one with Use for my companion.

Who can see a room

The owner, drivers on the roster who are linked to an account, the room’s team, and anyone added to it.

Adding people

• Invite link — opening it joins the room in one click. Signing in is required.
• Add from StintLab — pick a person and they are added instantly. They get a notification with Open and Leave.
• Add a whole team — adds every member of the team at once.
• Spectator link — read-only, for people without an account.

Existing rooms

Rooms made before this change stay open to anyone with the code for 14 days, then become members-only. Owners can switch earlier.

Tip: send the spectator link, not the invite link, to anyone who only needs to watch.

You don’t need the planner open for the plan to keep up. With no one planning, the server updates the plan lap by lap: measured rates, wet and fuel-saving rows, tire wear, the forecast and the strategy. Open the planner and it carries on from the same plan.

• When several tabs are open, one of them plans. The planner’s top line says when another tab does.
• Room owners press Take over planning to plan from the tab they are in, and Release to hand it back.
• Reset clears every manual setting.

Tip: you can close the planner during a stint. The pit menu and the plan keep going.

Start a race in a new room and it sets itself up from the game: track, car, race length, start, tank, and rates, then a recommended strategy. Rates come from your Saved data, the community, or your first laps. It works with no browser open, and it follows you to a new room when you change car or track.

• A Set up automatically — Review banner shows what was filled in. Check it and fix anything that looks off.
• The companion offers Start a room for this race when it sees a race without a room.

Tip: drive a few clean laps in practice first so the rates come from you rather than the community.

The log lists each change to the plan, newest first: what changed and when. Use it to answer “why did the stop move?” before asking the team.

Tip: read it from the top. The latest entry is the reason the plan looks the way it does now.

• Drivers are recognized automatically, by a paired companion or by their in-game name.
• The roster fills itself as drivers appear.
• When the order changes, the remaining stints are re-assigned fairly.
• The next driver gets a heads-up about 25 minutes before their stint.

Tip: make sure each driver’s in-game name matches their roster name, or have them sign in on the companion.

StintLab Ratings give each driver a Skill, Safety and Pace rating per class. LMU’s own driver and safety ranks (DR/SR) are a separate tab, LMU Ratings, on Leaderboards.

• Field strength is taken into account, and pace is measured relative to the car.
• Every rating carries an internal uncertainty that sets how fast it moves: new ratings move quickly and settle as you race. Provisional means there are too few races yet.
• Ratings decay if you stop racing.
• Ratings were recalculated at launch, so early numbers may differ from what you saw before.
• Why my rating changed explains the last movement.

Public profile and team rating

Every driver’s rating profile is public (class ratings, trend and records; never the race list). A team rating is combined from its members’ ratings, weighted by confidence. The team leaderboard is opt-in too.

Tip: ratings move more in your first few races, then settle.

• Roles — owner, manager, driver, reserve.
• Team rooms — rooms tied to the team, visible to its members.
• Availability requests — ask members to mark when they can drive.
• Shared team data — opt-in, rates only.
• Team Discord webhook — team updates go to your channel.
• Team stats — on the team page. See also Teams.

Tip: set the roles first; they decide who can manage the team.

• Next up shows your upcoming races.
• The LMU races overlay shows the game’s schedule. Press Remind me on a race to get a reminder.
• Download month (.ics) exports the month to your own calendar app.
• The schedule runs weeks ahead. Projected daily races show the track as TBA.
• Weekly races and special events are marked apart.

Tip: a TBA track is a projection, so check back before you commit.

Notifications pop up as cards with a button for the next step: Open or Leave for a room you were added to, Go for a race, Get it for an update.

Tip: press the button on the card instead of hunting for the page later.

Other things

“Lap count is 0 — check fuel/VE per lap”

Fuel per lap or VE per lap is zero or missing, so no laps fit in a tank. Fill in the Standard row on Plan › Rates.

Tire counters show —

There’s a plan but nobody has told the room how many dry tires you have. Fill in the allocation on Plan › Event, or press Fill minimum on Plan › Tires. A dash is the app declining to guess.

The times are all wrong by several hours

They are UTC, not local. Switch the top bar to Local to see them in your own time.

Energy shows nothing

Virtual energy is the least reliable input the app has. Lap times and fuel will still plan the race — the stint length then comes off fuel alone.

A teammate’s edits aren’t showing

Check you’re both in the same room code. Two people who each pressed “Create a new room” are in two different races.

The plan re-timed itself mid-race

That’s the point — a stop happened earlier or later than planned and everything after it moved. Stints already run are locked and won’t change.

The Race tab says the companion isn’t connected

Open the status pill’s checklist. It names the missing step: companion open, LMU in a session, in the car, right room code.