Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[Quantumcat]

Not sure how it was annoying either. Im genuinely getting sick and tired of seeing the words Toxic and Drama being toss around at anything. Like how people loosely use the word autistic. That is annoying.

It was annoying. If you don't like drama then don't try and create it?

 

[Joom]

If you think that the post was anyway toxic than you have more issues than you think and clearly does not know what being "toxic" is.

*slow claps*

 

[astronautlevel]

@Quantumcat I wasn't really paying attention, but it looked like you were going back into a lot of threads and a.) compiling a list of issues where the legacy builds helped, and b.) asking the OP of each thread if their problems were solved if they hadn't responded. Thank you for doing this.

That being said, a lot of the OPs were using 8.0, which did admittedly have bugs that Legacy solved. It's not a 1-1 comparison.

 

[Kazuma77]

Please, show me an issue with 8.1 that is solved by using the legacy branch and not user error.

I've got one. It's called booting a 9.2 EmuNAND. Legacy can do it. Luma 8.1.1 cannot.

Unless you make all EmuNANDs on the card minimum size, 8.1.1 crashes launching a 9.2 EmuNAND every time. And doing that breaks compatibility with Cakes and ReiNAND, as opposed to just making the last one a minimum sized RedNAND, while making the rest legacy sized, which is the most compatible option. I've got Puma working with B9S so I can boot 9.2 without wiping my configuration by launching Legacy. So, it's not really impacting me, but you asked for an example, so supply one I have. It is a genuine issue that is not caused by user error.

As for why I'm setting up a second EmuNAND to run 9.2 (aside from Menuhax being a fast homebrew menu launcher, and just because I can), well, *hax still isn't working in 11.5 or even 11.4 on the O3DS (which my SysNAND and first EmuNAND are running, respectively, and while the 11.4 is partial for obvious reasons, it probably still breaks *hax all the same). And as for why I still need *hax, Rosalina still has problems with:

3DSCraft: garbled graphics

ctrHexenII: crashes

ctrQuake: crashes

ctrWolfen: exits to the menu when you pick a game

eDuke3D: crashes

Spectre3DS: console not visible when entering "map start", garbled graphics and an endless stream of "WaitForEvent timeout" errors once game has been properly started

I'm not overly concerned about those first five, but Spectre3DS is Quake in true stereoscopic 3D. There's no menu yet, and you have to use a console command just to start the game, but it's still an impressive port overall.

Its my fault for not bringing any of this up. Honestly, it was considered to be one of the reasons as to why I kept switching to the legacy version of luma 7.1. Now that I think about it, I could have sworn there was a post saying that not all the homebrew files can work with it. This piece of information was buried within the first luma discussion thread. Maybe i'm seeing shit.

Well, you're the only one that can know what you are seeing, so you must decide whether you're seeing shit or not. But as far as homebrew not working, just look up.

 

[astronautlevel]

I've got one. It's called booting a 9.2 EmuNAND. Legacy can do it. Luma 8.1.1 cannot.

The only difference between master and legacy is the inclusion of Rosalina. There's absolutely no reason legacy should be able to launch and emunand and master cannot.

Unless you make all EmuNANDs on the card minimum size, 8.1.1 crashes launching a 9.2 EmuNAND every time.

This seems even weirder - EmuNAND size has absolutely nothing to do with how it boots. A full-size EmuNAND is the exact same as a minimum size EmuNAND - the only difference is the minimum size one has a large amount of unused, unpartitioned space. There is absolutely no reason this should affect an EmuNAND boot.

That being said, I've brought your issue to AW and Tux. AW has a 9.2 EmuNAND we can test on so I'll let you know if your problem is user error or reproducible soon enough.

EDIT: What console model do you have?

As for why I'm setting up a second EmuNAND to run 9.2 (aside from Menuhax being a fast homebrew menu launcher, and just because I can), well, *hax still isn't working in 11.5 or even 11.4 on the O3DS (which my SysNAND and first EmuNAND are running, respectively, and while the 11.4 is partial for obvious reasons, it probably still breaks *hax all the same). And as for why I still need *hax, Rosalina still has problems with:

3DSCraft: garbled graphics

ctrHexenII: crashes

ctrQuake: crashes

ctrWolfen: exits to the menu when you pick a game

eDuke3D: crashes

Spectre3DS: console not visible when entering "map start", garbled graphics and an endless stream of "WaitForEvent timeout" errors once game has been properly started

I'm not overly concerned about those first five, but Spectre3DS is Quake in true stereoscopic 3D. There's no menu yet, and you have to use a console command just to start the game, but it's still an impressive port overall.

This is known and we cannot do anything about it. Those games depend on oddities in how the *hax environment is set up, and replicating that environment without going through the same process (ROP, etc.) is extremely difficult. Those games will probably always require *hax, unfortunately.

 

[The Catboy]

The more I think about it, the more I realize that the two week waiting period is just a front to distract us. The Luma team has no intention to continue the legacy build, so they put on a front to pretend like they do. It's very much apparent that they want to stand behind Rosalina regardless of what we say.
So I purpose someone just fork it. It's open source and the source is still up, anyone can fork it right now and continue working on it. There's no reason to have the Luma team back it if they aren't willing to do so, but there's plenty of reasons for someone else to continue it. We need the option to run Luma3DS without Rosalina and if the Luma team isn't going to give us that, then we need someone to step in.

 

[Quantumcat]

The more I think about it, the more I realize that the two week waiting period is just a front to distract us. The Luma team has no intention to continue the legacy build, so they put on a front to pretend like they do. It's very much apparent that they want to stand behind Rosalina regardless of what we say.
So I purpose someone just fork it. It's open source and the source is still up, anyone can fork it right now and continue working on it. There's no reason to have the Luma team back it if they aren't willing to do so, but there's plenty of reasons for someone else to continue it. We need the option to run Luma3DS without Rosalina and if the Luma team isn't going to give us that, then we need someone to step in.

It's possible that 8.1.1 fixes the problems with it. Maybe we should give it a chance and see if people still have issues.

 

[astronautlevel]

The more I think about it, the more I realize that the two week waiting period is just a front to distract us.

Take your tin foil hat off, please.

The Luma team has no intention to continue the legacy build, so they put on a front to pretend like they do. It's very much apparent that they want to stand behind Rosalina regardless of what we say.

If there are actual, provable issues brought up we'll either

1. Correct them
2. Delay the discontinuation of legacy until they're corrected

So I purpose someone just fork it. It's open source and the source is still up, anyone can fork it right now and continue working on it. There's no reason to have the Luma team back it if they aren't willing to do so, but there's plenty of reasons for someone else to continue it. We need the option to run Luma3DS without Rosalina and if the Luma team isn't going to give us that, then we need someone to step in.

Do what you want, this is an open source project. I'm just going to discourage the thought process "rather than help fix the issues I claim there are I'm just going to take my ball and go home!"

Again, if there are issues that legacy does not have, we will correct them. It's not like we're trying to push broken software for some nefarious reason. And honestly, I kind of take offense to the idea that the Luma team doesn't want to fix issues.

 

[TuxSH]

3DSCraft: garbled graphics

ctrHexenII: crashes

ctrQuake: crashes

I think most, if not all, of those issues are solvable by simply rebuilding those games with latest ctrulib.

 

[ihaveahax]

The more I think about it, the more I realize that the two week waiting period is just a front to distract us. The Luma team has no intention to continue the legacy build, so they put on a front to pretend like they do. It's very much apparent that they want to stand behind Rosalina regardless of what we say.
So I purpose someone just fork it. It's open source and the source is still up, anyone can fork it right now and continue working on it. There's no reason to have the Luma team back it if they aren't willing to do so, but there's plenty of reasons for someone else to continue it. We need the option to run Luma3DS without Rosalina and if the Luma team isn't going to give us that, then we need someone to step in.

if rosalina was disabled then it would lose almost everything, in which case you might as well just go to reinand or whatever. you say people should have a choice, and they should but those should have limits; both for the end-user, and for the developers. adding something to disable the rosalina system module is too much effort for little gain. how many times does this need to be re-stated?

and yes, of course they want to keep rosalina going. an entirely new system module opens up new possibilities. the way certain things have been re-implemented in rosalina are better than they were previously (e.g. language/region emulation has better compatibility than it did pre-rosalina).

8.0 had issues, 8.1 fixed most of them, and hopefully with 8.1.1 the last major bugs are gone. if there's any more then it would be helpful if they were put onto the issue tracker (because a forum is not an issue tracker! it is very hard to use when trying to follow issues!)

just complaining and coming up with conspiracies like "devs want to push rosalina on us despite its flaws!" gets us absolutely nowhere. there is zero reason the devs would want to keep bugs in a cfw. but it doesn't help if they don't know what they are.

 

[The Catboy]

Take your tin foil hat off, please.

If there are actual, provable issues brought up we'll either

1. Correct them
2. Delay the discontinuation of legacy until they're corrected

Do what you want, this is an open source project. I'm just going to discourage the thought process "rather than help fix the issues I claim there are I'm just going to take my ball and go home!"

Again, if there are issues that legacy does not have, we will correct them. It's not like we're trying to push broken software for some nefarious reason. And honestly, I kind of take offense to the idea that the Luma team doesn't want to fix issues.

if rosalina was disabled then it would lose almost everything, in which case you might as well just go to reinand or whatever. you say people should have a choice, and they should but those should have limits; both for the end-user, and for the developers. adding something to disable the rosalina system module is too much effort for little gain. how many times does this need to be re-stated?

and yes, of course they want to keep rosalina going. an entirely new system module opens up new possibilities. the way certain things have been re-implemented in rosalina are better than they were previously (e.g. language/region emulation has better compatibility than it did pre-rosalina).

8.0 had issues, 8.1 fixed most of them, and hopefully with 8.1.1 the last major bugs are gone. if there's any more then it would be helpful if they were put onto the issue tracker (because a forum is not an issue tracker! it is very hard to use when trying to follow issues!)

just complaining and coming up with conspiracies like "devs want to push rosalina on us despite its flaws!" gets us absolutely nowhere. there is zero reason the devs would want to keep bugs in a cfw. but it doesn't help if they don't know what they are.

So I was still right, you guys are still planning to discontinue it no matter what the outcome. Even if it's delayed, it's still going to be removed at some point.
And quite honestly this stopped being about the errors and more so an argument of choice. The users are slowly loosing their choice to run this CFW without Rosalina. It's either have it your team's way or what? I'd suggest ReiNAND, but of course that would piss off the entire community who still chant, "Just use Luma."
Luma3DS is slowly becoming as controlling as Nintendo.

 

[Quantumcat]

So I was still right, you guys are still planning to discontinue it no matter what the outcome. Even if it's delayed, it's still going to be removed at some point.
And quite honestly this stopped being about the errors and more so an argument of choice. The users are slowly loosing their choice to run this CFW without Rosalina. It's either have it your team's way or what? I'd suggest ReiNAND, but of course that would piss off the entire community who still chant, "Just use Luma."
Luma3DS is slowly becoming as controlling as Nintendo.

Maybe just wait and see if 8.1.1 fixes the issues.

 

[The Catboy]

Maybe just wait and see if 8.1.1 fixes the issues.

It's not even about the errors anymore. It's the reality that we have to settle with a feature without an option or a choice in the matter.

 

[astronautlevel]

So I was still right, you guys are still planning to discontinue it no matter what the outcome

I said earlier in the thread why legacy will have to be discontinued eventually, in the release it said legacy would be discontinued eventually, what part of this was a secret? There are a lot of reasons legacy should be discontinued once the bugs are worked out. I stated them earlier in the thread but I'm on mobile now so I'm not gonna go back.

And quite honestly this stopped being about the errors and more so an argument of choice. The users are slowly loosing their choice to run this CFW without Rosalina. It's either have it your team's way or what? I'd suggest ReiNAND, but of course that would piss off the entire community who still chant, "Just use Luma."
Luma3DS is slowly becoming as controlling as Nintendo.

Did you read any of ihaveamac's response? He addressed this directly.

Edit: forgot to address that last part. You clearly have some angry vendetta against luma and it's developers so you just make some wide argument about "choice" and accuse the luma team of being some nefarious force trying to control the community. I swear to god you sound like Alex Jones right now.

 

[The Catboy]

I said earlier in the thread why legacy will have to be discontinued eventually, in the release it said legacy would be discontinued eventually, what part of this was a secret? There are a lot of reasons legacy should be discontinued once the bugs are worked out. I stated them earlier in the thread but I'm on mobile now so I'm not gonna go back.

Did you read any of ihaveamac's response? He addressed this directly.

I did read it and I still stand by my statements.

 

[ihaveahax]

So I was still right, you guys are still planning to discontinue it no matter what the outcome. Even if it's delayed, it's still going to be removed at some point.
And quite honestly this stopped being about the errors and more so an argument of choice. The users are slowly loosing their choice to run this CFW without Rosalina. It's either have it your team's way or what? I'd suggest ReiNAND, but of course that would piss off the entire community who still chant, "Just use Luma."
Luma3DS is slowly becoming as controlling as Nintendo.

quite honestly it doesn't feel like you're reading my/our posts, which makes it feel like a waste of time trying to explain......

not every last thing needs to become a choice, a toggle or whatever. some things are done and fixed in-place for a reason. some things are changed and thrown out if the new thing is better to use and easier to maintain. trying to maintain an option to disable the rosalina module will disable many of the features, and maintaining the old codebase is too much work and not worth it when the new thing is better.

legacy was created with the release of 8.0 since something major like this would obviously have issues. now we're at the point where most of the known issues are fixed, so legacy no longer serves a purpose.

 

[Quantumcat]

It's not even about the errors anymore. It's the reality that we have to settle with a feature without an option or a choice in the matter.

But if Rosalina isn't the cause of any issues, why would people need to turn it off? You can just ignore it.

 

[ombus]

This is so funny.. people that dont want rosalina use the legacy and dont complain when its not updated.. there done...you cant demand anything to the team, you get a great cfw if not the best (my opinion) so there you have it.. use latest legacy or use 8.1.1 and future updates WITH rosalina like it should be.

 

[DarkSynopsis]

But if Rosalina isn't the cause of any issues, why would people need to turn it off? You can just ignore it.

This! Nothing is forcing anyone to boot up Rosalina and it's not like it's slowing down games or anything? I'd bet most don't even know the button combo since they wouldn't use the features.

Been using since 8.0 and never had to go back to legacy, as said before the error screens are instead of a hard freeze not an issue with Luma

Urgh... why am I adding to fuel to the fire... Those who want to use Legacy, just stay on it? Apparently it's bug free and works anyway and 8+ is all Rosalina that legacy users won't use so why fuss?

Even though I've still not dived deep into Rosalina all the features it brings are great! still want to sit down and enjoy the input redirection without all the NTR fuss.

 

[Amapola62]

I don't know how to report issues on Github so...if I get a crash, I won't be able to report it unless someone explain me how to report stuff on Github...do I need to create an account there for example?