isle of reveries require the latest commit of atmosphere, the latest official version of atmosphere is not based around the current latest commit. it'll work with any version of atmosphere that is based around latest commit.
my fork is based...
zbic compressed related issues are fixed in the latest commit of atmosphere (not in the latest official atmosphere release);
such as for "Isle of Reveries", per testing.
It's an issue fixed in the latest AMS commits... But the official AMS has not been updated with that build.
Custom builds with that commit should work even with sys-patch only.
what exactly is the issue? im not aware what HOC is (but yes, anything that overrides loader.kip will remove my integrated exefs patching system, as that code is embedded in loader for my fork, same with mesosphere for FS patches)
> Horizon OC...
Atmosphere requires fusee.bin paired with your current atmosphere version. As in, you need the same fusee.bin that was compiled when that specific version of atmosphere was compiled.
example if you go use "HATS", or kefirmosphere or whatever...
i have try to use this atmosphere this fork of the Atmosphere with the up-to-date patches built-in , and tested on 3 different oled switch its working great, i can use ultrahand, ftpd, dbi, hats-tools, cyberfoil, edizon, play zelda botw, mario...
You are misinterpreting that, so no, it's not an atmosphere issue.
the "lines" you speak of are a concept of set-mitm, which overrides the values applicable from https://switchbrew.org/wiki/System_Settings
and no, the values you speak of should...
try upgrading your hekate https://github.com/CTCaer/hekate/releases/tag/v6.5.3
as for your error, https://github.com/CTCaer/hekate/blob/master/bootloader/hos/hos.c#L578
your emummc's partition layout probably is wrong / your emummc is corrupted...
Why would it be? Your battery draining problem isn't related to atmospheres things to address, if yours is caused by example desynced battery metrics, or a modchip, or similar, then that's not ever going to be fixed by atmosphere.
doesn't make sense unfortunately, my fork is still atmosphere, and does what sys-patch does, with only a few extra additions
network error on homebrew launch from album launched hbmenu doesn't make sense for qlaunch to crash - crashlogs must be...
You're on firmware version 22.1.0;
the crashlogs you have provided are from qLaunch;
one of the registers carry "TR_nn::nifm::detail::INetworkProfile::[0]Update_7101041b70"
https://switchbrew.org/wiki/Network_Interface_services#INetworkProfile...
im doubting the very existence of alleged problem, and am requesting crash and/or fatal crash reports to substantiate claim. As the more likely outcome is something foreign causing whatever problem (which the fatal/crash report would indicate to...
you don't "install" homebrew, if you people mean pirated games, stop calling those "homebrew apps".
so no, you don't have to "reinstall" any homebrew, and whatever problems he has is not with the fork. (providing crash report / fatal report...
That doesn't make much sense. When compiling atmosphere, you compile every homebrew atmosphere normally ships with.
even if theoretically something was compiler linked to libnx version, other ABI, and so on, those homebrew would be compile time...