New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DRZ80 not working #1701
Comments
Are you testing this with the current core? This core now has core options to force enable these modes. |
If you force enable one of these modes, check the info log that it replaced the CPU mame2003-plus-libretro/src/mame2003/mame2003.c Line 1693 in ee777f2
|
To be clear there are two issues:
mame2003-plus-libretro/src/mame2003/mame2003.c Line 1690 in ee777f2
mame2003-plus-libretro/src/mame2003/mame2003.c Line 1704 in ee777f2
|
It's possible the replacement CPU isn't fully compatible as the original. I'd assume this would be a case by case type of thing. Are the replacement cpus working at all after your fix?... to confirm the replaced cpu is operational at least even if buggy? The core option allows you to replace a main z80 CPU, z80 sound CPU, or both....so there maybe specific combo that works better for some games than others. |
Yeah so it seems DrZ80 doesn't work at all. Tried 88 games, with Cyclone+DrZ80 it freezes at the ROM OK screen; with Cyclone only it works fine. So, maybe not worth it after all. |
Yeah as i commented at the time they were first supported here the cyclone cpu cores are buggy for a fair few games i suppose back in the day a list would have been made as to which games should be played using it and which should |
Looks like cyclone received some updates recently: |
This was a strange one. I deleted the mame2003 plus folder and done a fresh git clone compiled it and 88 games works. I think the git might be locking or some other odd behavior on the retropie I installed it is old but its the latest on their website. Try deleting your mame source directory and grab it again then recompile. Ive included the retropie bin 4.8 I compiled if you using that. |
Originally posted by @wn2000 in #766 (comment)
The text was updated successfully, but these errors were encountered: