Revhead for macOS

Revhead is a car racing simulation where the garage is more important than the track. You start in a dusty small town in the Australian outback, not with a supercar, but with a pile of parts and the knowledge that every bolt you turn changes how the machine behaves.

1. Find your project. Look over a potential donor car. Its condition dictates your starting point. You're not just picking a vehicle; you're reading its wear and tear.
2. Strip it down. Unbolt the suspension, pull the engine, yank the transmission. Parts aren't locked to one car. A good radiator you pulled from a junker can cool a future build. You build a personal inventory of components that can be removed, replaced, or moved to another car.
3. Rebuild with intention. Slot in a new intake manifold, swap the gear ratios, or stiffen the springs. The car setup directly affects handling and performance. A tight rear sway bar and soft front springs behave one way on asphalt and completely differently on a rutted dirt track.
4. Make it yours. Repaint the body and change the exterior panels. The visual changes are functional pride — the machine finally looks as serious as its spec sheet.
5. Test and tune. Take it out on the back roads or the track. Listen for knock, feel for understeer. Come back, pull the log, swap a part, and go again.

The loop is tight: build, race, break, rebuild. Revhead understands that for a certain kind of gearhead, the satisfaction is in the differential shim as much as the checkered flag.

How does Revhead sit alongside the rest of macOS?

The game saves its progress directly to your home folder — look inside ~/Library/Application Support/Revhead for your career data. Backups are straightforward: copy that folder to an external drive or your iCloud Documents, and you can pick up where you left off on another Mac. The binary is a universal build, so it runs natively on both Intel and Apple Silicon machines without Rosetta overhead.

Because Revhead is a simulation, not a twitch shooter, it pairs well with the Mac's built-in screen recording. Hit ⌘⇧5 while a race replay runs, and you can capture a tricky corner entry to study your line later — the saved video drops onto your desktop as a standard H.264 QuickTime file. The game respects the system volume mixer, so you can keep Spotify or a podcast humming behind the engine noise without any virtual audio cable trickery.

Bringing a paddock find back to life: a full workflow

You spot a ute rusting on a farm outside town. The owner wants it gone. Here's how a build day actually flows.

1. Inspection. Walk around the vehicle in the garage view. The body panels show wear, but the chassis rails look straight. Pop the hood. The engine block isn't cracked — good. The radiator is shot. You check each part's condition percentage and note which items can be salvaged immediately.
2. Strip the donor. Remove the ruined radiator and bin it. Pull the brake calipers — they're at 40% but usable as spares. The gearbox is surprisingly solid. You drag it into your inventory, knowing it might slot into a future project.
3. Shop the gaps. Head to the parts store. You need a fresh radiator, new brake pads, and a set of rear shocks. The shop stocks by category — you scroll, compare stats, and weigh cost against the performance numbers the part sheet shows.
4. Assembly. Bolt the new radiator in. Fit the pads. The old gearbox slides back onto the engine. You notice the front left control arm bushing is worn; you swap it for a better one from your shelf of pulled parts. A quick respray covers the faded panels with a deep blue that hides the history.
5. Shakedown run. Take the ute onto a gravel loop. The rear end floats through washboard sections — you decide the shocks are too soft. Back in the garage, you stiffen the rear compression damping two clicks. Second run: the tail stays planted. The ute is ready for its first real race.

• macOS 10.11 or later
• Runs on both Intel and Apple Silicon Macs