The cloud icon means you probably have update/DLC data installed, not the base game.
it worked fine before updating atmos, hekate and firmware
The cloud icon means you probably have update/DLC data installed, not the base game.
Thanks for the answer, I haven't hacked my switch yet but I'll be looking forward to some more updates on Ubuntu for better multiplayer performanceI've used multiple controllers in Ubuntu (even native DS3 support!) and also regular HOS (switch) Retroarch. But depending on the game, it can really destroy performance. Multiplayer goldeneye was basically 10 fps.
Pretty sure Lakka doesn't support wireless or docked, so probably no multiplayer on that one.
It boots sysMMC by default.Thanks Lacius putting the signature file in the atmosphere folder I was able to Launch Atmosphere using fusee-primary, one question, is booting through fusee-primary loading system nand or emuMMC?
Is it possible to get it to boot emuMMC?It boots sysMMC by default.
Yes. Add emummc!enabled to emummc/emummc.ini (or whatever it is).Is it possible to boot emuMMC instead?
--------------------- MERGED ---------------------------
Is it possible to get it to boot emuMMC?
Thanks
Do you have a 0100000000001000 folder in atmosphere/contents? If so, delete it and try again.Im not a noob, installed before perfectly fine but now when I wanted to bring everything up to date this is what I get. I got the 10.0.4 official files, grabbed the latest atmosphere 13 from sdsetup and newest sig patches. Any idea why am I getting this screen all of a sudden when it wants to boot using fusee or anything pretty much. Goes into rcm mode, opens up Hekate but once i chose payload this is all she wrote... Thanks in advance!
Do you have a 0100000000001000 folder in atmosphere/contents? If so, delete it and try again.
Yes. Add emummc!enabled to emummc/emummc.ini (or whatever it is).
Forgive me, but I don't understand your setup. Per my instructions, you should be using fusee-primary, not Hekate. You should be enabling emuMMC using emummc.ini.I can't for the lift if me get this to boot the emuMMC.
The emuMMC ini already had enabled=1
The Alt hekate ini just loads the fusee-primary.bin payload but it's booting sysmmc.
I've tried adding emuMMCenable, didn't help gives a file missing error,
Any help guys, after all the warnings that it is better to install/and fw update on emummc, the fusee-primary is booting sysmmc, I assume if I was to update the fw I'll be updating the actual system nand.
As a matter of troubleshooting, follow these steps:Just checked, doesnt seem to be there:
Your Hekate config settings don't show you chainloading fusee-primary.I've basically followed this guide
https://nh-server.github.io/switch-guide/user_guide/emummc/sd_preparation/
I've partition the SD card for raw emummc. I think I'm using hekate to chainload fusee-primary. My ipatched switch works fine with hekate and emuMMC.