-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SaltyNX crashes on M.16.2, not crashing on 0.16.2 #1294
Comments
Can you provide a list of games? Or you have checked one of games I have listed and it works for you? I want to be as much be certain as possible that this issue is on my side. |
Ori 1 & 2 |
Thanks for info. So this is something from my side. I will try to clean up shit and try again. Closing issue. |
Bug Report
What's the issue you encountered?
I have V1.
SaltyNX 0.4.0a was working without issue on M.15.0.
Updated Atmosphere today to M.16.2 to investigate some issue. And it turned out no game now wants to load.
Heap size is set correctly, nintendo logo disappears and after few seconds any game is crashing.
Issue doesn't exist on 0.16.2, also when injecting plugins is disabled the issue doesn't exist on M.16.2
How can the issue be reproduced?
Crash Report
01608472125_010039400e8d6000.log
System Firmware Version
10.2.0
Environment?
fusee sysmmc
official M.16.2
no kips;
SaltyNX, Tesla, sys-clk, Noexs.
Deleted everything except SaltyNX and issue still exists.
I don't think it matters in this case, but I have few of my test homebrew, Daybreak, Checkpoint, Cheats Updater, hbappstore, moonlight, mtp-server-nx, NX-Shell, nxdumptool, nxmtp, PPSSPP, reboot to payload, Reset Parental Controls, RetroArch, ReverseNX-Tool, SaltyNX-Tool
Additional context?
It happens for both game cartridges and installed games with and without updates.
Tested on Witcher 3, LA Noire and Little Busters. All of them were working before.
SaltyNX 0.3.2a also doesn't work.
SaltyNX doesn't provide any error because plugin is injected successfully and game starts booting as expected.
I will understand if this report will be closed because of how SaltyNX works. But if mesosphere behaves differently than official kernel, I think it's worth investigating what is happening.
The text was updated successfully, but these errors were encountered: