Homebrew RELEASE N64 dynarec is out as beta release

  • Thread starter Thread starter Keylogger
  • Start date Start date
  • Views Views 326,667
  • Replies Replies 1,432
  • Likes Likes 20
Just for clarification, the dynarec enabled core is mupen64plus-next, right? Also, could someone share their config for that core? Mine doesn't seem right at all. Thanks!
 
Just for clarification, the dynarec enabled core is mupen64plus-next, right? Also, could someone share their config for that core? Mine doesn't seem right at all. Thanks!
It's on page 26. If you want to cut and paste to your cfg file, you need to either change all settings to point to the newer "next" version, or rename the mupen "next" version to be the same name as the other older version.
 
  • Like
Reactions: KuraudoSutoraifu
It's on page 26. If you want to cut and paste to your cfg file, you need to either change all settings to point to the newer "next" version, or rename the mupen "next" version to be the same name as the other older version.

Or look at the values and then go into settings and set each of the corresponding settings to those values :P

they share configs
I think this is true as despite making changes Ive never found anything other than mupenplus in the .cfg
 
Last edited by atypicalchaos,
  • Like
Reactions: KuraudoSutoraifu
Nah I asked m4xw a few pages back

does mupen64plus next just use mupen64plus options in the config? I changed settings in the next core and it just updated mupen64plus in the config, so I don't need to rename each line?

No, the core options are shared - but Per game core options are put in a different folder.
 
  • Like
Reactions: KuraudoSutoraifu
I tried ocarina of time and it works much better. Thank you very much m4xw for you work.

I changed the configuration manually with the options of page 26. I use retroarch with full ram (nro through hbl with redirection). However, there is some stuttering and sound crackling, in portable mode and docked. Is it normal? Is there anything I could do to solve it?

And another question: in what directory can I find the mupen64 next cfg file?
 
What's the smartest way of updating to the latest core each day? I've been deleting all of the Retroarch files from my SD card everyday (thousands of files) and copying over the files from the new nightly. I'm probably wasting time and wearing out my SD card for no reason. Are there any issues with just copying over the new Mupen Next core?

Yeah it takes forever i use nxmtp which allows you to transfer the files via usb but it still takes forever its about the same speed as putting your sd card in your computer.

Im not downloading new ones everyday though just when theres a big improvement.

You can remove something like ~6,000 files if you delete (or don't upload) the contents of the Overlays folder, as well as XMB. There might be another folder I am forgetting but since I use FTP, updating nightlies was a nightmare until I did this. By doing the above, it's something like ~1,500 files and much, much faster.
 
Guess I won't be able to use the newest patches SX OS is a must for me, I have Switch games on my external hdd.
With Atmosphere's new "Reboot To Payload" feature, you can set Hekate as the payload and change between Atmosphere and SX OS using that method. If/when SX OS implements this feature this would allow seamless switching between each CFW without the need for a jig/dongle. That would allow you to easily run Atmosphere when you wanna play RetroArch with patches, and SX OS when you wanna play XCI/NSPs off of your external HDD.
 
Last edited by stick267,
01/24 nightly with hekate called hekate_ControlCodeMemory_5x_6x
If u use a nightly then its pointless to use that hekate build lol

--------------------- MERGED ---------------------------

Great, thank you. Where might I find that version of Hekate?
You wait till its released.
 

Site & Scene News

Popular threads in this forum