That crash is unrelated to the patches, do you use the latest stable with jit-patches core in /retroarch/cores ?
Homebrew RetroArch Switch
- Thread starter ShadowOne333
- Start date
- Views 1,879,629
- Replies 9,158
- Likes 96
Its the latest nightly from here> http://buildbot.libretro.com/nightly/nintendo/switch/libnx/ with your recommended>mupen64plus_next_libretro_libnx_svc in the core folder
Use the stable release https://buildbot.libretro.com/stable/1.7.6/nintendo/switch/libnx/RetroArch.7z
Also make sure its not called mupen64plus_next_libretro_libnx_svc but mupen64plus_next_libretro_libnx.nro, but i assume you know that.
Could be broken nightly, we had roller-coaster issue the last days
Sorry dude still the same I had hope then but no good.Use the stable release https://buildbot.libretro.com/stable/1.7.6/nintendo/switch/libnx/RetroArch.7z
Also make sure its not called mupen64plus_next_libretro_libnx_svc but mupen64plus_next_libretro_libnx.nro, but i assume you know that.
Could be broken nightly, we had roller-coaster issue the last days
Does the hb menu load?
--------------------- MERGED ---------------------------
also, you didn't forget to replace the loader in /switch, right?
Yes the hbmenu loads fine it goes to RetroArch fine but loading the rom it freezes on the screen and then the Atmosphere error pops up does this every time I try. The strange part I cannot get my head round if I put all the sxos files back on the sd card it loads no issues but it’s not using the new n64 emulation.
Edit: I changed the nro file on the switch folder.
--------------------- MERGED ---------------------------
Where’s the best folder to put the roms should they be zipped or not? Mine are all unzipped in roms/n64 route
Last edited by Reecey,
You can make a directory anywhere. I used zipped roms. Make sure they're from a NoIntro set or RA won't import them into the collection.
PCSX rearmed 5+ track Issue fixed, soon on the nightles, this increases compatibility by a lot!
— m4xw (@m4xwdev) February 12, 2019
Grab your preview here:https://t.co/szIPujdKmz@libretro
D
Deleted-351540
Guest
I also had this issue. I fixed it by formatting my card FAT32/32K cluster size and putting my files back on the card. Then I downloaded the latest stable version of Retroarch (I was using the nightlies) and replaced the nro for Mupen64 with the one provided by m4xw. Then I downloaded Kosmos and replaced Hekate with the one provided by m4xw. I am also chainloading Hekate through the SX bootloader. So I booted SX bootloader, selected "Launch external payload", selected Hekate, then selected "boot CFW". Once Horizon launched, I held "R" and launched my selected title (Smash Brothers Ultimate, FWIW) and loaded HBL. Then I launched Retroarch and loaded the Mupen64 core. I did not launch a game. I selected "Exit Retroarch". Once it backed out to the HBL, I pressed home to go back to the Horizon menu and closed the title using "X". Then I rebooted the console. It has worked perfectly ever since.
I tried rayman, works for me.
It might need more RAM than u can get via Album, so u need to use https://gbatemp.net/threads/use-atmosphere-to-access-full-ram-with-homebrews-without-nsp.521240/
Thanks for trying for me and explaining, it was worth a good go but I still have the same results.
yes i use replace title .I m going to try other dump in bin cue , because ,now i use eboot
D
Deleted-351540
Guest
Dude you are killing it! Expect a second donation by me tonight or tomorrow.
You've earned a few beers/coffee's. Many thanks for keeping at it and keeping this updated.
It was worth a shot. Sorry it didn't help.
Last edited by ,
I kept getting this error no matter what yesterday too when using nsp.. it was really weird, cause i tried everything and it worked before hekate svc and kosmos update. I just wanted to try the new core, so i installed kosmos and updated hekate (was using fusee before with no issues at all for a long time)..And afte that i just could't get the nsp ra n64 core to work (tried latest nsp and prev versions), i even tried to fresh install kosmos and GETTING BACK to fusee, deleted all configs and stuff and still kept getting a hard crash when starting a n64 rom on nsp, every other core worked fine, tried also the maxw's core and the nighlies one and even my previously working.. it wasnt my sd for sure, eventually i just had to stick with hbl full ram access method, cause everything worked fine when lauching ra through hbl. I'm still curuios what could broke ra like that so that even reverting to my previous files didn't make any difference...some kind of x-files shit really
Last edited by bad361,
That error would happen if the patches dont apply - as in you used fusee.
Tho I rule that out based on the informations he gave me.
Also I call that ghost Issues
Similar threads
-
@
SylverReZ:
@Veho, Sounds and smells like bullshit. They don't give you cancer, and California should know that. I don't get why they stick labels that say "may or may not cause reproductive harm or cancer". -
-
-
-
-
-
-
-
-
@
Psionic Roshambo:
Mame should be two sets one for preservation of everything and one set for people who just want to play and enjoy the old old ganes -
-
-
-
@
SylverReZ:
@Psionic Roshambo, Believe Japan was going to make it legal at some point, according to a Kotaku story.+1
-
@
Psionic Roshambo:
I swear like 99% of arcade games wouldn't even exist these days outside of MAME the arcade machines are old and busted very few ever saw any sort of home conversion
-
-
@
SylverReZ:
@Psionic Roshambo, There's a lot of obscure Japanese arcade titles that are either lost to time or dumped.+1
-
-
@
Psionic Roshambo:
I mean if a company could use AI to do the work of a home conversion for essentially free why not? The rights for some games are completely lost though
-
-
-
-
-
-
