-
Notifications
You must be signed in to change notification settings - Fork 203
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
Genesis ROM black screen. #577
Comments
Can confirm this using the |
So if I match the ROM with that no intro set and use the Picodrive core it should work? I've tried using Picodrive with the rom itself and had the same issue. |
It's worth a try. |
No luck. Made sure I had no intro rom that matched and tried every core through on Hackchi2 through Retroarch for Genesis, still same issue. Weird. Thanks for trying to help. |
That probably uses old, outdated RetroArch and libretro cores. Using RetroArch 1.20.0 on Windows 11 and Ubuntu the game works fine in PicoDrive but not in Genesis Plus GX. Also tested the libretro BlastEm core (which is several years behind upstream BlastEm) and the game doesn't work there either. EDIT: Tested the latest upstream, standalone BlastEm nightly and Barkley Shut Up and Jam 2 works there. So it was something addressed in the last couple years in BlastEm. Regardless, it doesn't work in the current Genesis Plus GX. |
Ok, that may be the issue then. I'm using a modded mini SNES and not an emulator using Windows. It is what it is.. it was just the only game I ever had any issues with and thought it was odd. Never had any problems with any other ROMS. |
Barkley Shut up Jam 2 ROM for Genesis goes completely black when starting tournament mode. Any other game mode or menu within the game works perfectly fine. I've downloaded every ROM I could find, and also tried to repair ROMS with FIX CheckSum. According to that everything is good. I've also tried every core in Retroarch. Genesis Plus GX is what I use for every other genesis ROM and they work great. Any suggestions? Thanks.
The text was updated successfully, but these errors were encountered: