@kfleischmann This seems like a custom build - not something standard in a RetroPie installation. Check the onstart/onend script, they might have something to do with it - https://retropie.org.uk/docs/Runcommand/#runcommand-onstart-and-runcommand-onend-scripts.

New emulators? Sega Model 2/3? Naomi/Atom?

@Swedishkiller12 It has more power and an important software part (GLES compatibility) is solved/improved. The emulators on N64 still could need some work, but the Pi 4 will most probably be a big improvement on N64 games. We can't say more than this.

Okay,

I think I found the solution. There were a couple of roms without "[!]" in the name. Because I was trying anything I could think of, I deleted those files and now everything is fine. Emulation shows every N64 rom now.
Sorry for asking your help. Thank you for thinking with me for finding a solution.

Best regard to all of you!

@Thorr69 @Parabolaralus
Ok, thanks for the help and info!

@Efriim

Thanks! Gonna give it a go.

@mitu

Quick update.
Changing line 447 in /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh fixed my problem. I have changed pulse to alsa.

Further more I've created a simple script, named n64audio to run at start/boot.
In this script:

#!/bin/sh sed -i 's/pulse/alsa/g' /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh

Made the script executable sudo chmod +x n64audio
After that sudo crontab -e
And added the line @reboot /home/retropie/n64audio

Now after every reboot pulse will be changed to alsa in the file /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh , if the line pulse exists.

So if I update RetroPie and mupen64plus gets updated and overwrites my file (and put pulse back in to play) it will be overwritten on the next reboot.

Again, thanks for all your help!

Here are some settings for Conker's Bad Fur Day:
~mupen64plus.cfg

[Video-Rice] #This will fix the colored black tail and a few other things. Sometimes this setting isn't found in the cfg. #I think it loads only hi-res textures for when there are far away objects it would load lo-res. LoadHiResTextures = True #This will fix the transparency of the fence. NormalAlphaBlender = True

It might be possible to add these to the .ini files for the specific game. But I'm going to move on to other things for a while and probably won't get back to this. There are some settings that improve performance and I don't know exactly which ones these were, I could post my entire plugin configuration if someone wanted it. The setting for the dancing toadstools remains to be found, maybe I imagined it.

And here are two settings for Starcraft 64:
~mupen64plus.cfg

[Video-GLideN64] #The game fails without this, however it slows down the menus immeasurably. BackgroundsMode = 1 #FBinfo needed for scroll updates in-game, however the logos at the beginning are no longer able to be seen. DisableFBInfo = False

@Gameboy please fill out https://retropie.org.uk/forum/topic/3/read-this-first so we can get the full picture of your scenario, thanks :)

@traptedmind - Thank you for posting this! The googledrive link appears to require access. Can you post the contents of the .cfg file to the thread?

Thank you!

I also wrote this once:

https://retropie.org.uk/forum/topic/12836/guide-how-to-n64-controller-setup-with-micro-s-n64-pcb-converter-and-mayflash-usb-adapter

If you wanted to compare. :)

@edmaul69 I tried it, all of the buttons appear to be working properly.

lr-mupen64plus-next is released. And it is good, you must try it and ignore my previous post. It is in the experimental section.

@w0rM Best to start your own topic and please also post this info:

Pi Model or other hardware: (B, B+, 2 B, 3, X86 PC etc..)
Power Supply used: (If using a Pi)
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest):
Built From: (Pre made SD Image on RetroPie website, Berryboot, or on top of existing OS etc.. - please provide the filename of any image used)
USB Devices connected:
Controller used:
Error messages received:
Log found in /dev/shm/runcommand.log (if relevant):
Guide used: (Mention if you followed a guide)
File: (File with issue - with FULL path)
Emulator: (Name of emulator - if applicable)
Attachment of config files: (PLEASE USE PASTEBIN.COM FOR LARGE LOGS)
How to replicate the problem:

@Ashrill just be aware save states will not function when using omx as the audio plugin. Also the default volume is insanely loud and can't be adjusted as far as I know.

@pockketz said in mupen64plus-gles2rice-highres & mupen64plus-GLideN64-highres won't play .zip files:

on the doc page .zip files are accepted extensions

This is only for lr-mupen64plus, as it is the only one that is RetroArch configured through libretro. So yes, you will need to unzip your n64 roms if you want to use the other emulators. One of the many draw backs to n64 emulation.

@brunozero I have not noticed any issues with exiting mupen64plus on my pi. Please read and answer the questions so we can help you:

https://retropie.org.uk/forum/topic/3/read-this-first

@CursedLemon Its going to vary by game, some games can run playable in 720p with the right emulator. But some games, like the zelda games, are not going to render above the n64's native res. You may get better performance overclocking the gpu but it wont effect the resolution.

I'll take a look at what mine does with the framebuffer and get back.

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.