Viewing Issue Advanced Details
[ Jump to Notes ]
vsystem/suprslam.cpp
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
09161 Graphics Minor Always May 1, 2025, 19:10 Jun 11, 2025, 10:14
Tester yoshi200213 View Status Public Platform MAME (Official Binary)
Assigned To Resolution Open OS Windows 10/11 (64-bit)
Status [?] Confirmed Driver
vsystem/suprslam.cpp
Version 0.277 Fixed in Version Build 64-bit
Fixed in Git Commit Github Pull Request #
Summary 09161: suprslam: super slams sprite tearing in vs screen animation
Description Hello
the video game tv animation slam dunk super slams has sprite tearing during vs screen animation
heres a video from insert coin youtube channel
?si=G_Kie4h5klL-cJVi
Steps To Reproduce 1. start the game
2. select team
3 see sprite tearing in vs screen animation
Additional Information There are also sprite tearing issues during other screens like the attract mode
Github Commit
Flags
Regression Version
Affected Sets / Systems suprslam
Attached Files
png file icon Captura de pantalla 2025-05-01 131004.png (422,303 bytes) May 1, 2025, 19:10 Uploaded by yoshi200213
yoshi200213
Relationships
There are no relationship linked to this issue.
Notes
4
User avatar
No.23247
Robbbert
Moderator
May 2, 2025, 01:54
 1. Removed the "and clones" - the game doesn't have any clones.

2. The driver is marked as MACHINE_IMPERFECT_GRAPHICS, so this report could be considered as invalid. However there's no driver notes stating why this status is there.

3. I've confirmed it, although the tearing is only there for milliseconds, and would normally go unnoticed.
User avatar
No.23336
Kale
Developer
Jun 10, 2025, 20:17
 Duplicate of https://github.com/mamedev/mame/issues/13647
User avatar
No.23346
Robbbert
Moderator
Jun 11, 2025, 05:02
 Yeah, some ppl think that by logging the problem in multiple places it can get fixed faster. That's not the case.

Since it's not for the current cycle, that issue should be closed and the contents moved here.
User avatar
No.23350
Kale
Developer
Jun 11, 2025, 10:14
edited on: Jun 11, 2025, 10:14
 (Copy of https://github.com/mamedev/mame/issues/13647#issuecomment-2956371081)

1. no Video System driver have H/VSync measured, to not mention in this specific case.
2. No idea why it needs VIDEO_UPDATE_AFTER_VBLANK and the odd set_vblank_time.
        screen_device &screen(SCREEN(config, "screen", SCREEN_TYPE_RASTER));
	screen.set_video_attributes(VIDEO_UPDATE_AFTER_VBLANK);
	screen.set_refresh_hz(60);
	screen.set_vblank_time(ATTOSECONDS_IN_USEC(2300)); // hand-tuned
	screen.set_size(64*8, 64*8);
	screen.set_visarea(0*8, 40*8-1, 0*8, 28*8-1);
	screen.set_screen_update(FUNC(suprslam_state::screen_update));
	screen.set_palette(m_palette);