Thank you for the quick reply. Sorry, I pulled the logs from a VM I was running to reproduce the issue. I attempted to run it again on the Ubuntu box and it finally took. Not sure what the issue was, but it appears to be working now (of course after I post a question about it :) Thank you!!

Followed both of your guys' advice. Works perfectly now, thanks!

@quicksilver It is indeed 512 bytes. When my daughter relinquishes the hardware, I will try the rename and report the results.

i think the 2030 pi will support it lol

What is the better performance n64 emulator for pi3B+

@TONX it's not the same issue. The op had mupen64plus-next working but not the standalone emulator. Likely because his ROMs were zipped. You should open a new topic.

I think that's because the 1 PS4 controller appears to generate 2 input devices, so the numbering is skewed. Try the workaround proposed here.

@mitu ok I think I know what to do. Should I edit the file to the keycodes?

@pegasus1130 I am dealing with a similar issue and I am now very, very close to getting it working. I found a post from a year or so ago which suggested that opening the retroarch GUI from within the emulator, then remapping from the "control" menu therein. For me, this involved hitting f1 on a keyboard to bring up the retroarch gui and then switching each button around according to the results of jstest, and finally saving a "core remap file". This let me fix everything but a few buttons. The issue that remains is that there is no listing in that controls menu for buttons 0 and 1, which are my C up and C right.

@hhromic Amazing ! will give it a try haha funny , i cant change it to lower . maybe upper .

Look in the Docs page of the system to see what ROM extensions are accepted by the emulator and make sure you use the same format. The RetroPie image comes with the Mupen64plus installed, so it should be enough to copy the ROMs in the n64 folder and restart Emulationstation. I remember playing N64 games on my 2004 laptop and I got great performance, so I would hope the support is fairly strong now. Not so much, N64 is far from perfect and not all games are running well.

@syc0maniac Is there a specific setting you are trying to alter?

@tackskull I dunno, depends on the core and your hardware specs. Check the libtretro.com docs for your core and see if there are any notes about requirements. As noted in the docs This emulator is supplied for people who are running RetroPie on more powerful x86 systems.

@nightfire /opt/retropie/configs/n64/mupen64plus.cfg edits the standard mupen64plus emulator settings. At my level of expertise(or really a lack thereof) I am unsure how the cores are separated but the es_systems.cfg also lists editable extensions and I would presume if the mupen64plus.cfg doesn't also affect the libreto version, then this probably does. I base my info off of exploration and reading the docs : https://retropie.org.uk/docs/Nintendo-64/ ; so I could be wrong.

@Spartacus as the fellows told you before me, the main problem on loading the N64 games could be the extension. If the files are zipped, unzip them and throw those files into the proper folder. The N64 extension should .n64 .v64 or .z64. Most of the games should work properly depending on the configuration and your raspberry model. I always had problems with Killer Instinct since I'm not able to find a good file for that game. But for the others, I had no problem at all. Concerning the MAME incident, as @herb_fargus stated, the problem should reside on the romset you have. MAME has many different versions and a single game could work fine in one oh those versions but could not work in other. I don't remember but I guess most of the working games are in the romset 1.38 You can check it.

@quicksilver Glad I didn’t make a fool of myself. I remember the “olden” days where you had 2 working emulators for n64 and neither gave you everything you wanted.