Borderlands 4 Still Stutters a Year After Launch: The Shader Cache Fix, the Lumen Cost, and the Patch That Made It Worse

A PC Gamer writer fixed Borderlands 4’s stuttering by raising their NVIDIA shader cache size to 100 GB, then said out loud what everyone was thinking: that is something you should not have to do in a well-optimized game. That single tweak, buried in a control panel most players never open, tells you almost everything about why a Borderlands 4 stutter fix is still one of the most searched troubleshooting queries a full year after the game shipped.

Borderlands 4 launched on Steam on September 12, 2025, built on Unreal Engine 5. Nearly twelve months later it still sits at a “Mixed” 62 percent user rating across more than 57,000 reviews, and the single loudest complaint in that pile is not the writing or the loot. It is performance: hitching, frame-time spikes, and a frame counter that reads high while the game feels like it is skipping. If you just picked it up in a sale, or came back for the DLC, here is what is actually happening and what to change first.

A year on, the frame counter still lies

The trap with Borderlands 4 is the same one that catches a lot of modern Unreal Engine 5 games. Your overlay shows 80 or 90 FPS, so you assume the problem is somewhere else, maybe your connection or your monitor. It usually is not. The average frame rate can look healthy while individual frames arrive unevenly, and your eyes read that unevenness as stutter no matter what the number says.

That distinction matters because it changes what you fix. Chasing a higher average frame rate does nothing for frame pacing. You can drop from 4K to 1080p, watch the counter jump, and still get the same lurch every time you sprint into a new zone. The work is in smoothing the spikes, not inflating the average.

I have spent 20-plus years in IT operations, and this is the same lesson that shows up in any performance investigation: the headline metric and the felt experience are two different measurements. A server can report 99 percent uptime and still feel broken to users during the one percent. Borderlands 4 is that gap in game form.

Why the game leans so hard on your hardware

Borderlands 4 is demanding in a way the cartoon art style hides. The official system requirements ask for an RTX 2070 with 8 GB of VRAM at minimum and an RTX 3080 with 32 GB of system RAM for the recommended tier. Those recommended specs are aimed at 1080p, not 4K, which is the first sign of how heavy the engine is.

The reason is that two of Unreal Engine 5’s most expensive features, Lumen for global illumination and Nanite for geometry, are baked into the game and cannot be turned off. You can lower Lumen, but you cannot remove it. That floor is why native performance falls short of 60 FPS on almost every card. CORSAIR’s benchmark run at native, high settings put an RTX 5090 at roughly 45 FPS at 4K, an RTX 4090 at about 36, and an RTX 3080 at a rough 19. Without upscaling, even a flagship struggles to hold a smooth 60.

The practical takeaway: upscaling is not optional here, it is part of the intended pipeline. DLSS, FSR, XeSS, or TSR are how the game is meant to be played, and turning them off to “see the real frames” just guarantees a worse experience.

The two kinds of stutter, and why the fix differs

Almost every Borderlands 4 hitch falls into one of two buckets, and they have completely different causes.

Shader compilation stutter happens when the game meets a visual effect it has not compiled yet: a new gun’s muzzle flash, a new enemy’s ability, a new material. A pipeline state object, the compiled bundle of shaders the GPU needs to draw that effect, gets built on the spot, and the frame freezes for a beat while it does. Epic has written openly about the fix for this, which is precaching those states ahead of time instead of mid-fight. This is why the game asks you to sit through a shader compilation step, and why skipping it or changing a graphics setting (which invalidates the cache) brings the stutter right back.

Traversal stutter is different. It shows up when you fast travel or sprint across the open world and the engine streams in new geometry, textures, and rooms. No amount of shader precompiling touches it, because it is a storage and memory problem, not a shader problem. This is the one a faster GPU cannot outrun.

Knowing which one you have tells you where to spend effort. If the hitch happens the first time you fight a new enemy type, that is shaders. If it happens every time you cross a zone boundary or fast travel, that is traversal. The same split shows up in every UE5 release, and the shader side responds to the exact habits that fixed Space Marine 2’s shader compilation stutter.

The shader cache fix Gearbox should not have needed

Back to that 100 GB number. The default NVIDIA shader cache size is far smaller, and Borderlands 4 generates so many pipeline states that it overruns the default and starts evicting cached shaders it will need again seconds later. The result is a game that recompiles the same effects over and over, stuttering each time, because it keeps throwing away work it already did.

The fix is blunt but effective. On an NVIDIA card, open the NVIDIA Control Panel, go to Manage 3D Settings, and set Shader Cache Size to 100 GB or Unlimited. On AMD, the equivalent lives in the Adrenalin software’s graphics settings. Give the cache room to hold everything the game throws at it, and the repeat recompilation stops.

Two caveats worth stating plainly. First, this eats disk space, so make sure the drive holding your cache has room. Second, if you have already been stuttering, clear the existing shader cache once through your GPU vendor’s tool before you enlarge it, so the game rebuilds cleanly rather than inheriting a corrupted set. Then let the compile step finish, all the way, before you judge anything.

The settings that actually buy frames

You do not need to gut the visuals. A handful of targeted changes recovers most of the headroom, and they follow a clear priority order because a few settings dominate the cost.

• Lighting or Global Illumination to Medium. This is the single biggest win, worth somewhere between 10 and 27 percent depending on the scene, because Lumen is the heaviest cost in the game. Never run it on the top tier.
• Reflections to Low. Double-digit gains for a difference you will not notice while you are shooting.
• Textures one tier below your VRAM ceiling. With 12 GB or more you can run Very High. With 8 GB, drop to Medium, because textures spilling past your VRAM is a direct cause of progressive frame-time decay.
• Shadows and Volumetric Fog to Medium. Both cost real frames at the top tiers and look nearly identical in motion.
• Upscaling on, set to Quality. Large GPU saving, modest sharpness cost. This is not the setting to be a purist about.
• Frame Generation only above a stable 60 FPS. Generated frames on top of an already choppy base make the hitching feel worse, not better. Confirm a smooth baseline first, then decide.

One more that saves a lot of grief: cap your frame rate a few frames below the lowest number your CPU sustains during heavy combat. A stable capped 55 feels better than a frame rate swinging between 45 and 80, since the pacing is even. If your hardware is on the edge, the same system-level tuning in the Windows 11 low latency profile breakdown stacks on top of these in-game changes.

The September patch that made it worse

Here is the part that turned a rough launch into a trust problem. On September 25, 2025, Gearbox shipped a patch specifically meant to improve stability and performance. For a chunk of players it did the opposite. Gearbox acknowledged it directly: “We’ve received reports from some players that, although the September 25th patch is intended to improve performance, they’re experiencing the opposite,” per Notebookcheck’s coverage of the backfire.

Two useful things came out of that mess. Gearbox told players to give shaders a full 15 minutes to compile in the background after the update before judging performance, and to clear the shader cache if stuttering persisted past that. And they explicitly advised against the top “Badass” graphics preset, which hammers frame rates on high-end systems for almost no visual gain over Very High. That preset is a trap. Skip it.

The broader lesson is one every PC gamer should internalize: a patch is not automatically an upgrade. If your game got worse right after an update, the update is a suspect, and the same goes for GPU drivers. When stutter or crashes start immediately after a driver install rather than a game patch, roll the driver back before you blame the game, which is the exact logic behind the NVIDIA 610 driver stutter fixes from earlier this year.

When it is your connection, not the game

Everything above is local. Shader compilation, traversal streaming, VRAM overruns, the Lumen cost: those all live on your PC, and no network tool on earth will smooth them out. I would rather say that plainly than sell you a connection fix for a rendering problem.

But Borderlands 4 has a real online layer. It runs drop-in co-op across the whole campaign, and that is where a second, separate class of problem lives. If your frame pacing is fine but your co-op partner is rubber-banding, enemies teleport, or your shots register late in a shared session, that is not stutter, that is latency. That lives on the route between you and the session host, and it responds to completely different fixes than the ones above. Our guide on why your ping is high and how to actually drop it walks through diagnosing that side properly, and clearing out the background apps quietly eating your bandwidth and frames helps on both fronts at once.

This is the honest split. Local stutter, fix it with settings and the shader cache. Online lag in co-op, fix it at the network layer. A service like WTFast belongs in that second category: it reroutes your game traffic across a private network of optimized relays, and on a bad ISP path it can shave real milliseconds and smooth out packet loss between you and your friends’ sessions. It will do nothing for a Lumen frame spike, but for genuine co-op latency it is the fastest thing to test.

What to change before your next session

Set the shader cache to 100 GB or Unlimited, clear the old one first, and let the compile step finish without skipping it. Drop Lighting and Reflections, keep textures within your VRAM budget, leave upscaling on Quality, and cap your frame rate a few frames under your combat floor. Stay off the Badass preset. Keep the game on your fastest SSD so traversal streaming has the bandwidth it needs, and close the memory-hungry apps in the background before you launch.

Do that, and Borderlands 4 goes from “high FPS that feels broken” to something that actually plays as smooth as the counter claims. The frames were mostly there the whole time. A year later, the pacing is still the part you have to fix yourself, and now you know exactly which levers move it.