You’re cruising through a big open world, the FPS counter reads a healthy 120, and then you sprint over a hill or cross into a new district and the whole game hitches for a split second. Your frame rate looks fine on paper, but it sure doesn’t feel fine.
That specific kind of hitch has a name. It’s called traversal stutter, and it’s one of the most common complaints in modern open world games.
A lot of it comes down to how your system streams data, and you have real levers to pull. Here’s what’s actually happening and how to make it smoother.
What traversal stutter actually is
Traversal stutter is a streaming problem. As you move through a large world, the game engine loads new geometry, textures, and logic off your drive, decompresses it, and hands it to your GPU.
All of that has to happen fast enough to keep up with your movement. If any link in that chain is too slow, the main thread waits, and that pause is the freeze you feel.
This is why open world games hitch at zone boundaries and while sprinting, but a linear corridor shooter almost never does. The corridor game already has everything it needs loaded.
It also explains why the problem shows up even on strong hardware. A fast GPU can’t help if it’s sitting idle waiting for data to arrive.
How to tell it’s traversal stutter and not something else
Before you start changing things, make sure you’re chasing the right problem. Stutter comes in a few flavors, and each one has a different fix.
Traversal stutter happens when you move. You’ll notice it crossing into new areas, fast traveling, or sprinting across the map, and it tends to land in the same spots every time.
Shader compilation stutter is different. It shows up early in a fresh install or right after a game update, then fades as the game builds its shaders. If that sounds more like your issue, our guide on how to reduce shader compilation stutter covers it.
A quick way to check is to watch your GPU usage during a hitch. If GPU usage suddenly drops while the frame freezes, your system is waiting on data, which points straight at streaming.
For a wider look at every common cause, our guide to fixing stutter on a good PC is a solid companion piece.
Put the game on your fastest drive
This is the single biggest fix for most people. Traversal stutter is mostly a storage to memory issue, so the speed of your drive matters a lot.
If your game lives on a traditional hard drive, stutter is basically guaranteed in any modern open world. An HDD can’t feed assets fast enough as you move.
Moving the game to a SATA SSD is a massive jump, and an NVMe SSD is faster still for streaming-heavy titles. Most modern games now expect an SSD at minimum.
One easy thing people miss is keeping the drive from filling up. An SSD past 90% full slows down, so leave at least 10 to 15 percent free.
You don’t need to chase the newest Gen5 drive for this. The jump from HDD to any SSD is the part that actually moves the needle on stutter.
Cap your frame rate, even though it sounds backwards
This is the fix that surprises people, because lowering your frame rate to solve a smoothness problem feels wrong. It works because of how much time each frame gives the engine to stream.
At a high frame rate, each frame has very little time before the next one is due.
At a locked 60 or even 30 FPS, each frame gets a longer window, which gives your drive enough time to load the next chunk without forcing a pause.
A stable capped frame rate almost always feels smoother than a number that swings wildly between 90 and 140.
For the cleanest frame pacing, use a single external limiter like RTSS rather than stacking several caps at once. Our walkthrough on how to cap FPS without VSync shows the setup.
Try a cap a notch below what your system holds steady, then test the same trouble spots. If the hitches shrink, you’ve found your culprit.
Add more RAM and run it at its rated speed
Open world games lean hard on memory, and 16GB is now a common bottleneck. When RAM runs short, your system starts shuffling data around, and that shows up as hitching.
Moving to 32GB gives streaming far more breathing room and is one of the better upgrades for this exact issue.
Capacity isn’t the whole story, though. Plenty of people install fast RAM and never turn on XMP or EXPO, so it quietly runs at slow default speeds.
Hop into your BIOS, enable your memory’s rated profile, and you’ll get the speed you actually paid for. This won’t touch shader stutter, but it helps with streaming hitches.
Turn down the settings that hammer streaming
You don’t have to gut your visuals, but a few settings put real pressure on streaming. Dialing these back often clears up most of the hitching.
The usual suspects are texture streaming, view distance, foliage, and shadows. These control how much new data the engine has to pull in as you move.
Dropping view distance and foliage to medium tends to give the biggest smoothness win for the smallest visual cost. The game has less to load the moment you round a corner.
If your game has a texture streaming or texture pool setting, experiment with it. Lowering it can reduce hitching on cards with less VRAM, while raising it can help if you’ve got VRAM to spare.
Engine.ini tweaks for Unreal Engine games
Here’s the big one, because a huge share of stuttery open worlds run on Unreal Engine 4 or 5. Many of them let you adjust streaming behavior through a config file.
You’ll find it at a path like %localappdata%\[GameName]\Saved\Config\Windows, where that last folder might be WindowsNoEditor or WinGDK depending on the game. Open Engine.ini in Notepad to edit it.
Back up the file first by copying it somewhere safe. That way a bad edit is a quick undo instead of a headache.
The tweaks worth trying adjust texture pool size and asset streaming, nudging the engine to load data more aggressively so it’s ready before you need it. Exact values vary by game, so look for a tested config for your specific title.
Two cautions before you dive in. Some commands can cause crashes or get ignored, so add changes a few at a time and test between each batch.
Many games also overwrite this file on launch. Once your edits work, set the file to read-only in its Properties so they stick.
Clear out the background clutter
Some traversal stutter isn’t the game at all. It’s other software grabbing resources at the wrong moment, and these fixes are quick wins.
Background downloads and updaters are a classic offender. A launcher quietly patching another game can spike your drive usage right when you need it for streaming.
Overlays from various apps can interfere with frame pacing too, so try disabling the ones you don’t use.
The same goes for a power plan that parks your CPU cores, which can cause hitches as cores wake back up.
It’s also worth checking Windows Game Mode, which can help by holding back background activity while you play. Our breakdown on whether Game Mode helps walks through when to leave it on.
When it’s the game’s fault
Sometimes you’ll do everything right and still hit the occasional freeze. A portion of traversal stutter is baked into the engine and the game’s design, and there’s a limit to what you can fix from your end.
When that’s the case, game patches matter. Developers regularly improve streaming after launch, so keeping the game updated is part of the fix.
One thing that won’t save you is frame generation.
It boosts your displayed frame rate, but it doesn’t touch the underlying streaming hitch and can make uneven pacing more obvious. Our explainer on what frame generation does covers why.
Work through the drive, frame cap, RAM, and settings fixes first, since those clear up the bulk of it.
Tackle the engine tweaks if you want to push further, and you’ll get most open worlds running far smoother than they did out of the box.