Best Bang For My N64 Buck?
-
@dankcushions said in Best Bang For My N64 Buck?:
@alphabetapie
i would actually recommend mupen64plus-gliden64, which is essentially the same thing but should be faster, as it’s standalone. that said, there are a number of non-default options that can cause further slowdown with next, but as always we need info from your system to diagnose. including:verbose log
/opt/retropie/configs/all/retroarch-core-options.cfg
/opt/retropie/configs/all/retroarch.cfg
/opt/retropie/configs/n64/retroarch.cfgnote that lr-mupen64plus may still be sometimes faster because it’s old, inaccurate and so on. but that’s not enough to recommend it as it’s broken in a lot of ways, including crashing after ~30 mins use, if i remember right.
Sure, I will work on getting those logs when I get home later.
In the meantime, question about mupen64plus-gliden64. I have actually tried setting that as the default emulator (when I was experimenting last night), but the games just crash back to the select screen. Like it does when no emulator is found. This only happens with that version. As far as I remember, I didn't install this after the fact, so I believe it came with the Retropie image. Is the one that is already include the standalone version you mean? Or did you want me to try and find a git version I can install manually?
-
@alphabetapie i believe it's installed by default, yes, but obviously that will only be as up to date as your last install/update.
it doesn't run .zip files as per https://retropie.org.uk/docs/Nintendo-64/ - other than that I can't investigate any crashes without a log.
-
@dankcushions said in Best Bang For My N64 Buck?:
@alphabetapie i believe it's installed by default, yes, but obviously that will only be as up to date as your last install/update.
it doesn't run .zip files as per https://retropie.org.uk/docs/Nintendo-64/ - other than that I can't investigate any crashes without a log.
OK, so I just got in and pulled these. However, I'm not sure I'm giving you what you need. I went into Retroarch and turned on verbose logging. I had several options of what to log, which were info, warnings and errors. So I set it to debug, because I figured that would give you all three of those. I can change this if you need me to.
I pulled the config files and attached them. I also ran Super Mario 64 with mupen64plus-gliden64 so it would crash and hopefully log the issue. Let me know if I need to repost something else.
-
OK, so I just got in and pulled these. However, I'm not sure I'm giving you what you need. I went into Retroarch and turned on verbose logging. I had several options of what to log, which were info, warnings and errors. So I set it to debug, because I figured that would give you all three of those. I can change this if you need me to.
that's not really the right method. short memory? :) instructions to get a verbose log are in the sticked read this first link, and you've been linked to them several times
what you've done has probably turned verbose logging on permanently, which could have performance implications.
@alphabetapie said in Best Bang For My N64 Buck?:
retroarch config
this one is not default (which is much smaller) and looks like you've been in retroarch menu and saving settings. i wouldn't recommend this unless you have specific reason to, and it's too big for me to find if there's anything wrong.
i doubt it's your issue, but if you want to reset, update retroarch and replace it with the default backup file
retroarch.cfg.rp-dist. obviously that will replace any custom settings you put in there.core config
this is the same link as above. this is not
retroarch-core-options.cfg -
@dankcushions said in Best Bang For My N64 Buck?:
OK, so I just got in and pulled these. However, I'm not sure I'm giving you what you need. I went into Retroarch and turned on verbose logging. I had several options of what to log, which were info, warnings and errors. So I set it to debug, because I figured that would give you all three of those. I can change this if you need me to.
that's not really the right method. short memory? :) instructions to get a verbose log are in the sticked read this first link, and you've been linked to them several times
I don't have a short memory. Your link says that I need to use the runcommand to launch the game with verbose logging. When I select your gliden64 core you recommend, that option goes away. So I can't do that. It's only present on the other versions. So I went looking for verbose logging elsewhere.
Follow-up:
I'm planning to do a re-image soon, so much of these small snafus in the settings menus are going away (which is why I'm not worried about experimenting with menu settings at the moment, as I know this is not my final build). Is there a link to the standalone I could try to manually install? Maybe if I get the latest version (newer than from the last Retropie image), I might be successful. -
@alphabetapie said in Best Bang For My N64 Buck?:
@dankcushions said in Best Bang For My N64 Buck?:
OK, so I just got in and pulled these. However, I'm not sure I'm giving you what you need. I went into Retroarch and turned on verbose logging. I had several options of what to log, which were info, warnings and errors. So I set it to debug, because I figured that would give you all three of those. I can change this if you need me to.
that's not really the right method. short memory? :) instructions to get a verbose log are in the sticked read this first link, and you've been linked to them several times
I don't have a short memory. Your link says that I need to use the runcommand to launch the game with verbose logging. When I select your gliden64 core you recommend, that option goes away. So I can't do that. It's only present on the other versions. So I went looking for verbose logging elsewhere.
hang on, we were diagnosing your slowdowns in lr-mupen64plus-next, when i asked for those retroarch files.
i would actually recommend mupen64plus-gliden64, which is essentially the same thing but should be faster, as it’s standalone. that said, there are a number of non-default options that can cause further slowdown with next, but as always we need info from your system to diagnose. including:
verbose log
/opt/retropie/configs/all/retroarch-core-options.cfg
/opt/retropie/configs/all/retroarch.cfg
/opt/retropie/configs/n64/retroarch.cfgin any case, the link says:
Launch with verbose logging
When launching Libretro cores (those prefixed by lr-) the Runcommand launch menu presents the option to Launch with verbose logging. This outputs more information to the log file found in /dev/shm/runcommand.log which is useful, and often necessary, when diagnosing problems. Once the game is exited, the log file can be downloaded via SFTP or viewed directly via the command line.Note: If launching a non-Libretro ("standalone") core, the option will not be available, but they typically will still write useful diagnostic information to /dev/shm/runcommand.log.
(emphasis mine)
so, since mupen64plus-gliden64 is not prefixed by lr-, you don't have to turn anything on to get a useful log.
Follow-up:
I'm planning to do a re-image soon, so much of these small snafus in the settings menus are going away (which is why I'm not worried about experimenting with menu settings at the moment, as I know this is not my final build). Is there a link to the standalone I could try to manually install? Maybe if I get the latest version (newer than from the last Retropie image), I might be successful.again, i believe standalone is installed in default retropie. you just said you already ran it? it's called mupen64plus-gliden64. if for some reason it is not installed, you install/update it like anything else: https://retropie.org.uk/docs/Updating-RetroPie/#updatinginstalling-individual-packages
-
@dankcushions said ...
My goal is to top off my compatibly before I do my final build. When you said glide was the best performance wise, I wanted to switch to it and give it a try. But it crashing for seemingly no reason seems odd, since I didn't need to install it (as it was already here by default). But yeah, my focus is that at present, since you recommended it. Hope that clears things up.
Let me ask you this. I'm about to do a fresh system image and start again, to build up some other things I'm working on anyway. Can I assume that glide should load an n64 game on a pie 4 (on the default settings) if I just drop my roms in like normal and then set it as the default emulator? Pretty sure this will give me the best jumping off point I need to begin reverse engineering the issue.
-
@alphabetapie said in Best Bang For My N64 Buck?:
@dankcushions said ...
My goal is to top off my compatibly before I do my final build. When you said glide was the best performance wise, I wanted to switch to it and give it a try. But it crashing for seemingly no reason seems odd, since I didn't need to install it (as it was already here by default). But yeah, my focus is that at present, since you recommended it. Hope that clears things up.
ok, but either way the guide tells you how to get a log, so can i see log? to be clear, none of the retroarch config files i saw have anything to do with the crashng of mupen64plus-gliden64, only the performance of -next, since the latter is lr- (retroarch) and the former is not.
Let me ask you this. I'm about to do a fresh system image and start again, to build up some other things I'm working on anyway. Can I assume that glide should load an n64 game on a pie 4 (on the default settings) if I just drop my roms in like normal and then set it as the default emulator? Pretty sure this will give me the best jumping off point I need to begin reverse engineering the issue.
not really without seeing a log/full diagnostic info requested in https://retropie.org.uk/forum/topic/3/read-this-first. for example, if you're trying to launch .zip roms mupen64plus standalone will fail, as i said earlier.
-
@dankcushions said ... if you're trying to launch .zip roms mupen64plus standalone will fail, as i said earlier.
That was it. I unzipped them and it loads fine now.
I'm noticing the normal menus don't seem to load as with the other cores. Since it's a standalone, should I assume the normal hotkey > quick menu setup of Retroarch is not accessible? How would I pull up the new menu to find things like overlay and custom resolution options? I like to set all that per emulator/core.
-
@alphabetapie said in Best Bang For My N64 Buck?:
@dankcushions said ... if you're trying to launch .zip roms mupen64plus standalone will fail, as i said earlier.
That was it. I unzipped them and it loads fine now.
I'm noticing the normal menus don't seem to load as with the other cores. Since it's a standalone, should I assume the normal hotkey > quick menu setup of Retroarch is not accessible? How would I pull up the new menu to find things like overlay and custom resolution options? I like to set all that per emulator/core.
that's right. standalone emulators don't have any of that, unless they have analogous features. to increase resolution, use the mupen64plus-gliden64-highres emulator in runcommand, however since this is n64, you'll probably want to leave everything at default to maximise performance.
-
@dankcushions said in Best Bang For My N64 Buck?:
@alphabetapie said in Best Bang For My N64 Buck?:
@dankcushions said ... if you're trying to launch .zip roms mupen64plus standalone will fail, as i said earlier.
That was it. I unzipped them and it loads fine now.
I'm noticing the normal menus don't seem to load as with the other cores. Since it's a standalone, should I assume the normal hotkey > quick menu setup of Retroarch is not accessible? How would I pull up the new menu to find things like overlay and custom resolution options? I like to set all that per emulator/core.
that's right. standalone emulators don't have any of that, unless they have analogous features. to increase resolution, use the mupen64plus-gliden64-highres emulator in runcommand, however since this is n64, you'll probably want to leave everything at default to maximize performance.
Well, that is good information. I'm also simultaneously working on getting the standalone version of yabasanshiro up and running, but that seems to be a moot point now. All my consoles are Retroarch dependent regarding overlays and custom resolutions for my theme. I guess I'll just have to focus on optimizing the lr cores best I can.
-
@alphabetapie i doubt anything is going to be playable with an overlay or non-native resolution, but if you want to make sure lr-mupen64plus-next is running correctly (at default settings it can be a bit slower but shouldn't be obviously slower than standalone) we return to getting the verbose log and the core options file: https://retropie.org.uk/forum/post/255555
-
@dankcushions said in Best Bang For My N64 Buck?:
lr-mupen64plus-next
Is r-mupen64plus-next significantly better than the regular r-mupen64plus? Or just marginally?
-
@alphabetapie discussed here: https://retropie.org.uk/docs/Nintendo-64/#emulators-mupen64plus-lr-mupen64plus-lr-mupen64plus-next
note also that i believe lr-mupen64plus has a bug that makes it crash after ~30 mins.
-
@dankcushions said in Best Bang For My N64 Buck?:
@alphabetapie discussed here: https://retropie.org.uk/docs/Nintendo-64/#emulators-mupen64plus-lr-mupen64plus-lr-mupen64plus-next
note also that i believe lr-mupen64plus has a bug that makes it crash after ~30 mins.
Will research. Thanks for the info.
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.