If iRacing runs badly for you, the odds are heavily against your graphics card being the problem. iRacing is a DirectX 11 title with a rendering path that leans hard on one CPU thread, which sets it apart from the other titles in our best racing sim comparison, and the things that murder your frame rate are almost all CPU-side: shadow passes, mirror passes, and the number of cars the sim is being asked to draw. People go buy a new GPU, gain four frames at the Daytona rolling start, and quietly assume that’s just how it is.

So here’s the verdict up front. Turn shadow maps down or off, cap the cars you draw to something sane, stop rendering high-detail mirrors, and cap your frame rate below your refresh. That combination is worth more than any card you can buy this year. Then, if you still want to spend money, spend it on a CPU with a big L3 cache, not a GPU. Everything below is the detail behind that.

Find out what’s actually limiting you (two minutes)

In Graphics Options, turn on the frame rate display. You’ll get a small readout in the corner with your FPS and, more usefully, a split showing how loaded the CPU and GPU are. Now go do the ugliest thing you can: load a practice session at Le Mans or Daytona, spectate a big AI field, sit in the pack at the start.

Watch the two numbers. If your CPU load is pinned near the top and the GPU is sitting at 60%, congratulations, you have found your bottleneck and it is not the card. That is the normal result. It’s what most of the “help my FPS is bad” threads on r/iracing turn out to be once someone actually asks for the numbers, and it’s why the top reply is always some variation of “what CPU do you have.”

If it’s genuinely the other way round, GPU pinned and CPU coasting, you’re either running triples at high MSAA, VR at a silly supersample, or you’re on an old card. That’s the rarer case and it’s a much easier fix, because GPU load responds to resolution and anti-aliasing in a straight line.

The settings that cost real money

Shadows. Shadow Maps is the single most expensive slider in the sim. Every shadow-casting object gets rendered again into the shadow buffer, and with 40 cars on track that adds up brutally. Dropping from High to Low frequently buys 20-30% at a race start. Turning shadow maps off entirely looks flat and slightly wrong (the car looks like it’s hovering), but if you’re chasing a stable 90 in VR, it’s the first thing to go. Dynamic Track Shadows (the clouds moving across the surface) is another one that costs more than it visually gives. Kill it. Nobody has ever lost a race because they couldn’t see a cloud shadow crossing Eau Rouge.

Mirrors. iRacing renders your mirrors as additional passes of the scene. Higher Detail In Mirrors is a very expensive toggle for something you glance at. Turn it off, and if you’re desperate, reduce the mirror count or turn off dynamic cars in mirrors in favour of the virtual mirror. Yes, some people insist real mirrors are the only way to race. Those people usually also have a 9800X3D.

Cars drawn. The Max Cars setting decides how many cars the sim will actually render. It defaults high. In a 40-car GT3 field, you cannot see 39 other cars, and the ones behind the wall of bodywork in front of you contribute nothing but draw calls. Setting this to around 16-20 typically costs you nothing you’d notice on track and gives you back the frames you were losing precisely when you needed them, which is lap one into Turn 1 at Monza with the whole field alongside. Cars: Detail Reduction pushes lower-detail models further out, and it’s basically free performance. Use it.

Anti-aliasing. MSAA is a GPU cost, not a CPU cost, so this one only matters if the GPU is your limit. 8x MSAA is a waste at 1440p and above. 2x or 4x plus a touch of the in-sim sharpen filter looks fine and gives back a chunk of GPU headroom for VR or triples.

Here’s the rough shape of it, in the order I’d actually change things:

Particles, crowds, and heat haze are small individually. Turn them down anyway. They’re free.

Stutter is a different problem from low frame rate

This is where most guides get lazy. Sixty solid frames with a hitch every eight seconds feels far worse than a smooth 45, and the causes are completely unrelated to your graphics sliders.

The classic one: replay writing to a slow drive. iRacing continuously buffers replay data, and if that’s landing on a mechanical drive or a nearly-full SATA SSD, you get a rhythmic hitch. Move the sim and its replay folder to an NVMe drive. A 1TB NVMe SSD costs around $60-80 now and fixes this permanently, which makes it the cheapest performance upgrade in sim racing.

The second one: shader compilation after an iRacing build update. The first few laps at a track after a season release will stutter as things get compiled and cached. This isn’t broken, it’s just annoying. Do a couple of laps offline at any track you’re about to race before you join the session.

Third, overlays. SimHub, Racelab, the various telemetry dashboards, Discord’s overlay, and OBS all hook into the render path. I’ve seen a single busy overlay app cost 15% of the frame rate on a mid-range machine. If you’re running four browser-based overlays on top of a CPU-limited sim, that’s a choice you’re making. Close what you don’t need for the race, and check whether Chrome is sitting in the background with hardware acceleration on, quietly eating GPU time for a tab you forgot about.

Fourth, and this one catches people out: USB. Wheelbases and pedals poll at high rates, and hanging your wheel, pedals, button box, handbrake, and a VR headset off the same USB controller (usually all the front-panel ports, which share one internal hub) can produce hitching that looks exactly like a graphics problem. Spread devices across ports on different controllers, and put a VR headset on its own. Fanatec users have been arguing about this on the forums for years, and while a decent chunk of that is Fanatec’s own driver situation, the USB hub thing is real regardless of brand.

Fifth, sync. If your monitor is 165Hz and iRacing is spitting out 210 frames with vsync off, you’re going to get tearing and inconsistent frame pacing. If it’s producing 158 with vsync on, you get a stutter every time it misses. Use a G-Sync or FreeSync monitor, cap the frame rate a few frames below refresh (156 on a 165Hz panel, say), and leave vsync off in-sim. Frame pacing improves out of all proportion to the raw number. A rock-steady 120 feels better than a bouncing 130-165, and anyone telling you otherwise has never watched a frametime graph.

Triples and VR: where the CPU actually dies

Triple screens are not “the same load spread across three panels.” iRacing renders three viewports, which means the CPU work of building the scene happens three times. Draw calls triple. This is why someone on a 1440p 240Hz single screen can run a 40-car field at 200 FPS on a modest chip, and someone on triple 1440p with the same chip is fighting for 90.

If you run triples and your frame rate collapses in traffic, the fix is car count and shadows, not resolution. Dropping to a lower render resolution barely helps, because you weren’t GPU-limited to begin with. This is the single most common misdiagnosis I see.

VR has the opposite failure mode: it’s GPU-hungry (you’re rendering two eyes at high resolution, and any supersampling multiplies fast), but it’s also unforgiving about frame time consistency, because a missed frame in VR is a physical sensation rather than a visual one. Get shadows off, get the supersample down to something honest, and let the headset’s reprojection do its job. A Meta Quest 3 at around $500 is still the sane entry point (our best VR headset for sim racing guide compares it to the alternatives), and the various high-end PC headsets will happily consume a GPU twice as expensive as the one you have.

What to actually buy

If you’ve done all of the above and you’re still CPU-limited in traffic, this is the one time I’ll tell you to spend money on hardware, and it’s not on the thing you expected.

iRacing loves cache. AMD’s X3D chips (the Ryzen 7 7800X3D at around $350, or the 9800X3D at around $480) are the closest thing to a cheat code this sim has. The stacked L3 cache means far fewer trips to main memory during the heavy scene-building work, and the gain in exactly the scenario you care about (a full field, race start, everything on screen) is large in a way that’s rare in PC hardware. This is not marketing. It is the boringly consistent result across every benchmark and every thread where someone posts their before-and-after.

Pair it with 32GB of reasonably quick DDR5 and stop worrying about RAM. Windows, a browser, Discord, and a couple of overlays will happily use 16GB before iRacing gets a look in.

For the GPU: an RTX 4070 class card, roughly $500-550, handles single-screen 1440p at high refresh and triple 1080p comfortably. Above that, you’re buying frames for VR or for high-resolution triples, and only if you’ve confirmed you’re GPU-limited. Buying a flagship card to fix a CPU bottleneck is the most expensive way to be disappointed, and I’ve watched people do it more than once.

Note what isn’t on this list: your wheelbase. A direct drive base doesn’t cost frames. If your FFB feels notchy or clipped, that’s a force feedback settings problem or a USB problem, not a rendering one, and no amount of graphics tweaking will fix it. Our iRacing FFB settings guide covers the force feedback side.

FAQ

Why does iRacing stutter at the start of a race but run fine alone? Because that’s the moment the sim has to draw the most cars, cast the most shadows, and fill the most mirrors, all at once, on the CPU. Lower Max Cars, drop shadow maps, turn off high-detail mirrors. If it’s gone from stutter to smooth-but-lower-FPS, you’ve found it.

Will a better graphics card fix my iRacing FPS? Probably not, unless you’re on triples at high resolution, in VR, or running an old card. Check the CPU/GPU split in the frame rate readout first. If the CPU number is the one that’s pinned, a new card buys you nothing.

Should I cap my frame rate in iRacing? Yes. Cap it a few frames under your monitor’s refresh with a variable refresh display, leave vsync off, and enjoy the frame pacing. Chasing an uncapped number that swings by 60 FPS between an empty track and a full grid is how you end up with a sim that feels worse than the numbers suggest.

Before you spend anything

Do this in order, and stop as soon as it’s fixed. Turn on the frame rate readout and go sit in traffic. Shadow maps down. Dynamic track shadows off. High-detail mirrors off. Max Cars to 16-20. Cap frames below refresh. Close every overlay you aren’t looking at during the race. Confirm the sim and its replay folder live on an NVMe drive.

If after all of that the CPU line is still buried and you’re still losing frames into Turn 1, that’s your green light: buy the Ryzen 7 7800X3D, not the graphics card. It’s the cheaper of the two, it’s the one that fixes the actual problem, and it will still be doing the job in three years, when the guy who bought the flagship GPU is back on the forums asking why his frame rate collapses at the start of the Daytona 24.