# Le Mans Ultimate Setups

> Upload your .svm, remix it with your Race Engineer, and download a ready-to-load setup file. The full round trip, step by step.

Le Mans Ultimate setups are **fully round-trippable**: what you upload is a real `.svm` file, and what you download after a remix is a valid `.svm` the game loads directly. No manual steps in between.

> Setups is in **Public Beta** and requires a personal **Plus or Ultra** plan. A Team seat alone does not grant access.

## 1. Export Your Setup from LMU

Save your current setup from the LMU garage. Setup files live in your Le Mans Ultimate installation under the vehicle's setups folder as `.svm` files.

## 2. Upload It to Your Vault

In [Setups](https://app.brakinglab.com/ai-setups), click **New setup** and drop the `.svm`. Braking Lab parses it into a full parameter tree — car, track, and every garage setting — and stores it as **version 1**, the baseline. Every upload in the app creates a new setup.

The file can be up to 1 MB and contain up to 512 parameters. You can upload up
to 120 setups per hour, with at most 10 in a quick burst.

You can also choose its intended session type and personal tags while uploading.
They organize the setup and all its versions without changing the file — see
[Types and personal tags](/en/docs/ai-setups/types-and-tags).

## 3. Remix It

With your AI client connected (see [Remixing setups](/en/docs/ai-setups/remix)), describe what you want:

> "Soften the rear and add a touch of rear wing — the car is nervous on entry."

Your engineer edits only adjustable values, explains each change, and saves the result as a **new version** — with a parameter-by-parameter diff against its parent. A remix changes at most 8 parameters; one or two per hypothesis is the recommendation.

When Braking Lab has reviewed coverage for the exact LMU variant, every landed
change must pass that protected guard. If one requested option stop is not
certified, the whole remix is rejected before any version, conversation
milestone, or file is written; the parent stays current. Without reviewed
coverage, structural checks still run and the observed domain result remains
advisory: complete or incomplete, it does not certify the candidate. Keep the
hypothesis to one or two settings.

## 4. Download and Drive

Open the new version in your vault and click **Download .svm**. The file is byte-valid for LMU: place it in your setups folder, load it in the garage, and drive.

## 5. Iterate

After the stint, tell your engineer what changed on track. Each remix builds on the version you choose, so you can branch, compare, and roll back — the full history stays in your vault. Confirm a session driven with the setup and it becomes *Tested* automatically; remove that confirmation and its status returns to the evidence that remains.

## Files Through Your Engineer

Your engineer can also work with complete `.svm` files that you share with it in
your AI client. This is LMU only.

- **A new setup.** From a full `.svm`, the engineer creates a new setup with the
  file as version 1.
- **A new version of an existing setup.** If you changed the setup in the game
  and saved it again, the engineer can append that full `.svm` as the next
  version. The version is marked as **manual**, and it becomes the latest.

An appended version always builds on the latest version. If another version
lands first, the append fails with `SETUP_BASE_MOVED` and saves nothing; the
engineer re-reads the setup and tries again. One setup never mixes file
channels: an `.svm` cannot be appended to a setup that came from an iRacing
export.