libretro_builds VS mupen64plus-libretro-nx

I build a lot of my own via github actions at https://github.com/hunterk/libretro_builds, and I think that repo got recommended to me to "explore" by github's suggestion engine, IIRC.

I have some aarch64 linux builds at https://github.com/hunterk/libretro_builds, but it's far from all of them. You can also find a bunch here for both 32- and 64-bit ARM: https://github.com/christianhaitian/retroarch-cores

What architecture? If ARM linux, we don't build cores for that arch on the buildbot currently, but I have some in https://github.com/hunterk/libretro_builds.

The correct URL is https://github.com/hunterk/libretro_builds

It seems the bug introduced after RetroArch 1.9.11 was finally fixed. Tested the latest core from "Core Downloader" with several PC-98 harddisk images (.hdi) and didn't have any crash. PX68k core (Sharp X68000) still crashes on 64-bit Windows. Use the one posted on Hunterk's GitHub instead: https://github.com/hunterk/libretro_builds/releases/download/Windows_64-bit/px68k_libretro.dll.zip

. Getting the core from here, didn't work as the screen just fades to black as soon as I press reset;

Play! also has not been added yet, but in the meantime, you can download a nightly win64 build here: https://github.com/hunterk/libretro_builds/releases/download/Windows_64-bit/play_libretro.dll.zip or various linux/andrdoid builds here: https://gitlab.incom.co/libretro/Play-/-/pipelines

If you're on macOS/iOS, mupen64plus-next doesn't build. ParaLLEl-N64 builds, but I don't think there are any GL builds of RetroArch available right now, only Metal, which the core isn't compatible with.

mupen64plus-next doesn't build on macOS right now. ParaLLEl-N64 will (and there are builds at https://github.com/hunterk/libretro_builds) but the only macOS build of RetroArch is currently the Metal-only one, so AFAIK ParaLLEl-N64 won't launch.

The correct link is https://github.com/hunterk/libretro_builds

You can find previous core builds by downloading the RetroArch_cores.7z file that is next to each stable version, it include all cores as they were at the time of compilation of the stable version of RetroArch. For example, I'm holding the 12/6/2021 build of Mupen64Plus-Next due to this particular bug. The problem is, RetroArch has gone a few months without stable releases, so you'll have to see if these builds are good for you, recent enough to support the games you want and not new enough to have the recent bug.

I think the best course of action is to open an issue here: https://github.com/libretro/mupen64plus-libretro-nx. You can reference this thread.

The repo is here if you want to try building it yourself https://github.com/libretro/mupen64plus-libretro-nx

Yes https://github.com/libretro/mupen64plus-libretro-nx/issues/100

Seems cool if you'll only use GLideN64 and cxd4, which are great in their own right, but it doesn't seem to include parallel-rdp and parallel-rsp, which are responsible for the unique accuracy breakthroughs in N64 emulation I mentioned. As far as I know no standalone fork of Mupen have integrated these yet. It's quite the piece of work that was done in this core https://github.com/libretro/mupen64plus-libretro-nx m4xw works mainly on the Switch, but this core has become the main Mupen core in every platform since.