Hacker News new | past | comments | ask | show | jobs | submit
101008 | on: How to Make a Nintendo 64 Game in 2026
It may be counterintuitive at first, but why wouldn't be possible? It's one of the perks of "offline" hardware without subscriptions or DRM. You build a piece of hardware (cartridge) that attaches to another one (console) and it works. As long as the console works, there shouldn't be a problem.
jackb4040 | parent | next
Agree. There is a wall coming for "retro" video game nostalgia once we reach the end of the purpose-specific hardware era. Like, you can build an emulator for WiiWare games, but what does it mean to release a "new" WiiWare game when they're just built using an API like OpenGL which is still being used in new games today? What does following the constraints of an older system like that result in besides just another, lower, quality setting? What does "retro" Fortnite look like in 10 years besides just worse shaders?
loading story #49203211
chungusamongus | parent | next
Nintendo is notoriously litigious.
cubefox | parent
> It may be counterintuitive at first, but why wouldn't be possible?

For the same reason it wasn't possible at the time for a third-party to make N64 cartridges themselves to avoid Nintendo's fees. But I assume these lockout chips are replicated or circumvented by now.

phoboslab | root | parent | next
Related to this, every ROM needs a "boot loader" that has to be signed and is verified by the lockout chip.

Nintendo's boot code is under copyright and thus cannot be used. So the boot code distributed with Libdragon is signed by finding a hash collision with a brute force tool running on the GPU[1]. Fun stuff!

[1] https://github.com/DragonMinded/libdragon/tree/trunk/boot#bu...

yellowapple | root | parent | next
The “development” version of that is even crazier: it's a very tiny signed bootloader that does nothing but copies the “real” bootloader into memory, then trampolines into it, such that even developing your own IPL3 doesn't require having to re-brute-force the signature for every build.

And on top of that, libdragon's IPL3 doesn't just blindly copy the first megabyte of ROM code into RDRAM like the official Nintendo one does, but actually expects the ROM data after it to be a full-blown ELF executable, which it parses out and copies pieces of to the specified places.

Pretty slick stuff.

inigyou | root | parent
They might be able to get around it with an affirmative defense in court, but they obviously don't want to, lest they lose.

But it's legal to use the Sony and Nintendo trademarks in a similar way. The court ruled that since they are checked by the console, there was no way not to use them, and Nintendo lost their protection by doing so.

inigyou | root | parent
Fairly recently the chip was studied in detail and replicated. But like most systems of that era, I believe it was circumvented fairly quickly by pirates. The easiest way would be to piggyback a licensed cartridge - unlike the NES, it has to be one with the same region and bootloader as there are several lockout chip variants, but that basic technique still works.
cubefox | root | parent
I never saw a piggyback cartridge at the time though, or one that was obviously unlicensed. Of course, this could have more to do with Nintendo's legal pressure than with technological possibility.
monocasa | root | parent | next
The main pirating route at the time (a device (oh which there were several) that sat under the N64 and had either an Iomega Zip drive or a CD drive for holding ROMs), had a port for inserting a real cartridge to use its lockout chip.
loading story #49200549
inigyou | root | parent
I think a lot of the early flashcarts were piggybacks. I was never into that scene though.