@BuZz Well Ok then, i'll try later. Thanks for answering my question about keeping it. :)

@Lyle_JP the libretro core needs to support it.

I was searching for an answer to this for a while myself before I figured it out on my own. I'm running version 4 of RetroPie and dispite it being mentioned that the Scraper was fixed in a previous version, I still had some troubleshooting to do. What I found in the error logs is the XML file wasn't able to be written to... in my case, they didn't exist at all, so I wrote this Bash script to create a basic XML file to start it off. After running, hopefully the built in Scraper for RetroPie will be able to save all your data.

#!/bin/bash
#RetroPie gamelist.xml setup
#by Nathaniel Dragon on 2017-02-04
for d in ~/RetroPie/roms/*; do
if [ ! -f $d/gamelist.xml ]; then
echo "Make gamelist.xml in $d"
echo '<?xml version="1.0"?><gameList />' > $d/gamelist.xml
else
echo "$d already has a file."
fi
done
#Enjoy!

I know that not everyone trying to get this to work is a programmer, although, you probably have already found out something about scripts on Linux. In case you've never written or run a Bash script before, save that code in a file on your RaspberryPi as something like "setup.sh" and then make it executable with "chmod 755 setup.sh" and finally run with "./setup.sh" ...

Unfortunatly I am unable to provide the log at this time but kodi works fine until I plug in the usb
I plugged in the usb and let retropie create the file system and then i copy all the roms into their respective folders
I have wiped the sd card and reinstalled the os several times and I get the same results each time
Also once this happens retropie will no longer let me uninstall kodi either
hopefully this helps otherwise i will have to upload the log later

just fyi, I think I figured out how to set up the Bluetooth controller properly from the start so that it defaults to p1, granted I am using an nes30 pro so if there are firmware/hardware differences with the ps3 controller this may not work but its worth a try.

install a clean image boot for the first time. plug the controller in with a wired connection to PORT 4 (bottom right USB)
***DO NOT plug in a keyboard emulationstation should detect one gamepad. go ahead and configure it first (yes it is still wired in) next go to Bluetooth settings and register it
4.a while wired in, select the register option
4.b unplug the controllers wired connection from the controller side (not necessarily from the USB side)
4.c make the controller discoverable
4.d rpi should find the device
4.e plug the controller back in and complete the registration process (set udev rules, boot options, etc.) quit and go back to emulationstation (controller still wired) press start, navigate to configure input and select it - the screen should say that it is detecting TWO controllers UNPLUG CONTROLLER. now press a button for emulationstation to recognize the controller in Bluetooth mode. configure it! unplug the USB side and reboot the rpi reboot your controller and you should be connected in Bluetooth to port0/P1.

at this point you should be able to connect a keyboard as well but USE PORT 4. I also don't bother with configuring it as an emulationstation controller... I ONLY use it to do the typing required in the back end or when searching for roms with the scraper.

the advantage of this method is that your controller shortcuts and all p1 functionality is retained EVEN IN THE MUPEN64 emulator! Using the joypad_index remapping method above works find for libretro cores but I found that playing hires n64 games I didn't have any shortcuts or even an exit for mupen64. With this method you should be good to go.

one other note: if you connect your controller to other devices like me (I travel, so I connect my nes30 pro to my laptop quite a bit) when you reconnect it to your pi, I've found that it is easiest to simply remove the device, then re-register it. you don't need to recreate the udev rule or set boot options... you just remove the device then add it back and you're good to go.

lastly, I've tested pretty successfully with adding other controllers as P2 and it works flawlessly once you get your p1 Bluetooth controller set up.

hope this helps!

Yes.
the board with white connectors is for 90% sure is a Dragonrise Inc USB encoder. It hase kinda little delay for my tastes...
Working like a charm from Retropie 4.0 and above straight from initial flashing.
Done two cabinets with this set.

@Capt_MorganCreek Ok, I'll give that a try. Thanks.

I had the same issue; my PS4 controller would pair but then not work. So I had to buy the USB wireless adapter, and now the controller works fine.

I have updated retropie-setup to use a custom sdl2 for X11 targets now, which should hopefully solve this issue without having to manually build a SDL. Feedback welcome.

@ExarKunIv

Thanks for the response. I have manged to make progress thanks to the seo-michael.co.uk link. However, now that I have 5 VPN locations configured, my connectivity is failing me. I won't say more until I've fought for a while longer. It's possible that I overcome this obstacle, too.

@Xyb0t Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first - you should start a new topic as detailed

The freeze issue you quoted is fixed

@loop315 Which image are you using? What hardware are you on? Please read this as agreed on signing up to the forums https://retropie.org.uk/forum/topic/3/read-this-first and give us some more info.

From your post, I can kind of deduce that as you got this Retropie "kit" for Christmas, that it was purchased with the SD card pre-loaded. That type of image is not something that the devs here will support and you'd be better downloading the official image and following the initial setup guide on the wiki.

@AlexMurphy thank you. And there is no other addon to get them working?

Thanks for the reply. I thought that sounded confusing when I read it. Personally, I think it would be helpful to newbies like myself to see a separate page for the FDS since it is technically different hardware.

Thanks a lot for the help and advice. I appreciate taking the time to help us newbies out. I'm trying to learn as much as possible on my own in the docs but sometimes things get a bit confusing.

About the Famicom system (not the disk images - the .nes roms) - can I just put them in the "nes" folder with the standard nes roms or would that cause confusion with the emulator or scraper? I can't figure where else the Famicom roms would go if not in the nes folder.

@edmaul69 Nope no mausberry, I'm pretty comfortable just going through the menu. I would really like to, someday, figure out a way to plug in the power supply, and have a functioning switch to power on/off via the on/off switch on the Sega USB hub. It functions side to side but it's just for show, along with the vertical volume knob. I would like to plug in, switch it on, and it boot up, then switch off, and shutdown the system properly as if I went through the menu somehow. This one guy said he was able to accomplish this using python script, and I believe the switch wired into the GPIO. I'm not familiar with python or how I'd even go about configuring that, but I'm sure it's possible. Just need the know-how. That would be pretty sweet to just us the on/off switch like an actual Genesis console.

Also note that you will definitely, like no ifs ands of butts NEED a wireed controller (or at least a keyboard) to re-connect your Bluetooth controller when it looses signal. Which in my experience is pretty friggin often (not like constantly, but at lease once every other day...if not several times in a day if I'm playing a lot and rebooting a lot and such).

This is why I recommend Xbox 360 wireless controllers with the USB adapter that's half the size of the Pi 3. It simply works 99.9% of the time. It's a dedicated receiver so it doens't have to deal with the limitations of Bluetooth even if it's using pretty much the same ghz band.

EDIT darn it, replied to a 2-hour-old reply who replied to an 8-month old topic...

Yeah maybe a bad SD card, but scandisk ones work well for me on the pi3.