RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    Lost mupen64plus Standalone Emulator

    Scheduled Pinned Locked Moved
    Help and Support
    n64 nintendo 64 mupen64plus
    6
    16
    1.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • windgW
      windg
      last edited by

      After install the emulator (Binary) try to run this commands from terminal, i hope it works:

      cd RetroPie-Setup
sudo ./retropie_packages.sh mupen64plus configure

      My English isn't at a good level.

      IkyrusI 1 Reply Last reply Reply Quote 0
      • dankcushionsD
        dankcushions Global Moderator @Ikyrus
        last edited by dankcushions

        @Ikyrus said in Lost mupen64plus Standalone Emulator:

        I was tweaking around with the N64 emulators and I decied to update mupen64plus from source. The update seemd to go fine but now when I launch an N64 game, it no longer has the standalone mupen64plus as option. The offshutes still show up (like rice and gliden64)

        there's no 'standalone' mupen64plus - it's always going to use a graphics plugin ("gliden64", for example). 'standalone' in the retropie sense just means it's not got the libretro/retroarch front end. eg, mupen64plus-gliden64 is 'standalone' vs 'lr-mupen64plus-next', which uses the libretro front end. all 'mupen64plus-*' emulators are 'standalone' by this definition.

        perhaps you're thinking of mupen64plus-auto, that would automatically select the best graphics plugin for the game in question? this isn't necessary for pi4, so isn't installed. just use mupen64plus-gliden64 (best video plugin for pi4)

        but trying to launch a game with them just boots me back to Retopie

        Please supply the runcommand.log for mupen64plus-gliden64, as per https://retropie.org.uk/forum/topic/3/read-this-first

        IkyrusI 1 Reply Last reply Reply Quote 1
        • IkyrusI
          Ikyrus @dankcushions
          last edited by

          @dankcushions All I know is there used to be an option just called muper64plus and now there isn't. And every since I updated that core from source, mupen64plus-gliden64 now just kicks me back to Retropie when I try to run it.

          dankcushionsD 1 Reply Last reply Reply Quote 0
          • dankcushionsD
            dankcushions Global Moderator @Ikyrus
            last edited by dankcushions

            @Ikyrus

            All I know is there used to be an option just called muper64plus and now there isn't

            i can't remember the history of the naming but regardless of what is was called, it would have been running a graphics plugin, and given that -gliden64 is the best plugin for pi4, that's what you need to be getting working.

            And every since I updated that core from source, mupen64plus-gliden64 now just kicks me back to Retropie when I try to run it.

            right, so please provide the runcommand.log after that happens. instructions here https://retropie.org.uk/forum/topic/3/read-this-first

            IkyrusI 1 Reply Last reply Reply Quote 0
            • IkyrusI
              Ikyrus @dankcushions
              last edited by

              @dankcushions

              I apologize, I'm not seeing where it shows how to find the runcommand.log. I also did a search on my Pi and didn't find any file called that. I did find a file in /opt/retropie.configs.n64/mupen64plus called glide64.log:

              2023/08/01,16:20:57.313,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/01,16:20:57.314,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/01,16:25:07.768,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/01,16:25:07.769,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,11:11:22.697,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,11:11:22.698,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,11:13:18.961,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,11:13:18.961,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,11:14:09.322,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,11:14:09.322,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,11:21:36.292,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,11:21:36.292,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,11:23:55.779,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,11:23:55.780,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,11:38:37.181,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,11:38:37.182,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,12:46:47.961,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,12:46:47.962,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,12:49:13.671,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,12:49:13.672,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,12:49:49.751,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,12:49:49.752,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,12:50:26.261,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,12:50:26.262,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,13:06:12.152,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,13:06:12.153,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,13:13:06.583,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,13:13:06.584,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,14:14:02.132,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/03,14:14:02.132,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/04,09:40:37.063,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
              2023/08/04,09:40:37.065,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"

              Does that help?

              dankcushionsD 1 Reply Last reply Reply Quote 0
              • IkyrusI
                Ikyrus @windg
                last edited by

                @windg

                Unfortunately I tried this and it didn't fix it. Thank you though!

                1 Reply Last reply Reply Quote 0
                • dankcushionsD
                  dankcushions Global Moderator @Ikyrus
                  last edited by

                  @Ikyrus

                  I apologize, I'm not seeing where it shows how to find the runcommand.log.

                  sorry, my bad, it's the "verbose log" link on the read-this-first.

                  here's the link: https://retropie.org.uk/docs/Runcommand/#launch-with-verbose-logging

                  the important part:

                  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.

                  ie, run the game, get the crash, then download that file from that location.

                  IkyrusI 1 Reply Last reply Reply Quote 0
                  • IkyrusI
                    Ikyrus @dankcushions
                    last edited by

                    @dankcushions Awesome, thank you. here's what I got from runcommand.log after the crash:

                    Parameters:
                    Executing: /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh mupen64plus-video-GLideN64 "/home/pi/RetroPie/roms/n64/Super Mario 64.n64" 1280x720 0 --set Video-GLideN64[UseNativeResolutionFactor]=1
                    /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh: line 447: 9091 Segmentation fault SDL_AUDIODRIVER=${SDL_AUDIODRIVER} SDL_VIDEO_RPI_SCALE_MODE=${SDL_VIDEO_RPI_SCALE_MODE} "$rootdir/emulators/mupen64plus/bin/mupen64plus" --noosd $PARAMS ${WINDOW_MODE} --rsp ${RSP_PLUGIN}.so --gfx ${VIDEO_PLUGIN}.so --audio ${AUDIO_PLUGIN}.so --configdir "$configdir/n64" --datadir "$configdir/n64" "$ROM"

                    dankcushionsD 1 Reply Last reply Reply Quote 0
                    • dankcushionsD
                      dankcushions Global Moderator @Ikyrus
                      last edited by dankcushions

                      @Ikyrus thanks. unfortunately that's not telling me anything other than it crashed :( it would need a debug build to find the cause. you didn't say what specific image filename you're using - the current official retropie v4.8 image?

                      i have no idea if there's issues with the current mp64 binaries and not in a position to test. you could try lr-mupen64plus-next which should be the next-best one to use.

                      IkyrusI 1 Reply Last reply Reply Quote 0
                      • IkyrusI
                        Ikyrus @dankcushions
                        last edited by

                        @dankcushions Sorry, I'm using 4.8. I have been defaulting to lr-mupen64plus in the absence of the standalone. It works relatively ok. Is next better? I was under the impression it didn't work as well on the Pi because it has more accurate emulation which makes it run slower.

                        dankcushionsD 1 Reply Last reply Reply Quote 0
                        • dankcushionsD
                          dankcushions Global Moderator @Ikyrus
                          last edited by

                          @Ikyrus i suppose it depends on your definition of 'better'. lr-mupen64plus has been abandoned for 4 years - it might run faster in some situations but there will be lot of old bugs and inaccuracies, and they will never be fixed.

                          mupen64plus-gliden64 and lr-mupen64plus-next have essentially the same underlying (currently updated) codebase.

                          1 Reply Last reply Reply Quote 0
                          • X
                            xotihcan
                            last edited by

                            I have the same problem after running retropie's packages upgrade.

                            pi@retropie:~ $ cat /dev/shm/runcommand.info
n64
mupen64plus-GLideN64-highres
/home/pi/RetroPie/roms/n64/Mario Kart 64 (USA).n64
/opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh mupen64plus-video-GLideN64 "/home/pi/RetroPie/roms/n64/Mario Kart 64 (USA).n64" 640x480 0 --set Video-GLideN64[UseNativeResolutionFactor]\=2
pi@retropie:~ $ cat /dev/shm/runcommand.log
Parameters:
Executing: /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh mupen64plus-video-GLideN64 "/home/pi/RetroPie/roms/n64/Mario Kart 64 (USA).n64" 640x480 0 --set Video-GLideN64[UseNativeResolutionFactor]\=2
/opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh: line 447:  6142 Segmentation fault      SDL_AUDIODRIVER=${SDL_AUDIODRIVER} SDL_VIDEO_RPI_SCALE_MODE=${SDL_VIDEO_RPI_SCALE_MODE} "$rootdir/emulators/mupen64plus/bin/mupen64plus" --noosd $PARAMS ${WINDOW_MODE} --rsp ${RSP_PLUGIN}.so --gfx ${VIDEO_PLUGIN}.so --audio ${AUDIO_PLUGIN}.so --configdir "$configdir/n64" --datadir "$configdir/n64" "$ROM"

                            It happens with all non lr emulators.

                            1 Reply Last reply Reply Quote 1
                            • mituM mitu referenced this topic on
                            • mituM
                              mitu Global Moderator
                              last edited by

                              Can you try updating/re-installing the mupen64plus emulator now ? It seems there's a problem with the latest version, but updating from binary should install a previous version, which should work.

                              TPRT 1 Reply Last reply Reply Quote 0
                              • TPRT
                                TPR @mitu
                                last edited by

                                @mitu I hate to bump an old topic but I'm also getting the same error no matter which version of mupen64plus I use:

                                2024/05/17,14:16:01.948,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
                                2024/05/17,14:16:01.948,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"

                                I have removed mupen64plus from the build completely and just re-installed via the most recent update from the RetroPie-Setup script and that's the error I get everytime and it kicks me back to ES.

                                I have tried all three mupen64plus options in runcommand and they all do the same.

                                Any ideas?

                                Thank you.

                                mituM 1 Reply Last reply Reply Quote -1
                                • mituM
                                  mitu Global Moderator @TPR
                                  last edited by

                                  @TPR said in Lost mupen64plus Standalone Emulator:

                                  @mitu I hate to bump an old topic but I'm also getting the same error no matter which version of mupen64plus I use:

                                  The 'same error' is just a generic message that the emulator has crashed and it's not caused by the same issue. In fact, you've already commended in the topic where the recent Mupen64plus breakage was reported - https://retropie.org.uk/forum/topic/35444. Bumping an old topic is just rude.

                                  1 Reply Last reply Reply Quote 0
                                  • mituM mitu locked this topic on
                                  • First post
                                    Last post

                                  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.