Sprinter/mame
2
0
Fork 0
mirror of https://github.com/holub/mame synced 2025-07-02 16:49:22 +03:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Merge pull request #8003 from DavidHaywood/250421

Browse Source 
fix gigandes sprite offsets (regressed around december)
This commit is contained in:
ajrhacker 2021-04-26 12:17:50 -04:00 committed by GitHub
commit 73f578124c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/mame/drivers/taito_x.cpp
View File

@ -921,6 +921,8 @@ void taitox_state::gigandes(machine_config &config)
MCFG_MACHINE_START_OVERRIDE(taitox_state,taitox) MCFG_MACHINE_START_OVERRIDE(taitox_state,taitox)
SETA001_SPRITE(config, m_seta001, 16000000, m_palette, gfx_taito_x); SETA001_SPRITE(config, m_seta001, 16000000, m_palette, gfx_taito_x);
m_seta001->set_fg_yoffsets(-0xa, 0xe);
m_seta001->set_bg_yoffsets(0x1, -0x1);
/* video hardware */ /* video hardware */
screen_device &screen(SCREEN(config, "screen", SCREEN_TYPE_RASTER)); screen_device &screen(SCREEN(config, "screen", SCREEN_TYPE_RASTER));

8
src/mame/video/seta001.cpp
View File

@ -32,6 +32,14 @@
This should implement device_video_interface, since it generates the vertical This should implement device_video_interface, since it generates the vertical
and horizontal blanking and sync signals from a master clock. and horizontal blanking and sync signals from a master clock.
understand sprite limits / how sprite 0 sometimes must be skipped, maybe
layers being enabled counts against limits? maybe some chip revisions skip
the first sprite? see note in device_start
understand why we need offset kludges for some games, they can even differ
from layer to layer
*/ */
#include "emu.h" #include "emu.h"