Talk:INES Mapper 078: Difference between revisions
From NESdev Wiki
Jump to navigationJump to search
mNo edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
:I'm not clear why defining one of them as being a different mapper isn't better. I guess "fights with other refiling tools", but seeing as GoodNES hasn't been updated for years... The same is true for mapper 34 (BNROM v NINA-001) --[[User:Lidnariq|Lidnariq]] 10:28, 4 August 2012 (PDT) | :I'm not clear why defining one of them as being a different mapper isn't better. I guess "fights with other refiling tools", but seeing as GoodNES hasn't been updated for years... The same is true for mapper 34 (BNROM v NINA-001) --[[User:Lidnariq|Lidnariq]] 10:28, 4 August 2012 (PDT) | ||
::Due to existing already using the one mapper number. Because of this, I would think it might make sense to use submapper zero to tell the emulator to treat it the same as iNES and nonzero submapper numbers to tell more specifically what difference, to have compatibility (and if some emulator does not support submapper numbers it can treat it as iNES and hopefully work anyways), since mapper 078 already corresponds to both of these things so you can keep the mapper 078. (Of course if you do not like this, whoever documents and/or implement NES 2.0 format will do what they do like.) --[[User:Zzo38|Zzo38]] 10:46, 4 August 2012 (PDT) | |||
Revision as of 17:46, 4 August 2012
The problem about different mirroring control could be solved in both NES 2.0 format (using submapper numbers; perhaps 1=Uchuusen, 2=Holy Diver, 0=treat it as iNES and use checksums or whatever) as well as DotFami format (where the mapper definition is included in the same file as the ROM). You should probably work on defining the submapper numbers for NES 2.0. --Zzo38 20:50, 3 August 2012 (PDT)
- I'm not clear why defining one of them as being a different mapper isn't better. I guess "fights with other refiling tools", but seeing as GoodNES hasn't been updated for years... The same is true for mapper 34 (BNROM v NINA-001) --Lidnariq 10:28, 4 August 2012 (PDT)
- Due to existing already using the one mapper number. Because of this, I would think it might make sense to use submapper zero to tell the emulator to treat it the same as iNES and nonzero submapper numbers to tell more specifically what difference, to have compatibility (and if some emulator does not support submapper numbers it can treat it as iNES and hopefully work anyways), since mapper 078 already corresponds to both of these things so you can keep the mapper 078. (Of course if you do not like this, whoever documents and/or implement NES 2.0 format will do what they do like.) --Zzo38 10:46, 4 August 2012 (PDT)
