Hacking Atmosphere-NX - Custom Firmware in development by SciresM

  • Thread starter Thread starter Waze0613
  • Start date Start date
  • Views Views 2,778,817
  • Replies Replies 9,368
  • Likes Likes 93
Thanks, that made the trick on my 2nd Switch (Atmosphere 16.0.2).
Still, I didn't have to edit anything in my 1st Switch (Atmosphere 16.0.1), it reads carts just fine.
Because the game cart was properly updated. Default settings change sometimes and if you didn’t already have nogc=0 in BCT.ini, or autonogc=0 in hekate_ipl.ini (depending on what you were booted into when you actually upgraded) then perhaps that switch was upgraded before you updated Atmosphere (and/or hekate). Those are your only 2 options.
 
This is extremely frowned upon.

Why tho? Of course its not desirable to have everybody run around with custom builds and possibly report errors on it, if that's the point. But if you want to quickly test an experimental / unstable state of the Atmosphere repo, why not have the toolchain bundled inside a docker container?

I didn't know that this is a no-go from AMS maintainers' side - would you rather have it gone? Or am I missing credits / links to the official project repository?

UPDATE:
Reading your last post makes it clear. I wasn't aware of this at all. Will take it private, no problem.
 
Last edited by tuxuser,
Why tho? Of course its not desirable to have everybody run around with custom builds and possibly report errors on it, if that's the point. But if you want to quickly test an experimental / unstable state of the Atmosphere repo, why not have the toolchain bundled inside a docker container?

I have asked everyone who is interested in CI/etc to avoid building/distributing CI tooling for atmosphere, until we're at 1.0.0 -- around then, I'm intending to set up some kind of CI myself.

I don't mind if you make CI and CI-adjacent tools for yourself, but I very much frown upon making tools and sharing them with others at the moment. It just makes my life more of a hassle.

If you want to quickly test atmosphere (which you really shouldn't, since -master often does not boot because I make no attempt to keep it stable), you can do so without making public docker tooling.

So yeah, it's frowned upon. I can't control your behavior, but I'd appreciate if you would make your repo private or whatever.


---


Also, atmosphere only officially supports building on Windows, Linux isn't broken at the moment but I can't guarantee that will always be true, since I use windows exclusively.
 
Last edited by SciresM,
SciresM is making a re-implementation of the Horizon OS, which he calls "Mesosphere." It's still in its early stages, but seems to be stable enough to be implemented with version 0.17.0 of Atmosphere.

Source
For what I've looked (not so much), it means more for switch emulation, is that correct?

For common folk cfw user, there any noticeable gains in any ways?
 
SciresM is making a re-implementation of the Horizon OS, which he calls "Mesosphere." It's still in its early stages, but seems to be stable enough to be implemented with version 0.17.0 of Atmosphere.

Source
Mesosphere is the kernel re-implementation.
 
Last edited by 8BitWonder,
For what I've looked (not so much), it means more for switch emulation, is that correct?

For common folk cfw user, there any noticeable gains in any ways?
To answer your question: as a normal user, you will not see or feel any difference.

Maybe for the for the future there are additional features planned (like a reimplementation of the filesystem services system module to fix the exFAT problems), but for now there are no differences for the user
 
  • Like
Reactions: Tokiwa and almmiron
those. now the mesosphere is still optional, but it seems to have become recommended? Just before, they did not release releases with the mesosphere at the same level as without it
 

Site & Scene News

Popular threads in this forum