N64 performance question

Drdave79

@luckyluca I would assume since it's a live link that it's current by his last update. I could be wrong. Would be nice if he had a date on the spreadsheet somewhere.

quicksilver

@luckyluca I'm saying that gliden64 should be the default option for 80-90% of the N64 library.

The problem with the compatibility charts is that you have to trust whoever made it to have the same preferences as you do. Sometimes you have to choose between good performance or accurate emulation. Gliden64 is currently the most accurate and most performant for the vast majority of N64 games. The other plugin options are old and inaccurate but still have a few use cases.

luckyluca

@quicksilver thanks, I'm interested in compatibility and speed, I'll try that emulator first then.

On my installation both the lr-mupens and mupens core and emulator are from 29/10/2020.
Have there been more updates recently that would warrant updating?

One more thing, which I find confusing: the n64 emulators.cfg lists some gles2 options.
However under retroarch/cores/mupens I can see gles3 folders (rather than gles2), why is that?

Thanks again
Luca

dankcushions

@luckyluca

One more thing, which I find confusing: the n64 emulators.cfg lists some gles2 options.

mupen64plus-gles2n64? that's just a video plugin name.

However under retroarch/cores/mupens I can see gles3 folders (rather than gles2), why is that?

what are you specifically looking at? please show a screenshot or paste it.

luckyluca

@dankcushions
Thanks!
Regarding core and emulator versions, they're from the 29th Oct 2020.

Regarding that specific point, I was wondering where the GLES3 in the retroarch/config/ Mupen folders come from, considering that there is no mention of GLES3 in the n64/emulators.cfg file.

/opt/retropie/configs/all/retroarch/config
drwxr-xr-x 2 pi   pi    69632 Oct 31  2020 'Mupen64Plus GLES3'
drwxr-x--- 2 pi   pi     4096 Apr 13 00:21  Mupen64Plus-Next
drwxr-xr-x 2 pi   pi     4096 Jun 15  2020 'Mupen64Plus-Next GLES3'

mupen64plus-auto = /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh AUTO %ROM%
lr-parallel-n64 = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-parallel-n64/parallel_n64_libretro.so --config /opt/retropie/configs/n64/retroarch.cfg %ROM%"
lr-mupen64plus-next = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mupen64plus-next/mupen64plus_next_libretro.so --config /opt/retropie/configs/n64/retroarch.cfg %ROM%"
lr-mupen64plus = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mupen64plus/mupen64plus_libretro.so --config /opt/retropie/configs/n64/retroarch.cfg %ROM%"
mupen64plus-GLideN64 = "/opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh mupen64plus-video-GLideN64 %ROM% %XRES%x%YRES% 0 --set Video-GLideN64[UseNativeResolutionFactor]\=1"
mupen64plus-GLideN64-highres = "/opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh mupen64plus-video-GLideN64 %ROM% %XRES%x%YRES% 0 --set Video-GLideN64[UseNativeResolutionFactor]\=2"
mupen64plus-gles2n64 = "/opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh mupen64plus-video-n64 %ROM%"
mupen64plus-gles2rice = "/opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh mupen64plus-video-rice %ROM% %XRES%x%YRES%"
default = "lr-mupen64plus"

P.s.
@quicksilver @dankcushions I'd love if you could share your configs/all/emulators.cfg file guys, to take a peak at your n64 per-game settings, whether possible.

dankcushions

@luckyluca said in N64 performance question:

@dankcushions
Regarding that specific point, I was wondering where the GLES3 in the retroarch/config/ Mupen folders come from, considering that there is no mention of GLES3 in the n64/emulators.cfg file.
/opt/retropie/configs/all/retroarch/config
drwxr-xr-x 2 pi   pi    69632 Oct 31  2020 'Mupen64Plus GLES3'
drwxr-x--- 2 pi   pi     4096 Apr 13 00:21  Mupen64Plus-Next
drwxr-xr-x 2 pi   pi     4096 Jun 15  2020 'Mupen64Plus-Next GLES3'

i am not sure why you have both Mupen64Plus-Next and Mupen64Plus-Next GLES3 config overrides, but the name of the file is pulled from the library name and it looks like this was changed from the latter to the former after some refactoring, so i guess you have used it before and after the relevant update.

GLideN64 (the video plugin which both mupen64plus-GLideN64 and lr-mupen64plus-next use) has GLES3 code paths. it's nothing of note. the plugin is compiled to use GLES3 as appropriate in both contexts.

the ancient gles2n64 and gles2rice video plugins do not use GLES3.

VictimRLSH

I'm probably going to get rotting fruit thrown in my general direction for this, but I've actually found the best way to play N64 games on the Pi 4 is to run WoR with the latest 64 bit Win 10 ARM build and just use Project64. Getting Windows 10 ARM running on WoR (Windows on Raspberry) is a daunting task but well worth the effort considering how much it opens up.

lostless

@victimrlsh 🍅🥥🍅🍋🍎🍋🍋🍌🍅🍅. Might as well just plug my laptop into my tv at that point. Kinda defeats the ease of pick up and play of retro pie. 😂

luckyluca

@dankcushions
yes cores were updated at some point, which would explain the config folder naming switch.

@dankcushions
So that I understand correctly, the config folders
"Mupen64Plus-Next GLES3" and
"Mupen64Plus GLES3"

are not used anymore, so all per-game overlay configs should be copied to

"Mupen64Plus-Next"
and
"Mupen64Plus", respectively.

Am I getting it right?

dankcushions

@luckyluca what's an "overlay config"? do you mean override config? in which case, yes, in the case of Mupen64Plus-Next. I am not sure about Mupen64Plus - you'd have to check the code like I did for -Next.

it seems like it would be pretty trivial to figure this out, though. just load a game you have overrides for and see if they're applied via the RGUI, when they're in the wrong(?) folder, and whether they become applied when you move them to the right(?) folder.

luckyluca

@dankcushions

you're right, that's a quicker way of checking :-)

to answer your question, I was referring to per-game override configs that only contain a one line pointing to the overlay config (which in turn points to the graphics), if that makes sense.