Hacking Luma3DS - Noob-proof 3DS Custom Firmware

[The Catboy]

Neither will be implemented.

I can't make that my last post without this question be answered. Why not give the option to disable Rosalina to the user? Why does the user have to use Rosalina even if they don't want to use it? Why are you guys so adamant to make the user to use this feature?

 

[Quantumcat]

I can't make that my last post without this question be answered. Why not give the option to disable Rosalina to the user? Why does the user have to use Rosalina even if they don't want to use it? Why are you guys so adamant to make the user to use this feature?

I wish I was brave enough to compile stuff and run it on my own console to test, or I might try to fork it and implement a switch myself in the config.

 

[Aurora Wright]

Expect it's issues that I have yet to replicate on any other CFW. I can't accomplish the same ARM11 crashes that have become extremely common since Rosalina was introduced.
Then this would be a good time for someone from the Luma3DS team to actually go to these threads and suggest making bug trackers. The Luma3DS team is the one choosing the avoid the community.
Anyways, I will make this my last post in this thread. It's very much apparent that those you who are still involved in the community aren't willing to work with the community.

Since from the sound of it you ran tests and found reproducible crashes specific to Luma 8.x, maybe you could report them to the issue tracker instead of complaining here, which helps nobody. We'll be glad to investigate bugs reported to github but we have zero obligations to come read all threads here on gbafail (you know that I don't come here anymore as I don't feel respected as a human being by users and staff, so it surprises me that you of all people are complaining about this).

 

[ihaveahax]

I can't make that my last post without this question be answered. Why not give the option to disable Rosalina to the user? Why does the user have to use Rosalina even if they don't want to use it? Why are you guys so adamant to make the user to use this feature?

I'd like to re-post this old post:

Some features that were previously implemented in loader (3ds injector), or in "main" Luma, although with limitations (language emulation via loader had known incompatibilities with few games, ARM11 exceptions had very limited space they could use because they used padding in Kernel11) were reimplemented in a better way within Rosalina (language emulation specifically uses a completely different approach, instead of patching the game for the desired region, interprocess communication hooking in Rosalina makes it possible to spoof the response to the game when it asks for the console region). The GPU protection svc which was stubbed by patching the kernel is now "stubbed" via Rosalina as it hooks the svc table, same for adding "CFWInfo" (the svc used by Luma Updater and stuff) and svcBackdoor. Disabling Rosalina in 8.0+ means fully disabling language emulation and then you get people complaining it doesn't work and all those important features (NTR and other homebrew wouldn't work without svcBackoor FWIW), or making a mess to maintain both approaches to *everything* in the code.
It's not as easy as you think.

disabling rosalina system module would basically disable a lot of features.

if you mean the rosalina menu, the key combination can be changed if the default one is an issue. or disable the menu in source if you desperately don't want that.

 

[Quantumcat]

I'd like to re-post this old post:

disabling rosalina system module would basically disable a lot of features.

if you mean the rosalina menu, the key combination can be changed if the default one is an issue. or disable the menu in source if you desperately don't want that.

Oh ok, fair enough. Sounds like it would be very difficult to turn it off.

 

[Deleted member 412537]

Didnt even knew about these issues with Rosalina.

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.

 

[Bluespheal]

Since from the sound of it you ran tests and found reproducible crashes specific to Luma 8.x, maybe you could report them to the issue tracker instead of complaining here, which helps nobody. We'll be glad to investigate bugs reported to github but we have zero obligations to come read all threads here on gbafail (you know that I don't come here anymore as I don't feel respected as a human being by users and staff, so it surprises me that you of all people are complaining about this).

Woah, rare to see you here, I miss you, but yeah, seeing how toxic and nonsensical users are to devs here... I totally get it.

 

[The Catboy]

I wish I was brave enough to compile stuff and run it on my own console to test, or I might try to fork it and implement a switch myself in the config.

It actually can be removed from source.

Since from the sound of it you ran tests and found reproducible crashes specific to Luma 8.x, maybe you could report them to the issue tracker instead of complaining here, which helps nobody. We'll be glad to investigate bugs reported to github but we have zero obligations to come read all threads here on gbafail (you know that I don't come here anymore as I don't feel respected as a human being by users and staff, so it surprises me that you of all people are complaining about this).

You know me too well, I have run a few tests upon request and was able to replicate the results. Although this would require me to go through the forums to remember what I results I was able to replicate. Which is a task that is honestly not worth my time and the posts never got back to me after I suggested using the Legacy builds.

I'd like to re-post this old post:

disabling rosalina system module would basically disable a lot of features.

if you mean the rosalina menu, the key combination can be changed if the default one is an issue. or disable the menu in source if you desperately don't want that.

Oh yeah, y'all got too ahead of yourselves with this one.

 

[TheGuyMadeOfTofu]

Woah, rare to see you here, I miss you, but yeah, seeing how toxic and nonsensical users are to devs here... I totally get it.

This whole "muh toxic" thing is starting to look like some kind of tumblr talk. Really rustles my jimmies.

 

[ihaveahax]

Oh yeah, y'all got too head of yourselves with this one.

it's not necessarily a bad thing. the way rosalina implements the things listed is much better than before.

Which is a task that is honestly not worth my time and the posts never got back to me after I suggested using the Legacy builds.

that's pretty much what Aurora Wright/TuxSH wanted to avoid, people just sticking around on legacy because their issues got fixed, not trying them with newer versions (8.0 had issues, 8.1 fixed most or all of them we hope).

what I think we should be doing (since digging through several topics and pages of posts is a lot of work) is getting people to try 8.1.1 again, and if they still have an issue that isn't on legacy then we can file a proper issue and fix it. just staying on legacy makes this slower.

 

[Aurora Wright]

Here are three threads in the last month where using the legacy version fixed the issue. Maybe have a look, Tux & co.

https://gbatemp.net/threads/nintendo-3ds-an-exception-occurred-brick-3ds-unusable.478298/
https://gbatemp.net/threads/arm11-core-1-error-when-i-try-to-launch-mighty-gunvolt-burst.477359/ (went from black screen to 3DS loading screen after using legacy because he didn't have the seed)
https://gbatemp.net/threads/data-abort.477517/

There are others where we suggested they try it but they never got back to us as to whether it worked. That's probably a sign that it worked.

Two of these are Luma failing to start which is 99% due to the undefined behavior which happened in 8.0 (the way the kernel extension was handled). 8.1 changed it completely and fixed these failures on boot. The other is loader crashing because of seed missing, the difference in behavior is due to exception handlers being enabled by default in 8.x and being disabled by default in 7.x (so the exception in 7.x resulted in infinite logo loading).

This whole "muh toxic" thing is starting to look like some kind of tumblr talk. Really rustles my jimmies.

I'm glad you posted this, I needed a post to exemplify why I left

 

[RustInPeace]

Since from the sound of it you ran tests and found reproducible crashes specific to Luma 8.x, maybe you could report them to the issue tracker instead of complaining here, which helps nobody. We'll be glad to investigate bugs reported to github but we have zero obligations to come read all threads here on gbafail (you know that I don't come here anymore as I don't feel respected as a human being by users and staff, so it surprises me that you of all people are complaining about this).

I wanted to point that out because her arguing is honestly bothering me, as if she just wants to argue, seemingly forgetting she's defending this particular place and ignoring other avenues to voice concerns. But you said it better than I could. Personally I don't notice any issues with Rosalina, I get crashes mostly with using BootNTR, and I just chalk it up to that being unstable, the exception messages just replace the frozen screen I got before. The extent of my CFW uses stretches only to Pokemon, so at least in those fields, Rosalina hasn't done anything offensive, to the point that I forget it's there.

 

[RustInPeace]

Double post. Err, there's a program I use a lot, 3DSRNGTool that recently implemented Rosalina support, so in the future I'll be more familiar with it.

 

[TheCyberQuake]

Any crashes I get now happened before with either a legit crash or a loop. Except now it actually let's you know it crashed and gives potentially useful info.

 

[TheGuyMadeOfTofu]

Two of these are Luma failing to start which is 99% due to the undefined behavior which happened in 8.0 (the way the kernel extension was handled). 8.1 changed it completely and fixed these failures on boot. The other is loader crashing because of seed missing, the difference in behavior is due to exception handlers being enabled by default in 8.x and being disabled by default in 7.x (so the exception in 7.x resulted in infinite logo loading).

I'm glad you posted this, I needed a post to exemplify why I left

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.

 

[Quantumcat]

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.

You have to admit, it was kind of annoying though.

 

[Billy Acuña]

Can we stop the drama alreally?
Is not like Luma is the only CFW/Bootmanager out.

 

[TheGuyMadeOfTofu]

You have to admit, it was kind of annoying though.

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.

 

[RustInPeace]

Like how people loosely use the word brick.

More familiar in this community.

 

[Lacius]

@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.