@mitu

Great, I could disable changing the internal color palette in /opt/retropie/configs/gb/Gambatte/Gambatte.rmp:

input_player1_btn_l = "-1" input_player1_btn_r = "-1"

and put fast forward to the right shoulder button with

input_hold_fast_forward = "5"

I also added

input_rewind_btn = "10"

to map rewind to the Retroflag button from the gpi case 2W and

input_toggle_fast_forward_btn = "3"

to toggle fast forward with SELECT+Y.

@mitu Thank you so much! This fixed the problem. I was sure it wasn't a wiring issue, but I guess it goes to show how little I really know about computers, lol. Thanks for the help :)

@yctn said in no Gamepads Detected:

@mitu i found out that the start + home button will quit the emulation and return to th retropi menu when i am in a rom. this is nice cause i notice that the graphics of mupen64plus-glide64 are better then with the ir/libretro core.

/opt/retropie/config/all/autoconf.cfg

Mupen64plus_hotkey = "0"

!Turns off hotkey in N64 emulator only!

/opt/retropie/config/n64/inputAutocfg.ini

choose your button combination for exit/load/save

/opt/retropie/config/n64/mupen64plus.cfg

Find these options under [CoreEvents]

Joy mapping stop = "J0B10/B11" Joy mapping Load state "J0B10/B6" Joy mapping Save state "J0B10/B7"

This worked for my Wireless Xbox one controller, (usb-C wired is again different buttons).
I believe N64 8BitDo is J0B9/B12

Each controller type might have different button setup

Disclaimer: it will no longer adjust the hotkeys for other controllers for N64 as player 1. This is not flexible at all. If you want to change it, it must be done manually.

I tried my best to get it reproduced with the binary ES install, but whatever I do on my side I land correctly at "Teenage Mutant..." which is the first with "T" (in Arcade) and at "Tecmo Bowl" (first with "T" in "NES" and "All Games").

As it is non-deterministic on your side I am leaning towards the hardware and maybe in conjunction with "ThreadedLoading" value="true" but it is a vague guess.

If you have the patience, you may install the whole shebang Retropie on your Desktop or in a Linux VM or if you have a spare Pi4 at hand use that. If it also happens on a different RetroPie installation it indicates something with the filestructure/gamelist data, if not then the plot thickens that it might be hardware related.

@sleve_mcdichael is right - the overlay is not enabled by default. However, this happens now because RetroArch's defaults to 'false' to enable the overlay, whereas in the past the overlays were enabled by default.
RetroPie's configuration for RetroArch enables them, but you probably have reset the configuration and just discarded that. As @sleve_mcdichael said, try not to use the 'save'/'reset' configuration from RetroArch and leave the default configuration as is - either use the configuration editor or a configuration override. Debugging a configuration files that's hundreds of lines is not practical.

@mitu Ah thanks, that is good to know. But seems it doesn't have super pages enabled on that build, so I might just give it a shot and config it myself and see if it works.

If nothing else, it'll allow the system to switch to 4kb pages on the fly without having to change kernel to use aethersx2 or other abandoned applications in that situation

Edit: so I edited the above git pull to build with huge/super pages config on

pi@raspberrypi:~ $ uname -a Linux raspberrypi 6.13.0-v8+ #1 SMP PREEMPT Fri Jan 24 15:37:24 GMT 2025 aarch64 GNU/Linux pi@raspberrypi:~ $ cat /sys/kernel/mm/transparent_hugepage/enabled [always] madvise never

I am noticing a slight increase in a few spots, for example I can push some of the flycast games up to a higher internal resolution. Not noticing too much change on the gamecube side of things, unless there's a game or two that runs at say 55fps or 27fps and it can be nudged into full speed.

So tried star fox adventures and it seems to goes from around 25fps in the area Fox first explores to a more manageable 47fps. With VI Skip on it becomes playable imo, if not at the original 60fps the game was at

@Dekawar said in Help getting Amiberry to work on RetroPie Thanks:

@mitu have really been hoping an update would fix ..

If you have the right BIOS files (as specified in the documentation) and the game still doesn't work, then the issue might be the game. What game(s) are you trying to start, what is their filename and which emulator (lr-puae2021 or amiberry) are you using ?

If you start the Amiga test kit image, does it work ?

@mitu
Thank you, just realized I'd probably need an adapter and a good keyboard for this.

Please large configs or logs on pastebin.com.

You're right. I just picked a set of mp4 files and didn't look at them.
They are from a LaunchBox scraped set and have different file names.
I found the matching name set and it works just fine.

Thank you.

@carlosff2 this is not a rom site - see the forum rules and come back later when your ban has expired.

@stevejp1978 said in need help finding configs directory in retropie:

the setup instructions tell me to copy all files to /opt/retropie/configs/all but it's not there.

If it's not there, then maybe your system doesn't have RetroPie installed. If the system comes preloaded with RetroPie, then you need to ask the vendor for support.

@sleve_mcdichael ok i made the file amiberry.conf copyed and put the text in you gave us.

rom_path=/home/pi/RetroPie/BIOS/amiga

saved it over network to a the spashcreens fold and now going to move it to

/opt/retropie/configs/amiga/amiberry/conf/

if this works wow. Thanks does this mean i need to move or make a file called amiga in BIOS/ and that is where i need to put my kickstarts?

@sleve_mcdichael
Thanks for pointing out the obvious that was staring right in front of me...

Accomplished what I wanted in a much easier way.

Thanks for the help!

@mitu Thanks, i will have to wait until the next problem because:

journactl -U '12 hours ago'

tells me that the logs starts today... (the event happened yersterday)... Unless you have an another idea.

Thanks: Will update this post as soon as i have an another emergency mode !

@ExarKunIv

Just got sound working op the pi5.
I need to edit the chown line in the script in order to make sure the config file has the correct rights.
Seems the suggestion from Lolonois to edit that line wasn't correct.
If the rights are ok then you can alter the audio driver/output in the UI and it will be saved in the config file.

Made the commit.