Pokémon Ranger: Guardian Signs doesn't seem to be fully playable. At least not on my system, which is a DSi running TWiLight Menu++ and nds-bootstrap loader 24.1 via a 16 GB microSD card in an SD adapter.

The first few hours work fine (except for fairly notable graphical glitches on the title screen), but no progress seems to be possible beyond capturing Meganium in the Old Mansion. Once you leave the building, a cutscene plays followed by the screen fading to black and the music changing. Almost immediately after the music change, the game freezes, with even the music being left hanging.

What's supposed to happen here is that you end up in a special location of the game that supports multiplayer mode. Though you first have to go through some cutscenes and a scripted battle that I'm pretty sure are singleplayer-only, it's still possible the game already tries to do something related to wireless communication as soon as you arrive. Perhaps that's where the bug lies.

I originally ran into this bug on the NA version, but the EU version also has it, regardless of language (saves are cross-compatible).

I experimented with various different settings, but none of them helped. I hear holding L on startup is supposed to fix some games, but it just breaks this one even further by already making it freeze after the title screen.

If it helps, I can upload a save file from just before the bug occurs, but only via PM. I was dumb and put some private information in my name on this playthrough, so I don't want to share it publicly.

 

v0.26.1

What's new?

• DSi/3DS SD card: Load speeds have slightly improved!
  • The IPC-Sync IRQ now only handles the reads.
  • Games that render 3D on both screens will now have minimal to no swap flickers.
  • Certain game crashes have been fixed, such as loading certain save files in Pokemon HGSS.
• B4DS: If the `CARDENGINE_CACHED` setting is not set, the FAT table cache will now be built before the ce9 code, instead of before the game's heap.
• B4DS: For early SDK2 games, the FAT table cache is now built in an unused area of RAM.
  This fixes the opening FMV not starting in Castlevania DOS, and Kirby Canvas Curse now boots, but doesn't save.

Bug fix

• DSi SD card: Bookworm (DS version) now boots on DSi consoles.

 

Has anyone made a tutorial to run commercial games on a homebrew-only flashcard? I have an Action Replay DSi, I already patched the "b4ds-release.nds" file but when I launch it an error message appears: "nitroFSInit failed!", I tried running the .nds file from the Action Replay DSi menu and the Homebrew Launcher but still no success (When I launch it from the Homebrew Launcher it just kicks me back to the Homebrew Launcher menu).
(Edit: Forget it, I got it to work, never thought it was possible to run games on an Action Replay lol)

 

v0.27.0

What's new? (nds-bootstrap)

• Now confirmed working on CycloDS iEvolution, with DSi mode set in CycloDSi settings!
  You can also run DSi-Enhanced games in DS mode, without switching back to DSL mode in CycloDSi settings.
• DLDI driver is no longer re-inited, when booting a game.
  This should fix support for Acekard 2i.
• DSi/3DS SD card: You can now dump the RAM!
  To do so, hold L+R+DOWN+A for 2 seconds. The sound (and maybe game) will pause during dumping.
  The dump will be at "sd:/_nds/nds-bootstrap/".
  
• The cardEngine arm7 binary is now loaded in main RAM for DSiWarehax users running SDK5/TWLSDK games.
  Improves chances of SDK5 games booting.

 

The console's main memory will be dumped to a file on the SD card, and will be at "sd:/_nds/nds-bootstrap/ramDump.bin".

 

Nope. I don't see how RAM dumping will make that possible.

 

The RAM dump feature doesn't work for me at all. Even when I hold the keys in question, the sound never pauses and the file created always has a size of 0 Bytes. Tested it with multiple games. Either some games don't work or something's wrong on my end.

All of my specs are the same as before, except that I obviously updated nds-bootstrap. I didn't update TWiLightMenu, though. Should I have done that? I originally installed it about a month ago.

I was hoping this feature might unveil what's wrong with Pokémon Ranger: GS, though I suppose it's unclear if it'd even work with the game frozen.

 

I already thought of that, which is why I deleted the empty dump between two tests that involved different games. The new one was no different.

 

Okay, figured it out. I was my fault.

I didn't know that nds-bootstrap needs several minutes to create the initial RAM dump file, during which it gives you nothing but a white screen. So when that happened to me, I assumed the game had randomly frozen on startup and shut off my system. That's what left the RAM dump empty and prevented it from working later on. Everything's functional now.

I went ahead and tried to dump Pokémon Ranger: GS's RAM, but found that it doesn't work once the game has frozen. However, things got weird when I initiated the dumping process just seconds before the point where the game usually freezes.

The game went silent as usual during dumping, but once it was finished, it actually made it past the point in question. There were numerous missing sprites and other graphical issues in the area it just loaded, but it was fully functional from a gameplay and sound perspective. Once the cutscenes and the scripted capture were over and I automatically left the area again, everything worked perfectly again. Returning to the area causes no issues either (all images load correctly now).

So I'd assume the bug happens when the game tries to load some images for a specific cutscene. It's weird because most of these images always show up in this area, yet only this one cutscene seems to be bugged.

In case it's of any help, the cutscene that normally freezes the game begins at this point (Edit: Looks like GBATemp automatically removes timestamps from YouTube videos. It starts at 0:38):


I will also upload my RAM dump and PM the link to @ahezard again.

 

My o3ds was suffering from frequent crashes related to progress saving. The ultimate cause was an unsupported sdcard allocation size, 64kb, which boots faster. The recommended 32KB cluster size should be mentioned in the readme so people avoid these headaches.

Anyway, great piece of software, thank you for your time and efforts.