Open World Stutter — Traversal, Streaming and City Slowdowns
Smooth in the countryside, terrible in the city. That is a specific, diagnosable problem with specific fixes.
The short answer
Open world games slow down in cities because the CPU must process far more entities, draw calls and streaming requests, making dense areas CPU bound where open terrain is GPU bound. Traversal stutter, where the game hitches while moving quickly between areas, is caused by asset streaming from storage and is best addressed by moving the game to a fast SSD and increasing any streaming or texture pool setting available.
Verified and last updated August 12, 2026.
- Time needed
- 20 min
- Difficulty
- Intermediate
- Read time
- 4 min
Open world performance problems have a specific signature that makes them easy to identify: the game is fine until you go somewhere busy.
That is not a general performance problem. It is one of two specific ones.
Two problems, two fixes
City slowdown — sustained lower frame rate in dense areas. CPU bound. Graphics settings barely help. Traversal stutter — hitching while moving fast. Storage bound. An SSD and streaming settings help enormously. They are unrelated and people conflate them constantly.
Step 1: Two different problems
The test is simple: stand still in the city. If the frame rate is still low, that is city slowdown. If it recovers and only drops while moving, that is traversal.
Step 2: Traversal stutter is a storage problem
Move the game to your fastest drive 30 min
This is the single largest fix. An open world game streaming from a mechanical drive will hitch constantly and no setting compensates.
Raise the texture or streaming pool setting 10 min
If the game exposes one and you have spare VRAM. A larger pool keeps more assets resident so fewer need streaming. Raise in steps and watch VRAM usage — exceeding it causes the opposite problem.
Free space on the drive 10 min
A nearly full SSD writes and reads more slowly, and streaming is sensitive to that.
Stop other disk activity while playing 5 min
Downloads, backups, antivirus scans and shader compilation all compete for the same disk the game is streaming from.
Step 3: City slowdown is a CPU problem
The counter-intuitive part: graphics settings are largely the wrong lever.
Population density is the setting. It changes how the world feels, which some people mind, but it addresses the actual bottleneck rather than working around it.
The diagnostic that confirms everything: lower your resolution dramatically. If the city frame rate barely improves, you are CPU bound and no graphics setting will help.
The supporting fixes
Close background applications. A CPU-bound game has no spare cores for a browser.
Check for a frame rate cap in the wrong place. Some open world games have internal caps that interact badly with external limiters.
Disable overlays. They add CPU work in a game that has none to spare.
Verify the CPU is not thermally limited. A city is sustained heavy load, so this is where throttling appears first.
What works
What doesn't
Key takeaways
Frequently asked questions
Why is my frame rate fine in the countryside and bad in the city?
Because those are different workloads. Open terrain is mostly GPU work rendering distance and vegetation, while a city is mostly CPU work processing pedestrians, vehicles, traffic logic and vastly more draw calls. A city drop is a CPU limit, which is why lowering graphics settings barely helps and why a faster graphics card does not fix it.
What is traversal stutter?
A hitch that occurs while moving quickly through the world, caused by the game loading new assets from storage as you enter areas. It is distinguishable from other stutter by its correlation with movement speed — driving fast produces it and standing still does not. It is fundamentally a storage and streaming problem rather than a rendering one.
Does an SSD fix open world stutter?
It substantially reduces traversal stutter, which is the movement-related kind, because asset streaming is disk-bound. It does very little for city slowdown, which is CPU-bound. This is why some people report an SSD transforming their experience and others report no change — they had different problems.
Should I increase the texture or streaming pool setting?
If the game exposes one and you have spare VRAM, yes. A larger pool keeps more assets resident in memory so fewer need streaming from disk, which directly reduces traversal hitching. Setting it beyond your available VRAM causes the opposite problem, so raise it in steps and watch VRAM usage rather than setting it to maximum.
Does population density setting help?
Considerably, and it is the most effective single setting for city slowdown. Pedestrian and traffic density are pure CPU cost, and reducing them cuts entity processing directly. It changes the feel of the world, which some people mind, but it addresses the actual bottleneck rather than working around it.
About the author
PC Hardware & Performance Editor
Marcus has been building, breaking and repairing gaming PCs since 2011, first as a weekend favour for friends and then for eight years as a bench technician at an independent repair shop in Portland, where roughly a third of the job was diagnosing machines that "ran fine yesterday".
Found something wrong? Games patch and fixes go stale. If a step here no longer works, tell us at hello@spyld.com and we will retest it. Read how we test and our editorial policy.