Open World Settings: Why Cities Tank Your Frame Rate
Population density, draw distance and traffic settings cost more than graphics quality in open world games. Here is the order to cut them.
The short answer
Frame rate drops in open world cities are usually caused by CPU-bound settings such as population density, traffic density and draw distance rather than by graphics quality settings. Lowering density sliders recovers far more performance in urban areas than reducing texture or shadow quality does. Identifying whether your drops are CPU or GPU bound determines which set of settings to touch.
Verified and last updated August 12, 2026.
- Time needed
- 15 min
- Difficulty
- Intermediate
- Read time
- 3 min
I spent an embarrassing amount of time lowering shadow quality to fix frame drops in a city, and it never worked. It never worked because shadows were not the problem.
Cities are a processor problem. Every pedestrian is a state machine. Every car has a driver. Every shop has scripts. All of that happens before the graphics card draws a single frame.
Check GPU utilisation during the drop
If the GPU is below full while your frame rate tanks, graphics settings are irrelevant. The processor is the bottleneck and only CPU-side settings will help.
Which settings cost what
The order to cut
If your GPU is not pinned during the drops, work down this list and stop when you are happy:
- Population density — to around half. The city still feels alive; the CPU load drops sharply.
- Traffic density — same treatment. This is often the single biggest win.
- Draw distance — one step down. Distant detail you rarely look at.
- Detail distance — one step down. Controls when high-detail models swap in.
- Shadow distance, distinct from shadow quality, which is CPU-adjacent in many engines.
Only after all of that should you touch quality settings, and only if the GPU is actually the limit.
The frame cap that helps
Open world games have a wide performance range: 120 frames per second in the countryside, 55 in the city centre. That swing is more uncomfortable than a lower stable number.
Cap to something you can hold in the worst area. If the city centre gives you 60, cap at 58 or 60 rather than letting it swing from 120. Consistency reads as smoothness far more than peak frame rate does.
Find your worst-case number 10 minutes
Drive through the densest part of the map at your normal settings and note the lowest sustained frame rate. Set an external cap slightly below that with a frame limiter. The countryside will feel identical and the city will stop lurching.
Streaming stutter is a separate problem
If the drop is a brief hitch while moving fast rather than a sustained low frame rate, that is asset streaming rather than density.
Causes and fixes:
- Storage speed — an SSD is close to mandatory for modern open world titles
- Streaming or memory budget settings — some games expose these; set them a few GB below total VRAM
- Shader compilation — the first traversal through a new area, resolves on subsequent runs
The stuttering guide separates these signatures properly if you are unsure which you have.
What works
What doesn't
Key takeaways
Frequently asked questions
Why does my frame rate only drop in cities?
Because cities are a CPU problem, not a GPU one. Every pedestrian, vehicle and active script is work the processor does before the graphics card renders anything. In open countryside there is little of that, so the GPU becomes the limit and frame rates recover. Graphics settings barely affect the city case.
Which setting recovers the most performance?
Population and traffic density, by a wide margin, in any game that exposes them. Reducing pedestrian and vehicle counts removes CPU work directly. Draw distance is next, because it determines how much of the world is simulated and streamed at once. Both of these outrank every graphics quality setting in urban areas.
How do I know if I am CPU or GPU bound?
Watch GPU utilisation while the drop happens. If it sits well below full during the stutter, the processor is the limit and graphics settings will not help. If it is pinned at full, the graphics card is the limit and quality settings will. This single check determines which half of the settings menu is relevant.
Does more RAM help in open world games?
It helps up to the point where you are not swapping, and beyond that it does not. Open world games are memory-hungry and 16GB is the practical floor in 2026, with 32GB comfortable for heavily modded installs. Adding memory beyond what the game uses changes nothing.
About the author
Competitive & Settings Editor
Dan played CS:GO semi-professionally in a regional ESEA Main roster between 2017 and 2020, and has hit Radiant in VALORANT in three separate acts. He now spends most of his competitive energy on the unglamorous side of the game: input latency, sensitivity consistency and warm-up routines that actually transfer.
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.