Compare laps like in MoTeC
Speed, throttle and brake on a common distance axis, up to four laps, zoomed on any corner. Ask for it in plain words; Camber draws it from the samples in your file.
Lap 2 · 1:21.384 Lap 3 · 1:22.296 Example data
Assetto Corsa EVO · Le Mans Ultimate · iRacing · Windows 10 and 11
Your AI race engineer. Measured, not guessed.
After every session, Camber opens the telemetry your sim saves on your PC (Assetto Corsa EVO, Le Mans Ultimate or iRacing), finds where you lose time and the likely reason, and works out setup changes with you, one change at a time.
- AC EVO, LMU and iRacing telemetry
- Your own AI key
- Files stay on your PC
Camber
F2004 / Monza
Saved Games › ACE › MoTec › F2004 › Monza
Watching the MoTec folder · 1 new session
Today
- 21:42 just now1:21.384 New
- 20:58 44 min ago1:21.912
Yesterday
- 22:531:22.470
- 21:102:21.904
Run 2 · 14 laps · 31.4 L at start
Best1:21.384
Ideal1:21.051
Clean median1:21.702
| Lap | Time | Δ | Gap | Fuel | Err |
|---|---|---|---|---|---|
| 1 | 1:22.104 | +0.720 | 2.9 | – | |
| 2 | 1:21.384 | best | 2.9 | – | |
| 3 | 1:22.296 | +0.912 | 2.8 | 0.4 | |
| 4 | 1:21.596 | +0.212 | 2.9 | – | |
| 5 | 1:21.702 | +0.318 | 2.8 | – | |
| 6 | 1:21.655 | +0.271 | 2.9 | – |
Lap 3 · Ascari · 0.4 s lost · late braking, front-left lock-up
The front left keeps locking into the chicanes and lap 3 was a mess. Is it the car?
Engineer
A bit of both, and they are separate problems.
Driving · lap 3
At Ascari you braked 18 m later than on your clean laps and locked the front left: 138 km/h at the apex instead of 178, 0.4 s lost. That one is on you. measured
Lap 2 Lap 3 Built from S1 · laps 2, 3 · 3650–4400 m
Setup · clean laps
Even on clean laps the front left locks briefly in 3 of 5 braking zones and runs 94 °C inside, 81 °C outside. measured Likely too much negative camber: less tyre on the road under braking. hypothesis
Test it: front camber −3.0° → −2.7°, one run, same fuel, nothing else changed. Want me to prepare the file?
Setup change · waiting for you
Create Monza_FCAMBER from Monza_BASE
| Parameter | Before | After |
|---|---|---|
| Camber FL | −3.0° | −2.7° |
| Camber FR | −3.0° | −2.7° |
Every other value copied from Monza_BASE unchanged. Test: one run, same fuel, nothing else changed.
ApproveReject
Applied · backup saved · Undo
- Reads Assetto Corsa EVO · Le Mans Ultimate · iRacing · more sims planned
- AI from Anthropic · OpenAI · Google Gemini · any OpenAI-compatible endpoint
01How it works
Drive. Read the numbers. Talk it through.
Camber is a desktop app that works after the session, on the files your simulator has already saved. It never touches the game while you drive.
-
Drive
The session lands on its own
Assetto Corsa EVO saves MoTeC files; Le Mans Ultimate and iRacing save their own telemetry, which Camber converts to MoTeC. Camber watches those folders and lists each new session, with its best lap, as soon as it appears.
-
Measure
Camber does the maths
Runs split at pit stops, sectors, your ideal lap, driving errors corner by corner, balance, aero platform, dampers, pace and fuel. All computed on your PC from the file, not estimated by an AI.
-
Ask
Your engineer explains
Add the session to a chat and ask. The AI engineer reads Camber's numbers, tells you what is measured and what is a hypothesis, draws charts from your data and asks when something is missing.
-
Apply
One change, your approval
In Assetto Corsa EVO the engineer can prepare the new setup file for you: nothing is written until you press Approve, and every change can be undone. In Le Mans Ultimate and iRacing it gives you the exact values to set in the garage.
02Features
Everything a track engineer looks at.
The panels below are drawn the way Camber draws them. The values are examples.
Driving errors, corner by corner
Each sector is compared with your neighbouring laps. Time lost, where, and the inputs that changed. Setups are judged on clean laps only.
- −0.4 sLap 3 · Ascari braked 18 m later, front-left lock-up
- −0.2 sLap 7 · Parabolica late throttle, 0.3 s coasting
- −0.3 sLap 9 · Roggia wheelspin on exit, TC active
- 3 lapsRecurring · Lesmo 2 same loss on 3 laps: setup or style, not a one-off
Runs, sectors, ideal lap
Sessions split into runs at refuels and fresh tyres. Best, clean median, spread and fuel per lap, and the lap you could do with your best sectors.
S126.912
S228.004
S326.135
Ideal lap1:21.051best 1:21.384 · −0.333
Damper histograms
Damper speed per wheel, bump on the left and rebound on the right, the slow zone in dark, laid out like MoTeC workbooks.
bump ← mm/s → reboundExample data
Balance by corner phase
Understeer at entry, mid-corner and exit, slow corners against fast ones: mechanical grip or aero, told apart by the data.
EntryMidExit
Slow
Medium
Fast
oversteerundersteer
Setup files, with your approval
The engineer can create, edit, rename and tidy your .carsetup files. You see before and after, then Approve or Reject. Backups and Undo included.
Monza_RARB_SOFT from Monza_BASE
Rear anti-roll bar55 500 → 48 000 N/m
Everything elseunchanged
Approved · backup saved
An engineer who remembers
What you learn about a car and a track is kept as short notes on your PC. The next chat starts from them. You can read and edit every note.
- N4F2004 · Monza Rear tyre pressures climb about 1.5 psi over the first 3 laps.
- N7F2004 · Monza Fuel costs about 0.02 s per litre per lap.
A/B tests that add up
Camber spots two runs on the same car, track and road temperature with different setups, and puts the numbers side by side. You confirm and rate; trends build up over time.
Rear anti-roll bar softer medium confidence
Run ARun BΔ
1:21.7021:21.488−0.214
Clean median · 7 and 8 clean laps · fuel-corrected
03Simulators
Three sims today. More to come.
Every session ends up as a MoTeC file, so the same analysis, charts and engineer work the same way in every sim. The converted files open in MoTeC i2 too.
MoTeC files from the game
Assetto Corsa EVO
- Reads the MoTeC files the game saves
- You pick the setup you drove for each run
- The engineer can edit your
.carsetupfiles, after your Approve
Own telemetry → MoTeC
Le Mans Ultimate
- Reads the game's own telemetry and converts it to MoTeC
- The setup you drove is read from the telemetry: nothing to assign
- Tyre wear and hybrid energy included
.ibt → MoTeC
iRacing
- Reads the
.ibtfiles and converts them to MoTeC - The setup you drove is read from the telemetry: nothing to assign
- Turn on disk telemetry in iRacing (Alt+L in the car)
More simulators are planned. Camber does not edit Le Mans Ultimate or iRacing setup files: the engineer tells you what to change.
04How the AI part works
Camber computes. The AI reasons. You decide.
The heavy lifting on your telemetry happens in the app, on your PC. The AI gets a text summary of those numbers, and does what an engineer does with them: explain, question, propose.
01
Camber, on your PC
- Reads your sim's telemetry (converted to MoTeC for LMU and iRacing) and your setups
- Computes runs, sectors, ideal lap, errors, balance, dampers, pace, fuel
- Draws every chart from the samples in your file
- Writes an AC EVO setup file only after your Approve
02
The AI, at your provider
- Reads Camber's summary, never the files themselves
- Explains what the numbers mean for you and the car
- Keeps measured facts apart from hypotheses, and asks when data is missing
- Proposes one change at a time, and a way to test it
03
You
- Choose the AI provider and the model
- Choose which sessions go into each chat
- Approve or reject every setup change
- Confirm and rate each A/B test
Your PC
Your sim
MoTeC files
Camber
Files, setups, chats, notebook and your key stay here.
your question + text summary, signed with your key
answer, charts to draw, proposed changes
Your AI provider
Anthropic · OpenAI · Google Gemini · OpenAI-compatible
Bills your account for the tokens used, under your terms with them.
Camber's author
No account, no server between you and the AI. Only an anonymous daily count of answers per model, which you can turn off in Settings.
Bring your own key
An API key is a password that lets an app use an AI provider on your account. You create one on the provider's site, paste it in Camber's Settings, and it stays on your PC.
A chat subscription such as Claude Pro or ChatGPT Plus is not an API key: API use is billed separately by the provider.
Tokens, in plain words
Providers bill by the token, a piece of text of three or four characters. You pay for what goes in (your question, the summaries, the conversation so far) and for what comes out (the answer).
A session summary is 16–37 KB of text in the sessions tested so far, roughly 5,000–12,000 tokens. Camber shows the exact count under every answer; your spend is on your provider's dashboard.
Pick the model
Camber lists the models your account can use and suggests three: recommended (balanced, the default), most capable and fastest. Bigger models reason deeper and cost more per token; you can switch per chat.
What one message sends
Proportions are illustrative. The exact count is shown under every answer.
First message
Engineer instructions
Notebook · garage
Session summary
You
Answer
Next message
Conversation so far · read from cache where the provider supports it
You
Answer
Under every message, View data sent shows exactly what went to the provider.
05Your data
Who sees what. All of it.
Your telemetry, setups and chats go to one place: the AI provider you set up. Camber itself only gets an anonymous daily usage count, which you can turn off. Here is everything it handles, and where each piece goes.
| What | On your PC | Sent to your AI provider | Sent to Camber |
|---|---|---|---|
Telemetry files (MoTeC, LMU, .ibt) |
Always | Never the files. A text summary (laps, runs, sectors, corners, tyres, brakes, errors) of the sessions you add to a chat | Nothing |
| Charts | Drawn from your file | The AI only names the channels, laps and range to show | Nothing |
| Setups | Never uploaded | Values as text: the setup of each run (AC EVO: the one you assign; LMU and iRacing: the one recorded in the telemetry) and the main values of your saved AC EVO setups | Nothing |
| Your garage | Yes | At the start of each chat: which cars, tracks, sessions and setups you have, so the engineer knows them | Nothing |
| Engineer's notebook | Yes | At the start of each chat, then only what changed | Nothing |
| A/B test log | Yes | Confirmed tests: for all cars and tracks, only for those in the chat, or none. Your choice in Settings | Nothing |
| Chats | Last 10 saved | Your messages and the conversation so far | Nothing |
| Your API key | In the app's data folder | Only to that provider, to sign the request | Nothing |
| Usage count | Counted in the app's data folder | Nothing | Once a day, unless you turn it off in Settings: answers, errors and tokens per AI model, simulators used, times opened, app version and a random ID that changes every month. No IP address stored |
Who uses what you send? Your provider processes it under your agreement with them, including how long they keep it and whether it may be used to improve their models. Check their terms; some free tiers allow it.
This website sets no cookies and runs no analytics. A click on Download records the time, the version, the file and the country, nothing that identifies you. Privacy
06FAQ
Before you install.
Ten answers, from what Camber reads to the warning Windows shows when you install it.
Does it read live telemetry while I drive?
No. Camber works after the session, on the files your simulator saves. It never touches the game while it runs.
Do I need to pay for the AI?
You need an API key from Anthropic, OpenAI, Google or an OpenAI-compatible service, and the provider bills API use to your account. A chat subscription such as Claude Pro or ChatGPT Plus does not include API use.
How much does a chat cost?
It depends on the provider, the model and how much you send. A session summary is roughly 5,000–12,000 tokens, and every message re-sends the conversation so far, partly from cache where the provider supports it. Camber shows the tokens of each answer; the money is on your provider's dashboard. Faster models usually cost less per token.
Can I see exactly what was sent to the AI?
Yes. Under every message, View data sent shows the summaries, setups, notebook and garage that went with it.
Does Camber train an AI on my data?
No. Camber never receives your chats, telemetry or setups: only an anonymous daily count of AI answers per model, which you can turn off in Settings. What you send to your provider follows their terms: check whether your plan allows them to use it.
Will it change my setups on its own?
No. Camber edits setup files only in Assetto Corsa EVO, and each change waits for your Approve, with before and after shown. In Le Mans Ultimate and iRacing it never touches your setups: the engineer tells you the values to set. You can turn on automatic approval in Settings; it is off by default. Every applied change keeps a backup and can be undone.
Which simulators, cars and tracks?
Assetto Corsa EVO, Le Mans Ultimate and iRacing, with any car and track they record; more simulators are planned. When it edits an AC EVO setup file, Camber changes only the fields it has verified and leaves the rest of the file byte for byte.
Does it work without internet?
Sessions, runs, laps, the notebook and the test log work offline. The chat needs a connection to reach your AI provider.
Windows says “Windows protected your PC”.
The installer is not code-signed yet, so SmartScreen warns about it. Choose More info, then Run anyway. The installer runs for your user only and needs no administrator rights.
What do I need?
Windows 10 or 11 (64-bit), at least one of Assetto Corsa EVO, Le Mans Ultimate or iRacing (with disk telemetry on), and an API key from one of the supported AI providers.
Assetto Corsa EVO · Le Mans Ultimate · iRacing
One change at a time.
Your telemetry, your key, your call.
Download for Windows