I can find documentation on the MMC3 or MMC6 separately, but I think the wiki could use a bit of information/recommendation on how to implement mapper 4.
I've noticed that FCEUX, and loopy's PowerPak mapper 4 both seem to support StarTropics just fine without a CRC. Does this mean there is a "safe" way to implement both MMC3 and MMC6 as mapper 4 without negative consequences from any of the old games? Are there drawbacks/incompatibilities to this approach that I haven't noticed? If there is no drawback, what justifies Nestopia's CRC requirement for MMC6?
Obviously, if you want to homebrew for MMC3 or MMC6 it's important to have an emulator that supports all relevant features of the chip, not just the stuff needed to play old games, but at least homebrewers have a lot of options available for this (e.g. iNES 2 headers).
Anyhow, what I'm suggesting is that if there's a "good practice" version of mapper 4 that covers normal use cases and doesn't seem to have drawbacks for non-developers, we should probably have a recommendation on how to do this on the wiki.
I've noticed that FCEUX, and loopy's PowerPak mapper 4 both seem to support StarTropics just fine without a CRC. Does this mean there is a "safe" way to implement both MMC3 and MMC6 as mapper 4 without negative consequences from any of the old games? Are there drawbacks/incompatibilities to this approach that I haven't noticed? If there is no drawback, what justifies Nestopia's CRC requirement for MMC6?
Obviously, if you want to homebrew for MMC3 or MMC6 it's important to have an emulator that supports all relevant features of the chip, not just the stuff needed to play old games, but at least homebrewers have a lot of options available for this (e.g. iNES 2 headers).
Anyhow, what I'm suggesting is that if there's a "good practice" version of mapper 4 that covers normal use cases and doesn't seem to have drawbacks for non-developers, we should probably have a recommendation on how to do this on the wiki.