Neither do I but something is brewing...god i hope for a releaseGuys, there's "revamp all the makefiles" all aboard the project https://github.com/Atmosphere-NX/Atmosphere. I don't know what that means, but sounds cool
Neither do I but something is brewing...god i hope for a releaseGuys, there's "revamp all the makefiles" all aboard the project https://github.com/Atmosphere-NX/Atmosphere. I don't know what that means, but sounds cool
From what I can see, it's now getting close to being a public release.Guys, there's "revamp all the makefiles" all aboard the project https://github.com/Atmosphere-NX/Atmosphere. I don't know what that means, but sounds cool
So, those hits are true! Thanks for the great info!From what I can see, it's now getting close to being a public release.
All parts of atmosphere are starting to get compiled together to one main output as opposed to before being their individual parts and outputs.
Anywhere from tomorrow to the end of time.I wonder how close we are to the actual release ^^
I hope not too soon, I have an assignment due in 38 hours. I'll be "forced" to try it out if it releases :-/I wonder how close we are to the actual release ^^
The world revolves around youI hope not too soon, I have an assignment due in 38 hours. I'll be "forced" to try it out if it releases :-/
Duh. He is THE QuantumCat. Everybody knows the world revolves around him.The world revolves around you
Quantum is a cat with glasses. I doubt there's anything better the world could revolve around. Maybe the Queen beating the living shit out of Trump, but I take a cat with glasses until that happens.The world revolves around you
I thought emunand was low priority?Guys, it's "close", but not like "release coming in 24 hours close".
There's still things to be done, and I'm not even sure if they have emuNAND working yet. Just calm down, it could just be simple changes to work towards a future release while still being a bit off.
I'm honestly not certain. They may release it before emuNAND is ready, but one of the main points of creating atmosphere in the first place was to have emuNAND so users in lower firmwares could play newer games in an update emuNAND.I thought emunand was low priority?
You will get access to the CFW at the same time as everyone else, as long as you don't mind shorting a pin or 2. There is a softmod that you can utilize but it may not be released until the new revision of Nintendo Switches are released into the wildI’m 4.1.0, is there any advantage on being in this fw?
I’m 4.1.0, is there any advantage on being in this fw?
I'm honestly not certain. They may release it before emuNAND is ready, but one of the main points of creating atmosphere in the first place was to have emuNAND so users in lower firmwares could play newer games in an update emuNAND.
If they go with emunand they can put patches in such that it doesn't burn fuses when you update your emunand (they would have to, otherwise when you booted your sysnand there would be a kernel panic). I don't know if you could get away with sysnand-only cfw at this point, I think that it's probably worth keeping them seperate at this point so the devs at least get a chance to poke and prod for more software exploits before just rolling over them entirely.See, but I (personally) see no need for an emunand with what we're getting. Maybe on newer hardware revisions. However, we'll have permanent access to homebrew/cfw on any firmware for a time to come.
I guess with efuses you'd have to backup your nand with every update, so maybe not?
Except for higher fw you are bound to using some kind of hardware exploit to enter RCM, albeit an extremely simple exploit.See, but I (personally) see no need for an emunand with what we're getting. Maybe on newer hardware revisions. However, we'll have permanent access to homebrew/cfw on any firmware for a time to come.
Which won't mean much if we have a coldboot cfw coming our way. Still, the efuses are currently the only justified reason for emunand imo. Oh well, won't complain either way.Except for higher fw you are bound to using some kind of hardware exploit to enter RCM, albeit an extremely simple exploit.
Lower firms will have the advantage of using software to enter RCM, and with jamais vu/Deja vu they will have a way to boot cfw without needing RCM.
So there are a few reasons to stay low, though for many people those reasons aren't/weren't enough to stay.
It's not persistent coldboot though, at least not with what is currently public knowledge. You'll have to boot RCM and push the payload over USB for each rebootWhich won't mean much if we have a coldboot cfw coming our way.