Sprinter/mame
2
0
Fork 0
mirror of https://github.com/holub/mame synced 2025-06-05 20:33:45 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity

tecmo16: lower screen refreshrate to match fstarfrc video recording and also match gaiden (nw)

Browse Source
This commit is contained in:
hap 2020-03-01 11:49:30 +01:00
parent 00271822e2
commit de9dd09d0c
2 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/mame/drivers/conchess.cpp
View File

@ -35,7 +35,8 @@ note: XTAL goes to 4020, 4020 /2 goes to CPU clock, and other dividers to
IRQ and beeper. On A0, IRQ is active for ~31.2us.
P(A1) + M(A0) (Princhess)
- dual-module, each module has its own 6502
- dual-module, each module has its own 6502 - need verification, more likely
2nd module has no CPU
- ?
T8 (Plymate Amsterdam)

5
src/mame/drivers/tecmo16.cpp
View File

@ -15,7 +15,8 @@ special thanks to Nekomata, NTD & code-name'Siberia'
TODO:
- measure video timing, especially vblank+interrupt length:
fstarfrc relies on the interrupt being held for a while,
otherwise the titlescreen background goes wrong
otherwise the titlescreen background goes wrong.
If I had to guess: 24/4(6MHz) pixel clock, 384 hclocks, 264 scanlines
- there could be some priorities problems in riot
(more noticeable in level 2)
@ -345,7 +346,7 @@ void tecmo16_state::fstarfrc(machine_config &config)
BUFFERED_SPRITERAM16(config, m_spriteram);
SCREEN(config, m_screen, SCREEN_TYPE_RASTER);
m_screen->set_refresh_hz(60);
m_screen->set_refresh_hz(59.17);
m_screen->set_vblank_time(ATTOSECONDS_IN_USEC(1000)); // not accurate
m_screen->set_size(32*8, 32*8);
m_screen->set_visarea(0*8, 32*8-1, 2*8, 30*8-1);