Joined: 1/13/2007
Posts: 343
The most notable NES game i know of that actually needs 4 screen is Gauntlet (tengen). I'm sure there are others, though. Mapper 99 is almost like mapper 0, except for the extra 8k of CHR ROM, and the bankswitch to swap between the two banks. I'm not sure if implementing this bankswitch breaks any normal mapper 0 games. That said, vs games also have dip switches to read, and tend to parse input differently, hence the different mapper. But if using mapper 99 for mapper 0 games works in every case, then i see no reason not to merge them. Strangely enough Vs. Castlevania appears to use the same mapper as the original game, except of course for the added dip switches
Dwedit
He/Him
Joined: 3/24/2006
Posts: 692
Location: Chicago
Marking a rom as "Mapper 99" also does double duty, when the VS Unisystem bit isn't set in the iNES header, you treat it as if it is set.
Joined: 5/15/2007
Posts: 13
My personal 2p: * This shouldn't be used to replace cross-platform emulators until it has decent cross-platform support itself. Emulators that only support Windows for TASing at the moment? Sure, since this probably has more of a chance of becoming cross-platform than they do, I wouldn't mind that. * .tas is a really, really, really bad extension. * I'm indifferent about the name, though it sounds slightly like something the sort of person who owns a .biz address would come up with, if you see what I mean (probably not :p). * Accurate, fast emulation is also a good plan if you want to be able to replace existing emulators. How the fast part is going to be done with .NET I don't know.
adelikat
He/Him
Emulator Coder, Site Developer, Site Owner, Expert player (3571)
Joined: 11/3/2004
Posts: 4754
Location: Tennessee
So thanks to some generous help from the community we have managed to build a NES Accuracy test chart. I figure this page is quite relevant to this topic.
It's hard to look this good. My TAS projects
Brandon
He/Him
Editor, Player (191)
Joined: 11/21/2010
Posts: 914
Location: Tennessee
I wrote an .BKM to .FM2 Converter. This should be useful for comparing accuracy and detecting syncing issues, as well as stopping jerks from accusing me of trying to "prevent anybody from going back and using FCEUX after they've messed with it once." >_< Edit: port0 and port1 are now always enabled. Before, I had it just carry over those headers from the .BKM if they were there, possibly from a previous conversion from a .FM2 to a .BKM. This is apparently problematic though as it will never play back input unless these headers are there (Or at least port0). I noticed this when doing some syncing tests here.
All the best, Brandon Evans