- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
03606 | Multisession | Major | Always | Dec 26, 2009, 21:21 | Jul 18, 2010, 13:21 |
Tester | john_iv | View Status | Public | Platform | MAMEUI |
Assigned To | Atari Ace | Resolution | Fixed | OS | Windows Vista/7 (64-bit) |
Status [?] | Resolved | Driver | |||
Version | 0.135u4 | Fixed in Version | 0.138u4 | Build | 64-bit |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 03606: altbeast, aliensyn3: Graphic corruption on multiple segas16b.c launches in single session. | ||||
Description |
The ~third launch of a segas16b.c results in corruption if done within the same session. Easily repro'ed in MameUI; you can do it in baseline w/ the 'select new game' option in the [tab] menu. |
||||
Steps To Reproduce |
In MameUI 1. Launch altered beast. Quit. 2. Launch Alien Syndrome set 3. Quit. 3. Launch altered beast a second time. 4. Note graphic corruption. Baseline Mame Same steps but substitute in-game tab menu and 'select new game'. |
||||
Additional Information | Initially reported by Keith Kelly | ||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | altbeast, aliensyn3 | ||||
Attached Files
|
|||||
Relationships
There are no relationship linked to this issue. |
Notes
3
No.05994
Tafoid Administrator
Apr 22, 2010, 19:38
|
I tried this in 0.137u3 and it doesn't repro. Can anyone else reproduce this anymore? |
---|---|
No.05995
Agriffin Tester
Apr 22, 2010, 20:19
edited on: Apr 22, 2010, 20:44 |
I can confirm it happens here. followed steps above on 0.137u3 MameUI (Winxp 32 bit). Game hangs with Graphic corruption as stated above. Tested also with Baseline Mame 0.137u3 and MameUI 64 bit. (Win 7) Same results. Also after it hangs repeated attempts at starting albeast caused Baseline and MameUI to crash. |
No.05996
Tafoid Administrator
Apr 22, 2010, 20:30
|
Ahh, that was my problem. In checking I checked aliensyn set, not aliensyn3. The problem would appear to lie in that one set. Still valid then :) |