Closed GoogleCodeExporter closed 8 years ago
it's already fixed in r758, it was a regression introduced in r757, which was
done after the official 1.7.3 release, hence why your user said it worked fine
in the stand-alone version
As a technical reminder, when i fixed read-only registers on MAIN-CPU side in
r757, I forgot about PRG-RAM write-protection register, which was then never
set anymore. It appears this game accidentally tries to access the
write-protected area, which ended up corrupting the SUB-CPU side code in RAM
and later cause an exception.
Original comment by ekeeke31@gmail.com
on 2 Feb 2013 at 9:11
Thanks ekeeke.
BTW - as you can tell from the countless mails you've probably received from
that nintygaming guy - people are not satisfied with how RetroArch GX currently
looks like, and me and ToadKing are seriously not sure whether we are even
doing things right in that regard anymore.
Could you go over the RetroArch GX port and possibly look at gx_video.c and
tell us if/what we are doing wrong? I also heard from a guy that setting the
resolutions the way we do on GX caused adverse performance in HBC and even the
Wii Menu - so this has left me feeling very worried about the entire thing.
I would feel much more comfortable if somebody experienced like you could take
a good look at it and help me out there in that regard.
Original comment by libre...@gmail.com
on 3 Feb 2013 at 8:54
Original issue reported on code.google.com by
libre...@gmail.com
on 2 Feb 2013 at 2:02