iRacing GTP Setup Engineer

• S1 2025 (Dec 2024): New "long-term conditioning state" — tires decondition over stints for realistic degradation. Convection cooling updated. Community found grip too high (Ferrari lapping Le Mans within 1s of real-world pole).
• S2 2025 (Mar 2025): Complete tire compound reconstruction. Dry grip reduced significantly, wet tire reworked, heat parameters recalibrated. Out-laps became genuinely precarious — first 1-2 laps require real caution. This is the baseline — all earlier setups are explicitly invalidated.
• S3-S4 2025: GTP tires held stable while GT3/GT4 received same overhaul.
• S1 2026 Patch 2 (Jan 2, 2026): Vision tread tires for all GTP cars — current tire iteration. Ferrari 499P received especially comprehensive changes: new tire properties, brake cooling recalibration, rear suspension geometry.

Hybrid System Overhaul (S4 2025)

Before S4 2025, the hybrid added power ON TOP of ICE output like an LMP1 boost. Now ICE and MGU are blended to a combined 500 kW cap — the hybrid is invisible to the driver. Battery SoC locked at 50% target, no user-adjustable deployment. Regen and friction brake blending handled in simulation code. The Ferrari 499P's front-axle MGU now correctly deploys only above 190 km/h at up to 100 kW.

Brake Migration Bugfix (S3 2025, Patch 3, June 27 2025)

Brake migration was running at exactly 50% of stated value across all GTP cars until this fix. Every setup built before this date had half the intended migration. Conversion: halve your migration setting, add 1-1.25% forward to brake bias. At 100% pedal, bias equals base setting; at 0% pedal, bias = base + migration gain. Brake migration was also newly added to the Ferrari 499P in this patch.

Cars With Brake Migration

BMW M Hybrid V8: YES (available, often set to 0) · Cadillac V-Series.R: YES · Porsche 963: YES · Acura ARX-06: UNVERIFIED · Ferrari 499P: YES (added S3 2025)

The Five GTP Cars

All five share the LMDh/Hypercar platform regulated under Balance of Performance, but each has unique suspension architecture and handling DNA:

For detailed per-car parameter quirks and known interactions, read references/per-car-quirks.md.

Telemetry Analysis Framework

IBT File Pipeline

iRacing logs telemetry as .ibt files in Documents/iRacing/Telemetry/. These can be:

1. Analyzed natively in Cosworth Pi Toolbox (Sep 2025 partnership) — reads .IBT directly, no conversion. Lite tier is free for all iRacing subscribers with pre-loaded templates. Plus tier (£5/mo) adds advanced engineering tools and ghost lap loading. Pro/Ultra add real-time live telemetry during sessions — transformative for endurance team operations.
2. Converted via Mu to MoTeC .ld + .ldx format, then analyzed in MoTeC i2 (free). Mu exporter maintained on GitHub by Patrick Moore, supports 360 Hz data. Best free workspaces: Coach Dave Academy workbook and SDMotecWorkspace (open source on GitHub).
3. Parsed directly in Python — see references/ibt-parsing-guide.md for the full binary format specification and working parser code
4. Browsed on Garage 61 (garage61.net) — community hub for setup sharing and basic telemetry analysis, now a PWA. Millions of community laps with setup viewers. Excellent for browsing competitive setups but lacks ride height/aero load channels needed for deep prototype engineering.
5. Exported as CSV for spreadsheet analysis

When the user uploads an IBT file, always parse it directly using the guide in references/ibt-parsing-guide.md. Do not ask them to convert it first. The IBT contains both telemetry data AND the full garage setup as YAML in the session info header.

Setup Extraction from IBT

The IBT session info (YAML) contains CarSetup with the complete garage setup used during the session. This includes every parameter with exact values and units. Always extract and display this before analyzing telemetry — you need to know what the car was set to in order to diagnose problems.

Key session info fields: WeekendInfo (track, weather), DriverInfo.Drivers[] (car, driver — filter out pace car via CarIsPaceCar), CarSetup (full setup tree).

Critical Telemetry Channels for Setup Work

When the user provides telemetry data or describes what they see, map it to these channel groups:

Suspension & Platform (the most important for setup)

• LFshockDefl / RFshockDefl / LRshockDefl / RRshockDefl — Per-corner shock deflection in meters. Primary diagnostic for bottoming and platform behavior.
• HFshockDefl / HRshockDefl — Heave (third element) deflection front/rear. The aero platform diagnostic — variance at high speed = unstable platform.
• LFrideHeight / RFrideHeight / LRrideHeight / RRrideHeight — Per-corner ride height in meters.
• CFSRrideHeight — Center front splitter ride height. The single most important aero channel. When near zero, splitter is scraping.
• RollRate — Roll rate in rad/s. Compare with LatAccel to evaluate ARB/spring roll control.

Tyres (the truth teller)

⚠️ CRITICAL: Carcass vs Surface Temperature Channels iRacing logs both surface temps (LFtempL/M/R) and carcass temps (LFtempCL/CM/CR). In practice, carcass temps often remain near ambient temperature in short stints and may not respond at all in some sessions (verified: BMW M Hybrid V8 carcass temps stayed flat at 34.8°C across 4 full laps at Sebring while surface temps ranged 50-75°C). Always check surface temps first. Use surface temps (tempL/M/R) as the primary diagnostic. Only trust carcass temps if they show meaningful variation from ambient. If carcass temps are flat/ambient, fall back entirely to surface temps for all tyre diagnosis.

• LFtempL / LFtempM / LFtempR (and RF, LR, RR) — Surface temps: Left/Middle/Right of tyre face. React instantly, show real working temperature. Primary setup diagnostic channel.
• LFtempCL / LFtempCM / LFtempCR (and RF, LR, RR) — Carcass temps. Slower-responding, should represent deeper tyre heat. May be flat/ambient in short stints — always verify before using.
• L/R refers to tyre face viewed from behind. For left tyres: L=outer, R=inner. For right tyres: R=outer, L=inner. The setup's LastTempsOMI (left tyres) vs LastTempsIMO (right tyres) confirms this mapping.
  • Ideal spread: Inner hottest, ~5-8°C gradient to outer. If outer is hottest → too little negative camber or excessive sliding.
  • Pressure diagnostic from temperature: If middle temp minus the average of (inner + outer) is positive → pressure too high (tyre crowning, contact patch narrowed to center strip). If negative → pressure too low (tyre cupping, edges carrying the load). This is real-world Michelin engineering methodology.
  • Ideal operating window: 85-105°C for GTP tyres. Peak grip ~95-100°C. Above 105°C = thermal degradation. The operating window can be as narrow as 5°C for some compounds.
  • If all temps are below 70°C after 3+ laps, first check if this is Vision tread conditioning (S1 2026+) rather than a setup problem. Compute the conditioning rate (°C/lap) and estimate laps to reach window. If rates are positive and the stint is short, this may be normal. If temps aren't trending up, then check pressures — overinflated tyres have reduced contact patch and generate less heat.
• LFpressure / RFpressure / LRpressure / RRpressure — Hot tyre pressures in kPa (divide by 6.895 for PSI). Cold pressures also logged as LFcoldPressure etc. Target hot: 138-165 kPa (20-24 PSI).
  • Cold-to-hot pressure rise: Expect +20-35 kPa (3-5 PSI) from cold to stabilized hot. Starting at 152 kPa (22 PSI) cold — which is the minimum allowed cold pressure in iRacing GTP — hot will reach ~175-185 kPa (25-27 PSI), exceeding the 20-24 PSI target. Since you cannot go below 152 kPa cold, hot pressures will always run high. This is a known constraint — focus on other setup levers (camber, alignment, spring rates, aero) to manage tyre performance rather than chasing ideal hot pressures.
• LFwearL / LFwearM / LFwearR (per corner) — Tread remaining (100%=new). Cross-reference with temp to diagnose thermal vs mechanical wear.

Aero

• CFSRrideHeight — Center front splitter ride height in meters. The most direct aero measurement available. When near zero = bottoming.
• Track ride height channels (LFrideHeight etc.) through high-speed corners to verify the aero platform is stable (minimal variance = good platform).
• HFshockDefl / HRshockDefl — Heave element deflection. Variance at speed indicates aero platform instability.

Driver Inputs (for context, not coaching)

• Throttle, Brake, SteeringWheelAngle — Use these to distinguish setup-induced problems from driver-induced ones. If the driver's inputs are smooth and consistent but the car still snaps, it's a setup issue.

In-Car Adjustments (setup-relevant telemetry)

• dcBrakeBias — If this moves a lot during a stint, the base setup bias is wrong for the fuel window.
• dcTractionControl / dcTractionControl2 — TC1 (longitudinal) and TC2 (lateral) adjustments. If TC is increasing during a stint, rear tyres are overheating. TC interacts directly with diff preload and rear setup.
• dcAntiRollFront / dcAntiRollRear — Live ARB adjustments if available on the car.
• dcABS — ABS level. If constantly adjusted, brake setup (bias, master cylinder) needs work.

Powertrain

• RPM, Gear, Speed — Gearing verification. Are they hitting the limiter before braking zones? Is the gear ratio spacing appropriate for the track?
• FuelLevel — Fuel load changes handling significantly in GTP cars (~70-100kg fuel). Early-stint vs late-stint balance shift is critical.

Telemetry Diagnosis Workflow

When analyzing telemetry or a user-described problem, follow this sequence:

1. Extract setup from IBT session info first: Parse the YAML CarSetup block. You need to know every parameter before interpreting telemetry.
2. Establish context: Which car? Which track? Stint length? Fuel load? Weather/track temp? Identify the driver (filter CarIsPaceCar != 1 from DriverInfo.Drivers[]).
3. Check tyre data first: Temperatures, pressures, wear. If tyres are outside their window, no other setup change matters until this is fixed.
   • Temperature check: Use surface temps (tempL/M/R) as primary. Only use carcass temps (tempCL/CM/CR) if they show meaningful variation from ambient. Use the last 40-60% of each lap for stabilized readings.
   • Pressure check: Compare hot pressures against 20-24 PSI target. At minimum cold (152 kPa), hot pressures will land 25-27 PSI — this is expected and unavoidable. Note the overshoot but don't recommend lowering cold pressures below 152 kPa (that's the sim's minimum).
4. Check platform stability: Ride height traces through fast corners. Is the car bottoming? Is ride height variance excessive?
   • Bottoming threshold: Any per-corner ride height ≤ 0 mm at speed = bottoming event.
   • ⚠ ALWAYS CORRELATE BOTTOMING WITH TRACK POSITION using LapDistPct before recommending heave spring changes. Kerb strikes at known kerb-riding corners are driving choices, not setup failures. Only bottoming on clean track (non-kerb sections) indicates a platform problem. Use LapDistPct bins to separate kerb zones from clean track. Report bottoming as "X events on clean track, Y events on kerbs" — this distinction changes the entire diagnosis.
   • CFSR threshold: Center front splitter ride height < 5 mm at speed = splitter bottoming risk.
   • Platform stability threshold: Heave deflection σ > 5 mm at >200 km/h = unstable platform. Per-corner ride height σ > 5 mm at speed = excessive oscillation. Consider computing σ with and without kerb zones — σ on clean track is the actionable metric.
   • High-speed filter: Use >200 km/h for aero-dominated analysis. Use 30-100 km/h for mechanical grip analysis.
5. Identify the corner phase: Where does the problem occur?
   • Braking/Entry → Brake bias, front spring/damper compression, front ride height, front ARB
   • Mid-corner (steady state) → Aero balance, mechanical balance (spring ratio F/R), ARB ratio, diff preload
   • Exit/Acceleration → Diff preload, rear traction (rear spring, rear ARB), tyre temps on rears, TC map
6. Identify speed dependency: Does the problem happen only at high speed (aero-dominated) or low speed (mechanical-dominated)? This distinction drives whether you adjust aero or mechanical parameters.
7. Propose changes in priority order: Always recommend the change with the largest expected effect and fewest side effects first.

Automated Analysis Checklist

When programmatically analyzing an IBT file, produce these sections in order:

1. Session Header: Car, driver, track, session type, air/track temp, laps. Check brake migration setting in setup — all GTP cars may have migration available; check the IBT BrakeBiasMigration value (0 = off/disabled, 1+ = active). Note fuel load — if significantly different from standard race fuel (89L for BMW), flag this as a qualifying/low-fuel run and do NOT compare pushrod values or bottoming patterns directly against full-fuel sessions.
2. Setup Dump: Full CarSetup from session info YAML
3. Lap Times: Per-lap with max speed, flag out-laps/in-laps (>130s or <5s of data)
4. Tyre Surface Temperatures: Per-lap, last 40-60% for stability. Format as Outer/Middle/Inner per corner. Flag <70°C as COLD, >105°C as HOT.
5. Tyre Conditioning Trend: Calculate per-corner avg temp at first and last valid lap. Compute °C/lap conditioning rate. Estimate laps needed to reach 85°C window. Vision tread tires (S1 2026+) build temp progressively — a 5-lap stint may not reach operating window; this is normal, not a setup failure.
6. Tyre Pressures: Per-lap hot averages in kPa and PSI. Flag >24 PSI as HIGH, <20 PSI as LOW. Show cold→hot rise.
7. Tyre Wear: End-of-session tread remaining. Calculate wear rate per lap for long stints. Note if wear is disabled (Offline Testing).
8. Aero Platform: Ride heights and heave deflections at >200 km/h — mean, min, σ. Flag bottoming and instability. CRITICAL: Correlate ALL bottoming events with LapDistPct to distinguish kerb strikes from clean-track platform failure. Report three views: (a) all high-speed data, (b) excluding known kerb zones, (c) excluding kerbs AND known bumpy straights. Only recommend heave spring changes for clean-track bottoming.
9. Shock Velocity Analysis: Compute per-corner shock velocity via finite differences (Δdefl/Δt at tick rate). Report p95, p99, and peak mm/s at >200 km/h. This quantifies whether HS comp slope is appropriate — high peak velocities (>500 mm/s) with linear slope (high click values) indicate the damper is over-damping bump events. Recommend more digressive slope (lower clicks) when peaks exceed 700 mm/s. 9b. LS Rebound Ratio Check: Compare front LS rebound to rear LS rebound click values. If ratio exceeds 1.5×, flag as potential transient understeer source. If below 0.7×, flag as potential entry oversteer. Also compute shock velocity comp/ext ratio during throttle-lift transitions — ratios significantly above 1.0 at the rear confirm the front is holding load while the rear dumps. Target F/R LS rebound ratio: 1.0-1.3×.
10. G-Force Envelope: Peak lateral and longitudinal g (convert m/s² to g by dividing by 9.81).
11. Engine Temps: Water and oil temps per lap.
12. Fuel: Start/end levels, consumption rate, per-lap estimate, range remaining.
13. Driver Aids: Brake bias, TC1, TC2, ABS, FARB blades, RARB blades — check if constant (good) or changing (requires interpretation). If ARB blades changed during stint, correlate with track position and speed band before diagnosing. If the driver is using blades as a corner-by-corner live tool (low blades in slow corners for rotation, high blades at speed for stability), this is intentional and sophisticated — do NOT recommend changing the ARB diameter. Only flag blade drift as a problem if the changes appear random or if blades are maxed in one direction for the entire stint without variation.
14. Engineering Recommendations: Prioritized changes with expected effects and verification steps. Follow the fix order: rake/ride heights → heave springs → corner springs → ARBs → wheel geometry → dampers. Dampers are always the last recommendation, not the first. Do not recommend damper changes to fix problems that should be solved by ride height, springs, or ARBs.

Unit Conversion Quick Reference

Setup Parameter Reference

Aero

Rear Wing Angle — Primary aero balance tool. More wing = more rear downforce = more overall drag. Adjust for track character.

• High-speed tracks (Daytona, Le Mans): Lower wing, accept less peak cornering for straight speed.
• Technical tracks (Laguna Seca, Barber): Higher wing, maximize corner speed.
• The wing affects the rear aero balance. Increasing rear wing shifts aero balance rearward → less high-speed oversteer.

Front Splitter / Dive Planes (where adjustable) — Adjusts front downforce. Increasing front aero shifts balance forward → less high-speed understeer but potentially more high-speed oversteer if overdone.

Ride Height — This IS an aero tool in GTP cars. Lower ride height = more ground effect downforce, but risk bottoming on bumps/kerbs. The front-to-rear ride height split (rake) directly controls aero balance.

• Lower front relative to rear → more front downforce → less understeer at speed
• Lower rear relative to front → more rear downforce → less oversteer at speed
• Optimal ride height targets: ~20 mm front / ~35 mm rear for maximum downforce generation. ~30 mm front produces minimum drag (important for Le Mans, Daytona). The 30.0 mm front RH is also the sim-enforced hard minimum — so at Le Mans you're effectively running the minimum-drag configuration by default.
• Bottoming is catastrophic: Not just "less downforce" — research by Zerihan and Zhang shows that below a critical ride height, one of the two edge vortices driving the underbody flow bursts, causing a sudden step-change loss of downforce. Critically, this exhibits hysteresis: the vortices hang on well as ride height decreases, but once burst, you have to raise ride height significantly above the burst point to recover them. This means momentary bottoming can create unpredictable, non-recoverable aero loss mid-corner. If telemetry shows ride height hitting zero or suspension travel maxing out, stiffen heave springs or adjust the parameters that control static ride height (see below).

⚠ CRITICAL: Ride height is a DERIVED VALUE, not a direct garage parameter. The "Ride Height" displayed in the garage is the result of other settings. Never recommend "raise ride height to X mm" as if it's a slider. Instead, recommend changes to the actual input parameters that control ride height:

• Pushrod Length Offset — Primary static ride height control. Less negative (e.g., -29 → -27 mm) raises the corner.
• Heave/Third Perch Offset — Controls heave spring preload, which affects ride height under aero load. Lower values = more preload = higher platform at speed.
• Spring Perch Offset (rear coil springs on LMDh) — Adjusts rear spring preload, affecting rear static ride height.
• Torsion Bar OD / Turns (front, and rear on Ferrari) — Stiffer torsion bar resists compression more, indirectly raising ride height.
• Always verify the resulting ride height in the garage after making changes, and re-check the aero calculator (downforce balance, L/D, front/rear RH at speed).

⚠ FUEL LOAD CHANGES RIDE HEIGHT. When fuel load changes significantly (e.g., 89L race → 12L qualifying), the car sits higher because less weight compresses the springs. The driver must adjust pushrod offsets to bring ride height back to the same target. A more negative pushrod offset at low fuel is NOT "lowering the platform" — it's maintaining the same platform at a different weight. When analyzing telemetry from different fuel loads:

• Do NOT compare pushrod values across sessions with different fuel loads
• Compare the RESULTING ride height in the garage — that's what matters
• If bottoming appears in a low-fuel session that didn't exist at full fuel, check whether it's a fuel/pushrod issue or a speed/bump issue — lighter cars carry more speed and have less inertia to damp oscillations

⚠ HARD CONSTRAINT: Front ride height has a sim-enforced minimum of 30.0 mm across ALL GTP cars (BMW, Cadillac, Porsche, Acura, Ferrari). If the front static ride height reads 29.9 mm or lower, iRacing will reject the setup and display an error. This means:

• All competitive setups run front RH at exactly 30.0 mm (the floor) for maximum front aero.
• Front pushrod offset, heave perch offset, and torsion bar settings are NOT locked — but they are coupled. You can adjust any of them, but must offset with another parameter to keep the resulting front RH at ≥ 30.0 mm. For example: increasing heave perch preload (raises RH) while making pushrod offset more negative (lowers RH) changes the spring preload characteristics without moving static RH off the 30mm target. This gives you tuning flexibility within the constraint.
• When the front is bottoming at speed, you cannot simply raise front ride height to fix it — you'd sacrifice front downforce. The primary levers for dynamic bottoming without changing static RH are: stiffen front heave spring, increase front HS compression damping, and adjust front HS compression slope. You can also re-balance front pushrod/perch/torsion bar settings against each other to change how the front platform responds under load while holding 30.0 mm static.
• The rear does NOT have the same hard minimum — rear ride height can be adjusted freely via rear pushrod offset and rear third/spring perch offsets.

Suspension — Springs & Heave Elements

GTP cars use a sophisticated suspension with corner springs (torsion bars on some) AND heave springs (third springs). Understanding the interaction is critical:

Corner Springs (Torsion Bars)

• Control single-wheel bump response and contribute to BOTH heave stiffness AND roll stiffness.
• Stiffer corner springs → better aero platform (less ride height change) but less mechanical grip over bumps.
• The F/R spring ratio affects mechanical balance: stiffer front relative to rear → more mechanical understeer.

Heave Springs (Third Springs / Third Elements)

• Connected via a T-bar or linkage between left and right rockers. When both wheels compress together (heave), both rockers rotate the same direction, compressing the heave spring. When one goes up and the other down (roll), opposing rocker motions cancel at the central connection — zero net displacement of the heave spring in roll. This is geometric decoupling, not approximation.
• This resolves an otherwise impossible conflict: ground-effect cars need stiff vertical suspension for ride height control, but soft roll stiffness for mechanical grip. Corner springs increase both together — heave springs break this constraint.
• The effective wheel rate in heave = corner spring wheel rate + heave spring contribution. Real prototypes run heave springs 1.5-3× stiffer than individual corner springs at the wheel.
• Stiffer front heave → front doesn't dive as much under braking, maintains front ride height at speed → more consistent front aero.
• Stiffer rear heave → rear doesn't squat as much under acceleration/aero load → maintains rear ride height.
• Heave Perch Offset adjusts preload on the heave spring. Lower values = more preload = higher ride height through that element.
• If you soften corner springs without adjusting heave springs, total heave stiffness decreases (less than you'd expect, since heave spring contribution remains) but roll stiffness drops significantly. Always consider both when changing either.

Key insight: If you want to change aero platform stiffness without affecting mechanical roll balance, adjust heave springs. If you want to change mechanical balance without affecting the aero platform, adjust ARBs. This separation is the core of GTP setup philosophy. Real-world WEC teams (Williams F1 reportedly ran zero rear corner springs — only heave + ARB) take this to the extreme.

Front Suspension Load Path — Heave, Perch, Torsion Bar Interaction

The front static load on GTP cars splits between the heave spring and torsion bars. Changing any one parameter shifts load between them, producing cascading effects on read-only garage diagnostics. Understanding this load path is essential for producing legal, optimized setups.

Read-Only Diagnostics (iRacing auto-computes from tunable params):

• HeaveSpringDeflStatic: How much the heave spring is compressed at rest. Driven by heave rate + perch offset. More preload (lower perch) or softer spring → more static compression.
• HeaveSpringDeflMax: Maximum available spring compression travel. Depends ONLY on spring rate (stiffer = shorter spring = less max travel). Perch has zero effect.
• HeaveSliderDeflStatic: How far the slider mechanism has traveled from fully extended. Dominated by perch offset (21.8× the effect of heave rate per mm).
• TorsionBarTurns: How much the torsion bar has twisted under static load. At same OD, softer heave spring → torsion bars carry more static load → more twist → higher turns value.
• TorsionBarDefl: Torsion bar deflection in mm. Tracks turns proportionally.

Load Path Physics: When heave spring is softened, it carries less of the front static weight. The remaining load transfers to the torsion bars, which twist more. This changes:

1. Torsion bar turns/deflection (read-only, auto-computed)
2. Corner weight distribution and crossweight (must be re-checked in garage)
3. The effective static stiffness of the front platform at rest

Three Methods to Adjust Front Ride Height (ranked by side effects):

1. Pushrod Length Offset — Cleanest. Changes RH only. No preload, crossweight, or torsion bar effects.
2. Heave Perch Offset — Changes RH + heave spring preload. Affects HeaveSpringDeflStatic, HeaveSliderDeflStatic, and indirectly shifts load to/from torsion bars.
3. Torsion Bar Turns — Most side effects. Changes corner weight, crossweight, and torsion bar deflection. Use ONLY for crossweight tuning, not ride height.

HeaveSpringDefl Budget (critical constraint):

Available_dynamic_travel = HeaveSpringDeflMax - HeaveSpringDeflStatic

The heave spring must not bottom during dynamic excursion:

HeaveSpringDeflStatic + excursion_p99 < HeaveSpringDeflMax

Over-preloading (very negative perch) eats into available travel by increasing DeflStatic.

Heave Spring Deflection — Why High Deflection Kills Mid-Corner Grip

The Problem: Heave spring "deflection" (preload setting) controls how much of the spring's total travel is consumed statically. When deflection is too high (slider at 44-45mm on BMW), the spring has already used most of its static travel before the car even moves. Under braking, weight transfer compresses the front heave spring further through its remaining travel. When it runs out of travel, the car hits a rigid bump stop and becomes a board — no more vertical or lateral compliance.

The Failure Mode — Entry Rotation → Mid-Corner Push:

1. Trail braking phase: Weight transfers forward, compressing the front heave spring through its remaining travel. The spring is still compressing, which allows the front to load progressively. The driver feels good rotation and turn-in.
2. Mid-corner transition: The heave spring exhausts its travel (bottoms out). The front suddenly becomes rigid — no more suspension compliance. Mechanical grip drops because the front tyres can no longer absorb surface imperfections. The car pushes.
3. The trap: The good entry feel makes the driver think the front setup is working. The mid-corner push seems like a separate problem. But it's the same cause — too little available spring travel.

Spring vs Shock Compression Curves:

• Spring (linear): F = k × x. Position-dependent. Every mm of compression adds the same force. A 50 N/mm spring at 10mm = 500N, at 20mm = 1000N. Predictable, proportional.
• Shock/Damper (nonlinear): F = c(v) × v. Velocity-dependent with digressive characteristic. At low velocities (<50 mm/s, LS regime), force rises proportionally with velocity. At high velocities (>50 mm/s, HS regime), force tapers off (digressive slope). The shock doesn't care about position — only how fast you're moving through travel.
• Combined: Under braking (slow, steady weight transfer at ~20 mm/s), the spring dominates because the compression velocity is in the LS regime. The damper contributes ~100N (c_ls × v_braking ≈ 5060 × 0.02 = 101N) while the spring contributes ~2500N (50 N/mm × 50mm travel). Spring travel exhaustion under braking cannot be saved by shock tuning — the shock barely contributes at braking compression velocities.
• Under bump impacts (fast transient at 100-300 mm/s), the shock dominates. This is why HS damping slope matters for kerb strikes but is irrelevant for the deflection-exhaustion failure mode.

Travel Budget Formula:

DeflMax = 103.4 - 0.262 × HeaveSpring     (BMW, depends ONLY on spring rate)
StaticDefl = f(spring_rate)                 (how much travel consumed at rest)
AvailableTravel = DeflMax - StaticDefl
Required = excursion_p99 + braking_weight_transfer_compression
Margin = AvailableTravel - Required         (must be > 5mm)

Optimal Slider Position: Computed from physics — maximize available dynamic travel while maintaining minimum preload (>3mm static deflection to keep spring loaded). For BMW at heave 50 N/mm, this typically yields slider ~40-42mm. The perch offset is the tuning parameter: more negative perch → lower slider → more preload → more static deflection (less available travel, but spring stays loaded). The solver optimizes this tradeoff.

Telemetry Detection:

• HFshockDefl channel directly measures front heave element deflection (meters)
• Travel usage % = p99 deflection / DeflMax × 100
• Travel usage under braking (Brake > 0.3) is the critical metric

• 85% travel used under braking = significant, >95% = critical

• Direct bottoming events = deflection within 2mm of DeflMax

Suspension — Dampers

Dampers control the rate of suspension movement, not the amount (that's springs). Critical concept: "low speed" and "high speed" refer to shaft velocity (mm/s), NOT car speed. A car at 300 km/h on a smooth straight has low-speed damper activity; a car at 50 km/h hitting a kerb generates high-speed events.

Real-world damper velocity thresholds (Penske Racing Shocks):

• Low-speed: 0–75 mm/s shaft velocity — body roll, pitch, weight transfer from driver inputs
• High-speed: 75+ mm/s — bumps, kerbs, surface impacts
• Prototype kerb strikes can exceed 750–1000 mm/s (verified: RF hit 991 mm/s at Sebring T4 kerb)

Low-Speed Compression — Resists slow suspension movements (driver inputs, weight transfer, cornering). This is your transient handling tool and what the driver feels most directly.

• Controls the RATE of weight transfer, not the amount. Stiffer = slower transfer. Softer = faster transfer.
• More front LS compression → resists nose dive → weight transfers to front SLOWER → front tires load gradually. Can feel "locked down" and resist roll, creating entry understeer if the front isn't loading fast enough.
• Less front LS compression → nose dives faster on throttle lift/braking → weight reaches front tires sooner → sharper turn-in. Primary tool for fixing off-throttle/entry understeer at low speed where aero is irrelevant.
• More rear LS compression → more rear stability under acceleration, but can cause rear to slide if too stiff.

High-Speed Compression — Resists fast suspension movements (kerbs, bumps, track surface). This is your platform stability tool.

• More HS compression → better aero platform over rough surfaces, but the car transmits more shock to the tyres.
• On smooth tracks: can run stiffer HS compression for better platform.
• On bumpy tracks (e.g., Sebring, COTA): soften HS compression to let the suspension absorb impacts.
• If too stiff, the chassis deflects off bumps and tyres lose contact — this is worse than bottoming in some cases.

High-Speed Compression Slope — The most underutilized parameter in competitive GTP setups. Controls the damper force curve shape at high shaft velocities. This maps to real-world damper valving concepts:

• Digressive (lower slope values): High damping at low shaft speeds that tapers off at higher speeds. This is the dominant paradigm in professional motorsport (Penske, Multimatic DSSV). Provides body control where you need it while softening the blow on kerbs/bumps. Essential for Sebring, Watkins Glen, Bathurst.
• Linear (higher slope values): Proportional force increase with velocity. Suits smooth circuits (Road America, Monza) where extreme bump events are rare.
• Regressive (not available in iRacing but worth understanding): Force actually decreases above the knee point. Used in F1 for aggressive kerb riding.
• Think of it as: HS comp sets the amount of high-speed resistance, slope sets the shape of the resistance curve.

Low-Speed Rebound — Resists the spring extending back after compression. Controls how quickly weight transfers AWAY from that corner.

• More LS rebound → suspension extends more slowly → weight stays on that end longer.
• Less LS rebound → suspension extends faster → weight leaves that end sooner.
• If too stiff, the suspension "packs down" — fails to fully extend before the next input, causing the car to ride progressively lower through a series of bumps or direction changes.

⚠ LS REBOUND EFFECTS ARE SPEED-DEPENDENT — the same change can have opposite effects at different speeds:

At LOW SPEED (below ~150 kph, minimal aero): Pure weight transfer mechanics dominate.

• Softer front LS rebound → nose rises faster after braking → weight leaves front sooner → can reduce front grip too quickly on exit. But also lets the front "release" faster in transitions.
• Softer rear LS rebound → rear rises/unloads faster on throttle lift → weight transfers FORWARD faster → more front grip → promotes rotation. This is a primary tool for fixing low-speed off-throttle understeer. The rear lightening helps the car pivot.
• Stiffer rear LS rebound → holds weight on the rear → resists the rear from unloading → MORE rear grip off-throttle → resists rotation → can cause understeer.

At HIGH SPEED (above ~200 kph, significant aero): Ride height and rake effects dominate weight transfer effects.

• Stiff front LS rebound → holds nose down after braking → maintains rake → preserves rear aero grip through corner entry.
• Soft rear LS rebound → rear rises rapidly on throttle lift → diffuser exits efficient range → rear aero grip drops. At high speed this aero loss can overwhelm the mechanical rotation benefit.
• The crossover point where aero effects overtake weight transfer effects is car-specific and speed-dependent. On cars with aggressive ground effect (all GTP), the aero effect becomes significant above ~150-180 kph.

When diagnosing understeer, always identify the SPEED at which it occurs before recommending rebound changes. Low-speed understeer (T7 hairpin at 80 kph) and high-speed understeer (T15 at 250 kph) may require opposite damper directions.

High-Speed Rebound — Resists fast extension (after hitting a bump). If too stiff, the tyre can lose contact with the road as the suspension can't extend fast enough to follow the surface.

Rebound-to-compression ratio: Real-world racing dampers typically run rebound forces approximately 2× compression forces at equivalent shaft velocities. This produces roughly equal peak forces because compression sees higher velocities from bump inputs. Current meta (2025-2026): Rebound slightly stiffer than compression, prioritizing controlled platform recovery through direction changes.

Damper velocity histograms (telemetry diagnostic): A symmetrical bell-curve distribution of damper velocities indicates well-tuned dampers. Flat or asymmetrical distributions signal mis-valved dampers. If the histogram shows heavy concentration at extreme velocities, the springs are too soft (the dampers are doing the springs' job).

General damper philosophy for GTP: Dampers are step 6 of 6 in the setup workflow. Only adjust after rake, heave springs, corner springs, ARBs, and wheel geometry are sorted. If the car has a handling problem, exhaust steps 1-5 before reaching for dampers. Dampers control the rate of weight transfer — they fine-tune HOW the car transitions, not WHERE the balance sits. If the steady-state balance is wrong, dampers cannot fix it.

⚠ CRITICAL DIAGNOSTIC RULE: When a driver reports understeer or oversteer, ALWAYS identify the SPEED and CORNER PHASE first. The same damper change can have opposite effects at different speeds:

• Below ~150 kph: Weight transfer rate dominates. Softer front LS comp = faster nose dive = more front grip = less understeer. Softer rear LS rebound = rear unloads faster = promotes rotation.
• Above ~200 kph: Aero/ride height effects dominate. Changes that alter ride height and rake can overwhelm weight transfer effects. Stiff front rebound maintains rake. Rear ride height changes affect diffuser.
• The 150-200 kph range is a transition zone where both effects compete. Car-specific testing required. Never recommend damper changes for "understeer" without knowing the speed at which it occurs.

Anti-Roll Bars (ARBs)

ARBs are the single most important tool for adjusting mechanical balance in GTP cars. Because heave/third springs have zero effect on roll stiffness, ARBs carry the entire mechanical roll balance responsibility. This is fundamentally different from cars with conventional spring setups.

The physics: Lateral Load Transfer Distribution (LLTD). Total lateral load transfer in a corner is fixed by physics (mass, lateral g, CG height, track width) — ARBs cannot change total load transfer. They control its distribution between front and rear axles. A stiffer front ARB shifts more load transfer to the front. Due to tire load sensitivity (grip coefficient decreases as load increases), the more heavily loaded axle produces less total grip. So: stiffer front ARB → front carries more load transfer → less net front grip → understeer. OptimumG's Claude Rouelle calls LLTD the "Magic Number" — baseline should sit ~5% higher than static front weight distribution.

ARB Size — Primary roll stiffness control per axle. Larger diameter = stiffer.

• Stiffer front ARB → front carries more load transfer → front loses grip AND rear gains grip → understeer
• Stiffer rear ARB → rear carries more load transfer → rear loses grip AND front gains grip → sharper front-end bite, more rotation
• The effect is always on BOTH axles simultaneously — stiffer at one end means the other end carries less load transfer and gains relative grip
• Disconnecting an ARB entirely removes that axle's roll resistance through the bar — can dramatically change handling.

ARB Blades — Rotating a flat, tapered plate about its longitudinal axis. Vertical orientation = maximum second moment of area = maximum stiffness. Horizontal = minimum. The relationship is highly nonlinear with rotation angle because stiffness varies with the square of the cross-section dimension.

• Use blades for small adjustments between ARB diameter steps.
• Blades are adjustable from the cockpit via the F8 black box (dcAntiRollFront / dcAntiRollRear). Experienced drivers adjust FARB/RARB corner by corner during sessions — this is the most commonly used in-car tuning parameter. When analyzing telemetry, check dcAntiRollFront and dcAntiRollRear for changes during stints. If the driver is using the full blade range deliberately (soft for slow corners, stiff for high speed), this is sophisticated live management — do NOT recommend stepping the ARB diameter, as it would shift the entire range and potentially eliminate the soft end needed for rotation.
• Common GTP ARB strategy: Keep the front ARB blades at or near 1 (maximum front grip) and use rear ARB blades as the primary live balance variable. The mechanism works on BOTH axles through LLTD: stiffer rear ARB shifts load transfer to the rear → front carries less load transfer → front tires stay more evenly loaded → front gains grip and bites harder into turns. Simultaneously the rear loses grip from carrying more load transfer. Both effects compound: sharp front-end bite + freer rear = aggressive rotation. Softer rear ARB reverses this — load transfer distributes more evenly, front has less relative bite, rear has more grip, car is stable. The front CAN be adjusted but current coaching meta favors keeping it low and using the rear as the single tuning knob. This single-variable approach is clean and effective, especially on cars like the BMW that naturally resist rotation at high speed.
• This is a confirmed professional real-world technique. OptimumG teaches fixing one ARB and adjusting only the other as a single balance variable. It reduces dimensionality and gives clearer cause-and-effect. If the adjustable ARB runs out of range, it signals springs need changing — not adding more ARB.

ARB tuning strategy: ARBs primarily affect mid-corner and transitional balance. If the car understeers mid-corner at low-to-medium speed, soften the front ARB or stiffen the rear. This is independent of aero balance (which dominates at high speed). If you need to fix a slow-corner problem, use ARBs. If you need to fix a fast-corner problem, use aero (ride height, wing, heave springs).

Differential

Diff Preload — Static baseline locking force applied to the clutch pack. Controls how much the rear axle resists differential wheel speed at all times, including zero-throttle conditions.

• More preload → rear axle acts more like a locked diff → more stability on entry and mid-corner, but less rotation and can cause inside rear to drag (understeer on exit in tight corners).
• Less preload → more differential action → car rotates more freely, but can be unstable on entry, especially under trail braking.
• The Acura ARX-06 is especially sensitive to diff preload — small changes create large handling shifts.

Coast/Drive Ramp Angles — Angled ramps convert input torque into axial clamping force on friction plates. The angle determines how aggressively torque creates locking force.

• Drive ramp angles (typically 30°-60°, lower = more aggressive): Control locking under power application. Lower angles lock the diff more aggressively on throttle → improves traction but can create exit understeer as the inside wheel is dragged faster than its natural speed.
• Coast ramp angles (typically 60°-90°): Control locking under deceleration/lift-off. Lower coast angles add stability under braking and trail-braking but create entry understeer as the diff resists speed differentiation during turn-in.
• Drive and coast can be tuned independently to create different behavior under power vs off-power.

Clutch Friction Plates — Acts as a multiplier on total locking force. More plates = more clamping force for the same preload and ramp angles. Reducing plates weakens ALL locking (coast, drive, and preload effect) proportionally. If the car understeers off-throttle and the coast ramp is already set to less locking, reducing clutch plates is the next lever — it reduces the overall strength of the coast-side locking without requiring ramp angle changes.

Diff interaction with tyre temps: High preload or aggressive ramp angles overheat the inside rear tyre in long corners as it's being dragged. Check telemetry for asymmetric rear tyre temps — if inside rear is consistently hotter than outside rear, diff locking is too aggressive.

Diff interaction with hybrid regen: On cars with rear-axle hybrid (all LMDh), the MGU delivers torque through the differential. The diff's locking characteristics affect how regen braking distributes between left and right wheels. This means diff changes can alter the feel of brake-by-wire on cars that have it.

Tyre Pressures

Cold pressures are starting points. Hot pressures are what matter.

• Minimum cold pressure in iRacing GTP: 152 kPa (22.0 PSI). You cannot go lower. This means hot pressures will always run above the ideal 20-24 PSI window (~25-27 PSI hot). This is a known sim constraint across all five GTP cars.
• After 2-3 laps of pushing, check hot pressures. Target window: 20-24 psi depending on car and conditions — but accept that starting at minimum cold, you'll land above this.
• Tyre temp spread (inner/middle/outer) tells you about pressure AND camber together:
  • Middle hotter than edges → pressure too high (tyre crowning)
  • Edges hotter than middle → pressure too low (tyre cupping)
  • Inner much hotter than outer → too much negative camber (or driving-induced — check steering angle trace)

Temperature targets: 85-105°C operating window. Peak grip around 95-100°C. If tyres are consistently above 105°C, the setup is overworking them — look at alignment, ARBs, spring rates, and diff preload as potential causes.

Camber

• More negative camber → more lateral grip (up to a point) → higher inner tyre temps.
• Too much negative camber → inner edge overheats, outer edge underutilized, reduced braking/acceleration grip (smaller contact patch under longitudinal loads).
• GTP cars generally run -2.5° to -3.5° front, -1.5° to -2.5° rear as starting points, but this varies by car and track.

Toe

• Front toe-out → improves turn-in response, increases front tyre temperatures, reduces straight-line stability slightly.
• Front toe-in → reduces turn-in, increases stability, reduces front tyre heat.
• Rear toe-in → stabilizes the rear, adds drag, increases rear tyre temperatures.
• Keep toe adjustments small. In GTP cars, 0.5-1.5mm total toe adjustments are typical.

Brake Bias & Brake Migration

• While technically a "driving parameter," brake bias directly affects the setup's balance under braking.
• More forward bias → front locks first → understeer into corners.
• More rearward bias → rear locks first → oversteer/rotation on entry.
• In telemetry, if you see the front tyres saturating (tyre slip spike) under braking before the rears, bias is too far forward.
• Brake migration (available on Cadillac, Porsche, Ferrari 499P — NOT on BMW or Acura): dynamically shifts bias based on pedal position. At 100% pedal, bias = base setting. At 0% pedal, bias = base + migration gain. Cars with migration can run different base biases since migration compensates dynamically. Cars without migration (BMW, Acura) need more consistent pedal modulation from the driver.
• ⚠ S3 2025 BUGFIX: Migration was running at 50% of stated value until June 27, 2025. If converting an older setup: halve migration setting, add 1-1.25% forward to base bias.

Gearing

• Three preset stacks available: Short, Medium (where available), Long. Short suits tight, slow-corner tracks (Sebring, Long Beach). Long suits extended straights (Daytona, Le Mans).
• Le Mans MANDATES the Long gear stack since S2 2025 — no choice available.
• Verify top speed vs RPM at the end of the longest straight. If hitting the limiter well before the braking zone, the final drive or top gear is too short.
• If the car doesn't reach the limiter at all on the longest straight, gearing may be too tall (losing acceleration out of slow corners).
• Gear spacing should give usable RPM range in each gear through the important corners.

Setup Workflow — Analysis & Fix Order

Dampers are the FINAL tweaks, not the first tool you reach for. When analyzing a setup or diagnosing a handling problem, work through parameters in this order every time. Do not skip ahead to dampers before the foundation is right.

1. Rake (ride heights) — Front-to-rear ride height split is the single most powerful balance tool. More rake = more oversteer. Less rake = more understeer. Establish ride heights via pushrod offsets and perch offsets (NOT a direct "ride height" parameter). Verify in garage and aero calculator. At high speed, rake determines aero balance. At low speed, it shifts CG and roll center heights. This is always the first thing to evaluate and adjust.
2. Heave springs (third springs) — Control the aero platform stiffness under downforce. Ensure the car isn't bottoming on clean track. Set front heave to maintain ride height at speed without excessive bottoming. Set rear third spring to control rear platform oscillation. These operate independently of roll stiffness (ARBs).
3. Corner springs (torsion bars / coil springs) — Set mechanical stiffness appropriate to the track surface and the car's roll requirements. Stiffer = better platform but less mechanical grip. Softer = more grip but more ride height variation. Corner spring changes affect BOTH heave stiffness and roll stiffness — always re-check ride height and aero calculator after changing.
4. ARBs — Dial in mechanical mid-corner balance via LLTD. This is the primary steady-state cornering balance tool. ARBs do not affect heave stiffness — they are independent of the aero platform.
5. Wheel geometry (camber & toe) — Fine-tune tyre utilization and thermal behavior. Camber controls contact patch shape in roll. Toe controls turn-in response and straight-line scrub/heat. Adjust based on tyre temperature readings (inner/outer spread for camber, overall temp for toe).
6. Dampers — The final tweaks. Dampers control the RATE of weight transfer, not the amount. They fine-tune transient response (corner entry, exit, direction changes) after the foundation (ride heights, springs, ARBs, geometry) is established. Do not use dampers to fix problems that should be solved by rake, springs, or ARBs. Damper effects are speed-dependent — always identify the speed at which the problem occurs before recommending changes.

Supporting parameters (adjust as needed throughout):

• Diff — Rotation vs stability, coast vs drive locking. Adjust after ARBs establish steady-state balance.
• Brake bias — Match to the car's weight transfer and driver preference. Iterate after major suspension changes.
• Tyre pressures — Iterate based on running data. Constrained by 152 kPa minimum cold in iRacing GTP.
• Gearing — Match to track. Usually set once and left alone.

Always iterate: After changes to steps 1-4, re-check tyre data and ride height traces. Setup parameters interact — a spring change affects ride height which affects aero which affects everything.

Hierarchy of impact (highest → lowest): Rake/ride heights → Heave/third springs → Corner springs → ARBs → Wheel geometry → Dampers. The first three control the aero platform and mechanical foundation. ARBs control steady-state balance. Geometry fine-tunes tyre behavior. Dampers are the final polish on transient response.

The Parameter Cascade — Nothing Is Free

The fundamental cascade: spring rate → ride height → aero load → tire load → grip → balance. Every setup change propagates through this chain. Soften rear springs → more rear compression under aero load → rear ride height drops on straights → diffuser performance changes → aero balance shifts — all from a spring change intended to improve mechanical grip. Changing ride height simultaneously alters camber geometry, toe geometry, roll center position, and bump stop engagement.

Common setup traps (from real-world race engineering):

• Chasing understeer with more front wing angle → increases drag, may reduce rear stability at speed
• Softening springs for mechanical grip → car wanders through the aero map unpredictably
• Using ARBs to compensate for an aero balance deficit → works at one speed but creates the opposite problem at another
• Stiffening heave springs to stop bottoming that was actually kerb strikes → loses mechanical grip everywhere for a problem that only exists at one corner (see Sebring T4 lesson)
• The "fix one symptom, create another" trap: Always ask "what else does this change affect?" before recommending. Think through the cascade.

Fuel load variation: 80-110 kg of fuel burns off during a stint (8-11% of the 1,030 kg min weight). As fuel depletes: total weight decreases, ride height rises as springs uncompress, aero operating point shifts, weight distribution changes, tire loading decreases. Teams optimize for mid-stint fuel load and accept compromises at full and empty. If a driver reports the car "goes away" late in a stint, it may be fuel-related ride height/aero shift, not tire degradation. When switching between race fuel and qualifying fuel, the driver must re-set pushrod offsets to maintain the same target ride height. A more negative pushrod at low fuel compensates for less spring compression — it's maintaining the same platform, not changing it. Never compare raw pushrod values across sessions with different fuel loads — compare the resulting garage ride height instead.

Tire Conditioning Physics

Why new tires are slow: Fresh tires carry mold release agents on their surface and have polymer chains in their as-manufactured state — non-uniform with residual stresses from molding. The rubber compound's grip is governed by its glass transition temperature (Tg), where two mechanisms peak simultaneously: indentation (road texture deforms rubber) and molecular adhesion (Van der Waals bonding at the interface).

Conditioning involves two processes:

1. Surface scrubbing (2-3 laps): Removes mold release agents, roughens the glassy manufacturing skin.
2. Heat cycling (full operating temp → slow cool over 24+ hours): Breaks weakest molecular bonds, driving forces during cornering realign the granular structure, volatile petroleum components boil off. Upon slow cooling, broken bonds relink in a stronger, more uniformly aligned configuration. Result: more consistent (not necessarily peak) grip throughout the tire's life.

iRacing's Vision tread model (S1 2026+) simulates this conditioning process — temps build progressively over a stint as the "long-term conditioning state" develops. A 5-lap stint may not reach operating window; this is normal, not a setup failure. Out-laps are genuinely precarious (S2 2025+ tire model). For sprint qualifying, setup changes (more camber, more toe-out) can accelerate thermal buildup. For endurance, the model handles conditioning naturally over 8-15 laps.

Communicating Setup Changes

Default Response Style — Concise Engineering Brief

Unless the user explicitly asks for detailed explanations, keep responses tight and structured. Use this format:

✅ Good — What's working, leave alone ❌ Bad — What's broken, with data 🔧 Changes — Specific parameter adjustments (what, from → to). Always reference actual garage parameters (pushrod offset, heave perch offset, spring perch offset, etc.) — never recommend derived values like "ride height" as if they're direct inputs. ⚖️ Trade-offs — Pros/cons of each change (one line each) 📋 Summary — Priority-ordered action list

Do NOT over-explain the physics unless asked. The user is an engineer — state the diagnosis, the fix, and the trade-off. Save the "why" for when they ask "why."

When Asked for Detailed Explanation

If the user asks "why", "explain", "walk me through it", or similar — then expand with:

• What to change and by how much (or a direction + magnitude guidance)
• Why — what telemetry evidence or symptom drives this change
• Expected effect — what should improve and what might get worse (trade-offs)
• What to verify after — which telemetry channel to check to confirm the change worked

Example format:

Change: Increase rear ARB from 2 to 3 (or increase rear ARB blade by 2 clicks) Why: Telemetry shows mid-corner understeer at low speed — rear tyre temps are lower than fronts, suggesting the rear isn't working hard enough in roll. Expected effect: More rear roll stiffness → rear grip reduces in corners → car rotates more. Trade-off: rear may become less stable on power in slow corners. Verify: Check rear tyre temps after 3 laps — they should come up. Mid-corner understeer should reduce.

Critical: Cars Have Different Setup Architectures

Do not transfer parameter values between cars. The five GTP cars use different:

• Parameter naming (PushrodLengthOffset on BMW vs PushrodLengthDelta on Ferrari)
• Value types (BMW ARBs use "Soft"/"Medium"/"Stiff", Ferrari uses "A"/"B"/"C")
• Click scales (BMW damper LS comp 7 clicks ≠ Ferrari LS comp 15 clicks — completely different scales)
• Rear spring types (BMW: coil springs in N/mm, Ferrari: torsion bars with indexed OD)
• Diff architectures (Ferrari has front AND rear diff preload, BMW has rear only with ramp angles)
• Brake bias baselines (Ferrari 56.5% vs BMW 46% for the same track — do not compare across cars)

Always read references/per-car-quirks.md before giving car-specific advice. It contains verified numeric values from actual setups.

Wet/Rain Setup (Summary)

When TrackWetness or WeatherDeclaredWet indicate wet conditions:

1. Fit wet tyres — larger diameter raises ride heights, re-check aero balance.
2. Brake bias rearward 2-4% — fronts lock easier in rain.
3. Increase TC — raise both TC1 and TC2 by 2-3 steps from dry baseline.
4. Soften ARBs — helps tyres find grip on low-traction surface.
5. Soften heave/third springs — aero loads are lower in the wet (slower speeds), so stiff heaves add less benefit and hurt compliance.
6. Increase ride heights slightly for standing water clearance — adjust via pushrod length offsets and heave perch offsets, then verify resulting ride height in garage.
7. Add wing angle — extra downforce helps in low-grip conditions, straight-line speed penalty matters less.
8. Avoid the rubbered dry racing line — it becomes extremely slippery in wet. This is a driving consideration but directly impacts setup balance perception.
9. Ferrari 499P has a genuine wet advantage — front-axle hybrid deploys above 190 km/h providing partial AWD. Cornering mode becomes especially valuable for high-speed wet stability.

See references/per-car-quirks.md → Wet/Rain Setup section for full details.

Community Tools & Setup Services (as of early 2026)

Telemetry Analysis

• Cosworth Pi Toolbox — Native .IBT support, free Lite tier, real-time telemetry in Pro/Ultra tiers. The current gold standard for GTP engineering.
• MoTeC i2 Pro — Most powerful standalone analysis. Requires Mu exporter. Best for custom math channels and deep engineering work.
• Garage 61 (garage61.net) — Community setup sharing hub, PWA, basic telemetry. Great for browsing competitive setups, lacks deep aero channels.

Setup Subscriptions

• Coach Dave Academy (Delta) (~$12/mo) — All 5 GTP cars weekly, race/quali/safe/wet variants, 14-person team including 2x IVRA Endurance GTP Champions, auto-install, AI coaching insights, MoTeC data packs.
• Grid-and-Go ($5-15/mo) — Endurance event specialist, built by 8k-12k+ iRating drivers, Garage 61 integration.
• GO Setups (~$10/mo) — All GTP cars weekly, dedicated auto-installer app.
• SimRacingSetup (~£7/mo) — Budget option, full data packs.
• Apex Racing Academy — Free special-event setups (confirmed free Daytona 24 packs), premium coaching tiers.
• Track Titan — AI-powered e-sports setups, coaching flows using ML to identify root causes of time loss.

Free Resources

• Garage 61 community setups — Crowdsourced, variable quality but often competitive.
• Majors Garage (majorsgarage.com) — "Baseline+" quality, better than iRacing defaults.
• iRacing default setups — Suitable only below ~2000 iRating. Always replace for competitive racing.

AI Tools

As of early 2026, no AI tool automatically optimizes car setups. Track Titan's Coaching Flows and Coach Dave Auto Insights are driver coaching tools, not setup optimizers. Setup engineering remains a human craft.

Reference Files

• references/per-car-quirks.md — [V2: Contains verified setup values from real IBT/LDX data.] Detailed per-car parameters, architectural differences between cars, numeric baselines, track classification table, and wet setup guide.
• references/telemetry-channels.md — [V2: All 302 channel names verified from parsed IBT file.] Complete channel reference with exact SDK names, types, units, and diagnostic thresholds.
• references/ibt-parsing-guide.md — [V3: Verified from BMW M Hybrid V8 + Ferrari 499P IBT files.] Complete IBT binary format specification with header structure, variable header layout, data extraction code, and session info YAML parsing. Read this first when the user uploads an IBT file.