Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06522 Graphics Minor Sometimes Mar 22, 2017, 02:57 Nov 2, 2017, 03:27
Tester mmarino4 View Status Public Platform MAME (Official Binary)
Assigned To Resolution Fixed OS Windows Vista/7/8 (64-bit)
Status [?] Resolved Driver seattle.cpp
Version 0.183 Fixed in Version Build 64-bit
Summary 06522: blitz2k: Play selection screen graphics temporarily freeze
Description Often times the play selection screen will be frozen when you get to it. The counter will not appear to move and you will see no box around the play you are highlighting. The sound and controls will still work. If you press Turbo to bring up the next screen of plays, the graphics will "wake up" and work normally.
Steps To Reproduce This will happen several times during any game. It seems to be random but it happens often enough.
Additional Information Cannot replicate in blitz or blitz99.
Regression Version
Affected Sets / Systems blitz2k
Attached Files
mp4 file icon Blitz2K-Error 06522.mp4 (3,868,363 bytes) Mar 25, 2017, 17:06 Uploaded by mmarino4
Error 06522 in action.
There are no relationship linked to this issue.
User avatar
Mar 23, 2017, 13:34
This sounds the same as 00974 ?
If so, this is a duplicate.
User avatar
Mar 23, 2017, 14:29
00974 is an issue where it will freeze right when the game should start after you've picked your teams and options. It's bypassed by letting the attract mode run until it displays the in-game football field. 00974 also pertains to blitz99. The issue I posted here occurs during the game in blitz2k only. It's possible that the root cause of both issues is the same but they happen at different times and the workarounds are different.
User avatar
Mar 25, 2017, 17:08
I attached a short video showing this issue. I will also upload a video of the 00974 error on its page. The error also does happen on the defensive play screen so I've updated the information.
User avatar
Nov 2, 2017, 02:53
I've played a good amount in 0.191 and this didn't happen once. One of the recent updates must have fixed it.

Change to resolved.