Submappers. Already done for VRC4. I'm tentatively working through the N163, but I don't know enough to make an official stance. I'm not certain what the point of explicitly marking a "no sound" version of VRC7 for TTA2 (separate from the question of A3 vs A4 for the register selection).James wrote:So would you dedicate some of that space to defining different VRC4 revisions? How about something like whether or not expansion audio is used and how it's mixed on the cart?
I don't understand why keeping people from intentionally making their ROM collide with something else is useful. The ability to make a collision even seems useful to me, if you have a game that isn't describable using the conventional headers. The bit that started this entire thread is for exactly this reason: iNES1 headers are insufficient, and overly-precise hashes prevent useful intentional collisions.byuu wrote:Map database entries to SHA256 hashes. Barring a future intentional exploit that allows SHA256 hash collisions (which we don't have yet, and if there ever is one, we can use stronger hashes), there are more possible ROM combinations than there are atoms in the universe.
I guess the answer is: because there's two different objectives: One is denoting "This is the Real Original Game" and for that you want to prevent people from distributing broken things (But is that a real threat, or just an imagined one? CRC32 is enough to prevent almost any accidental collision). The other is "use this data as though it were on this PCB" and that's theoretically what the headers are for.