After a couple days of Nintendo releasing their 18.0.0 firmware update, @SciresM releases a brand new update to his Atmosphere NX custom firmware for the Nintendo Switch, with the new version being a pre-release v1.7.0, which adds basic support for firmware 18.0.0, as well as adding some improvements and bugfixes along the way.

The changelog for version pre-1.7.0 is the following:

1.7.0 is Atmosphère's seventy-eighth official release.
Please be sure to update fusee when upgrading to 1.7.0. fusee-primary no longer exists, and will not work any more.
Please note: Atmosphère 1.7.0 is currently in pre-release, and issues may be found that need to be fixed before full release.

• If any bugs are reported while Atmosphère is in pre-release, they will be fixed and the build will be updated.
• 1.7.0 will transition to release after a short amount of time has passed without pressing bug reports.

With thanks to the @switchbrew team, Atmosphère 1.7.0 is bundled with hbl 2.4.4, and hbmenu 3.6.0.
The following was changed since the last release:

• Basic support was added for 18.0.0.
  • The console should boot and atmosphère should be fully functional. However, not all modules have been fully updated to reflect the latest changes.
    • There shouldn't be anything user visible resulting from this, but it will be addressed in a future atmosphère update, once I am not traveling so much.
  • exosphère was updated to reflect the latest official secure monitor behavior.
  • mesosphère was updated to reflect the latest official kernel behavior.
  • spl was updated to reflect the latest official behavior.
• fusee no longer supports applying IPS patches to KIPs.
  • The only KIPs that are ever present are a) atmosphère modules, b) custom system modules, or c) FS.
  • The IPS subsystem was originally designed to make nogc patches work for FS, but these are now internal, and it appears the literal only kip patches that exist are for piracy.
    • I could not find any kip patches posted anywhere made for any other purpose.
  • It fundamentally does not make sense to slow down boot for every normal user for a feature that has no actual use-case, especially when fusee seeks to be a minimal bootloader.
• Minor improvements were made to atmosphere's gdbstub, including:
  • Support was added for QStartNoAckMode.
  • An issue was fixed that could cause a fatal error when creating too many breakpoints.
• A number of minor issues were fixed and improvements were made, including:
  • pt-BR (PortugueseBr) is now accepted as a valid language when overriding game locales.
  • A bug was fixed that could cause atmosphere to incorrectly serialize output object IDs over IPC when using domain objects.
  • A bug was fixed in pm's resource limit boost logic that could potentially cause legitimate boosts to fail in certain circumstances.
  • loader/ro will now throw a fatal error when using invalid IPS patches that go out of bounds, instead of corrupting memory.
  • Support was fixed for booting using a memory configuration of half of the true available memory (e.g. forcing a 4GB configuration on an 8GB board).
• General system stability improvements to enhance the user's experience.

For information on the featureset supported by 1.7, please see the official release notes.

Source
GBATemp's Atmosphere NX Discussion Thread

 

[TomSwitch]

I installed the new Atmosphere version with success, then I updated to 18.0.0 with daybreak and now I get a fatal error when I boot atmosphere

A fatal error occurred when running Atmosphère
Program ID: 01000000000bd00
Error Dec: std::abort() called (0xffe)
Report saved...

Do you know how to install properly? Delete the old atmosphere directory ( or rename it to something else ) then unzip the new release to your sd card. If you don't clean up first and just copy over and have problem you only have yourself to blame. Many home brew touch the atmosphere directory and copy over don't remove any customization.

HOS18 don't break many but some home brew will always break when there is a major HOS update.

Post automatically merged: Apr 1, 2024

All told, I am okay waiting until a new build of atmosphere, or at least not a pre-release edition. Or suddenly a new game I care about requires the new firmware. Hopefully the former, before the latter.

No worries, wait as long as you like, there is enough brave soles that will try whatever is new no matter the cost and plus those with emotional support animal that update their switch before they know it there is no lack of testers.

I would wait a day or two then it is mostly safe to update if there is no big out cry.

 

[realtimesave]

18.0.0 works fine except mission control is broken again. hopefully it gets an update soon

edit: downloaded mission control from discord. they are waiting for someone to test XBE2 controller so they can make an official release. now I just need to figure out where I put my DS4.

 

[impeeza]

18.0.0 works fine except mission control is broken again. hopefully it gets an update soon

https://github.com/ndeadly/MissionControl/issues/794

that is the place.

Post automatically merged: Apr 1, 2024

happy mission Control launch day!!!


https://github.com/ndeadly/MissionControl/releases

Official Mission Control with support for FW 18.0.0

 

[Dan-the-Rebirth]

So about the sigpatches...I usually boot Hekate via my PC and then I run the newest fusee.bin via Hekate payloader. That way everything should work as usual right?

 

[codezer0]

That's totally fine. From my own experience, everything worked right off the bat except for a few sys modules, MissionControl being the one that I use regularly and one (or both) of those overcloking modules that I don't use. Other than that, I'd say that it's fine to update at this point. Regular users shouldn't have any issues with the latest Atmosphere, despite being in pre-release state. Again, that's just me saying from my own experience. No games yet require 18.0.0 so you're still fine being on a lower firmware.

For my own anecdotal experience, pre-release atmosphere tends to be real crash happy. Was doing fine on 16(dot)whatever until a newer game forced me to go through the motions for 1701.

Pretty sure thousand year door will demand firmware 18, when it drops.

 

[impeeza]

So about the sigpatches...I usually boot Hekate via my PC and then I run the newest fusee.bin via Hekate payloader. That way everything should work as usual right?

nop, the new fuse do not load FS patches anymore, so you need:

change to boot using Hekates FSS0 to load Package3
get a new fusee.bin with the functionality recovered
use SYS-Patch sysmodule to apply all sigpatches.

Post automatically merged: Apr 1, 2024

For my own anecdotal experience, pre-release atmosphere tends to be real crash happy. Was doing fine on 16(dot)whatever until a newer game forced me to go through the motions for 1701.

Pretty sure thousand year door will demand firmware 18, when it drops.

yes is recommended to everyone stay on FW 17.0.1 far as needed, but, and is a big but: atmosphère prereleases has been so stable what the last two was prerelease until the next release some weeks and even months later.

 

[wurstpistole]

You can, you just have to load through Hekate, which at this point I don't know why someone would load Atmosphere through any other means.

So... Place sigpatches into atmosphere folder as usual and chainload fusee.bin through hekate?

 

[impeeza]

So... Place sigpatches into atmosphere folder as usual and chainload fusee.bin through hekate?

yes and not

Yes, put the sigpatches on the atmosphere folder
No to chainload fusee.bin, because that way will no load the sigpatches, again you need:

Load Package3 trough Hekate's FSS0
Install SYS-Patch Sysmodule
use a modified fusee.bin with the restored sigpatches load functionality.

 

[RedColoredStars]

So... Place sigpatches into atmosphere folder as usual and chainload fusee.bin through hekate?

Put the sigpatches into the atmos folder as you normally would.

Copy the contents of the sys-patch file to their proper locations.

Your hekate.ipi.ini file should look similar to this for the emuMMC,

[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/icon_payload.bmp

Then boot into hekate, then into your emuMMC without loading fusee.

 

[Medveitsi]

So how do i OC memory now?

 

[impeeza]

So how do i OC memory now?

The same before, you need upgraded homebrew.

 

[RedColoredStars]

The same before, you need upgraded homebrew.

Do you know if sys-clk is working on FW 18 with latest Atmosphere, Hekate, etc? Latest release is from last October and included "Support for HOS 17.0.0" and I don't see any recent commits regarding 18.

 

[impeeza]

i just read on one of the threads what is a new release, you can go to official github and look for it.

Post automatically merged: Apr 1, 2024

someone else is reporting old version is working on 18, so I don´t know.

 

[Medveitsi]

The same before, you need upgraded homebrew.

I'm using sys-clk OC and atmosphere wont start if i have the kip file in the kips folder

 

[RedColoredStars]

i just read on one of the threads what is a new release, you can go to official github and look for it.

Post automatically merged: Apr 1, 2024

someone else is reporting old version is working on 18, so I don´t know.

I don't see anything about a new version & the last commit on the official git was 5 months ago. Guess I'll just have to try it (and FPSLocker) at some point if I want to play Princess Peach Showtime in 60fps.

 

[jacobkoller]

Good, now they should update their logo. Its looking very low quality on the big screen.

 

[impeeza]

Good, now they should update their logo. Its looking very low quality on the big screen.

what are you talking about willis?

 

[jacobkoller]

what are you talking about willis?

The atmosphere logo, its pixely background in particular.

 

[impeeza]

Which ones? this?:

they are originally vectors (look for them on the zip attached) I am attaching the real files on the Atmosphère code, so no pixelation I see.

 

[jacobkoller]

Which ones? this?:
View attachment 429342

That's the 1, zoom on it the pic is not of a high quality and its the one they use all the time. Its especially visible on a big screen tv as i said earlier. On the switch itself, not so much.