While trying to be helpful, the above posts were not specific enough.

Using hints from the config files here:
/opt/retropie/configs/n64/InputAutoCfg.ini
/opt/retropie/configs/all/retroarch-joypads/WishTechnologiesAdaptoid.cfg

And the official documentation from both mupen64 and retroarch, I managed to create a configuration specific to the N64 controller with adaptoid USB<->N64.

(EDIT: The below confusion caused by one simple issue. One cannot restart emulation station to reload the /opt/retropie/configs/all/retroarch-joypads/, one has to restart the entire RPi!!! What a bug D:)
There is some confusion for me that I'm trying to work out. I set the save/load state, but somehow load state on button "12" and in the mupen config it's "DPad L = button(12)", yet start+C-left will load state... Weird stuff all around.

In WishTechnologiesAdaptoid.cfg:
#Start button
input_start_btn = "8"
#Start is now the "hotkey"
input_enable_hotkey_btn = "8"
#Left shoulder "L"
input_l2_btn = "6"
#Start (hotkey) + Left-Shoulder will exit the emulator
input_exit_emulator_btn = "6"

Full adaptoid config in /opt/retropie/configs/n64/InputAutoCfg.ini
I was using this to reference what button is what for the above changes. By default from the previously linked config, it had some issues, such as A button was C-down, C-down didn't do anything.

; Wish Technologies Adaptoid_START
[Wish Technologies Adaptoid]
plugged = True
plugin = 2
mouse = False
AnalogDeadzone = 4096,4096
AnalogPeak = 32768,32768
Mempak switch =
Rumblepak switch =
C Button D = button(1)
C Button L = button(4)
Z Trig = button(9)
Start = button(8)
Y Axis = axis(1-,1+)
DPad U = button(10)
C Button U = button(5)
B Button = button(3)
A Button = button(0)
DPad D = button(11)
X Axis = axis(0-,0+)
R Trig = button(7)
DPad R = button(13)
DPad L = button(12)
C Button R = button(2)
L Trig = button(6)
; Wish Technologies Adaptoid_END

Side note, I wanted to make sure keyboard and other controllers are disabled. I have some USB SNES style controllers, but I don't want them working with the N64 emulator.

In /opt/retropie/configs/n64/InputAutoCfg.ini
Find the "plugged" option for keyboard and other controllers you don't want to run in the N64 emulator, and change "plugged" from "True" to "False"
; Keyboard_START
[Keyboard]
plugged = False

#My case has these other USB controllers configured:
; 2Axes 11Keys Game Pad_START
[2Axes 11Keys Game Pad]
plugged = False

@meleu Yep, changed it, but it still wants to use controller #1 to control Luigi

@edmaul69 also, i forgot to tell you to go down to joystick mappings and set up both players controllers.

If youve just started with the image, I'd stop the update and write it again - Kodi is there (the lists arent alphabetical so scan through the full list) so no need to update.

If you do want to update (there is rarely a need), use the binary update, not the update from source option which it sounds like you may have done.

@vbs makes sense that you had slowdown now you mention the CRT filters. The filters adding approx 20% load so combined with resid thats going to cause slowdown. Testing the Edge of Disgrace demo with both switched on is causing stuttering/frame drop to 40fps

@Floob said in Sega Monoco GP:

THanks for that as well Floob :-)

@joaovlg try to follow these steps I'm talking here:

https://retropie.org.uk/forum/topic/2719/keyboard-stopped-working-after-i-played-around-in-the-controller-config-in-rtgui/2

@herb_fargus

Upon reading more of these links, I think the big problem for me is I have a Pi Zero, and if I'm not mistaken, installing add'l emulators really requires an Internet connection. This is obviously a problem, unless maybe if I had a USB hub.

I tried following the instructions, found the emulator on the list, but it simply complains it can't find it. So for now at least, I'm taking the path of least resistance and getting 3.8.1. If it does the job, I'll keep using it. If there's some way to install these add'l emulators thru a USB flash drive, please let me know. There seems to be a good bit of confusion around this.

Sorry Mate. My bad.

@ShawnS: No worries. It would have been cool if it were possible.

@GetKeyOpenDoor if we deleted everything that was solved on the forum we wouldnt have much of a forum now would we? guarantee at least one other person had the same question and now doesnt have the benefit of an answer because you've removed it.

@tastetestertt Please open a new topic providing details as mentioned in https://retropie.org.uk/forum/topic/3/read-this-first

Thanks Buzz, got it working by following your steps. Appreciated!

RetroArch bug - https://github.com/libretro/RetroArch/issues/3605 (or by design perhaps - but should be changed imho).

the default emulator is not a libretro core so doesn't have the retroarch gui. You can try "lr-glupen64" from optional packages though if you require a libretro emulator.

I had a look in /boot/config.txt, but there was nothing of use there. I did come across something else though;

https://github.com/tasanakorn/rpi-fbcp

This utility will copy all the data from my primary framebuffer (fb0 / HDMI) to my secondary framebuffer (fb1/ USB). I've set it up to auto-run on start-up and it kind of works now. My next problem is that the refresh rate is only around 1 fps!

No, there is no metadata stored in the actual ROM zip, it's just a compressed file containing one or more files of binary ROM data.

That binary data might be a valid parent ROM, a valid split child ROM, a valid non-merged child, a picture of your cat, or random garbage.

The only way to check the contents of the zip against known ROM contents is to checksum the contents and compare them to known checksums. Those checksums are what a DAT file contains.

@a7mag3ddon only a commit log on github