Scummvm standalone crashing/full ram mode

[the19thbear]

Whenever I launch a game with scummvm (downloaded from homepage not via retroarch), the switch crashes and I have to reboot.

This doesn’t happen if I press R when launching (full ram mode I think it’s called).

How can I fix this so it works every time without me pressing R?

Any fixes for this?


Thanks

 

[Badablek]

scummVM is a big boy now, it needs as RAM as possible.
install a forwarder (make your own or download one), you will be in Full RAM mode, everytime.

updated (for firmwares 12+) forwarders here (registration needed)

ps : if you launch scummVM from Homebrew Menu, you can also install a forwarder for HBM. So it will always launch in Full RAM mode (and all homebrews launched with it, of course).

 

[the19thbear]

Thanks! Will check it out

 

[the19thbear]

Do you have a link to the newest method to make forwarders? I used some software about a year ago but don’t know if any new way and better way has been developed. I will look for it myself of course, but feel free to post a link here

 

[Badablek]

it seems you can use SAK to make AMS 0.19+ forwarders (didn't try myself, I'm using psxtools.de ones)

https://github.com/dezem/SAK

 

[Draxzelex]

Do you have a link to the newest method to make forwarders? I used some software about a year ago but don’t know if any new way and better way has been developed. I will look for it myself of course, but feel free to post a link here

https://gbatemp.net/threads/gui-for-nsp-forwarder-tool-for-12.588018/

 

[Badablek]

https://gbatemp.net/threads/gui-for-nsp-forwarder-tool-for-12.588018/

Last time I tried this one, it was not using the correct loader (the exit code was removed)...so all homebrews crashed when using the "exit" function (to return to Homebrew Menu or Horizon OS) :

• launching a homebrew from homebrew menu (launched with the forwarder made with gui-for-nsp...12) → crash at exit
• launching a homebrew from a forwarder made with gui-for-nsp...12 → crash at exit

SAK uses a good one, where the exit code was re-implemented. Which is much better !

ps : If it was fixed since then, forgive what I said (mpham does not tell what loader he is using, and its gitlab only contains the compiled binary...so it's hard to see if it was changed or if the exit code is in it)