Please do not post a support request without first reading and following the advice in

lr-mupen64plus-next: experimental scriptmodule for testing

  • @quicksilver said in lr-mupen64plus-next: experimental scriptmodule for testing:

    @hhromic Yoshi's Story is performing much better now, thank you for bringing it to m4xw's attention!

    You are welcome, the idea is to easen the development :)

    Something else I have noticed is when toggling the bi-linear filter in the retroarch video settings the screen goes black. You can still hear the game audio playing but suddenly there is no display. In the old lr-mupen64plus you could toggle this setting on the fly with no issue.

    We will be investigating, m4xw mainly test using the Switch version and he said this does not happen there.

    Also now that this emulator is on parity with the current gliden64 is there any plans to incorporate the script module into retropie?

    The plan has been always to incorporate the scriptmodule into RetroPie eventually. I first launched this topic to help debug and gather feedback before submitting it formally.

    If you think this emulator is now on par with the other alternatives (I know your feedback is very trustful in terms of N64 emulation), I have no problem on polishing the scriptmodule and send it.

    @BuZz are you ok with adding this scriptmodule to RetroPie? As mentioned in the OP, the main developers do not plan to update the older lr-mupen64plus anymore in favour of this "next" version.

  • @hhromic in "Iggy's reckin' balls"the textures are now missing on the race tracks. Previously was working fine with lr-mupen64plus-next before the big gliden64 update. I should note that this matches the current standalone gliden64 as it is also missing the textures.

    Edit: nevermind, I found that by disabling less accurate blending that the tracks display properly again.

  • administrators

    @hhromic yes.

  • @quicksilver the scriptmodule is now part of official RetroPie (thanks @BuZz !).

    You will find it under the experimental package section after you update your RetroPie-Setup script :). I update the OP now to reflect this too.

    I hope it brings joy to your N64 memories! Feel free to report issues and feedback for future development too.

  • @hhromic Thank-you to you and BuZz! Would the lr-mupen64plus-next dev prefer direct bug reports to the github or should we keep reporting here? I saw some of his responses on there that seemed to imply he didnt want a plethora of bug reports on the github page.

  • I tested it on Super Mario 64. There are some slowdowns here and there, but I found it much more fluid than the previous versions of lr-mupen64plus-next.

  • I discovered this next version yesterday after realizing that the old lr-core was deprecated. What I saw was that next was running ok for the 2 or 3 games I have tested. I am on an Intel i5 CPU so it should have more power than a Pi. Is this core the recommended one even for a powerful machine? I am a bit confused by the many different N64 emulators in RetroPie.

    I think mupen64plus-glide64 (not GLideN64) ran best for me. At least it was the only one not producing artifacts in the title screens of 1080 snowboarding. Not sure if that one maybe is deprecated too and it sadly is not an lr core :(

  • Is anyone able to re-create a crash with OoT directly after acquiring the Kokiri Sword by trying to access the menu? If I attempt to press start in 'my house' , it works fine. Attempt to use it after getting the sword (or perhaps in Kokiri Forest in general) it crashes.

    (This apparently only happens in v1.2.)

  • @hooperre said in lr-mupen64plus-next: experimental scriptmodule for testing:

    Is anyone able to re-create a crash with OoT directly after acquiring the Kokiri Sword by trying to access the menu?

    exactly this happening.. works fine with lr-mupen64plus. ever figure it out?

  • @sdtom An issue is opened with lr-mupen64plus-next on GitHub. Happens across different platforms. It seems like it has garnered their immediate attention. May want to update from source, as they have it marked as internally hotfixed.

    Follow it here:

  • Hi all when trying to install this it gives me an error in the logs. I'm not quite sure what I'm looking for but here is the log file's detail below:-

    Log started at: Sun 22 Mar 17:53:36 GMT 2020

    RetroPie-Setup version: 4.5.1 (f90600a2)
    System: Raspbian GNU/Linux 9.9 (stretch) - Linux retropie 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l GNU/Linux

    = = = = = = = = = = = = = = = = = = = = =
    Installing dependencies for 'lr-mupen64plus-next' : N64 emulator - Mupen64Plus + GLideN64 for libretro (next version)
    = = = = = = = = = = = = = = = = = = = = =

    /home/pi/RetroPie-Setup/tmp/build/lr-mupen64plus-next /home/pi

    = = = = = = = = = = = = = = = = = = = = =
    Getting sources for 'lr-mupen64plus-next' : N64 emulator - Mupen64Plus + GLideN64 for libretro (next version)
    = = = = = = = = = = = = = = = = = = = = =

    git clone --recursive --depth 1 --branch GLideN64 "" "/home/pi/RetroPie-Setup/tmp/build/lr-mupen64plus-next"
    Cloning into '/home/pi/RetroPie-Setup/tmp/build/lr-mupen64plus-next'...
    warning: Could not find remote branch GLideN64 to clone.
    fatal: Remote branch GLideN64 not found in upstream origin
    fatal: Cannot change to '/home/pi/RetroPie-Setup/tmp/build/lr-mupen64plus-next': No such file or directory
    fatal: Cannot change to '/home/pi/RetroPie-Setup/tmp/build/lr-mupen64plus-next': No such file or directory
    HEAD is now in branch '' at commit ''
    Error running 'git clone --recursive --depth 1 --branch GLideN64 /home/pi/RetroPie-Setup/tmp/build/lr-mupen64plus-next' - returned 128

    Log ended at: Sun 22 Mar 17:53:38 GMT 2020
    Total running time: 0 hours, 0 mins, 2 secs

    Any ideas? Or is this happening with anyone else?

  • administrators

    @retropieuser555 your RetroPie-Setup is not up to date. Please also open a new topic for issues.

  • @BuZz Thanks for the reply. 4.5.1 isn't the most recent RetroPie? I was reluctant to do an update as whenever I do it always seems to take hours. Anyway, I'll give that a go on my pi this evening anyway as I guess that'll fix. If it doesn't I'll make a new topic.

  • @retropieuser555 just update retropie-setup script then update lr-mupen64plus-next. You don't need to update all packages.

  • Thanks guys! That worked perfectly and got a fair number of games running as smoothly as I did previously with the previous mupen64.

    Btw one thing I did notice is the AKI wrestling games (World Tour, WCW Revenge, Wrestlemania 2000, No Mercy, VPW2) all don't seem to work. But they do on the original lr-mupen64plus when using Glide64.

    With lr-mupen64plus-next, the display squashes into the top left corner of the screen and you get a couple of other graphical glitches. Has anyone else tested these games and been able to replicate this?

  • @retropieuser555 which pi are you using?

  • @quicksilver 3b+. I can get the games working great on the older mupen64 emulators. But when you set it to something other than Glide64, you get the game playing but no video display (you can tell the game is playing as you can press start, select items off the menu etc). So I wondered if it's something to do with needing to be that plugin?

  • @retropieuser555 I can't replicate your issues. Can you open a new help topic with an overview of your setup?

  • Hello all, a quick PSA :)

    The lr-mupen64plus-next core got updated some days ago and now is defaulting to 640x480 resolution for new installs. This resolution is a bit taxing for humble devices such as the RPI3 or less, so is strongly recommended that you set the rendering resolution to 320x240 (as it was previously the default) for these devices. Perhaps this is not necessary for RPI4, you have to see for yourself.

    This can be done after starting any game and going to the core options menu in RetroArch.

    It is important to note that this is not a RetroPie change, but an upstream change. We decided to not change the upstream defaults therefore it is your responsability to change this setting for your own setup.

    If you had the core previously installed, the new defaults will not apply because you already have the previous resolution set in your core options.

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.