Updated todo notes

This commit is contained in:
Angelo Salese 2009-04-07 13:52:35 +00:00
parent 78c969ac48
commit c8fd788499

View File

@ -21,8 +21,9 @@ Notes(general):
TODO: TODO:
-Back layer pens looks ugly in some circumstances (i.e. suchipi when you win, mjzoomin when coined up), -Back layer pens looks ugly in some circumstances (i.e. suchipi when you win, mjzoomin when coined up),
static or controlled by something else? static or controlled by something else?
-daireika attract mode positioning looks wrong when the screen scrolls vertically, likely that it -daireika: the ranking screen on the original pcb shows some hearts instead of the "0".
disables/enables the wrap-around for the tilemaps in some way; Some investigation indicates that the game reads area "fe100" onwards for these to be filled.
These are likely to be provided by one of the mcu snippets...
-Check if urashima has a "mode 3" for the layer 0 tilemap; -Check if urashima has a "mode 3" for the layer 0 tilemap;
-Complete the dip-switches for all the games; -Complete the dip-switches for all the games;
-There could be timing issues caused by MCU simulation at $80004; -There could be timing issues caused by MCU simulation at $80004;
@ -30,7 +31,8 @@ TODO:
(should be somewhere on the work ram/shared ram) (should be somewhere on the work ram/shared ram)
-urashima: might use three/four layers instead of two.It can be checked when you win -urashima: might use three/four layers instead of two.It can be checked when you win
a match in particular circumstances because there's a write in the 94000-9bfff region; a match in particular circumstances because there's a write in the 94000-9bfff region;
-Massive clean-ups needed for the MCU snippet programs and the input-ports; -Massive clean-ups needed for the MCU snippet programs and the input-ports, also check if
the programs are actually into the m68k program itself (like hachamf/tdragon/ddealer);
Notes (1st MCU ver.): Notes (1st MCU ver.):
-$f000e is bogus,maybe the program snippets can modify this value,or the MCU itself can -$f000e is bogus,maybe the program snippets can modify this value,or the MCU itself can