Well, I found the solution. And it had nothing to do with mupen :D Mupen uses a resolution of 640x480 and my TV-settings were configured to stretch 640x480 (4:3) to 16:9. Changing my settings to "4:3" fixed it. Also for usual 1920x1080 resolution it still keeps 16:9 aspect ratio.

@MRL2051 Don't bump a 4 year old topic. Start a new topic and read the pinned topics first. See my signature.

@darksarcasm Sorry dude, must've skim read that bit (character flaw of mine). Have you tried a different button combo instead of using 10 in both in case it is conflicting?

Solved!
Nvm, I figured it out after reading the wiki for the 15th time. You need to disable hotkeys in the autoconf.cfg file first and then edit the mupen64plus.cfg to enable whatever you want to exit the emulator. As stated above I use Z Trigger + Start button to exit back out. It works perfectly and you do not sacrifice any buttons.

/opt/retropie/configs/all/autoconf.cfg

mupen64plus_hotkeys enable hotkey auto configuration (0)

then go in and edit

/opt/retropie/configs/n64/mupen64plus.cfg

and set your control to the way you want it to exit out of game. I programmed mine for Z trigger and Start hit together

@BuZz all right, bought a new one, waiting for it to arrive.

but the "flash" signal shouldn't be appearing then?

@backstander just to make sure we're not having miscommunication, you're using multiple controllers at once? The hid quirk seemed to have no affect....
Thanks again for the replies!

I have been using mupen64plus-rice-hi_res legend of zelda oot. But this has been happening with other emulators in the past. I remembered the way I was able to make changes was by launching a freshly loaded rom (this instance was NBA showtime n64) , never been played on this system before, and access runcommand. Once in there I can change the default emulator. Then I exit the runcommand, and can now change the runcommand settings on the problem rom. I know that seems really confusing. Sorry about that.

I ran into the same issues as described here. The following steps resolved my problems:

Step 1: autoconfigure your joypads once by starting mupen53plus while having all controllers connected properly Step 2: in opt/retropie/configs/all/autoconfig.cfg -> Disable N64 Hotkey here (this was my biggest catch because it is in the all directory!) Step 3: in opt/retropie/configs/N64/mupen64plus.cfg -> assign the hotkeys and put the mode of all registered joypads from 2 to 0
After this it seems to work for me without any problems. So I hope it helps.

PS: I believe that the WIKI should be updated with Step 1, this is such a catch when trying to follow the WIKI N64 instructions.

@mediamogul said in n64 crash killer instinct mid game:

I am currently running my Rpi3 stock and I find that 'mupen64plus-GLideN64-highres' runs 'Killer Instinct Gold' very smoothly.

I should amend this comment, as I can no longer successfully run 'Killer Instinct Gold' either. However, as the software moves forward, these kind of regressions happen. Hopefully this game will come back around some time in the future.

@Finndersen should be in /opt/retropie/configs/all/retroarch-core-options.cfg

Apparently it was a problem with the .bak file for my controller located at /opt/configs/all/retroarch-joypads/. Deleting it solved the whole situation. I noticed that the script module is configured to ignore it, but I thought it might not be for some reason and sure enough it paid off. A new .bak has even been created and is not throwing Mupen64plus off, so I assume it was a fluke of some kind.

Perhaps the .sra file is made by one emulator and .srm by the other..I'll have to check tomorrow

Works also on my end. Thank you!

No problem:

vbs@vbs-XS35:~$ grep -a4 "(fbset)" /opt/retropie/supplementary/runcommand/runcommand.sh # get default fb_res (if not running on X) fb_orig="" if [[ -z "$DISPLAY" ]]; then fb_orig="$(fbset)" fb_orig="${fb_orig##*mode \"}" fb_orig="${fb_orig%%\"*}" fi

Well, I probably clicked that option in the runcommand menu "Select framebuffer Res" but I think I chose "320x240" which was the initially value anyway. But ok, that might be the reason! Thanks!

N64 doesn't flawlessly work on the Pi. Overclocking a little does help, but some games will always have lag, some unplayable. It's a shame but I think until we see a Pi 4, this will always be the issue.