Brad Corrupts, a new rom corrupting series
Moderator: Moderators
-
Reaper_Man
- Posts: 45
- Joined: Sat Jun 17, 2006 2:31 pm
- Location: Austin, TX
Brad Corrupts, a new rom corrupting series
Sup guys. I know I haven't posted here a lot, but I felt that I should share my youtube series with you guys. Anyway, What I'm doing here is taking NES roms and running them through a Python script that randomly changes bytes in random locations (in PRG ROM). I then take footage from the now corrupted game (10 iterations) and put them on youtube. So far, I have made three which are as follows:
1942
Abadox
Al Unser Jr.'s Turbo Racing
I plan to go through my entire collection when I was a kid. Afterwards I plan on taking various requests. Anyway, I wanted to share my series with you guys for 3 reasons:
1. We all have something in common. We're are all geeks that have a love for the NES and its hardware/software and how it al works etc. I'm certain that you guys will take interest in this. :D
2. Some games I've corrupted does some pretty weird, unexplainable shit and I'm really curious as to why some corrupted games exhibit such strange behavior (outside of the already "normal" corrupted behavior you'd expect) I figure some of you guys could enlighten me. :3
3. I'm hoping someone with hardware access can perhaps run my corruptions on real hardware and look for any discrepancies between hardware and various emulators. In other words, I'm hoping that maybe my corruptions might uncover some hidden secrets tucked deep inside the NES that'll hopefully lead to better and more accurate emulation (and yeah I know it's pretty damn close to perfect anyway, but the more we find out, the more it benefits all of us, right?)
Anyway, take a look, and let me know what you think :D
1942
Abadox
Al Unser Jr.'s Turbo Racing
I plan to go through my entire collection when I was a kid. Afterwards I plan on taking various requests. Anyway, I wanted to share my series with you guys for 3 reasons:
1. We all have something in common. We're are all geeks that have a love for the NES and its hardware/software and how it al works etc. I'm certain that you guys will take interest in this. :D
2. Some games I've corrupted does some pretty weird, unexplainable shit and I'm really curious as to why some corrupted games exhibit such strange behavior (outside of the already "normal" corrupted behavior you'd expect) I figure some of you guys could enlighten me. :3
3. I'm hoping someone with hardware access can perhaps run my corruptions on real hardware and look for any discrepancies between hardware and various emulators. In other words, I'm hoping that maybe my corruptions might uncover some hidden secrets tucked deep inside the NES that'll hopefully lead to better and more accurate emulation (and yeah I know it's pretty damn close to perfect anyway, but the more we find out, the more it benefits all of us, right?)
Anyway, take a look, and let me know what you think :D
Last edited by Reaper_Man on Tue Sep 21, 2010 5:04 pm, edited 2 times in total.
I used to do the same thing with random 6-letter Game Genie codes. I would keep track of interesting codes in a notebook and try variations when something would glitch up well.
That's how I found a level select for Journey to Silius and a super-jump & invincibility code for Shadow of the Ninja way back when (1991.)
Yep, I had too much time back in the 9th grade, obviously.
That's how I found a level select for Journey to Silius and a super-jump & invincibility code for Shadow of the Ninja way back when (1991.)
Yep, I had too much time back in the 9th grade, obviously.
-
Reaper_Man
- Posts: 45
- Joined: Sat Jun 17, 2006 2:31 pm
- Location: Austin, TX
I have very fond memories of doing that as a kid as well. The Game Genie was my favorite NES accessory and the rom corruptions are a bit of a homage to those times.ccovell wrote:I used to do the same thing with random 6-letter Game Genie codes. I would keep track of interesting codes in a notebook and try variations when something would glitch up well.
When you change a 2 or 3-byte instruction to a 1-byte instruction, that single byte change can do a lot, since it misses the next few instructions, executing junk instead, until it can eventually get back on track. If it misses a jump, call, or return, that's an even bigger effect.
Here come the fortune cookies! Here come the fortune cookies! They're wearing paper hats!
-
Reaper_Man
- Posts: 45
- Joined: Sat Jun 17, 2006 2:31 pm
- Location: Austin, TX
Oh I know that (at least the basics of what happens), but there are certain things that happen often and I am trying to figure out why it always shows such similar behavior. My next vid will show a great example of this.Dwedit wrote:When you change a 2 or 3-byte instruction to a 1-byte instruction, that single byte change can do a lot, since it misses the next few instructions, executing junk instead, until it can eventually get back on track. If it misses a jump, call, or return, that's an even bigger effect.
-
Reaper_Man
- Posts: 45
- Joined: Sat Jun 17, 2006 2:31 pm
- Location: Austin, TX
Alright guys, new vid is up. This one is for Bandai Golf: Challenge Pebble Beach.
Now pay attention to the first 4 or so iterations. I seem to have run into a very similar.... effect.... the flashing screen with the horizontal lines and such.... what I want to know is, what exactly is going on there, and how come I kept getting that?
Next game to get corrupted: A Boy and His Blob
Now pay attention to the first 4 or so iterations. I seem to have run into a very similar.... effect.... the flashing screen with the horizontal lines and such.... what I want to know is, what exactly is going on there, and how come I kept getting that?
Next game to get corrupted: A Boy and His Blob
-
Reaper_Man
- Posts: 45
- Joined: Sat Jun 17, 2006 2:31 pm
- Location: Austin, TX
Interesting. I think it may also have to do with how the game draws the course topography at the top of the screen. At least that was my guess. Would you, or anyone for that matter, want the IPS files to study the phenomena?tepples wrote:These flashing horizontal lines look like palette writes. Palette writes might happen when VRAM loading code crosses over PPU $3F00-$3FFF. It looks like data lengths might have been corrupted.
-
Reaper_Man
- Posts: 45
- Joined: Sat Jun 17, 2006 2:31 pm
- Location: Austin, TX
-
Reaper_Man
- Posts: 45
- Joined: Sat Jun 17, 2006 2:31 pm
- Location: Austin, TX
Well, I made a new video! This time, I corrupt A Boy and His Blob!
Please feel free to like, rate, comment, subscribe, annotate, and discuss in this thread.
Please feel free to like, rate, comment, subscribe, annotate, and discuss in this thread.
-
artakserkso
- Posts: 34
- Joined: Sun Nov 01, 2009 4:29 pm
- Location: Samobor, Croatia
-
Reaper_Man
- Posts: 45
- Joined: Sat Jun 17, 2006 2:31 pm
- Location: Austin, TX
-
Reaper_Man
- Posts: 45
- Joined: Sat Jun 17, 2006 2:31 pm
- Location: Austin, TX