"Failed Tech." Two words, no explanation, and the sim won't let you race until you deal with them. If you've just loaded a setup you paid for — or one of mine from the free archive — and hit that message, nothing is broken. The file is just illegal, and fixing it usually takes two minutes once you know where to look.
I got scrutineered for real for a decade. Same idea, fewer clipboards. Here's how iRacing's version works.
What tech inspection actually is
Every real series has scrutineering: officials measure the car against the rulebook, and if it's outside the limits it doesn't run. In F3 we'd get ride heights and wing angles checked before qualifying, and the skid block told the story afterwards. Nobody argues with the measurement.
iRacing automates the same thing. In an open-setup series, the sim inspects your setup before you take the car out — every value gets compared against that car's allowed ranges and the rules of the series you're in. Pass, and you grid. Fail, and you get the error and stay put until the setup is legal. There's no penalty attached, no stewards' report; the car simply doesn't turn a wheel until it passes.
Finding the problem is easier than the blank error message suggests: open the garage and look for the values that are flashing. Those are the illegal ones. It's usually one or two numbers, not the whole file.
What gets checked
The exact rulebook is per car and sometimes per series, but the checks fall into a few families:
- Ride heights — the classic. Cars have minimums, and since the 2026 Season 2 build some classes measure at the front splitter too. GTE cars even carry a special case: any layout that includes the Nürburgring Nordschleife requires a minimum 70 mm, because bottoming the compressions there at race speed is not a theoretical problem. I've done the real Nordschleife in a GT3 car — the rule is correct.
- Aero limits — wing angles and downforce packages have legal ranges, and some series restrict which package you can run at which track type.
- Tyre pressures — minimums exist, and they interact with ride height more than people think. The tyre is a spring; my tyre pressure guide covers why dropping pressures also drops the car, which can push a borderline ride height under the limit.
- Series rules — the same car can face different rulebooks. Since the Season 3 2026 build, series can run their own sporting regulations on top of the car's base rules, so a file that's legal in one series isn't automatically legal in another.
Real-world parallel that makes all of this feel less arbitrary: NASCAR changed its 2026 rules, so iRacing's Trucks and O'Reilly-series cars now carry a 4.25-inch minimum ride height and lost their rear anti-roll bars in the same build. The sim's tech rules move because the real rulebooks move.
Why your setup fails after every big update
This is the pattern behind most failed-tech moments: the setup was legal when it was made, and then iRacing shipped a build.
Four times a year, a season build lands, and physics move. Tyre models get rebuilt car by car, aero maps get adjusted, garage rules get rewritten. The 2026 Season 2 build is the perfect case study: GTE cars got new slick tyres, an aero balance retuned for lower rake, and a new ride-height measurement at the splitter — and iRacing said it plainly in the release notes: most old setups will fail tech, splitter too low. That wasn't a bug. It was the rulebook changing underneath a thousand saved files.
Season 3 did the same to GT3, with class-wide aero, mass, power and driver-aid changes. Any GT3 file from spring 2026 — including the older ones in my GT3 setup collection — should be treated as a baseline to check, not a finished lap.
So before you assume the setup shop scammed you: check which season the file was built for. A setup is dated the moment the next build ships, which is exactly why comparing it against the current iRacing baseline is the first skill I'd learn as a setup downloader, before tuning anything myself.
My two-minute fix, in order
- Load the iRacing baseline for the car. It always passes — iRacing refreshes its factory setups every season for exactly this reason. This confirms in ten seconds that the problem is the file, not the install, and gives you a legal reference to diff against.
- Reload your setup and find the flashing values. Garage, then work through the tabs. Nine times out of ten it's ride height or something dragging ride height down.
- Fix ride heights first. Raise the car until the numbers stop flashing, then re-check pressures — if they were below the new minimum, correcting them lifts the car a touch more.
- Sanity-check the rest against the baseline. Wing within range, camber sensible for the track type. A road-course file loaded at an oval can fail on geometry alone, which is a sign you loaded the wrong file, not that you should force it to pass.
- Decide if it's worth saving. If the file predates the current season's build and the class got a physics pass, patching it value by value is usually slower than starting from the fresh baseline and rebuilding the character of the old setup into it. That's tuning, and it's a better use of the hour.
If you're downloading files regularly, buy current-season ones — the good setup shops re-release for every build precisely because of tech — and make sure they're in the right folder so you're not debugging the wrong problem.
If you never want to think about this again
Race fixed. In a fixed-setup series iRacing supplies that week's file and the garage is locked, so tech inspection is effectively iRacing's problem instead of yours. I've made the longer argument in my fixed vs open guide — for most drivers still building consistency, fixed is where the improvement is anyway, and it deletes this entire article from your life.
FAQ
What does "Failed Tech" mean in iRacing?
Your setup file didn't pass the automatic legality inspection for that car and series — one or more values are outside the allowed ranges. The sim blocks you from driving until the setup is legal. It's not a penalty and doesn't touch your safety rating or iRating; you just can't grid with an illegal car.
How do I quickly fix a setup that fails tech?
Load the iRacing baseline to confirm the car itself is fine, then reload your setup and open the garage: the illegal values flash. Fix ride heights first, re-check tyre pressures, and compare anything else suspicious against the baseline.
Why did my setup fail tech after an iRacing update?
Season builds change tyre models, aero and garage rules, and iRacing's tech limits move with them. The 2026 Season 2 GTE update is the textbook example — a new splitter ride-height measurement meant most pre-existing setups failed until raised. Old files need re-checking after every build.
Do fixed setup series have tech inspection problems?
Effectively no. iRacing's own weekly file always passes, and the garage is locked so you can't make it illegal. Only the cockpit adjustments — fuel, brake bias, aids where fitted — remain yours, and none of those fail tech.
Can a legal setup be illegal in a different series?
Yes. Since Season 3 2026, series can carry their own sporting regulations on top of the car's base rules — so check tech per series, not per car. The Rules tab in the session tells you what applies that week.
Tech inspection annoyed me for ten years in real cars, and it took exactly one hacked-together, floor-scraping lap in someone else's sim setup to understand why it exists. The limits are the game. Learn to work inside them and a flashing garage value becomes a thirty-second fix instead of a ruined evening.