Closed GoogleCodeExporter closed 9 years ago
Ki no Bouken: The Quest of Ki
SHA1:8A5F3D42A90C39B6110F89B18937D2CB369FCD98
MD5:E9E7FE5152A94C92C71DDAE23DAB7605
My confirmed SHA-1 and MD5 from the No Intro dump. Soft reset works fine for
me.
Original comment by hegyak
on 23 Nov 2014 at 8:45
The hashes you posted match with those from the ROM I have (with the iNES
header).
C:\sums>sha1sum "C:\NES\Kai no Bouken - The Quest of Ki (Japan).nes"
\8a5f3d42a90c39b6110f89b18937d2cb369fcd98 *C:\\NES\\Kai no Bouken - The Quest of
Ki (Japan).nes
C:\sums>md5sum "C:\NES\Kai no Bouken - The Quest of Ki (Japan).nes"
\e9e7fe5152a94c92c71ddae23dab7605 *C:\\NES\\Kai no Bouken - The Quest of Ki (Jap
an).nes
Original comment by fsvgm...@gmail.com
on 23 Nov 2014 at 9:07
By the way, it should be noted that it soft resets fine on QuickNesHawk, but it
shows graphical glitches when using that core (expected, since it doesn't even
load on vanilla QuickNes).
Original comment by fsvgm...@gmail.com
on 23 Nov 2014 at 9:08
Interesting. This may be an emulation bug, or it may be nothing at all; from
our understanding of the console, it is possible for a game to continue more or
less uninterrupted after a soft reset, if it's programmed for that; as RAM is
not cleared.
Original comment by goyu...@gmail.com
on 24 Nov 2014 at 4:55
OK, so I've made a small video comparison between Nestopia, FCEUX 2.2.2 and
BizHawk's NesHawk core. FCEUX follows Nestopia's behaviour.
Here's a ZIP file with three AVI files. I enabled HUD recording on FCEUX and
BizHawk.
FCEUX and Nestopia jump back to the title screen on a soft reset (as in, the
Namco screen is skipped), while BizHawk's NesHawk core just continues running,
as if nothing happened.
Original comment by fsvgm...@gmail.com
on 24 Nov 2014 at 12:47
Attachments:
QuickNES does accept the Soft Reset, NESHawk does not. I checked my ROM and it
is still not doing it right.
Original comment by hegyak
on 24 Nov 2014 at 5:22
Original comment by hegyak
on 24 Nov 2014 at 5:22
bug seems to be NMI being set in the CPU immediately after the reset is
processed. neshawk currently doesnt emulate PPU soft resets at all; therefore
the NMI pending during the inter-frame period has no opportunity to clear.
correct emulation of ppu resetting is required. this wont be hard.
Original comment by zero...@zeromus.org
on 29 Nov 2014 at 6:23
fixed in r8278 by adding missing PPU reset handling
Original comment by zero...@zeromus.org
on 30 Nov 2014 at 5:03
Original issue reported on code.google.com by
fsvgm...@gmail.com
on 23 Nov 2014 at 6:29