Dirty NES Glitches

Existential Dread is part of the fun

The Nintendo Entertainment System (NES) is notorious for it's unreliability. In fact, half of everyone's nostalgia for it consists of blowing on cartridges. Nobody ever stops to think about why any of this is. Long story short: Nintendo didn't want anyone to know the NES was a video game. This was a reasonable position to take back then. Nintendo had no choice but to redesign the Family Computer (Famicom) if they wanted to release it in North America. Along with a drastic change in aesthetic, they completely redesigned it internally. With composite output and detachable controllers, the NES allowed the Famicom to become what could have been the best version of itself.

These are both the same machine

Unfortunately, the redesign introduced massive flaws that fundamentally change the experience. The Famicom, for all of it's problems, is very reliable. The NES? Well, if the title image doesn't give you war flashbacks, you're either tremendously lucky or have never played one.

The NES' cartridge port is fundamentally flawed. Most cartridge ports before and after were effectively self cleaning. Imagine you're inserting a game into a Sega Genesis or Game Boy Advance. You're going to feel resistance. The ports pins are scraping against the pins on the cartridge. This cleans them both and keeps the console from becoming finicky. It's not perfect, but it's far more effective than what the NES tried to do.

The ZIF connector in action

What the NES did is referred to as "Zero insertion Force". By design, the pins don't scrap against anything. You put the game in, press the cartridge down, and thats that. Any filth in your game is going to find its way into your console. The port is deep inside too, making it tough to clean.

This is a horrible design. Once the problem became apparent, Nintendo needed to invent new tools just to clean the thing. Unlike a Genesis or a Super Nintendo, you couldn't just open a flap and clean it with an old toothbrush and some alcohol. In my experience, the cleaning kits didn't work. Nintendo explicitly claimed that rubbing alcohol could harm your game, so we didn't use it. Whatever solvent they included with the kit wasn't as effective.

Furthermore, once Game Genie came around, the problems only got worse. The Game Genie had a thicker than normal board in order to make contact with the cartridge port without depressing the tray. This thick board would stretch out the pin connector and over time, it would become impossible to use the console without a Game Genie.

To this day, people believe that normal usage would warp the consoles contacts. I don't think this is true. I've been using the same console since 2009. That's 17 years from the time I'm writing this. I've only ever needed to clean my pin connector. I've never needed to bend them back into shape.

Because of all of this, you may end up spending more time preventing games from crashing than actually playing them.

To add insult to injury, the NES also added a primitive form of DRM. It's almost like they had to screw something up for each improvement they made over Famicom. You gotta balance things out, you know?

the chip responsible for everything

They called it the 10NES chip, and it’s responsible for everything wrong with your life when you were six. There's an IC each game as well as your console and they're constantly talking to eachother. These two chips must be in perfect sync in order for the game to boot. Since the cartridge port is poorly designed, you’ll often find yourself dealing with a game that works perfectly, but isn't being properly authenticated by the DRM. This'll manifest as the legendary blinking light. You'll see the games title screen, you'll hear it's music, but you can't play because the console is constantly resetting itself. This can easily devolve into a massive point of failure and lead people to think the console is dead. If you were playing one of the few games that had the ability to save, may God have mercy on you because the 10NES won't. The act of power cycling the console in order to fix this had the nasty side effect of wiping out save data.

Sometimes, the 10NES would fail mid game. Like I said, the DRM chips require continuous syncronization. Every microsecond that your NES is powered on, those chips are talking. The slightest interruption will trigger the reset circuit and kill your game. One time, my grandma gently brushing against the wall near my NES was enough to set it off. It was relentless and excessive. Both SNES and N64 had similar DRM but since those were properly implemented, you'll rarely see them trigger. Even if you do, you'd never know it.

gives a whole new meaning to "crash"

Game's were tough in the NES days. You'd constantly be getting your ass kicked, you couldn't save, and the threat of random, uncontrollable crashes loomed over you like the Sword of Damocles. We were used to it, as a result, we rarely took these games seriously. I didn't beat Super Mario Bros. 3 without warping because I was skilled, I got lucky. Grandma didn't graze any doorways, the dog was outside, and no molecules decided to randomly shift or briefly lose conductivity.

How NES Games store Graphics internally. Look familiar?

Unlike most gaming consoles, the NES continued running despite severe graphical glitching. Traditionally, an NES cartridge consists of a PRG-ROM - which contains game code, and a CHR-ROM for graphics. These two chips communicate with the the CPU and the PPU respectively. The CPU is self explanatory. PPU is short for Picture Processing unit, and is more or less isolated.

The PPU and CPU communicate, but they don't verify each others work. Allow me to explain as simply as I can: the PPU loads an abstract pattern table from the cartridge (see above). The CPU will give it instructions on how to construct an image from the pattern. It'll tell the PPU "Hey! Put Tile $A5 over here!" but it doesn't know or care what tile $A5 actually looks like. the PPU will simply reference whatever it sees and place it.

Now, Let's say the cartridge connector is making perfect contact with the CPU, but poor contact with the PPU. what'll happen?

this

You could boot up Duck Hunt, and end up with something that sounds and plays like Duck Hunt, yet appears on screen as a scrambled abomination. This was always a treat because it was infrequent. often the connection would be so tenuous that you could actively see it struggling. Lines would flicker back and forth, Mario’s face and legs would be swapped, The Duck Hunt Dog would have two faces -- weird stuff.

My copy of Quattro Adventure was always dirty. I don’t think that I ever saw what Linus Spacehead was supposed to look like. His entire body would always be a garbled mess. We never played Quattro Adventure because it sucks, but If I wanted to show other kids this phenomenon, that’s where I knew I needed to go. Sometimes we actively wanted to see graphical glitches. We'd screw with the cart with varying results. Often only getting jail-bars for our trouble. It's difficult to intentionally invoke these things.

I love it when NES games boot into the wrong thing. Imagine putting in Mega Man 5 and seeing a random glitched up stage instead of the title screen. This happened to me more than once, with multiple games.

Occassionally, Dragon Warrior would boot directly to this

When I first tried to play Dragon Warrior, all I could get it to show was the above. It would loop that animation over and over again. Of all the strange things I've seen an NES do, this is the most prominent in my mind. I still can't explain it. Not because I refuse to learn, but because I don't want the mystery to be spoiled. A few bytes are misread, and it leads to this? What kind of spaghetti code is Dragon Warrior running on?

Other instances of this include:

• Tetris booting into the rocket sequence and launching a glitch rocket


• Double Dragon booting to a garbled screen while the Game Over music plays repeatedly


• Super Mario Bros./ Duck Hunt booting straight to Duck Hunt.

That last one doesn't sound so bad but listen: I was afraid of Duck Hunt growing up. I don't even remember when it happened. I remember being afraid it would happen again. When I was in my mid 20's, I repaired an NES. While testing it, I triggered this one. I felt quite vindicated when I saw it, actually.

what my child brain probably saw

There was once an instance where every single glitch imaginable happened all at once. Upon booting Mega Man 5 the lockout chip was blasting that reset circuit, and it was booting into a garbled Gravity Man’s stage. Another time, Mega Man rode his jetski clean through the opening cutscene. It was ridiculous.

I wish I could recreate these on command but I can't. Inducing them in an emulator just isn't the same, either. Being caught off guard by one of these is one of the weirdest experiences you can have with any game console. In fact, I'd go so far as to say the NES experience isn't complete unless you've witnessed this kind of thing with your own eyes. It's even better when there are other people in the room to watch and react to it with you.

my favorite air fortress level

Sadly (but not that sadly), this isn't the norm for me anymore. In fact, I had to induce some the examples seen in this article. Keeping your NES clean and treating your games with respect makes a world of difference.

During the winter months of 2022, I played through all of Final Fantasy III on my newly repaired childhood NES. The same exact NES that gave me the issues I've been discussing this entire article. I used an Everdrive, and plugged multiple weeks of play into it. It’s completely unmodded, so the lockout chip could have started its shit, but never did. I don’t recall it crashing once, even after hours and hours of play.

Unless you're someone like me that grew up with this stuff, there's no good reason to play an actual NES anymore. Even if you can repair it, just use an emulator. The official Nintendo one is fine, and you can even buy proper controllers for it. The emulation doesn't have any issues and the controller is as close to the original as you're going to get. There's some input lag, so your mileage may vary. Furthermore, it's on hardware you almost certainly have and is bundled with a bunch of other crap that you'll probably want. I'd be surprised if anyone reading this didn't already have access to these. Of course, you can emulate however you want. All I'm saying is that it's the quickest, simplest way to play NES games on a TV with an authentic controller.

I find it amusing that people have been emulating NES longer than it was ever on the market. NESTICLE popped up nearly 30 years ago and while it had issues, they were nothing compared to the kind of crap the real thing was doing. As time passes, what I experienced as a child will cease to be common knowledge. One aspect of this era will always persist though. You'll never see a NES clone without an absurdly tight pin connector. That's the legacy of Nintendo's first time to bat in America. That's of course, if you look past the fact that Nintendo went on to legitimize and subsequently dominate* an industry for the next 40+ years because of it.