Super Mario Galaxy 1 & 2 crashing - help

[anon730]

How's it going bros?! I wanted to see if anyone had run into the same issue running Super Mario Galaxy 1 and 2 on the switch. I have downloaded 3 different sets (nsp and xci), and they crash on startup. Funny thing was Galaxy ran the first time fine and I played it for 10 minutes. I updated the firmware to 20.1.1, then 20.5.0. All my other games run fine. Even Silksong which also required v20+ firmware. Sys-patch V1. 5.6, it runs great. I had held back on v18.0.1 forever weary of the bugs on later firmware. I've reinstalled the games through DBI, awoo and tinfoil to see if that made a difference and got the same result. The games start, but crash within a few seconds after. I don't know what it could be. My SD card is formated fat32 as well. Has anyone run into this? I have sys-clk oc 1.2.7, switchcraft 1.6.9, ultrahand 2.1.3, no cheats downloaded, fps locker 3.0.1, salty nx 1.5.2,. The image I posted is the same screen I get on my switch. Thanks in advance for your help!

 

[thesjaakspoiler]

*harhar* sigpatches maybe?

 

[Hayato213]

Try with the sysmodules off, such as salty NX off your list, you get that message when there is not enough memory to run games so the game crash, it happens with pokemon games.

 

[tglaria]

disable salty-nx for these games ?

 

[Hayato213]

disable salty-nx for these games ?

On firmware 20.x.x you have 14MB memory, if you run salty NX and other sysmodules you would not be able to run again, so in this case it looks like it might be memory related, it is same message when there is not enough memory for pokemon games.

 

[tglaria]

On firmware 20.x.x you have 14MB memory, if you run salty NX and other sysmodules you would not be able to run again, so in this case it looks like it might be memory related, it is same message when there is not enough memory for pokemon games.

I beleive this was the message that appeared with Silksong game and uncompatible version on salty-nx.
Anyway, disable sysmodules is a better option, probably.

 

[Hayato213]

I beleive this was the message that appeared with Silksong game and uncompatible version on salty-nx.
Anyway, disable sysmodules is a better option, probably.

Well the problem is there is not enough memory for homebrews and sysmodules on higher firmware, compare to like 18.x.x, 19.x.x and 20.x.x it went from 40MB to 24MB to 14MB.

 

[anon730]

*harhar* sigpatches maybe?

You know, I have relied on sys-patch, but went ahead and downloaded the HATS pack with sigpatches anyway from thestix. It didnt work. I'm going to upload the hats pack updated today. And disable salty-nx! Thanks for all these replies! I will update on whether that did it. Thanks!!!

 

[TheStonedModder]

You know, I have relied on sys-patch, but went ahead and downloaded the HATS pack with sigpatches anyway from thestix. It didnt work.

Maybe be because you ignored the other 6 replies telling you the issue..

 

[anon730]

Maybe be because you ignored the other 6 replies telling you the issue..

I went ahead and reinstalled them both using the English modded dbi included in the HATS pack. And they both started up! Crazy
I forgot to add, I had disabled SaltyNX and only left Tesla/ultrahand running. I just re-enabled SaltyNX, restarted the system and both galaxy games would crash again. Disabling all sysmodules with the exception of the tesla menu allowed the games to run again. Thanks for the suggestions to unload sysmodules to help eliminate the crashing!. Hopefully this will help others in the future. Thanks!!

 

[Thelastunicorn]

How's it going bros?! I wanted to see if anyone had run into the same issue running Super Mario Galaxy 1 and 2 on the switch. I have downloaded 3 different sets (nsp and xci), and they crash on startup. Funny thing was Galaxy ran the first time fine and I played it for 10 minutes. I updated the firmware to 20.1.1, then 20.5.0. All my other games run fine. Even Silksong which also required v20+ firmware. Sys-patch V1. 5.6, it runs great. I had held back on v18.0.1 forever weary of the bugs on later firmware. I've reinstalled the games through DBI, awoo and tinfoil to see if that made a difference and got the same result. The games start, but crash within a few seconds after. I don't know what it could be. My SD card is formated fat32 as well. Has anyone run into this? I have sys-clk oc 1.2.7, switchcraft 1.6.9, ultrahand 2.1.3, no cheats downloaded, fps locker 3.0.1, salty nx 1.5.2,. The image I posted is the same screen I get on my switch. Thanks in advance for your help!

sys-clk oc 1.2.7 is Bad and Games crashed Install atmosphere New version.

 

[anon730]

sys-clk oc 1.2.7 is Bad and Games crashed Install atmosphere New version.

Good to know, I am going to make sure I'm on a newer version. It's been at least 6 months since I updated it because it's worked great. This Mario Galaxy situation for me only occurs if I have saltynx running. I've updated it through the last update a week ago or so and it still keeps these two games from running. Which is a bit of a bummer since I have to disable it and reboot to play either games. Anyone else running saltynx, sys-clk, fpslocker without it crashing Mario Galaxy 1 or 2? It's got to be that and the available memory that's shrunk for sysmodules on firmware 20+. I've become very comfortable using the switch in cfw exclusively because of sys-clk, fpslocker and saltynx after TotK. It runs great with a bump in clocks to 1200mhz and ram at 2500. I regret not running sys-clk earlier after seeing the magic of that small bump in performance. I tend to run behind on firmware by at least two whole number versions until it's required by a game. In order to keep that "just works" setup running while kinks in sysmodules get worked out.

 

[anon730]

Just a quick update for anyone else dealing with this problem. I added the title ID to the exceptions.txt file in the /SaltyNX folder. This keeps salty from running for the game allowing it to load. It also allows for SaltyNX to continue to run for sysmodules like sys-clk, fpslocker, etc. Mario Galaxy 1 & 2 load up great this way without having to disable Salty-nx completely, and rebooting the switch in order to launch either title.