![]() One bsnes-mercury is already too much, I won't make another. I'll even use the SHA256 hash of the supplied firmware in order to select which DSP is active rather than hardcoding it based on the game's internal header. If, in the future, I add high-level emulation of the DSP# series chips and the ST010, I will do the same thing. If you remove the Cx4 data ROM, the game will report an “IMMEDIATE ROM ERROR”, but it will probably still work (not tested) after pressing the A button on the error screen. Note that this does not give you an excuse to omit the Cx4 data ROM from the firmware/ directory! I tweaked the HLE's checksum routine to actually take a checksum of the data ROM instead of returning a constant. The accuracy and compatibility profiles will use low-level emulation as usual. ![]() This enables Mega Man X2 and Mega Man X3 to work in the performance profile, and they will run faster because they don't have to emulate the HG51BS169 chip. This release also adds high-level emulation of the Cx4 that will only be activated when using the performance profile. It is based on bsnes v106r44, but some bugs in icarus have been fixed in order to allow Tengai Makyou Zero's English translation to work (it won't work in bsnes's public beta). Well, at least the Cx4 firmware is legal to redistribute, and the other coprocessors (DSP#, ST010, ST011, and ST018) appear to work just fine with LLE in the performance profile.īsnes-mcfly v106r06 has been released. And that means that bsnes-classic has an advantage in this area. It was the switch to low-level emulation that broke those 2 games in the performance profile. bsnes v079 and earlier, which have high-level emulation of the Cx4, can run Mega Man X2 and Mega Man X3 in the performance profile. There was no way to play Mega Man X2 or Mega Man X3 on bsnes v080's performance profile!ĮDIT 3: Exactly as I feared. But unlike with higan v094 and later, reloading the game wouldn't fix it. I think it goes all the way back to bsnes v080, when low-level Hitachi DSP (Cx4) emulation was introduced.ĮDIT 2: Yep, bsnes v080's performance profile cannot handle the Cx4 either. I made it stop working after April 1st for exactly this reason.ĮDIT: higan v094's performance profile also suffers from the same bug. It restored the HLE of the DSPs and Cx4 and disallowed headerless ROMs (offering to convert your ROMs to headered). In fact, I once made an April Fools satire of Lunar Magic that I called Lunar SNES. I don't want to encourage people to simply ignore the firmwares as they can with bsnes-mercury. If I bring back high-level emulation of the DSPs and the Cx4, I'll have to modify it slightly in order to still require the firmware in order to activate. I really don't want to become the next bsnes-mercury. The scary part is that it likely will work if I bring back high-level emulation of the Cx4 like what bsnes v073 and bsnes-classic have. And when running my homebrew program that dumps the ST018 and Cx4 firmwares and the DSP# data ROMs, bsnes-mcfly outright crashes while higan simply hangs (only with the performance profile, of course). The bug also affects Mega Man X3, the only other Cx4-based game. ![]() And just like with bsnes-mcfly, higan-accuracy and higan-balanced can run Mega Man X2 the first time, and higan-performance requires reloading the game in order to work. I have since gathered more information about the performance profile Cx4 bug: it also affects higan v098, the last version of higan to have the balanced and performance profiles.
0 Comments
Leave a Reply. |