That crash is unrelated to the patches, do you use the latest stable with jit-patches core in /retroarch/cores ?I removed the update file it makes no difference with or without.
https://filetrip.net/dl?W7UMzKC5Zu
That crash is unrelated to the patches, do you use the latest stable with jit-patches core in /retroarch/cores ?I removed the update file it makes no difference with or without.
https://filetrip.net/dl?W7UMzKC5Zu
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 folderThat crash is unrelated to the patches, do you use the latest stable with jit-patches core in /retroarch/cores ?
Use the stable release https://buildbot.libretro.com/stable/1.7.6/nintendo/switch/libnx/RetroArch.7zIts 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
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?Sorry dude still the same I had hope then but no good.
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.Does the hb menu load?
--------------------- MERGED ---------------------------
also, you didn't forget to replace the loader in /switch, right?
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
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.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.
oohh
I tried rayman, works for me.oohh
Rayman hangs on the ubisoft logo screen =(
Thanks for trying for me and explaining, it was worth a good go but I still have the same results.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.
yes i use replace title .I m going to try other dump in bin cue , because ,now i use ebootI 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/
Dude you are killing it! Expect a second donation by me tonight or tomorrow.
It was worth a shot. Sorry it didn't help.Thanks for trying for me and explaining, it was worth a good go but I still have the same results.
ywDude 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
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 reallyYep keeps giving me error code 2168-0002 all the time.
That error would happen if the patches dont apply - as in you used fusee.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 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
Sweet
That's great! what was the issue after? was it an easy fix?