Mark Brown rewrites GTA 3 code to show Liberty City streaming magic

Mark Brown’s source-code rewrite turns GTA 3’s invisible streaming into something you can actually watch, and it shows just how hard Liberty City had to work to fit inside PlayStation 2 limits.

The trick was never raw power

The first thing this teardown makes clear is that GTA III was built on a trick, not a miracle. The PlayStation 2 only had 32 MB of main memory, yet Liberty City’s assets came in at roughly 130 MB, which meant the entire world could never live in RAM at once. Rockstar North’s answer was to make the city feel continuous while constantly loading and unloading pieces behind the scenes.

That is why Brown’s rewrite matters so much to a modern audience. He did not just describe the system, he rebuilt parts of the code so the streaming could be seen, with nearby chunks of the city appearing and disappearing as the camera moved. For anyone used to thinking of GTA III as simply the moment the series went 3D, this is the more useful lens: it was also a lesson in how to fake scale under brutal memory constraints.

How Liberty City was split apart

Rockstar North’s solution started with division. Liberty City was broken into three separately loaded islands, then each island was subdivided into thousands of smaller sectors so the game could keep only the relevant pieces in memory near Claude. That kind of partitioning is the foundation of the whole system, because it lets the engine decide what the player can actually see, rather than pretending the whole city exists at once.

Even the opening island, Portland, was no small job. Yahoo Tech’s summary says it still needed about 40 MB to 50 MB of assets on its own, which is already larger than the PS2’s total memory budget for the game. The point is not just that the map was large, but that Rockstar had to slice it with surgical precision so the player could move through a city-scale space without ever seeing the machinery working too obviously.

Why the pop-in was easier to hide than it looks

The rebuilt demo is useful because it reveals the tradeoffs that made the illusion hold together. As the camera shifts, nearby sectors pop into view and then disappear again, which sounds crude until you remember the alternative was running out of memory entirely. The engine also leaned on lower-detail assets at distance, so objects could fade into the world instead of violently snapping in and out at full fidelity.

That is one of the reasons GTA III still rewards technical scrutiny. The game was not trying to render a perfect simulation of Liberty City at all times, it was trying to preserve the feeling of a living city while ruthlessly managing what the hardware could afford. Brown’s breakdown makes that engineering visible, and once you can see the seams, the achievement gets bigger, not smaller.

The launch context makes the feat even sharper. GTA III arrived on PlayStation 2 on October 22, 2001, was developed by DMA Design, later Rockstar North, and published by Rockstar Games. It was the first fully 3D entry in the series, and that shift is inseparable from the streaming solution that made the world feel vast enough to matter.

Why this still matters to modders and reverse engineers

For reverse engineers, the value here is in the method. Brown’s rewrite is a reminder that game worlds are not just art pipelines and mission scripts, they are memory maps, loading rules, and visibility systems built to survive hard limits. If you want to understand how an open world really works, you start by asking what gets loaded, when it gets unloaded, and how the engine keeps the player from noticing the handoff.

That is also why GTA III remains such an important reference point for modders. A city that had to be assembled from sectors, islands, and lower-detail fallbacks is a perfect case study for how to think about performance before you add anything else. It is the kind of design that teaches discipline, because every extra object, texture, and draw distance problem has to justify the memory it consumes.

The broader series history gives the same lesson in another form. Rockstar later returned to Liberty City with Liberty City Stories, showing how much the setting still mattered after the original PS2 breakthrough. The official GTA III page still describes Liberty City as a massive and diverse open world, and that phrasing makes sense only because the original game solved the storage problem so effectively that the city could feel much larger than the hardware should have allowed.

A landmark that still reads like engineering

Even the commercial scale underlines how important that solution was. One long-running series account says GTA III sold 6 million units in one year, which helps explain why this streaming model became so influential beyond one game. The success was not just about crime sandbox freedom, it was about proving that a dense open world could run within severe technical limits and still feel alive.

That is the real value of Brown’s teardown. It takes Liberty City out of the realm of legend and puts it back into the realm of systems, where sectors, islands, memory budgets, and low-detail fallbacks do the heavy lifting. GTA III still matters because it showed how to make an open world feel bigger than the machine that powers it, and Liberty City’s streaming magic is still one of the cleanest examples of that trick ever shipped.