whel found it this is the solution (found it on yourtube)

@hsamuels said in >5s delay when starting each arcade game:

Does modetest need to check the current and available resolution each time a game starts up? Can it happen once at power-up?

Not sure if you still have the test system around, but we added a modification to runcommand to skip the modeset invocation on systems without KMS (i.e. Pi3 and olders). Give it a try to see if the loading speed is down to the previous timings from the older versions.

Kodi is quite outdated on RetroPie (18.7) in comparison to the latest available version 20.3 so this might be a bug / issue in that outdated version.

I wouldn't also put much hope in getting support for a product only included in RetroPie like Kodi in this forums, better look for support at e.g. https://kodi.tv

@harmeetsingh0013 You've bumped again a very old topic, even though I asked you not to. Also, per the forum rules - don't ask for ROMs. Come back when want to respect the forum's rules.

@Danrancan said in NeoGeo CD - Romset is unknown. Help?:

Does NeoGeo CD Even need a bios? If so where do I put it and what is the name of the bios file?

https://docs.libretro.com/library/fbneo/#how-do-i-launch-a-neogeo-cd-game

@Danrancan said in NeoGeo CD - Romset is unknown. Help?:

My Neo Geo CD Roms are in .chd format. Could that be an issue?

https://docs.libretro.com/library/fbneo/#how-do-i-launch-a-neogeo-cd-game

@mitu My note about continuing to use related to my original post. So... Am I able to run the backup from the same pi that I'm using retropie on, whilst for example playing games at the same time?

What I'm wanting to avoid is having to use my windows laptop for the process as it's used for other things by the family and robocopy is so slow.

Ideally, I'd want to back up the ROMs on the usb directly to a network drive but all from within the pi (so that this can happen in the background and other life can carry on!)

I've managed to find some helpful tips for using rsync so will investigate those as well

@UrHombreAbe said in Keyboard:

I would not know where to begin in connecting via SSH

Maybe the documentation page I pointed at earlier ? If that's something that you're not familiar/confortable, maybe try a different keyboard ?

@wtstreetglow1 any update?

@mitu the "O" button.

Please add more details about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first. There's no need for adding also a German translation, this is an English forum.

The controller seems to be recognized, what inputs are not working ? From the screenshot, it looks like you started an arcade game - those kind of games will usually not register your inputs until you add a 'Coin' (which is usually set to the Select button in RetroPie/Libretro cores).

@mitu said in "No Gamepads Detected" upon start, even though there are definitely gamepads:

Does the controller have an additional D-Input mode ? Try switching to it and see if it's detected.

Problem solved, my man. I don't know if it was D-Input mode thing, but I found the controller's literature which mentioned you must power on the RP, and then plug the controller in, while holding the B-button down. Once I did this, the RP recognized the controller and we are in business.

I appreciate your help, man. Y'all are the best.

@biojudgement The Raspberry Pi 4 has bluetooth built in. So you don't need an adapter. In the DOCS section of this website there a page with instructions on how to do bluetooth pairing. (retropie.org.uk/docs/Bluetooth-Controller/)

You might also need to map the controller in EmulationStation. That's covered in the docs as well.

Also, if you plug in the PS3 controller with a Mini-USB cable, it should show up as a normal D-Input controller.

I recommend to read the RetroPie Doc's about arcade emulation: https://retropie.org.uk/docs/Arcade/

Of course, we can't provide links about bios or roms files because is illegal and against of RetroPie community rules.

whel thanx to @mitu whit out nowing it igot it to work i think.
the problem was the first stap what i dident notis.
and @mitu did say i a noder post "
The GCC version included in Raspbian Buster is stricter now and because of the all warnings being treated as errors compilation parameter, it refuses to compile libhid.
What you can do is to remove the -Wall usage by running configuring the libhid build (and probably the other libraries included), with

./configure --disable-warnings "
wel so i try that and its working.
so for so far i can thel i can turn the leds on and of using the command line (in terminal).
hope the rest is working to i gone try that now.

@Turrican2k I had the same problem, played with all settings but none of them did the trick. Only downgrading to 3.3 worked for me.
ssh to the system then

wget https://github.com/BlitterStudio/amiberry/releases/download/v3.3/amiberry-v3.3-rpi3-dmx-32bit.zip unzip amiberry-v3.3-rpi3-dmx-32bit.zip cp amiberry /opt/retropie/emulators/amiberry/ cp capsimg.so /opt/retropie/emulators/amiberry/

Hello,
I had the same issue and found another work around rather than reverting to the previous version.

The topic is discussed here:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931

It seems that this is intentional will not be changed in future versions.
As mentionned right at the beginning of that post the workaround is the following:

Set ClassicBondedOnly=false in /etc/bluetooth/input.conf Run: systemctl restart bluetooth # or reboot

It worked for me.
Maybe its worth digging a little bit more to know what is the more suitable way of handling this new way of working of BlueZ...