put the dirty hacks to get into test mode in the code, the sound tests are useful at this point, definitely looks like it's writing sample triggers (nw)

This commit is contained in:
mamehaze 2015-04-01 00:06:17 +01:00
parent fe9339fa30
commit 7d434392e1

View File

@ -1020,17 +1020,34 @@ UINT32 hng64_state::screen_update_hng64(screen_device &screen, bitmap_rgb32 &bit
UINT32 animbits;
UINT16 tileflags[4];
#if 0
#if 1
// press in sams64_2 attract mode for a nice debug screen from the game
// not sure how functional it is, and it doesn't appear to test everything (rowscroll modes etc.)
// but it could be useful
if ( machine().input().code_pressed_once(KEYCODE_L) )
{
address_space &space = m_maincpu->space(AS_PROGRAM);
if (!strcmp(machine().system().name, "sams64_2"))
{
space.write_byte(0x2f27c8, 0x2);
}
else if (!strcmp(machine().system().name, "roadedge")) // hack to get test mode (useful for sound test)
{
space.write_byte(0xcfb53, 0x1);
}
else if (!strcmp(machine().system().name, "xrally")) // hack to get test mode (useful for sound test)
{
space.write_byte(0xa2363, 0x1);
}
}
#endif
bitmap.fill(hng64_tcram[0x50/4] & 0x10000 ? m_palette->black_pen() : m_palette->pen(0), cliprect); //FIXME: Is the register correct? check with HW tests
screen.priority().fill(0x00, cliprect);