Forty miles of rolling countryside: flawless. Sixty frames, silent fan, not a care in the world. Then you walk through the city gates and the whole thing folds like a deckchair.
This is so consistent across so many games that it stops being a bug and starts being a law of nature. Here is what is actually happening.
A field is cheap. A city is a spreadsheet.
A hillside is, computationally, a lovely thing. It is one big mesh, a couple of textures, some grass drawn by a clever shader, and nothing on it has opinions. Your graphics card eats that for breakfast.
A city is a different category of object entirely:
- Hundreds of distinct meshes — buildings, signs, railings, crates, market stalls, all separate
- Hundreds of distinct textures, because variety is the entire point of a city
- Dozens of NPCs, each running pathfinding, animation, and a schedule
- Dynamic lights — every lamp, window and sign, each with a cost
- Interiors loaded or streamed in case you open a door
- Audio sources everywhere, each needing to be mixed and positioned
The countryside asks the machine to draw something big. The city asks it to keep track of an enormous number of small things that all change.
It is your CPU, not your graphics card
This is the part that surprises people, and it is why upgrading a GPU so often fails to fix it.
Every distinct object needs a draw call — the CPU telling the GPU "render this thing, here, with this material". The GPU is extraordinarily fast at drawing. The CPU issuing thousands of individual instructions per frame is the bottleneck, and that work is stubbornly hard to parallelise.
So the pattern is: GPU sitting at 50% utilisation, one CPU core pinned at 100%, frame rate on the floor. Which is exactly the signature of a game that has run out of ability to describe the scene rather than draw it.
Then add the things only cities do: NPC pathfinding, hundreds of animation blends, physics on debris, and the streaming system frantically loading assets as you walk because you might turn any corner.
The stutter is a different problem from the low frame rate
Worth separating, because the fixes differ.
A consistently lower frame rate in a city is the CPU work above. It is steady, predictable, and it settles.
Stutter — a smooth run interrupted by a hard hitch every few seconds — is usually one of two things. Either the streaming system fetching assets off the disk in time for you to see them, or shader compilation: the game encountering a visual effect it has not prepared and stopping the world to build it, right at the moment you first see it.
The second is why so many PC games stutter horribly for the first hour and behave afterwards. It is also why "shader compilation" progress bars started appearing on launch screens — studios eventually accepted that doing it upfront, once, is better than ambushing the player mid-fight.
What actually helps
Setting-wise, the useful moves are the ones that reduce the number of things, not the prettiness of each thing:
- Crowd density / NPC count — the single most effective city setting where it exists. Fewer people is fewer everything.
- Draw distance / level of detail — decides how many objects exist at once, which is precisely the problem
- Shadow quality — every dynamic light casting shadows multiplies work; in a city that multiplication is enormous
- Volumetric lighting — expensive, and cities are full of it
Turning down textures, by contrast, does almost nothing for a CPU bottleneck. You are treating the wrong organ.
Hardware-wise: an SSD helps the streaming stutter genuinely and dramatically. More RAM helps if you were swapping. A faster CPU with strong single-core performance helps. A better graphics card, for this specific problem, frequently helps not at all — which is an expensive lesson people keep buying.
Why studios ship it anyway
Because a city is where the game is. It is where the quests, shops, characters and atmosphere live, and no amount of beautifully performant meadow substitutes for it. Given a choice between a dense, alive city that runs at 45fps and an empty one that runs at 60, most players want the former, and studios know it.
The honest criticism is not that cities are expensive — it is that so many games are tuned and demoed in the countryside, then ship with a city nobody profiled properly.
The diagnosis, in one test
Open a performance overlay and walk into town. If GPU usage drops while the frame rate falls, you are CPU-bound: reduce crowd density and draw distance, and stop adjusting textures. If GPU usage stays pinned at 99%, it is genuinely a graphics load, and the usual settings apply.
Ninety percent of the time, in a city, it is the first one.