Driver: San Francisco Review — DriveVision Makes Crashing Feel Like a Feature

Driver: San Francisco is a game about losing control, and it makes that loss feel thrilling rather than punishing. Developed by Ubisoft Reflections and published by Ubisoft, the 2011 action racer drops players into a city full of cars, and it asks them to take over the minds of other drivers mid-race. That twist, called DriveVision, is the whole reason to play. It works.

The premise is simple on paper. You drive a car, you crash, you wake up in a hospital bed, and then you start taking over the bodies of other characters. The game calls this a “dream state,” and it is the engine that drives the entire experience. Instead of loading a checkpoint, you jump into someone else’s vehicle and keep moving. It sounds gimmicky, and it is, but it is also the rare idea that actually delivers.

Trailer, via moviemaniacsDE.

DriveVision and the Dream State

DriveVision is the star of Driver: San Francisco. When you hit a wall, a pedestrian, or a police car, you stop controlling your own body and start controlling someone else’s. The transition happens in seconds, and it changes the feel of every chase sequence. One minute you are sliding sideways through traffic, the next you are speeding down a highway in a stranger’s sports car.

The mechanic rewards risk. The faster you drive, the more likely you are to lose control, and the more likely you are to need DriveVision. So the game pushes you toward the edge of the road, and the edge is where the fun happens. It is a clever way to make a racing game feel less like a test of patience and more like a test of nerve.

The dream state is not just a novelty. It shapes the level design. Roads are built with moments where the player must take over another driver to avoid a wreck, and the game leans into that structure. Chases become a chain of decisions: crash here, take over there, repeat. It is a loop that rarely grows stale.

The City and Its Chase Routes

San Francisco itself is the second lead in this story. The game renders the city as a dense network of streets, bridges, and tunnels, and it asks players to know them well. The map is large enough to support multiple routes between points, but it is also tight enough that a wrong turn can cost you dearly.

Chase sequences are the heart of the game, and they are built around momentum. A successful pursuit feels like a wave of energy that carries you forward, while a failed one sends you careening into a wall. The controls respond quickly, and the game never slows down to explain itself. You learn through repetition, and that repetition is satisfying rather than tedious.

The presentation is solid for its time. The graphics hold up well, and the lighting on the Golden Gate Bridge and the Bay Area skyline is particularly strong. The sound design supports the action, with engines roaring and tires squealing at the right moments. It is a polished package that backs up its ambition with technical execution.

Story and Characters

The story follows John Tanner, a cop who crashes his car during a chase and wakes up in a hospital bed, unable to move his own body. He discovers that he can take over the minds of others, and he uses that power to hunt down the criminals who framed him. The plot is pulpy, but it gives the game a reason to exist beyond the mechanics.

The characters are memorable. Tanner is a gruff, sarcastic veteran, and his interactions with the people he takes over add a layer of humor to the proceedings. The villains are cartoonishly evil, and their schemes are easy to follow even when the plot drags. The pacing is uneven, with some missions feeling rushed and others feeling padded, but the core loop remains strong throughout.

The game also includes a handful of side activities, including driving challenges and collectibles. These are optional, but they extend the playtime without diluting the main experience. They are a nice touch, though they are not essential to the overall journey.

Comparing the Platforms

Driver: San Francisco released on three platforms: PlayStation 3, Wii, and PC. The PC version offers the best performance, followed by the PS3 version, with the Wii version lagging behind. The differences are not dramatic, but they matter for anyone considering which version to buy.

The Wii version is the weakest link. It runs at a lower frame rate and suffers from input lag, which makes the DriveVision mechanic less effective. Anyone who wants the full experience should avoid the Wii version and look at the other two.

The Schedule of a Typical Session

A typical session of Driver: San Francisco follows a familiar pattern. Players spend the early minutes learning the roads and the controls, then they dive into a chase, take over a few drivers, and finally complete the objective. The game is designed for short bursts of play, and it rewards players who return regularly.

Here is a rough breakdown of a standard session:

The schedule is flexible. Players can skip the warm-up entirely and jump straight into a chase, but the game is at its best when you take your time and let the city breathe.

Final Word

Driver: San Francisco is a bold experiment that mostly pays off. The DriveVision mechanic is a genuine innovation, and it transforms a standard racing game into something far more interesting. The city is a joy to drive through, and the chases are tense and rewarding. The story is thin, and the Wii version is weak, but those flaws are minor compared to the strengths.

The game is a reminder that video games do not need to follow the same rules as movies or books. A chase sequence can be a puzzle, a rhythm, and a thrill all at once, and Driver: San Francisco proves it. It is a game about being somewhere else, and it makes that feeling feel real.

Driver: San Francisco earns its reputation as a standout entry in the series. It is a game that rewards curiosity and punishes hesitation, and it does both with style. The final score reflects that balance: 8.2 out of 10.

2011 games · Driver San Francisco · game review · racing games · Ubisoft