09277: sws99: Random freeze in the attract mode

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
09277	Crash/Freeze	Major	Random	1 day ago	19 hours ago

Tester	Robbbert	View Status	Public	Platform	MAME (Self-compiled)
Assigned To		Resolution	Open	OS	Windows 11/10 (64-bit)
Status [?]	Confirmed			Driver	namco/namcos12.cpp
Version	0.281	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	09277: sws99: Random freeze in the attract mode
Description	In the attract mode, this game can freeze at one of three places. 1. When the camera pans to the right, just before the demo game starts, it can freeze, with the fence sometimes twisted. Music keeps playing. 2. In the demo game, rarely a fielder catches the ball and it freezes. Only saw this once. Music keeps playing. 3. If it gets through that, then after the demo game it says "ID or NOT ID", then gets a black screen. If it gets this far, this problem always happens. No music at this point. The fence randomly changes colour and texture, but this could be normal.
Steps To Reproduce	>mame sws99 Don't touch anything, just watch what happens. You can try pressing INS to try getting the rarer freezes.
Additional Information	Already confirmed by hap.
Github Commit

Flags
Regression Version
Affected Sets / Systems	sws99

Attached Files	1. freeze after panning.png (73,887 bytes) 1 day ago Uploaded by Robbbert
	2. freeze in the field.png (27,260 bytes) 1 day ago Uploaded by Robbbert
	3. about to black screen.png (41,106 bytes) 1 day ago Uploaded by Robbbert

No.23720 hap Developer 22 hours ago edited on: 22 hours ago	I tried bug 1 on older MAME versions (wait for scroll to end, SHIFT+F3 to hard reset if no lockup, repeat). The oldest MAME version I have locally is 0.256 and it's also broken there. I have not tried further back. I assume it picks a random demo sequence from the RTC and/or nvram and lockups happen on specific ones, and it's not due to an uninitialized class variable. Bug 2, I got it in-game a couple days ago, so it's not just attract mode that's suspectible to lockups.
No.23722 Robbbert Moderator 19 hours ago	I went further back - 0.144, 0.145 and 0.146 seem to work correctly, at least it never locked up. My next version is 0.155 and it eventually locked up in the field. Bug 3 didn't exist back then, it seems to have manifested somewhere after 0.232. So what would happen in prior versions is that the first round usually worked, but a lockup in the field happened in the 2nd round. So, it's another very old bug that nobody noticed.

No.23720

hap

Developer

22 hours ago

edited on: 22 hours ago

I tried bug 1 on older MAME versions (wait for scroll to end, SHIFT+F3 to hard reset if no lockup, repeat). The oldest MAME version I have locally is 0.256 and it's also broken there. I have not tried further back.

I assume it picks a random demo sequence from the RTC and/or nvram and lockups happen on specific ones, and it's not due to an uninitialized class variable.

Bug 2, I got it in-game a couple days ago, so it's not just attract mode that's suspectible to lockups.

No.23722

Robbbert

Moderator

19 hours ago

I went further back - 0.144, 0.145 and 0.146 seem to work correctly, at least it never locked up. My next version is 0.155 and it eventually locked up in the field.

Bug 3 didn't exist back then, it seems to have manifested somewhere after 0.232. So what would happen in prior versions is that the first round usually worked, but a lockup in the field happened in the 2nd round.

So, it's another very old bug that nobody noticed.