search

IVBeatz / genplus-gx

Automatically exported from code.google.com/p/genplus-gx
Other
0 stars 0 forks source link

Earthworm Jim Special Edition (BIN) hangs up after getting killed #236

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Start a new game
2. Get killed

What is the expected output? What do you see instead?
After the dying animation, the screen fades to black but stays there without 
trying to reload the level.

What version of the emulator are you using (official, SVN revision,...)?
1.7.0

Please provide any additional information below (Emulator settings, Console
setting,...)
USA version
2.0 BIOS

Original issue reported on code.google.com by superballena on 5 Jul 2012 at 5:47

GoogleCodeExporter commented 9 years ago 
The European version does work properly, though, using the Mega-CD 2.0 European 
BIOS.

Original comment by superballena on 5 Jul 2012 at 11:12

GoogleCodeExporter commented 9 years ago 
Both versions are fine for me, using Model 1 or Model 2 BIOS, unless you are 
speaking about a specific dying animation (i tried dying at various spot in 
first level and it always restarts fine).

Maybe a bad dump ? Mine has CRC = 0xDFD74862 and is 14313472 bytes

Original comment by ekeeke31@gmail.com on 5 Jul 2012 at 11:20

GoogleCodeExporter commented 9 years ago

Original comment by ekeeke31@gmail.com on 5 Jul 2012 at 11:21

GoogleCodeExporter commented 9 years ago

Original comment by ekeeke31@gmail.com on 5 Jul 2012 at 11:40

GoogleCodeExporter commented 9 years ago 
That's odd, it happened to me while dying anywhere in the first level... so I 
guess it might be the image I was using, then.

In case it makes a difference, the European image that worked for me was in an 
ISO+MP3 format, while the US one that didn't was in BIN+CUE.

Original comment by superballena on 6 Jul 2012 at 12:15

GoogleCodeExporter commented 9 years ago

Original comment by ekeeke31@gmail.com on 7 Jul 2012 at 8:47

GoogleCodeExporter commented 9 years ago 
I could not verify this issue with the BIN image (CRC = FA170ECA), with none of 
the BIOS so I guess it's a problem with the image you are using.

Original comment by ekeeke31@gmail.com on 9 Jul 2012 at 7:23

GoogleCodeExporter commented 9 years ago 
It doesn't happen anymore in the latest test DOL you posted with the fixes, so 
it's all good.

Original comment by superballena on 10 Jul 2012 at 3:31