White screen when launching gbc games. Everything else works fine.
-
@jonnykesh lol Aladdin launching on your setup doesn't necessarily mean that my roms are bad, there could be a myriad of other factors at play here but I guess I'll try to hunt down some Aladdin test roms from other sources. My current is set is No-Intro which is usually considered the gold standard so I don't know.
-
@edmaul69 I tried that already, thanks though :)
-
@twinparadox Which "other factors"? I literally downloaded the first ROM off a random site (that I trust) and it worked. I have never played a GBC game in my life.
No Intro sets are just as capable of being corrupted as any other. "Gold standard"? Wise up. -
@jonnykesh Hahaha what's with the smugness? I just tried a 3rd versions of the rom and it still doesn't work. I appreciate you trying to help but I don't understand why I am getting an attitude from you. I have learned a great deal about how retropie works over ther years and I don't appreciate being belittled and told to "wise up". I'm glad you got it up and running so fast but if everyone's setup worked exactly the same way then there would be no need for these forums.
Oh and the "other factors" could be my version of "gamebatte", an update i'm not aware of, a setting within the emulator that I need to change, an inconsistency with my bluetooth controllers, a limitation with the number of systems I have, etc, etc, etc.
-
@twinparadox Not an attitude or smugness. I would guess user error. Good luck.
Edit: Worked for me out of the box. You are doing it wrong obviously. -
@jonnykesh Like I said, I setup 13 other consoles up with no problem including MAME, which can sometimes be a bear. That should indicate to you that I'm not some random moron who hasn't tried all of the normal troubleshooting options already. But right out of the gate you were like, "Have you ACTUALLY tried other roms?" I've been involved with front-ends and dealing with rom sets for years and I know what I am doing. This is an unusual problem which I haven't faced before so that's why I posted about it.
-
@twinparadox Good for you. You clearly know what you are doing. You seem to be the one with the attitude. I appreciate you may be frustrated but getting angry at me isn't going to help you, is it?
My point was, testing your ROMs on a PC is no indicator of whether the will work on the Pi. The emulators will be different versions.
Anyway, the version I used to test was the USA version. It was a.zip
file with a.gbc
file inside. What is inside your.zip
files? -
@jonnykesh I'm not angry, I just felt like you were talking down to me, but if you weren't then its all good.
All three Aladdin roms I tried were the USA version and they were all .zip files with a .gbc file inside. This last test was the third Aladdin GBC rom I have tried. I have moved all of the rest of the roms out of the roms folder and I let emulation station rebuild a new gamelist.xml file just in case there was something wrong with the old one. Still getting a white screen and I have to unplug the pi to restart. About to try a 4th version of the rom and then I will await some other suggestions. -
@twinparadox I'm genuinely at a loss in that case. I know it's kind of a generic reply but try updating everything and / or uninstalling and reinstalling the emulator core.
-
@twinparadox said in White screen when launching gbc games. Everything else works fine.:
As far as viewing the runcommand log, I can't because my entire system locks up when I launch certain gbc games and I cannot exit to the command prompt.
You may still be able to connect remotely with ssh. Another option is using an SFTP client to access the log. It's advised that you do this anyway, as it's much easier to relay the information from the log.
-
@jonnykesh I figured it out! Since my entire romset for Game Boy works fine and it uses the the same emulator (ir-Gambatte) as Game Boy Color games I thought that perhaps there was a setting within the emulator that was being applied to GBC games that wasn't being applied to regular GB. I read through the Retroarch.cfg files for each system and noticed that the video driver for GB was set to "gl" but for GBC it was set for "dispmanx". I changed the GBC color video driver to "gl" and everything is all good. I never changed that option to begin with so I'm not sure why it was set to "dispmanx" in the first place, but if anyone else ever has this problem, please benefit from my misfortunes! Mark this down as solved!
-
@mediamogul Just figured it out! Thank you though :)
-
@twinparadox Hey man, gl is the default. Who knows how these things happen. But you figured it out, cool. Glad you got it sorted. Enjoy.
We could have argued all day and I would never have guessed that! -
Nice troubleshooting. These types of problems with RetroArch turn up often when 'Save Configuration on Exit' is enabled, so be sure to make those files your first port of call for any other inexplicable issues going forward.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.