If you want one answer to take to a checkout page: a Ryzen 7 7800X3D, an RTX 5070 or RX 9070, 32GB of DDR5, and a 1TB NVMe drive runs iRacing, Assetto Corsa Competizione, and Automobilista 2 on a single 1440p monitor at high refresh with room to spare. Call it $1,300 to $1,500 for the tower if you build it yourself. If you’re on a 1080p screen, drop to a Ryzen 5 7600 and an RTX 5060 Ti 16GB and you’re around $900. Triples and VR change the math, and I’ll get to those, because that’s where most people overspend on the wrong part.

The published requirements are almost useless. iRacing’s official minimum spec would run the sim like a slideshow the moment rain shows up at a 60-car Daytona start, and ACC’s “recommended” line was written for 1080p at 60 fps in dry conditions with a short field. Nobody races like that. What follows is what actually holds frame times steady in the sessions you’ll really be in, which I’ve learned by watching my own frame-time graph go jagged in more cars than I’d like to admit.

The three sims want different things, and that matters

Treating “sim racing” as one workload is the first mistake in every recycled spec list. These three engines are nothing alike.

iRacing is a DX11 engine with roots going back to 2008, and it’s stubbornly single-thread heavy. The renderer thread does a huge amount of work per frame, so what it wants is fast per-core performance and a big cache. This is why the 7800X3D became a meme on r/iRacing: AMD’s 3D V-Cache chips don’t just raise average fps, they flatten the frame-time spikes that cause the little hitch when 40 cars funnel into turn one. Since the 2024 rain update and the night lighting overhaul, the GPU side got heavier too, but the CPU is still the ceiling for most people. A 4090 paired with an old six-core will still stutter at the Daytona 24 start. I’ve seen it.

ACC runs on Unreal Engine 4 and is the opposite problem: it eats GPUs. Thirty GT3s in the rain at Spa with mirrors turned up will bring a mid-range card to its knees, and it’s the worst of the three in VR by a wide margin. The settings that actually cost you are mirror resolution and view distance, car LOD, volumetric fog, and “materials quality.” Temporal anti-aliasing makes everything a bit soft, and people spend hours in the Discord arguing about resolution scale versus sharpening to fight it.

AMS2 uses the Madness engine, the same lineage as Project CARS, and it’s the best-optimized of the bunch by a long way. It scales across cores properly, runs 90 fps in VR on hardware that ACC laughs at, and looks better doing it. If you have an older PC and want to try VR racing tonight, AMS2 is the one that will actually work.

CPU: buy cache, not cores

For a dedicated sim rig the choice is simple. The AMD Ryzen 7 7800X3D is the value pick at around $330 to $380, and the Ryzen 7 9800X3D is the one to buy if you’re building new and want to not think about it for five years, at around $450. The 9800X3D runs cooler under load and clocks higher, which iRacing notices. Both are eight cores. You do not need sixteen. A 16-core chip won’t move your minimum frame rate in any of these sims, and the money is better spent one GPU tier up.

The budget answer is the Ryzen 5 7600 at around $180. It’s a plain six-core with no extra cache, and it’s fine for 1080p and single-screen 1440p. Where it falls short is the exact scenario you care about: big fields, rain, night. You’ll get maybe 15 to 25 percent lower lows than the X3D chips in iRacing’s worst moments. Whether that’s worth $150 to you depends on how often you run 40-car ovals versus 20-car GT3 sprints.

Intel is not a bad choice. It’s just not a better one for this. The Core Ultra and 14th-gen parts trade blows with AMD in most games, but in iRacing specifically the X3D cache advantage is real and repeatable, and the AM5 socket has upgrade life left in it. If you already own a 13700K or similar, don’t swap it. It’s plenty.

One quirk worth knowing: iRacing benefits from turning off simultaneous multithreading on some chips, and the setting is buried in the app.ini rather than the graphics menu. People on the forums swear by it. I’ve measured it as a small but real gain in frame-time consistency on a 5800X3D, and nothing on newer chips.

GPU: pick by output, not by hype

This is the part where the tier you need depends almost entirely on how many pixels you’re pushing and at what refresh rate. Rough guide, assuming you want high settings and a steady frame rate matching a 144Hz-class panel:

The VRAM line matters more than the model number. iRacing at triple 1440p with car detail turned up will happily use more than 8GB, and ACC’s texture streaming falls apart when it runs out. The 8GB cards look cheap on paper and become the first thing you replace. Pay the extra for the 16GB variants every time.

Triples get a warning of their own. Running three screens in iRacing is beautiful and it’s also the most punishing way to play, because the sim renders three separate projections rather than one stretched image. Frame rate at 7680x1440 is closer to 4K than people expect, and you lose the ability to lean on upscaling as easily. If you’re on a budget and want the field of view, three 1080p 27-inch panels with a 5070-class card is a much better experience than three 1440p panels with a card that can’t hold 100 fps.

RAM, storage, and the parts nobody argues about

Get 32GB of DDR5. iRacing itself will run in 16GB, but you won’t be running iRacing itself. You’ll have Discord, Crew Chief, SimHub driving a dashboard, a Chrome tab with the pit strategy calculator, maybe OBS, and iRacing’s own overlays. 16GB works until the day it doesn’t, and that day is usually mid-race. Pick a 6000MT/s CL30 kit for AM5 and enable EXPO in the BIOS, because AMD’s memory controller is happiest right there.

Storage is bigger than people expect. A full iRacing install with all purchased content passes 100GB and grows every season. AMS2 with DLC is around 80GB. ACC is a comparatively modest 50GB. A 1TB NVMe is the floor. 2TB is what you’ll wish you’d bought once you add Le Mans Ultimate and rFactor 2. Any decent PCIe 4.0 drive is fine; load times are not where you’ll notice the difference between a good drive and a great one.

Power supply: a genuine 750W unit from a brand you’ve heard of, ATX 3.0 or 3.1 if it’s going in front of a 50-series card. Transient spikes on modern GPUs will trip protection on a marginal unit, and the failure mode is a black screen at the worst moment. Also budget for the fact that a direct drive wheelbase has its own brick and does not draw from your PC, so don’t oversize the PSU for it. People do.

The USB problem nobody puts in a spec sheet

Here’s the thing that will actually ruin your first month, and no requirements page mentions it. Sim rigs are USB nightmares. A wheelbase, pedals, a shifter, a handbrake, a button box, a headset, a webcam for the stream, and a dashboard display all want to talk to the PC at once, and consumer motherboards share USB bandwidth across controllers in ways that aren’t visible until things start dropping out.

Rules I follow after too many mid-race disconnects:

• The wheelbase goes straight into a rear motherboard port. Never a hub, never a front-panel port. Fanatec bases in particular are notorious for hating hubs, and this is a real chunk of the “my wheel randomly disconnected” threads on their forum. Moza and Simucube are more tolerant, but why gamble.
• Pedals get their own rear port too, especially load cell sets, which send a lot of data.
• Low-bandwidth stuff (button boxes, shifter, handbrake) can share a powered hub. Powered, not bus-powered. The unpowered $8 hub is how you get phantom button presses.
• Turn off USB selective suspend in Windows power settings. It’s on by default and will put your handbrake to sleep during a long safety car period.

When shopping a motherboard, count the rear USB ports before you look at anything else. Eight or more is the target. Most B650 and B850 boards in the $150 to $200 range manage this; the cheapest ones do not, and you’ll be buying a PCIe USB card within a month.

Monitor refresh and the frame cap

Match your target frame rate to your panel, then cap it. Uncapped frames in iRacing waste CPU headroom on frames you never see and make the frame-time graph noisier. If you have a 144Hz screen, cap at 141 in the sim or the driver, and turn on VRR (G-Sync or FreeSync). A stable 120 fps feels better than an average of 200 with dips to 70. This is the single cheapest performance improvement available and almost nobody bothers.

If you’re choosing between a 4K 60Hz panel and a 1440p 165Hz panel for the same money, take the 1440p every time. Resolution is nice for scenery. Refresh rate is what makes catching a slide feel connected to your hands.

Laptops and prebuilts

A gaming laptop with a mobile RTX 4070 or 5070 runs all three sims perfectly well at 1080p and 1440p. What kills the experience is thermals over a two-hour race, when the CPU starts throttling around lap 40, and the port situation, since you’re back to hubs for everything. If a laptop is what you have, use it, plug the wheelbase into the one port closest to the motherboard (usually the rear or side one), and put the machine on a cooling stand. Don’t buy a laptop specifically for a sim rig though. Same money buys a much better desktop.

Prebuilts are fine now in a way they weren’t five years ago. Check three things: that the RAM is actually running at its rated speed and not 4800MT/s, that the PSU is a named brand and not a rebranded mystery unit, and that the case has intake fans. Those are the three corners prebuilt vendors cut.

Upgrading what you already own

An i7-8700K or Ryzen 3600 with a GTX 1080 Ti or RTX 2070 still runs iRacing at 1080p and AMS2 at 1440p with settings turned down. It’ll struggle with ACC in rain and it won’t do VR well. If that’s your machine, the upgrade order is: SSD if you’re on a hard drive, then GPU if you’re moving to 1440p or triples, then CPU and motherboard together if iRacing stutters in big fields. Don’t upgrade the GPU first if your complaint is iRacing hitching at race starts. That’s the CPU, and a new card will do nothing for it. I watched a friend put a 4080 into a 3600 system for exactly this reason and he got the same stutter in prettier resolution.

FAQ

Can I run iRacing on a laptop? Yes, comfortably, at 1080p on anything with an RTX 3060 mobile or better and a modern six-core CPU. Expect throttling on long stints and be prepared for USB hub headaches with the wheelbase. iRacing’s own minimum spec is far below this, and technically true, but you won’t enjoy it.

Is 16GB of RAM enough for sim racing? For the sim alone, yes. For the sim plus Discord, Crew Chief, SimHub, and a browser, it’s borderline, and ACC in particular gets stuttery when Windows starts paging. 32GB of DDR5 costs about $30 more than 16GB. Just get it.

Do I need a 4090 or 5090 for VR sim racing? Not for a Quest 3 in iRacing or AMS2, where a 5070 Ti holds 90 fps with sensible settings. You need that class of card for ACC in VR at decent clarity, or for high-resolution headsets like the Pimax Crystal Light and Bigscreen Beyond. Match the card to the headset before you match it to the sim.

Buy this if, check this before you order

Build a 7800X3D, an RTX 5070 or RX 9070, 32GB of 6000MT/s DDR5, and a 1TB NVMe if you’re on a single monitor at 1440p and want all three sims to just work. Step the GPU up to a 5070 Ti or 9070 XT and the drive to 2TB if you’re planning triples or a Quest 3 within the year, because you will, and rebuying the card hurts.

Before you click order, go to your motherboard’s product page and count the rear USB ports. If it’s fewer than eight, pick a different board, no matter how good the price looks. And if you’re upgrading an existing PC because iRacing stutters at race starts, put the GPU back in the cart and price out an X3D chip instead. That’s the part that’s actually holding you back.