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

    mupen64plus upstream issue with the gonetz/GLideN64 repo

    Scheduled Pinned Locked Moved Help and Support
    mupen64plusblack screenissueupstreamworkaround
    15 Posts 5 Posters 2.1k Views
    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.
    • abjA
      abj
      last edited by

      Thanks! Emulator is working again.

      `Please be patient, my English is not very good.`

      1 Reply Last reply Reply Quote 0
      • mituM
        mitu Global Moderator
        last edited by

        There's a regression seemingly caused by https://github.com/gonetz/GLideN64/commit/1a0621ddf4a70835e9b38cf5a326cbb34d7067aa in the upstream project, let's see if it can be fixed.

        TPRT 3 Replies Last reply Reply Quote 1
        • TPRT
          TPR
          last edited by TPR

          I just updated everything from source and I get the following error if I run the stand alone version of Mupen64plus:

          2024/05/02,14:46:56.033,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
          2024/05/02,14:46:56.034,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
          2024/05/02,14:47:49.430,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
          2024/05/02,14:47:49.430,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
          2024/05/03,19:00:50.588,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
          2024/05/03,19:00:50.588,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
          2024/05/06,17:48:59.449,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
          2024/05/06,17:48:59.450,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
          2024/05/06,17:54:17.098,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
          2024/05/06,17:54:17.098,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
          2024/05/06,20:07:17.771,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
          2024/05/06,20:07:17.772,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
          2024/05/07,18:07:11.156,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
          2024/05/07,18:07:11.157,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
          2024/05/07,18:07:38.989,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
          2024/05/07,18:07:38.990,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
          2024/05/07,18:12:08.173,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"
          2024/05/07,18:12:08.173,opengl_Utils.cpp:60,WARNING, "Could not query EGL extensions on this device"

          I get that error both with or without the edit to the scriptmodule file mentioned above.

          1 Reply Last reply Reply Quote 0
          • mituM mitu referenced this topic on
          • TPRT
            TPR @mitu
            last edited by

            @mitu Sorry, I didn't mean to bump the other topic. Just someone else had the same error so I wan't sure if this was something that had been fixed or if I was doing something wrong. I guess it just hasn't gotten fixed yet?

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

              @mitu Also, again just to mention that I'm getting that error with or without the edit mentioned above. I do not get this symptom:

              games will not to render (black screen), although audio can be heard and fps counter (if enabled) will display correctly.

              For me, the game starts to load, then I see "INIT NOISE TEXTURES, PLEASE WAIT...." flash on screen for a brief second, and then it kicks me back to ES.

              Not sure if this is the same issue or not that is mentioned above.

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

                @mitu I noticed an update in the setup script and I installed that but the core is still crashing. Did this get fixed or am I doing something else wrong?

                1 Reply Last reply Reply Quote 0
                • mituM
                  mitu Global Moderator
                  last edited by mitu

                  The latest update to the scriptmodule should fix - temporarily - the crash since it uses an older commit, until upstream commits (!) to a fix.

                  @TPR did you re-install from source the mupen64plus emulator after the update ?

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

                    @mitu I just did the update. I'll re-install now. Thank you.

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

                      @mitu It just kicks me back to ES when I try to load a rom with that core. I updated the setup-script. Updated from source, re-installed from source, and then when that didn't work, I deleted the core from the emulators folder and removed any reference from emulators.cfg, re-installed again and I get the same issue.

                      Any ideas?

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

                        @TPR said in mupen64plus upstream issue with the gonetz/GLideN64 repo:

                        It just kicks me back to ES when I try to load a rom with that core.

                        Are you talking about the Libretro core or the standalone Mupen64Plus + GlideN64 ? This topic is about the latter - can you post the /dev/shm/runcommand.log from running the emulator where you have issues ?

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

                          @mitu Standalone. Here's the log:

                          Parameters:
                          Executing: /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh mupen64plus-video-GLideN64 "/home/pi/RetroPie/roms/n64/D/Diddy Kong Racing.z64" 1920x1080 0 --set Video-GLideN64[UseNativeResolutionFactor]=1
                          /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh: line 434: 2801 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"

                          mituM F 2 Replies Last reply Reply Quote 0
                          • mituM
                            mitu Global Moderator @TPR
                            last edited by

                            @TPR Then it might be a different issue. Does the libretro core work ?

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

                              @mitu It does.

                              1 Reply Last reply Reply Quote 0
                              • F
                                FoxRacing @TPR
                                last edited by

                                @TPR Hey @TPR I am experiencing the same problem with my N64 roms. Did you end up fixing it? Thank you

                                1 Reply Last reply Reply Quote 0
                                • 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.