MiSTer FPGA Forum

Hi all,

I recently attempted to play Ecks vs. Sever on the GBA core, but the game seems to freeze any time I press the B button during gameplay.

Has anyone else experienced this issue, or know of a possible solution? Any response is greatly appreciated!

Works with:
- Current Core Release - 20.05.13
- Ecks vs. Sever (U) (M5) (MD5 - 6E76914FA33B3436079AC16ECF778D15)
- Original Bios (MD5 - A860E8C0B6D573D191E4EC7DB1B1E4F6)
- Pressing B to open first Door/Gate

Please verify these things or tell me what exactly does not work.

Those first three bullet points are correct. I am using the current core release, as well as that particular Ecks vs. Sever rom, with the original bios.

Attempting to recreate the issue today, and the result is more inconsistent. Usually pressing B, even before approaching the door, will cause the game to freeze. I am sometimes able to get through the first door, but the game freezes shortly afterwards.

Have no Idea what that could be, as it's working here.

- Did you really check the MD5? There are bad Bios files on the road.
- Are you using DDRRam or SDRam?
- Are other games/cores working?

Can somebody else verify please?

On my side It is working.
Could you please make a save state when the issue happens to see if we can have the issue with your save state ?

- I used WinMD5Free to check the MD5 for the rom and bios, and the checksum matched what was posted for both.
- I'm using 128mb SDRAM.
- Other games and cores are working without issue. I've recently been playing an extensive amount of Sonic Advance 2 in the same core without any issues

I've uploaded a save state of the frozen game here: http://s000.tinyupload.com/?file_id=648 ... 3428727852 (lemme know if I should upload this somewhere else)

If it's working for both of you, I'm assuming there's just something funky going on with my MiSTer.

I don't know if it matters or not, but I don't have an I/O Board attached to my device, just a fan.

Please try with setting Memory to DDR-Ram, Save settings and reload core.
This way it rules out faulty sdram.

I don't have an IO Board either.

The savestate doesn't help, it's already crashed there. (Programcounter is in BIOS data segment)
I still can see where you are, right at the start of the level, as the VRAM and Registers are intact.
It's difficult as I cannot reproduce it here, otherwise i could probably see the reason...

However, as it's working for Wark, too, it is more likely your setup.

Sorry, but i have no more ideas currently.

I tried it with DDR-Ram memory and still had the same issue.