Pi 0 w 2 Vs pi 3 mupen64plus performance
-
Pi Model or other hardware: pi zero w 2
Power Supply used: DC usb cable
RetroPie Version Used 4.7.19
Built From: RetroPie website nightly
USB Devices connected:
Controller used:
Error messages received:
Verbose log (if relevant):
Emulator: mupen64plusSo with the retroflag gpi, standalone mupen64plus seems to have much lower performance than the lr-mupen64plus core. Has anyone had a mess around with the pi 0 w2 and found that as well? As I would've thought the standalone would have better performance? I remember on my older pi3 the standalone worked quite well but that was a few years back and I presume there's been a few updates since then?
-
@retropieuser555
there is no single "standalone mupen64plus" in retropie - via the runcommand there's mupen64plus-auto, mupen64plus-GLideN64, mupen64plus-gles2n64 and so on. all of these use different video-plugins (the part after the hyphen) which dictate performance and compatibility. can you please be more specific as to which one you're using?lr-mupen64plus is basically mupen64plus-GLIdeN64 but a version from a years ago, so it's surely faster than that, but for sure less compatible. mupen64plus-GLideN64 uses the latest upstream GLideN64, so it's cutting edge and slower. that's just the nature of n64 emulation - it will only get slower on weak hardware.
mupen64plus-gles2n64 will be probably the fastest for limited subset of the games it supports. mupen64plus-auto is the best to use as it selects the optimal videoplugin based on your hardware, but IIRC usually it uses GLideN64 anyway as that is most compatible/accurate, if slowest.
i don't know what's on the image this setting that is the current default in the script will improve things for mupen64plus-GLideN64, if it's not set already.
/opt/retropie/configs/n64/mupen64plus.cfg- search forEnableInaccurateTextureCoordinatesand ensure it's set totrue -
@dankcushions that's interesting, the enableinaccurate option isn't in this mupen64plus.cfg file. I see it's quite a recent addition? Anyway let's take Mario 64 as an example. In gles2rice or gles2n64 or gliden64 it runs pretty slowly (haven't got the frame rate counter on but I'd guess 10 FPS). In lr-mupenplus it's happily running at a much faster speed. Which surprises me as I'd figure the overhead of RetroArch would be slower than running mupen64plus on it's own. But apparently not
-
@retropieuser555 said in Pi 0 w 2 Vs pi 3 mupen64plus performance:
@dankcushions that's interesting, the enableinaccurate option isn't in this mupen64plus.cfg file. I see it's quite a recent addition?
yes. so you'd need to update the retropie-setup script and then update mupen64plus via the retropie-setup script and then it should appear within the
[Video-GlideN64]section (ie, beneath that header), and should be set correctly.Anyway let's take Mario 64 as an example. In gles2rice or gles2n64 or gliden64 it runs pretty slowly (haven't got the frame rate counter on but I'd guess 10 FPS). In lr-mupenplus it's happily running at a much faster speed. Which surprises me as I'd figure the overhead of RetroArch would be slower than running mupen64plus on it's own. But apparently not
retroarch does negatively impact, but probably dwarfs in comparison to the latest version of GLideN64, however the others should perform ok in mario 64. please provide a log of mupen64plus-gles2n64: https://retropie.org.uk/docs/Runcommand/#launch-with-verbose-logging
-
@dankcushions Interesting, will probably update the script for the emulator recompile and report back once i've changed that setting. I can't run mupen64plus with verbose logging as it's not retroarch, but here is the log file in dev/shm
Any ideas from that? Here's my config file as well btw:-
-
@retropieuser555 said in Pi 0 w 2 Vs pi 3 mupen64plus performance:
@dankcushions Interesting, will probably update the script for the emulator recompile and report back once i've changed that setting.
remember that it only effects mupen64plus-GLideN64
I can't run mupen64plus with verbose logging as it's not retroarch, but here is the log file in dev/shm
2 is mupen64plus-gles2ricei said run mupen64plus-gles2n64
Any ideas from that? Here's my config file as well btw:-
they both look fine. i would have thought a pi3 and gles2rice or gles2n64 should run mario 64 at near enough full speed (ie 30fps - with certainly some drops). if the pi0 2 is not i would assume power supply issues, unstable overclock, or the hardware has some difference i'm not aware of.
a (stable) core_freq and v3d_freq overclock may help, but i don't bother with overclocking these days.
-
@dankcushions oh sorry here it is with gles2n64:-
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.