Change any settings in mupen, save, then go to your retroarch folder and edit the mupen config it made

 

I just use mupenplus for n64 seems to run better than next for me.

 

that happened sometime to me, when i had cores that werent on the retroarch nightly (placed by me later), it dissapeared when i closed the app and returned to the main switch menu

 

You're doing something wrong then but if the games you want to work are working then it doesn't matter I guess.

 

Note: For mupen64plus-next you currently need a *specific build*, you can grab it here:https://t.co/w1S4Ua3la2
Note2: You don't need the hekate version if you are on 4.0-4.1
Note3: This will *not* work if you are on 3.x or lower

— m4xw (@m4xwdev) February 11, 2019

 

Not sure if anyone else is getting this but I've tried the latest Hekate with Atmosphere but everytime I try and load Retroarch now, it keeps shutting my switch down?

 

Probably I've been using sxos so this is the first time I have tried it how do I do it properly?

 

I'm sure I am loading Atmosphere properly through Hekate but it still shuts my switch down. Don't you just select fusee primary as payload through Hekate settings and then it loads the secondary and boots Atmosphere up properly?

 

Can anyone please let me know how to boot Atmosphere properly without "chainloading" I feel @m4xw is just teasing me with answers! I'm sure Atmosphere and Patches are booting properly on screen but Retroarch keeps shutting my switch down everytime I boot it up.

 

Wow it's pretty crazy! Good stuff!