Graphical glitches with March 26 core

[neodivad]

I updated the Neo Geo core to the latest March 26 version and I've been experiencing some graphical glitches in every game I've tried. Whether I get the core through the update all script or downloading it from GitHub I encounter the same issue. I haven't noticed any issues with any other recently updated cores (NES, Genesis, etc). The previous Neo Geo cores worked without issue and I've reverted to using the February 12 version.

Is anybody else experiencing these graphical glitches? Any ideas what it could be and how to resolve it? Or do I have to wait and see if the next version fixes it? I'm using the DE10 Nano with the USB hub, analog I/O, and 128 MB RAM that I got from MiSTerAddons.com.

[Chris23235]

I just tried Fatal Fury 2 and Strikers 1945 and didn't experience any glitches.

[jurkevicz]

I've updated today and loaded 3count bout and no Issues.

[rgn]

ask at github, you'll have more chances to get answered

[neodivad]

ask at github, you'll have more chances to get answered

Thanks! I'll try there as well.

[aberu]

https://github.com/MiSTer-devel/Distrib ... omsets.xml

update your romsets.xml

It got updated recently. It looks like you and the others replying on github are using the darksoft set, not the terraonion .neo set. The .neo set works without any of these special prerequisite files, hence why I usually suggest people use it instead. The darksoft set is compatible, but it requires romsets.xml to be updated and working properly.

[neodivad]

https://github.com/MiSTer-devel/Distrib ... omsets.xml

update your romsets.xml

It got updated recently. It looks like you and the others replying on github are using the darksoft set, not the terraonion .neo set. The .neo set works without any of these special prerequisite files, hence why I usually suggest people use it instead. The darksoft set is compatible, but it requires romsets.xml to be updated and working properly.

I just updated the romsets.xml file with no luck. I'm using a romset with the .neo extension.

[jca]

If you are using a romset with the .neo extension romsets.xml is not involved and updating it will not change anything regarding your problem.

[aberu]

Right, someone in the issues thread mentioned they were using darksoft, only reason I brought it up

[Hectic]

Erase corrupt core. Download again.

[jca]

Right, someone in the issues thread mentioned they were using darksoft, only reason I brought it up

You can use both at the same time. I use Darksoft but also have a few .neo.

[aberu]

Yup, I never suggested you can't use both at the same time. I still suggest people use .neo because they are like the equivalent to properly headered NES ROMs in that sense, whereas the darksoft set works fine but only if the romsets.xml is correct.

[Kitrinx]

This looks like marginal timings failing to me. Probably is a bad build that fails timings depending on silicon lottery of your fpga. It's probably caused by all the recent additions to the scaler stressing the fpga. Try building without adaptive scanlines and see if that build clears up the issues.

[jca]

I just made the post for anyone reading this thread and not familiar with MISTer NeoGeo.
I have a few questions:

How do you deal with the game naming with .neo roms?
The name of these roms is very short and not descriptive. I first renamed them with a descriptive name but the OSD does not display this name but the name contained in the header which is the short, non descriptive name. Next I zipped them and gave a descriptive name to the zip file. It show up properly in the OSD, but as a folder which opens when trying to run the rom and displays the neo file which has to be selected again to run the game. It works but not very elegant. Is there a better way?

Are these .neo roms usable with the arcade version of the core (from Blackwine) or only the DarkSoft ones?

So far I have been unable to find a .neo collection. Is it available somewhere?

[TheLegendaryPaiMei]

I'm having this exact same issue, although my graphical corruption is slightly more blocky in nature.

Things i've tried:

*Rebooting
*Erasing the core and redownloading through update all.
*Running Memtest - which seems fine.
*Running CPS2 core for signs of similar problems - None arose.
*Removing video scaling options

All to no avail. Last core was running perfect before recent update.

Would love to hear from more people trying the latest core out!?

[neodivad]

I just made the post for anyone reading this thread and not familiar with MISTer NeoGeo.
I have a few questions:

How do you deal with the game naming with .neo roms?
The name of these roms is very short and not descriptive. I first renamed them with a descriptive name but the OSD does not display this name but the name contained in the header which is the short, non descriptive name. Next I zipped them and gave a descriptive name to the zip file. It show up properly in the OSD, but as a folder which opens when trying to run the rom and displays the neo file which has to be selected again to run the game. It works but not very elegant. Is there a better way?

Are these .neo roms usable with the arcade version of the core (from Blackwine) or only the DarkSoft ones?

So far I have been unable to find a .neo collection. Is it available somewhere?

HTGDB Gamepacks on archive.org has a .neo set. It's a good source for MiSTer and Everdrive packs.

https://archive.org/details/htgdb-gamepacks

[neodivad]

I'm having this exact same issue, although my graphical corruption is slightly more blocky in nature.

Things i've tried:

*Rebooting
*Erasing the core and redownloading through update all.
*Running Memtest - which seems fine.
*Running CPS2 core for signs of similar problems - None arose.
*Removing video scaling options

All to no avail. Last core was running perfect before recent update.

Would love to hear from more people trying the latest core out!?

I've tried all sorts things and also done what others have suggested with no luck. The latest version still has issues while the previous one from February 12 works perfectly. Others with the same issue on the thread I started on Github are saying this core from April 2 doesn't have any issues.

https://github.com/MiSTer-LLAPI/NeoGeo_ ... 220402.rbf

I haven't tried it yet, but I guess that's a good sign the next release will not have the issues some of us are experiencing.

[jca]

@ neodivad
Thanks, I used this "site" before and indeed it is very good but I missed the neo pack. I will try it and hope to find a solution for the naming of the roms.
Sorry to hijack this thread.

[mikaeltarquin]

I am also experiencing graphical issues with one of my MiSTers and the latest neo geo core. This MiSTer is in an aluminum case from MiSTerAddons. I tested on another MiSTer, a MiSTercade setup in an Astro City, and it did not have the same errors (identical romsets on a shared network drive).

[neodivad]

I am also experiencing graphical issues with one of my MiSTers and the latest neo geo core. This MiSTer is in an aluminum case from MiSTerAddons. I tested on another MiSTer, a MiSTercade setup in an Astro City, and it did not have the same errors (identical romsets on a shared network drive).

The graphical issues in the latest release seem to only be affecting some DE10-Nanos, just like you experienced. It looks like a new build has fixed the problem.

[Lloyd2084]

My NeoGeo core has messed up graphics in all games now, it was fine before the latest release.

I’ve tried updating the core but it still shows the 26/3 update.

[Lloyd2084]

Update. There is a new build on the GitHub from yesterday.

All is working fine with the new .rbf

[Xbytez]

Sorgelig has just pushed the updated .rbf to the MiSTer NeoGeo github here:

https://github.com/MiSTer-devel/NeoGeo_ ... 220403.rbf

[Wave]

Glad it's resolved for now.

Is there any technical insight into what happened here? Is it indeed not consistent between DE-10 samples?

[cursedverses]

Looking at the change, it looks like a few compiler optimizations and the change of a connector (is that even the right term?) from a wire to a register.

It's more technical than I know at this point.