Author
|
Topic: NES Horizontal/Vertical mirroring (Read 2190 times)
|
Kitsune Sniper
Guest
|
|
« on: October 14, 2006, 11:49:29 pm » |
|
So remember when I was complaining about NINJA patches made against a certain version of a ROM that may or may not be available in the future? Well, seems like my comments rang true. Yes, this is related, read on. I just learned that a new GoodNES set was released sometime in the past few months. So I got it and checked out Yume Penguin Monogatari; it turns out that the CRC changed between versions, and the ROM I used in the past was no longer on the romset. So I decided to compare this new rom to the one I based my patch on, and what was the difference? One freakin' byte. The mirroring was flipped. My question is, does this make a difference when it comes to emulation? The game seemed fine in emulators with the old mirroring (Vertical).
|
|
|
|
DaMarsMan
Guest
|
|
« Reply #1 on: October 15, 2006, 12:05:57 am » |
|
I woudln't think so.
|
|
|
|
Dan
Guest
|
|
« Reply #2 on: October 15, 2006, 05:20:21 am » |
|
I wasn't even aware that GoodNES actually took into account the header. In the past, I've downloaded NES ROMs, scanned them, and GoodNES reported them as the proper non-bad, version of the ROM. However, they wouldn't run until I fixed the ROM header.
|
|
|
|
D
Guest
|
|
« Reply #3 on: October 15, 2006, 09:56:21 am » |
|
Kitsune: You are welcome to write a tool to hack the source md5sum of the NINJA patch to match the target file.
|
|
|
|
Kitsune Sniper
Guest
|
|
« Reply #4 on: October 15, 2006, 10:49:45 am » |
|
Actually, this may be simple to fix.
Do Ninja patches take into account the -entire- file or just the ROM data? Is there a way to ignore the header?
|
|
|
|
D
Guest
|
|
« Reply #5 on: October 15, 2006, 12:16:45 pm » |
|
.... NINJA of course ignore headers dude. That's kind of the point. Anything that exists in the UNIF header or iNES/Famtasia header will not be examined for patching.
The ROM itself has to be different. Not just the file format.
|
|
|
|
Lenophis
Guest
|
|
« Reply #6 on: October 15, 2006, 12:38:15 pm » |
|
.... NINJA of course ignore headers dude. That's kind of the point. Anything that exists in the UNIF header or iNES/Famtasia header will not be examined for patching.
The ROM itself has to be different. Not just the file format. *sigh* Did you ever take into account that those headers can be changed, and that hacks will change them? If not, you break every single NES hack that does change them.
|
|
|
|
Ryusui
Guest
|
|
« Reply #7 on: October 15, 2006, 01:13:22 pm » |
|
He's right, you know. The header tells the emu which mapper to use, and in the magical world of NES ROM expansion, that telltale mapper byte is going to get changed.
In other words, NINJA breaks every NES translation/hack that changes the mapper. Holy crap. Guess that's why NINJA 2.0 still counts as beta, huh? (Doesn't stop me from using it, though...awesome stuff. ^_^)
|
|
|
|
KingMike
Guest
|
|
« Reply #8 on: October 15, 2006, 01:19:57 pm » |
|
Maybe in a few years I'll release a patch for Famicom Board Game - The Rail King. I changed the mapper from 3 (writes to the low 4 bits of $8000+ control 8KB CHR) to 66 (same thing, except the addition that the upper 4 bits control PRG). Sometime I'll figure out why the game sometimes barfs when I load strings from the extra PRG bank (text won't show, colors screw up).
|
|
|
|
Kitsune Sniper
Guest
|
|
« Reply #9 on: October 15, 2006, 01:42:42 pm » |
|
My Ys 3 patch changes the mapper because it used to be incorrectly set in a previous version of the GoodNES set. I dunno if it's been fixed or not in this new one and I'm too busy to check.
Perhaps there should be some sort of expansion to NINJA so it takes into account iNES format mapper data...
|
|
|
|
Ryusui
Guest
|
|
« Reply #10 on: October 15, 2006, 01:49:39 pm » |
|
Well, the obvious workaround if I'm looking at the Patch Creator right is to choose "raw" instead of "nes"...but I'm probably wrong.
|
|
|
|
Kitsune Sniper
Guest
|
|
« Reply #11 on: October 15, 2006, 02:04:03 pm » |
|
But if you choose Raw, you'd basically be getting an IPS file, losing the best part of Ninja - namely, that romkiddies don't apply the patch to the wrong version of the game.
|
|
|
|
D
Guest
|
|
« Reply #12 on: October 15, 2006, 03:39:11 pm » |
|
But if you choose Raw, you'd basically be getting an IPS file, losing the best part of Ninja - namely, that romkiddies don't apply the patch to the wrong version of the game.
Not really any choice. At least it would still have the MD5sum validation for the file. The only other choice would be making two patches, one NES to patch the ROM data, and one RAW to fix the header. I am not going to change the format on this one because defaulting to include headers in a patch for NES would basically break the whole consistency of the format.
|
|
|
|
Kitsune Sniper
Guest
|
|
« Reply #13 on: October 15, 2006, 03:49:07 pm » |
|
I never said it would have to be something "default". The default in this case would -be- no header. The current spec shouldn't be changed.
But there should probably be (if there isn't already) a way to also include RAW data in the patches for cases such as this... or at least a way to tell the program to do both in one fell swoop (patch Ninja first, patch RAW second). Or something. I dunno.
|
|
|
|
Aerdan
Guest
|
|
« Reply #14 on: October 15, 2006, 04:10:00 pm » |
|
How about expanding the format so that mutliple NINJA patches can be put in one file [and all patches in a file would be applied in order of appearance]? That would solve this particular issue, at least.
|
|
|
|
|