Those we're originally a thing, but we're removed as booting DS games got faster. Now it's just "nds-bootstrap: Please wait...".Hey @Robz8 man, good night, I wonder if you could add to Extras some Loading screens for the booting of nds games, please? Thanks in advance.
Those we're originally a thing, but we're removed as booting DS games got faster.
Thanks! I get the graphical glitch 100% of the time when booting 3DS TWLMenu++ -> Slot-1 Flashcard TWLMenu++, I've seen reports of it being a random issue, but it's not random for me at all, which is why I thought I'd mention it. Autoboot or going through AKAIO doesn't make a difference for that. Never happens when running directly from the flashcard or running from 3DS only. It goes away if I sleep the 3DS and reopen, but if I go into settings or the DS Classic menu and come back, the glitch always reoccurs, just as long as I have 3DS TWLMenu++ and the flashcard TWLMenu chainloaded.
- The graphical glitch is a TWL_FIRM bug that happens randomly.
OK, nice to know. Not a problem, just wasn't expecting it.
- The "SCFG access in Slot-1" overrides the "SD access in Slot 1" option in TWLMenu++.
Cool, this is not a problem either since I was aiming for autoboot, was just poking around with "Slot-1 MicroSD access", but my goal was to end up running it from the flashcard in the end.
- The white screen issue with "S1SD: Use nds-bootstrap" set to "Yes" is expected, since arm7 cannot init the AK2i DLDI successfully for some reason.
That's why it recommended to run TWLMenu++ from the flashcard instead, with autoboot set up as well.
Why a ROM doesn't boot (via AKAIO) when launched by TWLMenu++, idk.
I set up autoboot, the Acekard now autoboots TWLMenu++, but it seems to break loading all roms when nds-bootstrap is disabled, doesn't matter if booted directly from Slot 1 or via the 3DS TWLMenu++. White screen on both screens, gets stuck for a while, then goes back to TWLMenu++ after clicking buttons. Any pointers on how to debug this would be appreciated, I can set up a dev environment (or raise an issue on GH) if needed.
- The .nds not found error should be fixed by setting up autoboot. If that doesn't fix it, idk.
What should happen with nds-bootstrap disabled, is to show a black screen, then a "Loading..." text, then boot the game.I set up autoboot, the Acekard now autoboots TWLMenu++, but it seems to break loading all roms when nds-bootstrap is disabled, doesn't matter if booted directly from Slot 1 or via the 3DS TWLMenu++. White screen on both screens, gets stuck for a while, then goes back to TWLMenu++ after clicking buttons. Any pointers on how to debug this would be appreciated, I can set up a dev environment (or raise an issue on GH) if needed.
Also about this, I checked both files in HxD and they're the same, but as said one works and the other does not. Maybe is in the naming of the file?Hello! I'm here to report a small issue with the Widescreen feature. For me it works with Pokémon Oro Heartgold, however, it does not with Plata Soulsilver (both versions the spanish ones). Is there a solution to this? Also, recently I updated my TwilightMenu to the last version.
Nope, though you can copy the widescreen .bin file for the game, and rename it to the ROM filename, plus ".bin".Also about this, I checked both files in HxD and they're the same, but as said one works and the other does not. Maybe is in the naming of the file?
Gotcha! Thanks again RobzNope, though you can copy the widescreen .bin file for the game, and rename it to the ROM filename, plus ".bin".
Are you sure it's only the settings menu with this issue?Hi people, everyone are safe at home?
I installed the latest TM++ in my R4 (Original R4 or maybe a clone of it), and the settings menu of TM++ is "bugged", I followed instructions from the site, I can't remember if I used TM++ before in this flashcard since I have some different flashcards.
UPDATE: For some reason, aparently the problem is the EzFlash IV, removed it from Slot-2 and the TM++ is not bugged anymore
Are you sure it's only the settings menu with this issue?
The DSi, 3DS, Saturn, and HBL themes use the same font code, so the bug should've happened in those themes as well.
It currently doesn't work because of unpatched functions, and yes, it should work in the 100th version of nds-bootstrap.
The cheat menu can only be opened, if the game being played is from the console's SD card.Before I forget, for some reason I cannot use cheats in my flashcart while using Twilight Menu. Last time I tried in the 3DS version, it worked ok, but when using the flashcart version (either standalone or in conjunction with the 3DS version) the cheat menu doesn't appear. The "x" to open cheats is nowhere to be seen, and even if I press it, nothing happens. I made sure to place usrcheat.dat inside the extras folder, but it's not working. Any idea why?
Just follow the updated guide in the first post.hello, I haven't used my 3ds in a while, just updated TWLightmenu, something happen on widescreen config?, I cant play on it anymore, do I need a new version to patch the widescreen? does it work with autoboot from flashcards or only works on TWL installed on the 3ds itself?
Just to let you know, for some reason if I use TW++ in my OR4 the EZ-Flash IV gets corrupted and the glitched menu appears in TW++, sadly I can't use both for now, will try with Acekard 2i to see if that happens too.Are you sure it's only the settings menu with this issue?
The DSi, 3DS, Saturn, and HBL themes use the same font code, so the bug should've happened in those themes as well.