DKC2 - Glitched Rom after doing Castle Crush Glitch
Uploader Comments (pakitovo)
Top Comments
-
This bug does NOT work on the Wii Virtual Console. It's been fixed (Thank Heavens)
All Comments (62)
-
I'm guessing that this glitch merely corrupts the battery RAM data in a way that crashes the game when it first examines it when powered on. This would explain the problem on the SNES and in an emulator. This theory predicts that a "damaged" cartridge could be fixed by clearing the battery RAM in a copier or other device that allows direct access to it. There's no way I can imagine that it actually damages the cartridge ROMs.
-
@ColorPrinter42 Than name a possibility on how the computer interprets the code cause I'm in college dude.
-
@UndertakerU2ber You apparently have no idea how an actual computer handles and runs actual code at a level deeper than C++. It's no fake.
-
Yeah I'm gonna go outa my way to say this but I think this is fake...BECAUSE I do not believe that the game could screw itself up internally with just a glitch. I know C++ and with all of the knowledge I know I will stand with my accusation.
-
@pakitovo couldn't have messed up the actual ROM or emulator. Has to be something in the save file. Would be interesting to examine it and see what the heck happens to cause this.
-
@Outside998 I think thats amazing that even though the SNES programming technology is probably in a dusty closet somewhere at Nintendo HQ yet they still pulled it out, either still had someone on staff from the SNES days or hired somebody and began fixing it. Then porting it.
-
they could do "copy and paste" of the rom file before doing this, no? :D (means not true for original cartridge)
-
This is probably caused by the fact that when you have that mysterious barrel, the effect is called on something in environment, which... well, makes the game crash. Depending on what's grabbed it can make the game do all sorts of things, ranging from silly graphical errors to rewriting parts of the SRAM. Nasty!
-
Yeah, if it can do that to the rom... wow, I see why you don't need to do it on the real thing. :\
-
@EggmanDrCuckooMan "Graphics glitches have always kinda given me a very slight nauseated feeling looking at them". Im having same strange feelings when im seeing some glitches i allways tought its just me.
I want to know if you played it on a real cart or via an emulator. If you did the later, did it actually change the ROM file? It's a bit of a curiosity from a long time gamer.
SirVG 1 year ago
It was on emulator, it didn't change anything on the rom at least not size or name, but definetly the file was messed up.
pakitovo 1 year ago
@pakitovo Well, a file name wouldn't change, that's expected. I'm curious that if you ran a SHA-1 or MD5 check on the file, if the results would state that the file was changed. It would be easy to check on a computer, but also possible on a real cart if there was access to a SNES cart dumper. I'm mainly curious to know if the ROM (the game) or the SRAM (save file) is what gets changed. It would be quite strange if it was the ROM itself, given what ROM is...
SirVG 1 year ago
I lost all the files and videos themselfs when my computer broke, try it yourself if you are so curious! :)
pakitovo 1 year ago
This is somewhat disgusting to look at. It looks like the game just threw up all over itself, and it makes me feel just a little like I have to do the same. Graphics glitches have always kinda given me a very slight nauseated feeling looking at them, and this is no exception. So when you tried to load your game, did it just go back to the last moment before the fatal error itself or was that you loading state?
EggmanDrCuckooMan 1 year ago 10
This was years ago, but I think I couldn't even load the previous savestate, the emulator freezed.
pakitovo 1 year ago