-
Notifications
You must be signed in to change notification settings - Fork 355
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
NeoGeo Red Warning Screen on several titles #1706
Comments
This is usually happening because you used overclocking and the emulated neogeo detected there is something wrong with your machine, the fix is usually the following :
|
Thanks a lot @barbudreadmon ! Indeed I’m using overclock to 200% as that’s the only way to smoothly play Metal Slug 2. Do you think it could be worth to make any enhancement so that overclocking is not triggering the protection? Many thanks, |
I'd recommend using
|
Thanks a lot, those info are really useful. Do you think is there anything that can implemented on core level to better handle those situations? |
Delaying overclocking until eeprom has been generated does seem realistic, i have yet to look into this though. |
barbudreadmon, that's really a bad idea that could mess with a lot of things, so let's not :) |
fine by me, i'll close then :) |
Hi all,
I’m running retropie 4.8.6 (raspberry pi4b) with latest lr-fbneo release available from source. Neo Geo romset used fully complies with provided DAT files. Bios used is Unibios in MVS Europe mode.
The issue is related to several games being stuck in Neo Geo red warning screen while loading (usage of this cart is not authorized…etc). It happens for instance with Metal Slug 2 or King of Fighters 98. The only workaround is to patch memory as described in the below link.
https://github.com/eniva/MisSTer_Guides/wiki/NeoGeo-Red-Warning-Fix
Doing the above patching will solve the issue for all the affected games.
Would it be possible to fix this behavior?
Happy to provide further details if needed.
Many thanks,
Michele
The text was updated successfully, but these errors were encountered: