Homebrew [DS(i)/3DS] TWiLight Menu++ - GUI for DS(i) games, and DS(i) Menu replacement
- Thread starter RocketRobz
- Start date
- Views 4,229,300
- Replies 16,080
- Likes 256
I'm not sure if this is a bug, but the L button to return to previous page of DSiware doesn't seem to work. Pressing R to go to next page works though.
Edit: I just modified the settings to go back to PAGE 0, but it becomes a pain when pressing R accidentally :-). By the way why is it that when I press down on the DSIware page it goes back to display the DSIWAREs but I cannot launch any of them then when I press up and the screen is refreshed, it's ok again.
Edit: I just modified the settings to go back to PAGE 0, but it becomes a pain when pressing R accidentally :-). By the way why is it that when I press down on the DSIware page it goes back to display the DSIWAREs but I cannot launch any of them then when I press up and the screen is refreshed, it's ok again.
Last edited by vinzanity,
yeah, but why cant i use a rom? i could before, besides, even when i have my mario kart DS cart on my slot 1 it still doesnt get past the save corruption error in tetris DS
Got no problem with the touchscreen while playing Layton and The Diabolical Box on my o2ds (Game on SD, CFW Luma latest, 11.6 fw)
I don't understand! Either the touch screen works or it doesn't. The 2ds and 3ds are basically the same. Does the touch screen work on 3ds? Yes or no? About to take a hammer to my 3ds.
Also is there a fix for the dsiware selection where the L button will not work to go back a page on the dsi? I've had to delete my settings file a few times just to get it back to the first page.
- Joined
- Apr 17, 2018
- Messages
- 46
- Trophies
- 0
- Age
- 22
- Location
- What the hell are you doing?
- Website
- imtakingapi.ss
- XP
- 290
- Country
(11.6, Boot9strap+Luma CFW) So I was able to get a game to work (Super Mario 64 DS) but now the touch screen doesn't work?
Last edited by Hepointatsquib,
I could not get the my flashcard to work. Unlike TW Loader there is no menu in DSiMenu ++ to select a flashcard. In TWLoader I used TWLoader to launch my roms from my DSTT that would normally not load in the 3DS home menu. Now nothing works. I copied all files as described in there locations on the 3DS SD card and on the SD card on the flashcard. DSiMenu++ crashes if I start my flashcard from it and if I put that flashcard in my DS Lite it refuses to start and gives me "error 1". Do you have any idea what goes wrong?
As far as I really like that change from TWLoader to DSiMenu++... I have a problem with running games from it on my 3DS.
For example: on my 3DS it restarts to HOME Menu after selecting any title and even after turning on Quick-start ROM, it's not working pretty well. New Super Mario Bros. throws out "Could not erase data" error after launching. Some titles on the other hand freeze on "Creating save file...." screen.
Tried to run MKDS and it loads without any problem, but for some reason, it automatically skips every demo screen in the game. Same goes with Sonic Rush. Automatically skips to the title screen, skipping characters introduction.
I have no idea what is going on or what am I doing wrong.
For example: on my 3DS it restarts to HOME Menu after selecting any title and even after turning on Quick-start ROM, it's not working pretty well. New Super Mario Bros. throws out "Could not erase data" error after launching. Some titles on the other hand freeze on "Creating save file...." screen.
Tried to run MKDS and it loads without any problem, but for some reason, it automatically skips every demo screen in the game. Same goes with Sonic Rush. Automatically skips to the title screen, skipping characters introduction.
I have no idea what is going on or what am I doing wrong.
Last edited by ChipJockey,
The only problem i faced were lags in ingame (expected), no sound in video clips, and whenever i want to launch a game, i need to search it in the sd, click on a, gets me back to the home menu then relaunch dsi menu ++ and select last-ran game instead of start dsi menu++
This was the very first release targeting the 3DS. Of course there are problems.
The issue is that SRLoader worked properly on 3DS, and changes made recently for DSiMenu++ broke 3DS support.
It's not an important issue becuase right now 3DS owners can till use TWLoader. It's been discontinued but it didn't stop working.
My point is, this should've been tested more before the release. Especially for such a giant flaw that you couldn't possibly ignore.
Perhaps it was a rushed release but the incomplete savedata support in nds-bootstrap shows the present state of affairs.
I guess Robz8 is just trying to get things done by focusing on one detail at a time.
yep, i mean, the DSi version isnt even that different from SRloader's last build, the NES emulator is still shit (there are better DS NES emulators) and GBArunner2 is still outdated
Well, I didn't know the new rebooting into selected game method won't work for some users (me included), so I added the Quick-start ROM option to work around that issue, so as a result, the touch input won't work when using that option, and the issue won't be fixed, 'til there's new bootstrap version released.
--------------------- MERGED ---------------------------
Did you put the "_nds" folder on the flashcard root? Error 1 means that the file trying to be booted is not found.
Touch input works for him, because he's not using the Quick-start ROM option.
I only had one page of DSiWare, so didn't know that bug was even a thing.
The touch issue when using the Quick-start ROM option is the cause of your issue. Will be fixed in the next nds-bootstrap version.
Yes. That's why I said "DSiMenu++ Launcher", not "DSiMenu++".
Last edited by RocketRobz,
Similar threads
- No one is chatting at the moment.
