February 20, 2019, 03:13:04 pm
0 Members and 1 Guest are viewing this topic.
Might be a game-specific problem. Or just s**t code. I'll do some testing.EDIT: This works on shitty emulators, hyper-accurate emulators, and emulators that force GB mode. Strange.EDIT 2: aaaaaand i've raped the game. Not a suprise.
I also tried a friend's flashcart on his GBA SP, and it was present there, albeit inconsistent.
Quote from: Parzival on September 01, 2017, 08:16:10 amI also tried a friend's flashcart on his GBA SP, and it was present there, albeit inconsistent.I'm assuming you mean a GB(C) flashcart like the old parallel-port ones from Bung?
Quote from: Wack0 on September 01, 2017, 02:01:47 pmQuote from: Parzival on September 01, 2017, 08:16:10 amI also tried a friend's flashcart on his GBA SP, and it was present there, albeit inconsistent.I'm assuming you mean a GB(C) flashcart like the old parallel-port ones from Bung?It's some weird-ass GBA cart... "GBA Movie player" or some such. Takes those stupid fucking CompactFlash cards. He's got an 8MB... drive? card? in it, but he says it takes max. 256MB ones, and he can't find one that size.Looks like this, but the card's flush with the cart end.
Given that I own a DMG, a CGB and a GBASP plus two flashcarts, I'd be eager to test this - however I don't have the necessary ROM.
Maybe it only works on normal Game Boys, like that glitch where the player's sprite gets corrupted when using an Escape Rope?
I tried but it yielded no valid result (now I get why, I typo'd the name)This didn't work on my GBC, and Torchickens mentioned it didn't work on her GBA SP, so I believe the cart was faulty.
I didn't think about that, maybe the ROM I used was indeed a bad dump (causing the errors on an emulator) and my physical cartridge (being official) was a good dump hence didn't have the glitch on GBA SP and my physical SNES/Super Game Boy.This is the MD5 checksum of the ROM I used on emulator.6C124C8C7FBF7D330EBC2F06DAD7E270DAT-o-MATIC says this is a trusted dump, but with the information now maybe that was a false positive.
Quote from: Torchickens on September 04, 2017, 10:07:27 amI didn't think about that, maybe the ROM I used was indeed a bad dump (causing the errors on an emulator) and my physical cartridge (being official) was a good dump hence didn't have the glitch on GBA SP and my physical SNES/Super Game Boy.This is the MD5 checksum of the ROM I used on emulator.6C124C8C7FBF7D330EBC2F06DAD7E270DAT-o-MATIC says this is a trusted dump, but with the information now maybe that was a false positive.Actually, it seems as if that ROM is a bad dump.DAT-o-MATIC says that two dumps were made in 2014 and both have MD5 hash of 3029C962C483DF174FC6F5C9202326E3.