Kosmos
Kosmos copied to clipboard
AtlasNX
Add uLaunch
uLaunch has just been released. It just consists on a bunch of replacements for system titles, and was tested working (barely) even on 1.0.0.
Right now we're not sure how we're going to handle uLaunch and other alternatives. This is likely a thing we're going to solve with v15.
I am against uLaunch. Its a nice thing but dont force it on people by default. I was utterly confused by how it works (buttonmapping) etc and the default "Launcher" is more fluid and still looks better in my opinion.
Having a neat AIO CFW is fine but adding more than necessary and "bloating" the cfw is not.
@XorTroll maybe ask @noahc3 if he adds it to SDSetup.
@Slluxx Perhaps you should look at it from a different angle. Perhaps they can integrate it into Kosmos but not make it the default thing. For example you would get more features when using Ulaunch, but they would need to select that when downloading the newest zip. It is then their choice is they want to use it or not.
@hax4dazy uLaunch Replaces the default and there is no switching between them. Also that kind of impementation wouldnt be Kosmos's Task but Xor's. And having multiple Kosmos versions to choose from a release in this project is also not a solution.
[...] but they would need to select that when downloading the newest zip.
Thats exactly why SDSetup exist. There is literally no need to put it in Kosmos itself.
I didn't mean putting it in Kosmos directly just them working together to add some features that will only be there when ulaunch is there. Adding it as an option in sdsetup.com is the idea I was trying to push in the first place.
I didn't mean putting it in Kosmos directly just them working together to add some features that will only be there when ulaunch is there. Adding it as an option in sdsetup.com is the idea I was trying to push in the first place.
or you can just download it from the homebrew store? ulaunch replaces eshop (probably the biggest downside) and is in beta (example of issues currently: alot of features are missing such as the options in the plus menu as well as some titles refusing to launch, not exactly user ready yet) and i doubt alot of users would want this forced on them.
ulaunch replaces eshop (probably the biggest downside) and is in beta (example of issues currently: > alot of features are missing such as the options in the plus menu as well as some titles refusing to launch,
Yeah that's normal when stuff is in beta. You said it for yourself.
You seem to overlook that it completly replaces the eshop. As piracy isnt a thing at Kosmos, why would you override one of the main ways to get games by default.
I dont understand what you think the value of uLaunch is. It has missing features, is sometimes buggy, would completly override the default launch, make the eshop unable to use and also might even contribute to console bans by using other titles that are not intendet to use by a regular switch.
Yes, its cool but features and bugs considered it doesnt make sense to include it as default to Kosmos. . If you want it, you should just use SDSetup and put it in, just like with every other homebrew aswell.
From your profile i can see that you like uLaunch but keep in mind that there are people that dont like and dont want to use uLaunch.
Anything that doesnt improve the experience shouldn't be in a CFW/AiO package.
EDIT: If you dont have any arguments that speak for uLaunch then this discussion should be over. If however you have valid and good arguments that correspond to the latest release (and not something in the future) and outweigh all the arguments that are against it, then we can talk again.
EDIT2: Not trying to be rude and cut you off though. I just feel like any further conversation is useless unless some real pro arguments show up.
I do agree with your point @Slluxx, with adding it to Kosmos mainly meant adding it as a possible add-on, like on sdsetup, not as a default launcher, since overriding the console's HOME menu by default probably isn't something most of the users would want.
We are definitely interested in including uLaunch into Kosmos, but we want to give it as an option to the end user. Right now we don't have anyone working on the method to allow users to choose, but it is something we have talked about, and have done some brainstorming on.
It's not just uLaunch there is more things we would like to give the end user options for. (Ex. nx-hbc vs hb-menu) We are looking for something like an initial setup.
I am imagining one universe(al - see what i did there) kosmos homebrew. you run it and it does the universal setup and then unlocks toolbox functionality etc. Assets will be downloaded after chosing your setup and not be shipped with it (to keep the size down) though there should be some kind of offline installer too.
Having only one homebrew that does everything will simplify and unify design and handling. Different parts of the hb could be managed by working on the project itself or submodules.
I do like the idea very much, though i have some issues with it. The sdsetup homebrew for example never worked and always ruined my sdcard. Stuff like that shouldnt happen at all with an online setup via homebrew. Also Kosmos and its packages should have some design rules to keep it clean and distinguish itself from other homebrew.
I know this is already way ahead and the wrong place to put my two cents but currently there is no other place i guess.