Interstate ’76 gets a Godot rebuild with co-op and an F12 trip back to 1997
The fan project separates Activision’s car-combat data from a replacement engine, with a charter that demands measured fidelity and makes deliberate deviations optional.

F12 is a pleasingly small answer to an argument remasters keep having. I26’s README says you can toggle the original graphics at any time, while the replacement engine runs in Godot. The project, published under the GitHub name vahokif, puts that choice alongside online campaign co-op. You can want the old picture and new company in the passenger seat.
Activision’s original has plenty of personality to preserve. GOG’s description puts Groove Champion in an alternate 1976 American Southwest, seeking revenge for his sister’s death. His Picard Piranha has 425 horsepower, roof-mounted machine guns and a side-mounted flamethrower. Apparently the options package was extensive. The store’s Arsenal bundle includes the original game and the Nitro Pack expansion.
The practical catch comes before the first drive: “I26 contains no game data,” the README says. Its GPLv3 replacement engine needs your legal copy. That separation makes your existing purchase useful again without bundling Activision’s art and missions into the fan download.
The player documentation explains the surprisingly accommodating installation path. You can provide an installed game directory or a GOG offline installer, which I26 unpacks itself. The smaller Galaxy downloader contains no game data and cannot substitute for the backup installer. Multipart downloads need their accompanying files, too. A file ending in .exe can be either the meal or the menu, and choosing the wrong one leaves the engine hungry.
Play the video on YouTubeThe same guide explains why the original executable remains in an extracted installation: I26 reads the computer drivers’ tactics from it. That is a more interesting preservation detail than simply reusing some textures. An opponent’s behavior belongs to the remembered game, too; replacing every old decision with a modern approximation could change what a familiar encounter asks of the player.
The project charter explicitly requires “Faithful by default.” Intentional differences belong behind options, while simulation changes must reproduce traces from the real executable. It also excludes third-party ports and leaked source as implementation material. Those are the project’s declared rules, rather than an independent certification of every system, but they give players something concrete to ask about when a turn feels different.
Online play has its own practical boundary. Custom maps still use the original game’s folders, and the player guide says everyone joining a network game needs matching map data. An absent or different map produces a message on joining. Preservation gets much more useful when the next person can actually join your session; it also inherits the familiar business of getting everybody’s files lined up before game night.
A replacement engine can keep the appearance, controls and behavior as separate choices. That leaves a better question for this rebuild’s next revision: which differences will players spot when the new simulation follows the old drivers’ tactics?