While I feel that he has a point, he could've said or asked it differently and in a nice manner like how @kidkat210 did.
But let's not bombard this thread with of all these nonsense and just stick to what it's about.
- Status
While I feel that he has a point, he could've said or asked it differently and in a nice manner like how @kidkat210 did.
But let's not bombard this thread with of all these nonsense and just stick to what it's about.
Never said I wasn't thankful, just that it couldn't have been hard for him to post it to the main thread, especially with his reasoning for not doing so being flimsy at best due to how this site can directly link to posts.
Says the person who stoops down to name-calling. Maybe you're the one who's actually butthurt here, lol.
Last edited by pofehof,
All working thank you for these...Am i right in saying that the exosphere.ini still sits on the root of the SD card? as I have seen it in the config templates with AMS13
Yes, exosphere.ini must be in the root directory of the SD card.
And don't forget to set these values in case you want to use the native Incognito mode:
blank_prodinfo_sysmmc=1
blank_prodinfo_emummc=1
Last edited by Muxi,
Done that I had my old exosphere.ini on root but in previous AMS releases it was not bundled in...in this one it was bundled in to the default templates folder..
Thank you for your reply much appreciated.
Last edited by burhansalih,
I personally don't mind the new thread, thank you for testing before you shared!
If the new thread is so upsetting, please help out by commenting/linking from old ones.
If the new thread is so upsetting, please help out by commenting/linking from old ones.
@Ibcap what is the difference between your sigpatches for fusee primary and these ones?
https://github.com/HarukoNX/PKG2-Patches/releases/tag/10.0.4-2
I saw that yours have a folder like exefs_patches and in the ones in the link just called fs_patches
https://github.com/HarukoNX/PKG2-Patches/releases/tag/10.0.4-2
I saw that yours have a folder like exefs_patches and in the ones in the link just called fs_patches
The patches you linked to are for people who use hekate (which uses fss0/fusee-secondary) to launch atmosphere. The patches posted in this topic are for those who use fusee-primary to launch atmosphere. If you want to, it is possible to chainload fusee-primary through hekate.
Hmm, trying to understand this as my brain is working slow today after work...
In the link I added, it says
In my current config I am running with the hekate patches from that link and the fusee patches from this thread, not the ones for fusee from the link.
My config file is running the following, which is starting up fusee secondary.
Code:
[CFW - emuMMC]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmpand the folowing, which is running fusee primary
Code:
[Atmosphere]
payload=bootloader/payloads/fusee-primary.bin
icon=bootloader/res/icon_atmosphere.bmpHow would I need torun my config in order to use the fusee patches from the link I shared?
You can't use both sets of patches at the same time on a microSD card. You need to pick one configuration. If you only ever use Atmosphere with your emuMMC, then fusee-primary is recommended. If you have a situation requiring multiple emuMMCs (I don't know why you would want this, aside from having a 4.1 ipatched Switch), then you should use the Hekate+fusee-secondary method.
Hmm, ok. Not the best day to try to understand this for my brain but think I got it while looking at the file contents.
Thanks for the reply in any case
Are you using more than one emuMMC? Why are you using an emuMMC? Do you use online play? Do you use AutoRCM?Hmm, ok. Not the best day to try to understand this for my brain but think I got it while looking at the file contents.
Thanks for the reply in any case
I am keeping my SysNAND on 4.1 FW not to burn fuses and keep it stock. All the rest I am doing in EmuNAND. I have never connected to the internet with my console and do not plan to do so. When I updated my EmuNAND with ChoijoudourNX i selected AutoRCM, but I believe it does not have any effect when using EmuNAND (corerct me if I am wrong).
Why all these questions?
If you have AutoRCM installed, you don't need to use an emuMMC for your fuses to be preserved.
Yes, but I do not want to use AutoRCM due to:
- Not liking the way the console works in that mode for horizon use (already tested it back in the day and did not like it)
- Cost of Micro SD cards is quite acceptable, and easily replaceable if broken/corrupted.
Just to bring up some numbers to the table, and for anyone else who might be asking what configuration to choose, in my current setup I have a 200 GB card with 32 GB taking place for the partition. I have 17 games installed out of which 3 I have not started yet, 4 I have finished but keep installed as I come back to and the rest they are ongoing. And I still have 75 GB free of storage in the card.
If I ever start running out of space in the card, I will delete games I no longer play. And if for whatever reason I decide to keep them installed, by that time higher capacity micro sd cards will have better prices therefore space issue is non-existent.
In any case, thank you for brining another option toi the table.
I thought you said you were using AutoRCM when you brought it up in ChoiDujourNX, but you were in emuNAND.
The original intended way to boot atmosphere is via fusee-primary. Hekate added its own method called fss0 which skips fusee primary and requires different patches for homebrew/converts. The FS patches in your post are for normal games, it has patches for both fss0 and fusee primary that will make them run on 0.13.0, however its acid patches are out of date and will not work for either.
If you want to launch fusee primary from hekate, cause many people like using hekate as a bootloader, open up your hekate_ipl.ini file in the bootloader folder and change the line in your config that says "fss0=fusee-secondary.bin" to "payload=atmosphere/fusee-primary.bin" and then put the fusee primary payload that corresponds to your atmosphere version in the atmosphere folder.
Thanks for the answer. This was what I wanted to know with my question. I already have it configured like that (one of the launch options) and with my current setup everything is working great.
--------------------- MERGED ---------------------------
In my reply I mentioned that when using ChoiDujourNXI had selected the autoRCM option but that I thought it had no effect as I was running EmuNAND
Using the autorcm option in choi does nothing if you're updating your emunand. So you can leave it enabled or not, doesn't matter.
I keep it enabled because i'm too lazy to disable it heh
Last edited by Tokiwa,
- Status
Similar threads
-
Xdqwerty
what are you looking at?
-
-
-
-
-
@
AncientBoi:
And a part of my immediate family passed also. Sending my good suit to the cleaners for the funeral Saturday -
-
-
-
-
-
@
Xdqwerty:
@SylverReZ, may I ask you something? What are your favorite animes? (Aside of serial code lain)
-
-
@
Xdqwerty:
Mines are all the dragon ball animes. Im also enjoying Fullmetal alchemist and my hero academia+1
-
-
-
-
-
-
-
-
-
-
-
-
