From what I've read, it's more of a placeholder ATMWorking perfectly for me and 0 crashes.The "Settings" icon thing doesn't seem to work yet though.
From what I've read, it's more of a placeholder ATMWorking perfectly for me and 0 crashes.The "Settings" icon thing doesn't seem to work yet though.
It should allow those of us who think they're on thin ice with Nintendo to avoid their monitoring, especially after homebrew apps are updated to work with the expanded permissions that Rosalina+new-hbmenu allows (aka full arm11 system permissions). That way, many 3DSX apps can be effectively feature-for-feature identical to their CIA forms; the only ones that aren't would be apps which require ARM9 kernel access, and most apps that are important and need ARM9 access run as .firm payloads these days. Either way, whichever one you use would become a matter of preference (or as some of us see it, a matter of whether you feel like getting banned).This is a great work.
But I've got one question. Is there any reason to still use .3dsx apps today, especially if you are on 11.4 SysNAND with Luma3DS + boot9strap?? I mean, isn't .3dsx a bit obsolete?
For example, many emulators in .3dsx form aren't as fast as their .CIA counterparts because .CIA allows dynarec usage...
Stock 3ds's still need .3dsx files from the hbl to install cfwThis is a great work.
But I've got one question. Is there any reason to still use .3dsx apps today, especially if you are on 11.4 SysNAND with Luma3DS + boot9strap?? I mean, isn't .3dsx a bit obsolete?
Since we have full control of the system, what's keeping us from having the CFW patching out the 300 limit?Practically sounds like a bypass to the 300 icon limit
Someone has to program a whole new home menu - this has been possible from the beginning with a9lh and no one has done it so very unlikely it will suddenly happen now.Since we have full control of the system, what's keeping us from having the CFW patching out the 300 limit?
Yeah, I've never held my breath, I just thought it could be patched like the restrictions and signature checks. I guess not though.Someone has to program a whole new home menu - this has been possible from the beginning with a9lh and no one has done it so very unlikely it will suddenly happen now.
edited....A grand total of three emulators can use dynarec for better performance - one of which performs badly regardless (PSX rearmed), another of which introduces a nasty random crash bug if it is switched on (gpsp) leaving only a single lone emulator with a clear and stable benefits when launched as a cia on CFW (picodrive).
Of all the reasons to install CFW I'd have to say that running better performing emulators has got to be almost bottom of the list (unless you're the world's biggest 32X fan).
It still needs quite a few more bugfixes before it becomes a viable option for avoiding Ninty...My homebrew apps are freezing on hbl 2.0
(If i Start them i get blackscreen and it stays there)
See here:I just noticed that the latest version of decrypt 9 is broken on b9s 1.2.
Decrypt9 version that works with this:
https://twitter.com/SciresM/status/871517702778757120
Follow this guide: https://3ds.guide/a9lh-to-b9sIs there any way to update from a9lh to boot9strap that works? It never reboots when you go into safehax
From what I read, it's more of a hardware limitation. It doesn't have enough RAM to do more than 300 (maybe CPU too). It would probably start to lag seriously. It's Nintendo being Nintendo by cheaping out on bits to be profitable from the start.Yeah, I've never held my breath, I just thought it could be patched like the restrictions and signature checks. I guess not though.
Follow this guide: https://3ds.guide/a9lh-to-b9s
Uh.. why do you need safehax?It never reboots when you go into safehax