managed to get past the initial screen did the first battles, tried to save, froze againdoes this support pokemon black & white? for some reason it gets really slow on the intro scene sometimes even crashing, using a r4i-sdhc, actually it doesn't crash, it just freezes, and it's not sometimes it's everytime... i can't get past the "tell me your name part"
How likely is it that forwarders for Acekard 2i get figured out soon? Should I keep a close eye on the thread or just check back in a month or two?
What CFW are you using? And SysNAND or EmuNAND?I just get the "An error has occurred" screen, sadly, despite the flashcard working. Any suggestions? My card is a DSTT clone
You need to rebuild them for the DSTWO, since it uses a different forwarder template.@Robz8, I've been using this forwarder on my DSTT clone for about a month now. Only tried MegaMan StarForce and StarForce 2. Both work great. I just saw you added support for DSTWO. But with this forwarder, do the dstwo real time save or slow motion feature works? Also, does that mean the forwarder work with the DSTWO plus as well? (BTW, I don't have a DSTWO or DSTWO plus) Thanks.
Use short names for games ,For some reason this isn't working on my 3DS. I'm using a Supercard DSWTWO+ on a Luma3DS(6.0.1 Dev) CFW n3DS running 11.0, and I'm attempting to play after installing it on sysNAND. The game is Pokemon White, and it's not customized or edited, but the icon/banner is still white/blank, and whenever I attempt to load it I get the "error has occurred" message.
I'm using Luma3DS on emunand. The flashcart works perfectly on emunand though.What CFW are you using? And SysNAND or EmuNAND?
What CFW are you using? And SysNAND or EmuNAND?
--------------------- MERGED ---------------------------
You need to rebuild them for the DSTWO, since it uses a different forwarder template.
Also, the DSTWO forwarders only work on Luma3DS v6 developer branch.
Edit: Misread your question. I think they should work on the DSTWO+ too since it uses the same loader for NDS games. But who knows?
--------------------- MERGED ---------------------------
Do you mean the Forwarder3DS app? I made it, and it's closed source right now. I will probably release the source in github once I'm not able to update it anymore.
And if you were talking about the NDS template files and all those 3DS-side files, everything is mostly work of @Robz8 and some are from @ahezard
Originally, the app generated either a NTR (DS normal game) forwarder or a TWL (DSi enhanced game) forwarder, each with its own template. However, this made impossible to move correctly the NTR forwarders in the 3DS DSiWare management options. So, we talked about it and decided to always use a TWL template, so even NTR games with 0x840 length banners would translate to a 0x23C0 byte length banner for the TWL template to be alright with it.Oh, sorry about that... I thought @Robz8 made the GUI... shows how much I pay attention...
I've made a forwarder file that does things a little differently than the ones provided and I have a couple suggestions / requests for using external NDS forwarder files
You can get the banner offset of the NDS file from bytes 0x68 - 0x6C
I've made a sample java file
For the .nds path and length, what about searching for some marker strings in the forwarder instead of hard coding the offset and length?
Something like <<<NDS Path Start and NDS Path End>>>
The banner size won't always be 0x23C0 bytes...
For example, ndstool compiles a .nds with a banner size of 0x840 bytes (do you know why or have a workaround @Robz8?), bytes 0x208 - 0x20C contain the size... You could probably modify this byte range with the size of the replacement banner and add the additional bytes to the NDS file (not tested)... currently if I try to give your app a .nds with a 0x840 byte banner it generates no output
These changes would make it easier for testing new / updated forwarders since it would auto-detect all of the file offsets (you could still give the user the prompt to confirm they're correct though...)
Thanks for that info, that explains the size difference...Originally, the app generated either a NTR (DS normal game) forwarder or a TWL (DSi enhanced game) forwarder, each with its own template. However, this made impossible to move correctly the NTR forwarders in the 3DS DSiWare management options. So, we talked about it and decided to always use a TWL template, so even NTR games with 0x840 length banners would translate to a 0x23C0 byte length banner for the TWL template to be alright with it.
Here you can find specs about the banners: http://problemkaputt.de/gbatek.htm#dscartridgeicontitle
We fill the banner data with more titles so we cover the extra language titles that aren't in NTR games, and put the icon and palette data in the places where the animation has their first banner and palette, so it gets alright with the TWL icon data.
After all of this, the CRC16 checksums are calculated again, just as the link I put says they should be.
Oh. I hadn't understood what you meant.Thanks for that info, that explains the size difference...
But, as far as the external templates go...
Would it be possible to auto-fill the GamePath offset, banner offset, and GamePath length based on my above post? I have some sample code
You could still show the dialog but auto-fill the text fields with the detected data
That way for testing new templates, you wouldn't need to go into a hex editor to find the offset values / length for everything
For the .nds path and length, what about searching for some marker strings in the forwarder instead of hard coding the offset and length?
Something like <<<NDS Path Start and NDS Path End>>>
By the way. I've changed my mind about the source.Thanks for that info, that explains the size difference...
But, as far as the external templates go...
Would it be possible to auto-fill the GamePath offset, banner offset, and GamePath length based on my above post? I have some sample code
You could still show the dialog but auto-fill the text fields with the detected data
That way for testing new templates, you wouldn't need to go into a hex editor to find the offset values / length for everything
Oh. I hadn't understood what you meant.
Yeah, I can add that. Still leaving it open for editing for if someone else wants to try something different.
I don't get this part at all. This would mean @Robz8 should hard code some markers in every template, right? And anyone wanting to make a template to test would need to remember to add these markers. It's not a standard thing right now, like the banner location you commented.
We would need to talk about it.
Just rolled out update v2.1, including all of your suggestions. Excepting the ARM9 byte, will look into it later, and if @Robz8 implements it to the other templates.Actually...the NDS cartridge header does specify where the banner is located... 0x68 and is 4 bytes...
But on the topic of the markers... if you take a look at my template on line 57, you'll see what I mean
It would make it easier to find the string programatically than just putting game.nds followed by a bunch of spaces in the code
You could certainly still pop up the offset dialog in case someone didn't use the markers but have them pre-filled if they did
I also added another thing specific to my template (which your GUI obviously wouldn't support...)
There's a string with the value of Double ARM9 Speed = 0 which if you change the 0 to a 1 my code would double the ARM9 speed. (implementation can be found here)
Maybe you could search for this string and if it exists add a checkbox to the individual game options? Then the other templates could implement