Translation Chrono Trigger (DS) - KWhazit / Chrono Compedium Fan Translation Patch Port

  • Thread starter Thread starter rsc-pl
  • Start date Start date
  • Views Views 3,076
  • Replies Replies 26
  • Likes Likes 10
Thank you for the answer, i have succeded patch the game, but after press load or new game, its just blank
Im using ndsi and my flashcart is r4i
 
Its doesn't work on my new 3ds LL at all. Running from latest twilight menu or forwarded into home menu, both just show a white screen. My rom has the correct hash so I just don't know what went wrong.
 
V0.8.2 New
Its doesn't work on my new 3ds LL at all. Running from latest twilight menu or forwarded into home menu, both just show a white screen. My rom has the correct hash so I just don't know what went wrong.
Thank you for the answer, i have succeded patch the game, but after press load or new game, its just blank
Im using ndsi and my flashcart is r4i

I've updated the thread.
I don't know if this fix will solve your problems, I wasn't able to reproduce the issue on any of my devices, since the game ran without any problems for me on both the 3DS and DSi XL, as well as on the emulator, but I did find one reason why certain configurations might not have loaded the game correctly.

In addition, the latest ZIP file contains both the original, unmodified fan translation and a polished version that corrects many awkward sentences and literal Japanese grammatical structures.



In addition to this fix, in the patch-building process itself, here are a few notes:
Chrono Trigger uses anti-piracy checks. When running a patched ROM through TWiLight Menu++ or a 3DS/DSi forwarder, use TWiLight Menu++ v27.17.3 / nds-bootstrap v2.8.3 or newer. That nds-bootstrap release specifically fixed white-screen boot failures affecting Chrono Trigger ROM hacks.

If a correctly patched ROM still boots to white screens, reset the game's per-game settings to defaults, disable cheats, and delete sd:/_nds/nds-bootstrap/fatTable/ plus sd:/_nds/nds-bootstrap/patchOffsetCache/ so nds-bootstrap rebuilds its caches.
 
Last edited by rsc-pl,
I've updated the thread.
I don't know if this fix will solve your problems, I wasn't able to reproduce the issue on any of my devices, since the game ran without any problems for me on both the 3DS and DSi XL, as well as on the emulator, but I did find one reason why certain configurations might not have loaded the game correctly.

In addition, the latest ZIP file contains both the original, unmodified fan translation and a polished version that corrects many awkward sentences and literal Japanese grammatical structures.



In addition to this fix, in the patch-building process itself, here are a few notes:
Chrono Trigger uses anti-piracy checks. When running a patched ROM through TWiLight Menu++ or a 3DS/DSi forwarder, use TWiLight Menu++ v27.17.3 / nds-bootstrap v2.8.3 or newer. That nds-bootstrap release specifically fixed white-screen boot failures affecting Chrono Trigger ROM hacks.

If a correctly patched ROM still boots to white screens, reset the game's per-game settings to defaults, disable cheats, and delete sd:/_nds/nds-bootstrap/fatTable/ plus sd:/_nds/nds-bootstrap/patchOffsetCache/ so nds-bootstrap rebuilds its caches.
I tried your new v0.82 version and verified the patched ROM's hash correctly (unmodified fan translation version), but it still hangs on a white screen when booting. Tested this with both the newest version of TWiLight Menu++ and version 27.17.3 / nds-bootstrap v2.8.3 after completely reinstalling TWiLight Menu++.
 
I tried your new v0.82 version and verified the patched ROM's hash correctly (unmodified fan translation version), but it still hangs on a white screen when booting. Tested this with both the newest version of TWiLight Menu++ and version 27.17.3 / nds-bootstrap v2.8.3 after completely reinstalling TWiLight Menu++.
At this point I'm honestly running out of ideas on the project side as to what could still be wrong. The new build no longer has the ROM layout issue from the previous version, it works on my 3DS, my original DSi XL and in emulators, and there are also other people running the same patched ROM without problems. So I don't want to keep changing the patch blindly when I can't reproduce the white screen here.

Could you try a few things for me?

First, please check whether the clean, unpatched US Chrono Trigger ROM boots on the exact same 3DS and SD card through TWiLight Menu++. This is probably the most useful test right now. If the clean ROM also white-screens, then we know the translation patch itself probably isn't the cause.

Also, please manually delete these folders if they exist:

SD:/_nds/nds-bootstrap/fatTable/

SD:/_nds/nds-bootstrap/patchOffsetCache/

Then reset the game's per-game settings in TWiLight Menu++ to defaults and make sure cheats and patches are disabled.

If it still doesn't work, please turn on nds-bootstrap logging. This is the part I'd especially like you to do, because otherwise we're pretty much guessing.

Open:

SD:/_nds/nds-bootstrap.ini

and set:

LOGGING = 1

Then try launching the patched ROM again and let it reach the white screen.

Afterwards there should be a log file called:

SD:/NDSBTSRP.LOG

Please send me that file, or paste its contents.

It would also help if you tell me:
  • whether the clean US ROM boots
  • SD card size
  • whether the card is FAT32 and what cluster size it uses
  • whether cheats were enabled
If the clean ROM works but v0.82 still doesn't, and the log shows where nds-bootstrap stops, that should finally give me something concrete to investigate instead of just trying random changes.
 
Alright, tried everything you listed.

Clean US ROM boots fine on the same 3DS/SD card. I deleted patchOffsetCache (fatTable wasn't there), everything in the per-game settings is default and cheats are off. Patched ROM still gets stuck on the same white screen though.

SD card is 32GB, FAT32 with 32KB cluster size.

I enabled logging and attached the log from trying to boot the patched ROM. I noticed it says Card read addr not found a couple times under the ARM7 stuff, but then continues with ERR_NONE, Card patch successful and AP-fix applied, so no idea if that's relevant.

Hopefully the log has something useful in it.
 

Attachments

Site & Scene News

New Hot Discussed User Submitted