What setups does Track Engineer generate?

What the output actually looks like

The most common question we get is "what exactly do I get back?". The short answer: a list of concrete setup values, grouped the same way Assetto Corsa's in-game setup menu is organized, that you enter directly. No "increase the front spring a bit" — actual numbers.

A typical Track Engineer output for a GT3 car at a medium-downforce track looks roughly like this:

Illustrative example — actual values depend on your telemetry, the car, the track and the AI model you connect.

Alongside the values, the tool returns a short analysis of your driving — where you're losing time, whether the issue is grip, balance or technique — so you understand why each change is recommended, not just what to change.

The setup parameters it covers

Track Engineer covers the full set of parameters exposed in Assetto Corsa's setup menu. Here's what each group does and what the tool tunes.

Suspension

Springs (front and rear), anti-roll bars, bump and rebound dampers, ride height. This is where most of the car's balance lives. Softer front springs = more front grip but slower response; stiffer rear = more rotation but more oversteer on power. The tool reads your telemetry to decide whether your problem is balance, grip or bottoming, and adjusts accordingly.

Aerodynamics

Front and rear wing levels (where the car has them). Higher wing = more grip in corners, less top speed. The tool balances front and rear aero so the car doesn't understeer at high speed or oversteer in fast corners. For tracks with long straights it leans toward lower drag; for twisty tracks it prioritises downforce.

Alignment

Camber (front and rear) and toe. Camber is the most alignment-sensitive parameter for grip — too little and the tyre doesn't work in corners, too much and you overheat the inner edge. The tool reads your tyre temperatures across the three zones (inner, middle, outer) to set camber so the contact patch stays even under load.

Brakes

Brake bias (front/rear distribution) and max brake pressure. Bias is the single most common cause of braking complaints — too far forward locks the fronts, too far back makes the rear unstable under braking. The tool reads your wheel lock-up events from telemetry and shifts bias to where it needs to be.

Tyres

Cold pressures per corner. The right pressure is what gets your hot pressure into the ideal window after a few laps — and that window depends on the compound, the track and your driving. The tool uses your actual hot pressures from telemetry to back-calculate the cold pressure that lands you in the window. See our tyre pressures guide for the full logic.

Gearing

Final drive and individual gear ratios where the car allows it. The tool adjusts gearing so you hit the rev limiter near the end of the longest straight, not before — and so you don't have a gap between gears that hurts acceleration out of slow corners.

Output format and how to read it

The output is plain text, grouped by parameter group, with concrete values and a short reasoning block per change. The reasoning is what separates a useful setup tool from a random number generator — you can see why each value was chosen and judge whether it makes sense for your case.

A typical reasoning block looks like:

This format means you're never applying a setup blind. If the reasoning doesn't match what you felt on track, that's the signal to give feedback and regenerate — not to override the value manually.

How to apply it in Assetto Corsa

The output is grouped the same way the in-game setup screen is organized, so applying it is a straight pass through each tab.

1. Open the setup screen in AC (or Content Manager's setup tab) for the car and track.
2. Go to Suspension — enter springs, ARB, dampers and ride height values.
3. Go to Aero — set front and rear wing levels.
4. Go to Alignment — set camber and toe per axle.
5. Go to Brakes — set bias and max pressure.
6. Go to Tyres — set cold pressures per corner.
7. Go to Gearing — adjust final drive and individual gears if the car allows.
8. Save the setup with a descriptive name (e.g. nurburgring-gt3-te-v1) and take it to track.

The whole process takes about 3 minutes. Most of the time isn't in entering values — it's in the 2-3 test laps you run afterwards to feel whether the changes landed.

Refining with feedback

The first generation is a starting point built from your telemetry. From there, you test on track and tell the tool what you felt — in plain language, the way you'd describe it to a human engineer.

Useful feedback looks like:

• "Still understeers mid-corner at the hairpin — turn-in is fine."
• "Rear snaps oversteer on the kerbs at the chicane exit."
• "Braking is stable but I'm locking the front-left into the heavy braking zone."
• "Top speed is 4 km/h down on the straight — too much wing."

The tool combines that feedback with your telemetry and regenerates only the affected parameters. Most setups are race-ready after 2-3 iterations. The point isn't to replace your judgment — it's to skip the 30 laps of blind tweaking you'd otherwise spend finding the direction to move.

You can also export a fresh telemetry file after each test session and feed it back in, so the tool works from updated data instead of just your verbal feedback.

Why this beats a generic setup

A setup from a forum or Discord was built by one driver for their exact reference points — when they brake, how they turn in, where they apply throttle. If your reference points differ, and they almost always do, that setup will feel wrong or slower than the default.

Track Engineer reads your telemetry — how you use the brake, how you feed throttle, where you lose time — and adapts the car to that. The difference is the difference between an off-the-rack suit and a tailored one. Both are jackets; only one fits.

That's also why the output includes reasoning, not just values. A generic setup gives you nothing to validate against. A Track Engineer setup tells you exactly what it changed and why — so you can confirm it matches what you felt, or correct it with feedback if it doesn't.

Frequently asked questions