Pokemon Ruby doesn't load at all. Sad face
Make sure you have game_config.txt in the root of the SD card. I think I had a link to that in the main post, let me double check though.
Pokemon Ruby doesn't load at all. Sad face
Make sure you have game_config.txt in the root of the SD card. I think I had a link to that in the main post, let me double check though.
I followed the tutorial exactly as described.
Here's my layout:
SD:/3ds/CitrAGB/CitrAGB.3dsx
SD:/game_config.txt (the one provided in the OP)
SD:/gba_bios.bin (Tried both the open source one and a proper one)
Running 9.2.0-20E, if that helps. Maybe it could be my SD card? I doubt it is. It just freezes on a white screen and does nothing - I can exit with "X" though.
My SD card max read/write speed is about 88MB/s (Yeah - fast or what? Using the "professional" SD cards that are used in pro camera gear - bit over kill for the 3DS, as it can't even take advantage of such speeds -_-)
Hm, that happens on Ruby if the save file type is incorrect. Is this a New 3DS? I've noticed that it seems to be that on mine it won't read game_config.txt for some reason, but it will on my old 3DS.
I've had a few blackscreen lockups when starting CitrAGB, but trying enough times gets it working. Guessing it's libkhax related, and I'm planning to try the advice from one of the cfw threads (ntr I think) about waiting a few seconds before starting Cubic Ninja, because I'm probably normally hammering the A button like an impatient twat.
e: I'm using a new3ds, if it helps with testing, what's an easy way to tell if the game_config.txt is being loaded?
For Fire Red, it shouldn't complain about the 1M circuit board being missing.
For Fire Red, it shouldn't complain about the 1M circuit board being missing.
For Fire Red, it shouldn't complain about the 1M circuit board being missing.
Has the problem with the emulator not loading up been fixed yet?
Also fwiw I haven't yet had any more blackscreen freezes when starting CitrAGB, since I started waiting a few seconds before running Cubic Ninja. Try it if you're having that trouble.
Has the problem with the emulator not loading up been fixed yet?