Aaah damn I didnt realise how much it was restricted. I wonder if it would be possible to add support for .xml and game selection, that would be awesome.
I thought it would be cool for people's homebrew games because it would kinda seem like their games where more legit since legit and homebrew games are separated. Also if it had support for everything then it would completely remove everyone asking for developers to release their homebrew as a .cia
--------------------- MERGED ---------------------------
damn :L try wading through the pages of the hblauncher thread for a solution because thats how I found my information. Good luck :L
--------------------- MERGED ---------------------------
OHWIAT I think I may know what is wrong. Did you choose the firmware of your sysnand or emunand when getting the payload because it needs to be that of your emunand.
Thank you very much for posting this! I have CTRBootManager setup to autoboot my emuNAND but occasionally need to run the Homebrew Launcher from within emuNAND. It's a real pain going through it every time from within emuNAND but I don't want to disable autoboot either for a number of reasons. This way when I run that it goes straight to that instead.
Actually, maybe it would be better to edit the other way around? Modify MenuHax to go straight to CTRBootManager instead? I may mess with that later. For now this is quite good enough.
EDIT: On my 2DS I couldn't get it to download the payload yet and while I was at it I just went ahead and did it the other way around. MenuHax now boots ctbm.3dsx and that way all other entry points will default to the normal Homebrew Launcher. That should make stuff like reinstalling MenuHax easier too if I ever need to.
This has all actually saved me. SVDT would not graciously exit when I had CTRBootManager as the thing the launcher was running. Probably too much going on in the system along the way before it. With this fix in place, now I can run SVDT and when it insists on completely exiting it exits back to the launcher instead of freezing on a red screen. Whew!
Actually, maybe it would be better to edit the other way around? Modify MenuHax to go straight to CTRBootManager instead? I may mess with that later. For now this is quite good enough.
EDIT: On my 2DS I couldn't get it to download the payload yet and while I was at it I just went ahead and did it the other way around. MenuHax now boots ctbm.3dsx and that way all other entry points will default to the normal Homebrew Launcher. That should make stuff like reinstalling MenuHax easier too if I ever need to.
This has all actually saved me. SVDT would not graciously exit when I had CTRBootManager as the thing the launcher was running. Probably too much going on in the system along the way before it. With this fix in place, now I can run SVDT and when it insists on completely exiting it exits back to the launcher instead of freezing on a red screen. Whew!
Last edited by Nazosan,
No Problem! Happy to help
The reason I chose not to edit the payload for menuhax is because it requires to change two 'boot.3dsx' instead of one xD
I mean whatever works for whoever is whatever. When I get a proper computer I might look into rebuilding the .cia and everything so that people can have multiple ones. I'm not sure if the hbhomebrew launcher is able to be compatible with .xml and game selection in the future but it would be awesome if that became a possibility in the future. Also if I became anywhere close to a decent developer it would be awesome to make a program that automatically creates the .cia for you (enabling custom banner, icon and such), also having a file in the root of the sd card with all the different things so that it doesnt block up root. Someone somewhere told me that Yellows8 said it was possible but idk where and I currently have no way to do anything but hopefully in the future this will be a thing.
I know all of this can be done in gridlauncher but 1 less step is what people want right?
Well, I think the external configuration thing is what makes the most sense really. It doesn't even have to be as complex as a menu-bearing XML. Just a plain text with single line entries saying which files to boot would be quite sufficient. Oh well. Hopefully he or someone else will think of this at some point.
It depends on your use in the end. For me this means editing only one and then everything works more directly "out of the box" so to speak. I'm using CTRBootManager with MenuHax and if you're not doing that then you don't want to go that way around perhaps. This way around though my system boots the unusual file that I won't update terribly often by default and all the homebrew stuff that may just get frequent updates I can just extract straight to the card.
Similar threads
-
- Article
