- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
06927 | Crash/Freeze | Major | Always | Apr 2, 2018, 15:12 | Mar 20, 2019, 22:56 |
Tester | StHiryu | View Status | Public | Platform | MAME (Unofficial Binary) |
Assigned To | AmatCoder | Resolution | Fixed | OS | Windows Vista/7/8 (64-bit) |
Status [?] | Resolved | Driver | |||
Version | 0.196 | Fixed in Version | 0.208 | Build | 64-bit |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 06927: cpc464, cpc6128: Hundra gets stuck in a black screen after leaving main menu | ||||
Description | After selecting yor controls in the main menu, the game gets stuck in a black screen. | ||||
Steps To Reproduce |
-Grab any version of Hundra from Cpc.power.com (tape or disk). -Use |CPM to load the disk image. -Select keyboard or joystick in the menu. |
||||
Additional Information | |||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | cpc464, cpc6128 | ||||
Attached Files
|
|||||
Relationships
There are no relationship linked to this issue. |
Notes
9
No.16219
AmatCoder Tester
Mar 7, 2019, 15:32
|
I have created a pull request for this issue: https://github.com/mamedev/mame/pull/4730 This program waits indefinitely until vsync are enabled. But MAME was checking for vsync after increasing line counter so it was never enabled when line=0. |
---|---|
No.16220
StHiryu Tester
Mar 7, 2019, 16:12
|
Big thanks, will test some amstrad and spectrum stuff after your commits. |
No.16245
Gryzor1363 Tester
Mar 15, 2019, 22:46
edited on: Mar 15, 2019, 22:46 |
Similar problem with Adios a la Casta 2, which works until after the title screen, then there is only the background music and a blackscreen with seemingly no controls. Should I raise a dedicated ticket for this ? Problem is confirmed up until Mame 0.206. |
No.16246
StHiryu Tester
Mar 16, 2019, 00:53
|
Tried Adios a la casta 2.cdt and works great. However Adios a la casta 2 crashes emu when selecting dsk image at file manager. |
No.16247
Gryzor1363 Tester
Mar 16, 2019, 01:00
|
It crashes in 0.206 ? I recall it crashed mine too a few versions back but not with 0.206 which I tried before my previous comment. Blackscreen + music after title, confirmed again a moment ago. Tried with the .dsk image. |
No.16248
StHiryu Tester
Mar 16, 2019, 01:15
|
As I said, the game is playable in current 208 GIT, but the dsk crashed the emu, so I played the cassete version. I don't have 206 to test, but seems that the issue was the same that Hundra. |
No.16249
AmatCoder Tester
Mar 16, 2019, 11:17
|
"Adios a la Casta 2" does not work in 0.206 but it works now. The issue was not the same than "Hundra", but the same than "Profanation 2" fixed here: https://github.com/mamedev/mame/pull/4725 Note: "Adios_a_la_Casta-2-vs-1.0" dsk from: https://www.4mhz.es/adios-a-la-casta-episode-2-de-buen-rollo/ leads a segfault if loaded with internal file manager. It works if loaded via command line (although it aborts at exit). Version "Adios-a-la-casta-2-loader-reprogramado-Joseman-para-4Mhz" from: https://www.4mhz.es/adios-a-la-casta-episode-2-de-buen-rollo/ works fine. Version "Adios A La Casta - Episode 2 v1.0 (UK) (128K) (2016)" from: http://www.cpc-power.com/index.php?page=detail&onglet=dumps&num=13113 works fine. |
No.16250
Gryzor1363 Tester
Mar 17, 2019, 00:45
|
Glad to see you killed those two bugs in one go ! Information acknowledged, and thanks for all the great work, AmatCoder. I guess several "contemporary" release use some exotic coding practices not initially taken into account by CPC emulators, MAME/MESS or otherwise. Star Sabre seems to suffer from this in the intro sequence, although it is playable. |
No.16256
AmatCoder Tester
Mar 20, 2019, 22:56
|
For the record, with this commit: https://github.com/mamedev/mame/commit/66a4629631b8796896a4dc3bd080399b8531ada0 "Adios_a_la_Casta-2-vs-1.0.dsk" no longer produces a segfault but an error. It is a double-sided image so it needs a double-sided floppy drive. "35ssdd" works but only on drive A (for unknown reasons - most probably another bug...) |