MiSTer FPGA Forum

Hello, not sure where to post this since it involves switching cores:

It has happened twice to me now that after an extended session of playing the SNES core and then switching over to the Neo Geo core, I have observed corrupted graphics on screen, like cycling screens of garbled graphics while the OSD displayed over it just fine. One of the times, I was able to make out that parts of the corrupted graphics seemed to belong to the Neo Geo bios. The problem disappeared once I loaded a game.

I have no idea what is actually happening, but it feels as though memory leftovers from the SNES core are not being cleared properly when switching to another core, which causes corruption.

I am not able to reproduce this consistently, as simply loading a SNES game and switching to the Neo Geo core does not exhibit the issue. It seems that a SNES game must be played for a significant amount of time first it seems.

Has anyone ever seen something like this? Is this known?

I will keep trying and hope to find a consistent reproduction method.

Thanks!

Graphics stuff like this just happens sometimes. The way to fix it is to do a hard reboot (or hold the button on the reboot option on the OSD until it resets). There's some kind of issue when changing cores a few times that happens less frequently now since sorg fixed it, but it still happens occasionally. Some people experience it more than others.

What is the version/release number for both SNES and NeoGeo cores?

bootsector wrote: ↑Fri Aug 13, 2021 3:10 pm What is the version/release number for both SNES and NeoGeo cores?

SNES - 21.07.13
NeoGeo - 21.07.13

Both cores should have the latest framework which supposedly fixes this issue when switching between them.

Are you sure that before going to the NeoGeo core you didn’t open an arcade core or something?

bootsector wrote: ↑Sat Aug 14, 2021 4:29 am Both cores should have the latest framework which supposedly fixes this issue when switching between them.

Are you sure that before going to the NeoGeo core you didn’t open an arcade core or something?

I didn’t open any other cores beforehand.

I’ve had it happen again yesterday, and this is what happened:

Do a Full reboot via the menu. never happened again.