Skip to content
Power Up Gaming

How GTA 3 Hit 30fps With a Trick Crash Bandicoot Fans Will Recognise

Illustration of GTA 3’s Claude and Crash Bandicoot against city and jungle environments with wireframe graphics.

Rockstar’s Grand Theft Auto III nearly had to settle for 20 frames per second before a last-minute rendering trick helped push it to 30fps – using a principle that also helped Naughty Dog work wonders with Crash Bandicoot.

Former technical director Obbe Vermeij has explained how Liberty City was wasting processing power drawing cars and buildings hidden behind other buildings. Fixing that problem helped the team reach 30fps just weeks before development finished.

Speaking to MattJ155 in an interview marking GTA 3’s 25th anniversary, Vermeij recalled how uncertain that target had been.

“For the longest time it looked like it was going to be 20, that we were not even going to make 30,” he said.

GTA 3 was rendering an entire view behind a wall

The problem becomes easy to picture when you imagine standing directly in front of one of Liberty City’s buildings.

The wall blocks your view. Behind it might be another street, several cars and more buildings. You cannot see any of them, but the game was still spending resources rendering them.

“If you’re like in front of a building and you look in the direction of the building, it would still render everything behind it, like the cars and the buildings behind it,” Vermeij explained.

His solution was a system that divided the world into blocks and recognised when objects were obscured, allowing the game to skip drawing them.

The principle is known as occlusion culling. If a solid building completely conceals a car, drawing that car contributes nothing to the picture the player sees. Identifying that obstruction lets the engine avoid unnecessary rendering work.

This was not simply a matter of reducing the draw distance or stripping detail out of Liberty City. The visible scene could remain intact while the game stopped drawing objects hidden behind it.

Vermeij recalled implementing the system during the final month, or possibly the last couple of weeks, before GTA 3 went gold.

“That was actually the thing that took it from 20 to 30,” he said.

He also credited fellow technical director Adam Fowler with most of the rendering work, including handling RenderWare, models, loading and streaming. His own system tackled a particular source of wasted processing at a crucial moment.

Naughty Dog used a similar principle for Crash Bandicoot

The explanation echoes the visibility tricks behind Crash Bandicoot on the original PlayStation.

As co-creator Andy Gavin explained in his development retrospective, Naughty Dog used controlled camera paths to calculate visibility ahead of time. Trees, cliffs, walls and bends concealed sections of the levels, allowing the game to present detailed environments without rendering everything at once.

Crash programmer Dave Baggett later described how the team calculated views along those camera paths on its development workstations. The PlayStation could then skip polygons already known to be hidden.

The implementations differed: Crash exploited its carefully controlled camera, while Vermeij describes a block-based system for GTA 3’s freely explorable city. But the underlying saving was similar: avoid spending precious rendering time on things the player cannot see.

For Rockstar, that saving arrived at the end of a development process Vermeij remembers as frequently unstable. Elsewhere in the interview, he recalled crashes interrupting missions and frame rates even dropping into single figures while the game was being built.

The finished classics still inspire technical experiments, including a mod that runs Vice City inside GTA 3, which itself runs inside San Andreas. Getting the original GTA 3 ready for players, however, required the team to squeeze out every bit of performance it could.

By Vermeij’s account, one of the decisive improvements came from work players would never notice directly: teaching Liberty City’s buildings to hide what was behind them.