Excellent, thanks@Ibcap is normally very good at posting on the main page when sigpatches have been updated.
Excellent, thanks@Ibcap is normally very good at posting on the main page when sigpatches have been updated.
Couple possibilities. First, make sure you're using fusee primary and not hekate. Second, some stuff when installed via sx' installer won't work on atmosphere so maybe you can try reinstalling via atmosphere. Third, you can try the maintenance mode trick, that will sometimes fix bad data.
It works for me on 10.1.0. The sigpatches arent your issue.dosent work with mario all stars though does when running on 10.0.1
Boot to rcm, hold volume up and down. Inject fusee and continue holding volume while it loads. It should load to maintenance mode. If it didnt then you let go too early. after that reboot to cfw and try the game again.What is the maintenance mode trick. I know how to get into it but what am I supposed to do after that. Sorry I'm am kinda new to modding this system. Thanks in advance
works for me on 10.1.0. The sigpatches arent your
I can't install 3d all-stars. I accidentally updated my firmware to 10.2 and, afterwards, I installed ATMOS 14.3.... but now I can't install the collection. Do I need new sig patches? When will we get those?
with atmos 14.3 ?It works for me on 10.1.0. The sigpatches arent your issue.
Boot to rcm, hold volume up and down. Inject fusee and continue holding volume while it loads. It should load to maintenance mode. If it didnt then you let go too early. after that reboot to cfw and try the game again.
Primary and nsp. I used the link the leaker posted to reddit, not any rehost. fw 10.1.0 ams 0.14.1. the mario 64 bug is a known issue, probably an atmosphere bug.Are you booting via fusee primary or secondary? And did you install the game from nsp or xci?
Maybe this matters. I boot via primary and installed the nsp. For me it works as long as I dont exit mario64. Otherwise, I have to hard reboot my switch
0.14.3 doesnt have sigpatches yetwith atmos 14.3 ?
okPrimary and nsp. I used the link the leaker posted to reddit, not any rehost. fw 10.1.0 ams 0.14.1. the mario 64 bug is a known issue, probably an atmosphere bug.
0.14.3 doesnt have sigpatches yet
Why do you think so?probably an atmosphere bug.
And you dont even have problems, when exiting mario64 using the "-" button to switch to mario galaxy?Primary and nsp. I used the link the leaker posted to reddit, not any rehost. fw 10.1.0 ams 0.14.1.
Thanks!!!It works for me on 10.1.0. The sigpatches arent your issue.
Boot to rcm, hold volume up and down. Inject fusee and continue holding volume while it loads. It should load to maintenance mode. If it didnt then you let go too early. after that reboot to cfw and try the game again.
Because sxos users on the latest version dont have the bug. Some sxos users on older versions are experiencing it however and it seems to happen to everyone on atmosphere. Also its very unlikely that a corrupt rom has no issues doing anything besides exiting that one specific game.Why do you think like that?
Doesn't cartridge owners have these issues at all?
Known issue. Just use the unofficial port instead for mario 64, its better anywayAnd you dont even have problems, when exiting mario64 using the "-" button to switch to mario galaxy?
I use fw 10.0.2 with ams 0.14.2, and also installed the nsp.