View attachment 168875​

@Reisyukaku's ΔLaunch has officially released a ΔLaunch early build together with ReiNX 2.3!

We've already covered this project in its first development stages in a previous news post, however, if you need a quick refresher, ΔLaunch is Home Menu replacement for the Nintendo Switch. It replaces the qlaunch process of the Switch's OS, which handles the Home Menu as well as a few applets, such as the news and system settings. Most of its appearance can be customized by editing an INI file on the SD card: not only this will allow for easily installable and distributable themes without relying on custom formats, but you can also edit the various elements' position and layout effortlessly! Several background layers are supported and, for those who want a fresh new look for their system, a PS4-style aesthetic is also available. Last, but not least, you won't have to worry about removing and reinstalling the themes after a system update, as ΔLaunch effective overrides the firmware's system menu! However, some of the previously announced features are missing or in a non-working state in this early build, such as folder support and the web browser icon.

As previously mentioned, ΔLaunch is available as an optional sysmodule with the latest version of ReiNX (2.3). The project is still very much a work in progress, so there could be unexpected bugs and issues. If you want to try it, a link to its GitHub's release page can be found in the sources below. Keep in mind there may be untrustworthy builds floating around the internet due to an unauthorized source leak that happened earlier today, so users are advised to only download officially released builds from its repo.

- This news thread is about the homebrew's official release. Please avoid discussing its source leak or the events leading up to it in the comments below. -

Source
Official thread

 

[guitarheroknight]

Been looking forward to this. Good job!

 

[gnmmarechal]

Nice, I'll take a look.

 

[mathew77]

Thanks!
Does it support Atmosphere, right?

 

[hippy dave]

Thanks!
Does it support Atmosphere, right?

As far as I can see, it checks that it's running on ReiNX and fatals if not.

 

[mathew77]

hippy dave
Awwww, that's a pity.

 

[hippy dave]

hippy dave
Awwww, that's a pity.

If & when the source code is officially released, it could probably be worked around for unofficial builds.

 

[Ericthegreat]

Interesting I'll try it soon.

 

[regnad]

I’m on Atmosphere. What would I have to give up switching to ReiNX? Is there something like title redirect so that HB can have full access?

 

[regnad]

You dont need to give up anything, just remove their "DRM" by commenting the code block on their github repo at DeltaLaunch/deltalaunch: in the file source/Core/Engine.cpp at line 33. Then you just need to adjust paths (s/ReiNX/atmosphere/g), and their loader title id thing

No way I'll screw that up

 

[Django68]

No way I'll screw that up

Just saying, there's no real dependency to ReiNX other than ipc checks and folder conventions. You could very well refactor the loader tid set call out. Also at worse it wont load, and you'll have to remove it from your sd.

 

[xxNathanxx]

This is great news, although I admit the dev trying to make outlandish claims of others 1337 hacking his account to publish the code early, when it's pretty obvious that he just dun goofed for a minute and accidentally published it, was funny. Also, coming up with imaginary GPL clauses in an attempt to illegitimately discredit those others even further. Also, the anti-Atmosphere clause, genius.

Still, great news and great work, for which everyone will be thankful. This is a big step in putting the 'custom' in custom firmware.

 

[regnad]

Just saying, there's no real dependency to ReiNX other than ipc checks and folder conventions. You could very well refactor the loader tid set call out. Also at worse it wont load, and you'll have to remove it from your sd.

It's just a matter of time, I assume, before this has been implemented in Atmosphere as well.

 

[RattletraPM]

FYI that is not "their" GitHub repo: it's the leaked source. The guy hosting the repo has just cloned it from their GitLab server.

 

[ombus]

Funny that when sxos takes from atmos its users lose it.. But when its the other way around its okay. People already saying to wait fo unoficial build or comment part of the code.
Hilarious.

 

[Adran_Marit]

FYI that is not "their" GitHub repo: it's the leaked source. The guy hosting the repo has just cloned it from their GitLab server.
There's a pull request made by Elise asking to delete it too.

Circumstances given, this was a reasonable outcome I believe, however in saying that, this is an early build.

It's just a matter of time, I assume, before this has been implemented in Atmosphere as well.

Considering people were bitching that reinx was an atmo clone, rei was developing this uniquely for reinx, it won't be official support, I assume given time if people want it or now even it will be modified for atmosphere however

 

[Django68]

FYI that is not "their" GitHub repo: it's the leaked source. The guy hosting the repo has just cloned it from their GitLab server.

I see I wasnt aware of the repo source. However they should've just reported it as a PR would not "hide" the infringing code, and is unlikely to be merged.

Funny that when xxos takes from atmos its users lose it.. But when its the other way around its okay. People already saying to wait fo unoficial build or comment part of the code.
Hilarious.

What are you saying there ? There's a difference between people building stuff for themselves (tho sharing unofficial builds is frowned upon), and taking code and claiming it's yours. I mean for all it matters, that's exactly what Rei NX did in the first place (commented code = exo checks, also labelled "DRM" as a meme, in commit ec72f51531165f78d8d567abd6287a49d91e2800 of the Reisyukaku/NX_Sysmodules github repo). So what's your claim ?


Also, stop dm'ing me for builds lol wtf

 

[Adran_Marit]

I see I wasnt aware of the repo source. However they should've just reported it as a PR would not "hide" the infringing code, and is unlikely to be merged.



What are you saying there ? There's a difference between people building stuff for themselves (tho sharing unofficial builds is frowned upon), and taking code and claiming it's yours. I mean for all it matters, that's exactly what Rei NX did in the first place (commented code = exo checks, also labelled "DRM" as a meme, in commit ec72f51531165f78d8d567abd6287a49d91e2800 of the Reisyukaku/NX_Sysmodules github repo). So what's your claim ?


Also, stop dm'ing me for builds lol wtf

Official build is in the 2.3 reinx git release

 

[Django68]

Official build is in the 2.3 reinx git release

?

 

[Idontknowwhattoputhere]

?

https://github.com/Reisyukaku/ReiNX/releases