You know what’s funny? I spent forty years thinking racing games were just cars going around in circles, maybe because the only exposure I had was watching other people play them for five minutes here and there. Then I discovered retro gaming in my forties and started working backwards through all these classics everyone kept talking about. San Francisco Rush on the N64 wasn’t even on my radar initially – my daughter had mentioned it once as “that crazy jumping car game” but honestly, I was more focused on the RPGs and platformers everyone said I absolutely had to experience.
Found my copy at a local game shop in Denver, tucked between some sports games nobody wanted. Twenty bucks. The guy behind the counter – probably in his thirties, definitely someone who’d played this as a kid – got this nostalgic look when he saw what I was buying. “Oh man, Rush! You’re gonna love the shortcuts.” I nodded politely, figuring he was just being friendly, but I had no idea what he meant by shortcuts in a racing game. Aren’t you supposed to just…follow the track?
Loaded it up that evening after work, still in my work boots because I was too eager to try it out properly. The first thing that hit me wasn’t the graphics or the music – though both were pretty impressive for what the N64 could do – it was how completely unhinged everything felt. This wasn’t racing, this was automotive chaos with a loose racing structure wrapped around it. Cars were launching themselves off ramps that would kill you in real life, spinning through the air like they were auditioning for a stunt show, landing with crashes that should’ve turned everyone inside into jelly.
I mean, I work construction. I understand physics, at least the basic “what goes up must come down” variety. Rush took physics, gave it a wedgie, and shoved it in a locker. Cars don’t work like this. Ramps don’t launch you three blocks forward. You can’t drive up the side of buildings and somehow keep going. But within the first ten minutes, I was completely sold on this alternate universe where San Francisco had been redesigned by someone who clearly failed driver’s education.
The tracks themselves were brilliant in their complete disregard for how cities actually work. I’ve been to San Francisco a few times for work – worked on a hotel renovation there back in ’08 – and while the city definitely has some steep hills, it doesn’t have launching ramps scattered around like some kind of municipal extreme sports park. But Rush’s version made perfect sense within its own logic. Of course Lombard Street should have jumps. Of course you should be able to use the Golden Gate Bridge as a springboard. Why wouldn’t Alcatraz be a checkpoint on your way to automotive madness?
What really got me hooked was discovering those shortcuts the game shop guy had mentioned. Took me probably three weeks of casual playing before I accidentally found my first one – hit a wall at just the right angle and suddenly I was flying through the air, landing two corners ahead of where I was supposed to be. Felt like I’d discovered buried treasure. Started hunting for more, which turned into this obsessive exploration phase where I was spending more time looking for secret routes than actually racing.
This is something I’ve noticed about a lot of retro games that modern games have lost – they reward curiosity. Rush didn’t just want you to memorize the racing line and optimize your lap times. It wanted you to experiment, to try hitting that suspicious-looking ramp, to see what happened if you approached a corner from a completely wrong direction. Sometimes you’d find gold. Sometimes you’d end up embedded in a building. Both were entertaining.
The car selection was perfect too, though not in any way that would satisfy someone looking for automotive accuracy. These weren’t real cars with proper licensing and historically correct specifications. They were arcade archetypes – the taxi that drove like a refrigerator but could ram through anything, the sports car that was fast but fragile, the muscle car that sounded like it was permanently angry about something. Each one handled completely differently, which gave you actual reasons to experiment beyond just cosmetic preferences.
Playing solo was fun, but Rush really came alive when I had people over. My daughter visited with a couple of her friends one weekend, and we ended up having these four-player marathon sessions that went way later than any of us planned. The split-screen chaos was incredible – four cars all trying to take the most ridiculous line possible, ramming each other off jumps, arguing about who got the good controller versus the one with the slightly loose analog stick.
There’s something beautiful about perfectly-timed ramming in Rush. Not in a violent way, but in a slapstick comedy way. Catch someone just as they’re about to land a huge jump and you can send them spiraling into the bay while you sail past. Do it wrong and you both go flying in random directions, usually laughing too hard to care who was actually winning. It’s automotive ballet performed by people who clearly never took ballet lessons.
The sound design deserves special mention because it sold the experience completely. Engine notes that growled and whined in all the right places, the metallic scraping when you bounced off walls, that satisfying whoosh when you nailed a perfect jump sequence. Played through my decent speakers – the ones I’d invested in after discovering I was actually going to be spending serious time gaming – it felt like San Francisco was happening in my living room.
What impressed me most was how confident Rush was about being completely ridiculous. No apologetic nods to realism, no attempts to justify why cars could suddenly become aircraft. It just said “this is how things work here” and committed fully to that premise. I respect that approach as someone who’s spent decades in construction – sometimes the best solution is the one that shouldn’t work but does anyway.
The graphics hold up better than you’d expect too. Sure, everything has that slightly blurry N64 anti-aliasing that makes distant objects look like they’re swimming, and the frame rate occasionally chugs during particularly chaotic moments, but the core visual design is solid. Those tracks still look imposing, the jumps still look dangerous, the city still looks like somewhere you’d want to drive way too fast.
Playing Rush taught me something important about arcade racing that I’d completely missed during my gaming-free decades – it’s not about cars, it’s about freedom. The freedom to ignore every traffic law ever written, to treat city infrastructure as your personal playground, to solve problems by launching yourself into the sky and hoping physics works out in your favor. That’s genuinely liberating when your day job involves following building codes and safety regulations.
I’ve gone back and played other games in the Rush series since then, and while some added weapons and even crazier stunts, there’s something pure about the original San Francisco Rush. It established the template – racing game plus complete disregard for how the world actually works equals pure entertainment. Simple formula, perfect execution, still fun twenty-five years later.
That game shop guy was right about those shortcuts. Still finding new ones.
Timothy discovered retro gaming at forty and never looked back. A construction foreman by day and collector by night, he writes from a fresh, nostalgia-free angle—exploring classic games with adult curiosity, honest takes, and zero childhood bias.
