Viewing Issue Advanced Details
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|08317||Graphics||Major||Always||May 18, 2022, 01:01||Jun 8, 2022, 01:19|
|Tester||ICEknight||View Status||Public||Platform||MAME (Official Binary)|
|Assigned To||crazyc||Resolution||Fixed||OS||Windows 10/11 (64-bit)|
|Version||0.243||Fixed in Version||0.245||Build||64-bit|
|Fixed in Git Commit||1f5ab99||Github Pull Request #|
|Summary||08317: pcega [arknoid2 and clones]: Screen flickers and doesn't refresh properly|
|Description||Only when an EGA card is used, the screen will heavily flicker and all sprites leave a trail behind. Also, the scrolling text in the intro doesn't properly scroll.|
|Steps To Reproduce||
-First load the pcega driver (or another one where you've assigned an EGA card)
-Go to File Manager/harddisk1 and load msdos5 before the PC starts booting.
-Go to File Manager/floppydisk1 and load arknoid2 or arknoid2a.
-When prompted, make sure that EGA/CGA graphics are selected (and MOUSE isn't selected if the drivers aren't installed).
It's advisable to throttle the loading process as much as needed, as it takes a while.
CGA mode and EGA/VGA mode with a VGA card seem to behave properly.
A similar problem happens in bublboble, another game in Taito's "Fun Time Arcade" series.
|Affected Sets / Systems||pcega [arknoid2 and clones]|
0004.png (10,976 bytes) May 18, 2022, 01:01 Uploaded by ICEknight
0006.png (13,301 bytes) May 18, 2022, 01:02 Uploaded by ICEknight
Same problem in bublbobl
|There are no relationship linked to this issue.|
May 18, 2022, 01:02
|Attached a screenshot of the same problem happening in bublbobl.|
Jun 5, 2022, 11:19
edited on: Jun 5, 2022, 20:34
bublbobl has been fixed with this commit: https://github.com/mamedev/mame/commit/ad7cbf9c0a1d888d28d70b2c29c20350592482e0
arknoid2 now has the intro text and screen trails fixed but the racket and ball flicker heavily. Everything else seems to behave cotrrectly now.
Jun 8, 2022, 01:19
|There's still some sprite flickering going on in the latest builds after the fixes, is that confirmed to be normal behavior then?|