Closed GoogleCodeExporter closed 9 years ago
ran VBA-M, video is correct in VBA-M.
Original comment by katiecom...@gmail.com
on 20 Jan 2009 at 9:58
WOW that's pretty trippy in the game there...yes this is an interesting one.
Original comment by dborth@gmail.com
on 21 Jan 2009 at 8:43
The whole game is in graphics mode 4, which is a double-buffered 256-colour
bitmap
graphics mode.
The game does NOT use "mode 7" style graphics. It is purely software-rendering.
Most games don't use this graphics mode.
The bug is also present in r61. I haven't tested any versions older than that.
Original comment by Carl.Kenner@gmail.com
on 13 Mar 2009 at 6:52
The bug is caused by the game trying to write to palette memory at addresses
higher
than 0x5000400.
The emulator wraps these writes around to the start of the range, overwriting
the
palette.
I can fix the problem by adding the check that the address is < 0x5000400 in
palette
memory writes.
HOWEVER... VBA-M, and PC versions of VBA don't have this check, yet they still
work!
So... Something very weird is going on with this game on vba-wii which causes
it to
write to memory addresses that it wouldn't normally write to. Either that, or
the BKPT_SUPPORT behaves differently on other platforms.
I have also got crashes playing this game. So there is possibly a serious
problem
somewhere in the GBA CPU emulation.
Anyway, I'm going to put this in as a workaround for this game, but I think I'm
treating the symptoms rather than the cause.
Original comment by Carl.Kenner@gmail.com
on 13 Mar 2009 at 8:15
Original comment by Carl.Kenner@gmail.com
on 26 Apr 2009 at 8:17
Original comment by dborth@gmail.com
on 25 May 2009 at 6:30
Original comment by Carl.Kenner@gmail.com
on 27 May 2009 at 8:26
[deleted comment]
Original comment by dborth@gmail.com
on 19 Oct 2010 at 10:06
Original comment by dborth@gmail.com
on 17 Apr 2011 at 7:35
Original issue reported on code.google.com by
katiecom...@gmail.com
on 18 Jan 2009 at 11:58