Massive iRacing Load Times After an Update? Here's What Happened

Introduction

There's nothing quite like finishing an iRacing update, jumping into a session, and being greeted by an endless loading screen. Especially when you've just registered for a race, and qualifying starts in 2 minutes time.

This was the situation we recently found ourselves in. What would normally be a quick transition into a race session suddenly became a wait of several minutes, and by several, we mean like 10 minutes. The iRacing loading screen just wouldn't budge.

The worst part? Nothing had changed on the hardware side. The system had been running flawlessly for months and race sessions would normally load in just a minute or so.

As it turns out, the culprit wasn't our CPU, GPU, SSD, or internet connection. It was something far less obvious: iRacing rebuilding its caches after a major update.

The Symptoms

Immediately after updating iRacing, we noticed:

• Session load times had increased dramatically
• Car and track combinations that previously loaded in under a minute now took significantly longer
• CPU usage appeared normal - was not maxing out or causing bottle-necking
• The active time on the SSD we exclusively use for iRacing was maxed out at 100%, continuously

Naturally, the first assumption was that something had broken.

We checked Windows updates.

We checked graphics drivers.

We checked SSD performance.

We even considered whether a recent hardware change was responsible.

Nothing looked out of place.

Chasing The Wrong Problem

Like many sim racers, our first reaction was to assume the latest update had introduced a performance bug.

Forums started filling with similar reports:

"Loading takes forever."

"Is anybody else's sim hanging at 15%?"

"My PC was fine yesterday."

When enough people experience an issue simultaneously, it's easy to conclude that the update itself is fundamentally broken.

But there was a clue hiding in plain sight.

Most users reported that load times improved after a few launches.

What Was Actually Happening?

iRacing maintains various shader and content caches to speed up loading and improve performance.

Following significant updates, these caches can become invalid or require rebuilding.

When that happens, iRacing effectively needs to regenerate large amounts of data before it can efficiently load content again.

The result is that:

• The first load of a car or track combination can take significantly longer.
• CPU utilisation can spike while data is processed.
• Session loading appears stalled even though work is occurring in the background.
• Subsequent loads become progressively faster.

In other words, the simulator isn't necessarily broken—it's simply rebuilding information it can no longer use from previous versions.

The Fix

Fortunately, the solution was surprisingly simple.

We stopped troubleshooting and started waiting.

After allowing several sessions to fully load, performance gradually returned to normal.

No reinstall was required.

No hardware upgrades were required.

No tweaking Windows settings.

No deleting random folders recommended by strangers on the internet.

Just patience.

In some cases, manually clearing iRacing's cache folders can help if the rebuild process becomes corrupted, but for most users the simulator simply needs time to regenerate its data.

Why Modern PCs Can Make This More Noticeable

Ironically, high-end systems can make the problem feel even worse.

When you're used to loading into a session in 20 to 30 seconds, waiting several minutes feels catastrophic.

The contrast is dramatic.

For newer iRacing users who haven't experienced a large cache rebuild before, it can easily look like the update has broken something major.

Lessons Learned

This experience was a reminder that not every performance issue requires immediate troubleshooting.

When a major iRacing update lands and load times suddenly explode:

1. Don't panic.
2. Let sessions fully load.
3. Try the same content a second or third time.
4. Monitor whether load times improve.
5. Leave the reinstall button alone for a while.

Sometimes the simulator is simply doing housekeeping behind the scenes.

Final Thoughts

As sim racers, we're conditioned to chase tenths of a second and optimise every detail of our setups. So when something suddenly slows down, our instinct is to start hunting for a fix.

In this case, the fix wasn't a registry tweak, a new driver, or an upgraded SSD.

It was understanding what iRacing was doing in the background and letting it finish the job.

The next time an update turns your loading screen into an endurance event, remember: it might just be the cache rebuilding itself.

And unlike many sim racing problems, this one usually solves itself.