Is there a way to change the "Global root folder" so I can run a scrape for ALL SYSTEMS with that altered path? I often play around with multiple boxes at the same time so I like to give them different names, RECALBOX2 etc. The only way I can see to get around this (other than renaming the boxes) is to go into each system change the path and scrape one at a time starting each manually.
@substring Update, I don't see a read only issue and I also plugged a different controller (I can't be certain I haven't config'd this one before) I happen to have and went through the configuration process and it didn't get stuck in a "loop" the way it does when I try to configure the remote. I also plugged in a controller I know for sure I had previously configured and it did not ask me to configure it again.
EDIT: I am able to break out of the "loop" by hitting the controller's hotkey on a my previously configured controller. I'm wondering about the fact that my remote is detected as a controller called "keyboard". Maybe because the controller has both a remote buttons side and a keyboard side, recalbox is confused and detects it as a controller, yet does not store the result of configuration because it also believes the device is a keyboard? I will add that when I go through the configuration process whether I flip the remote over to the keyboard or remote side, the resulting issues are the same.
@substring It's seen as a controller I guess, I mean it asks me to configure it and when I do it says "keyboard" as the name of the controller.
I am not sure about forcing a reboot but perhaps, I'll check that. But that would only explain the "loop" situation, not why it forgot the remote's previous configuration to begin with. I guess I should plug my controllers back in and see if they have also been forgotten, though I don't have them at hand right now.
Thanks
I have a T3 style remote/keyboard for Kodi, like this:
http://imgur.com/M1Mrbkm.jpg
The USB receiver for it is always plugged in whether I'm playing games in recalbox or using Kodi.
Recalbox keeps detecting it as a new controller and asking me to configure it, and even after I configure it the detection prompt just keeps reappearing over and over. I have somehow been able to resolve this at least once in the past, actually I think twice, I cannot recall how, and I had it configured so that I could press a couple buttons to get back into Kodi. But then eventually after awhile (several weeks, many power cycles) it detects it as new again and I get stuck in this asking to configure "loop".
So I'm curious, what makes it seem to be a new device? Is it possible some kind of device ID is changing, or maybe my recalbox configuration is occasionally "forgetting" it for some reason? Anyone have any ideas to solve this problem?
@slakka said in Can't get official PS3 controller working on RPi3 with dongle:
Maybe I need to go find a verified compatible bluetooth dongle? Because I had success with the 8bitdo controllers I figured the dongles I have are compatible.
I got a compatible dongle and it's working now, guess there are some dongles that are compatible with some controllers but not others. Thanks for the quick reply.
@Substring said in Can't get official PS3 controller working on RPi3 with dongle:
you need
controllers.ps3.enabled=0to make your pad work on usbyou shouldn't replug after. If i'm not mistaken, the leds will never stop blinking once successfully paired and recognised as a BT pad
Well I want to make it work wireless so I should leave controllers.ps3.enabled=1 correct?
Whether I proceed to replug after the point where the instructions would say to stop hasn't made a difference, it never worked regardless while the LEDs were blinking fast. I only discovered that the replug would make the #1 LED stay lit beacause I was messing around trying various things to get the controller working.
To check again I just did it now from a clean power on, followed the Recalbox manual's instructions and stopped at the point where I press the Home button and all LEDs blink fast. Same result, the controller does not work.
[ 103.648925] usb 1-1.5: new full-speed USB device number 5 using dwc_otg
[ 103.818185] usb 1-1.5: New USB device found, idVendor=054c, idProduct=0268
[ 103.818201] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 103.818208] usb 1-1.5: Product: PLAYSTATION(R)3 Controller
[ 103.818215] usb 1-1.5: Manufacturer: Sony
[ 115.189762] usb 1-1.5: USB disconnect, device number 5
[ 117.771989] input: PLAYSTATION(R)3 Controller as /devices/virtual/input/input0
Maybe I need to go find a verified compatible bluetooth dongle? Because I had success with the 8bitdo controllers I figured the dongles I have are compatible.
I'm trying this on a Raspberry Pi 3 with 2 different bluetooth dongles, one generic "BT2.0" and one "Broadcom CCBT2035BDGP23-2", and a genuine Sony DualShock 3 controller. I am aware of the problems with the built in bluetooth, is there a way I can be sure Recalbox is using the dongle and not the built-in bluetooth? Note that I can pair an 8bitdo NES30 Pro and it's fully functional, not sure if that verifies I am using the dongle and not the built-in. I have tried without USB controller or keyboard/mouse as well just in case they were somehow interfering.
Here are the details of each bluetooth dongle.
Generic BT2.0
http://pastebin.com/vVsxLkgK
Broadcom CCBT2035BDGP23-2
http://pastebin.com/Qi20CmFc
I checked for these in my config file as well, both were present:
controllers.ps3.enabled=1
controllers.ps3.driver=official
Throughout this process, the Recalbox GUI never responds to the PS3 controller, even when plugged in with USB. The controller seems to successfully pair via bluetooth but again it never actually functions. If I then set Main Menu->Controller Settings->Input P1 to the PS3 controller and launch a game, the controller still doesn't function.
Connect controller via USB, all LEDs blink slow, wait 10+ seconds
Disconnect controller from USB, all LEDs turn off
[ 1161.324258] usb 1-1.5: new full-speed USB device number 7 using dwc_otg
[ 1161.493498] usb 1-1.5: New USB device found, idVendor=054c, idProduct=0268
[ 1161.493511] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1161.493517] usb 1-1.5: Product: PLAYSTATION(R)3 Controller
[ 1161.493524] usb 1-1.5: Manufacturer: Sony
[ 1202.566120] usb 1-1.5: USB disconnect, device number 7
Push controller home/PS button, all LEDs blink fast and never stop blinking fast until my next step, this is where my experience differs from the Recalbox instructions
[ 1218.987136] input: PLAYSTATION(R)3 Controller as /devices/virtual/input/input4
Connect controller via USB again, fast blinking stops and then #1 LED stays lit
[ 1419.915759] usb 1-1.5: new full-speed USB device number 8 using dwc_otg
[ 1420.202507] usb 1-1.5: New USB device found, idVendor=054c, idProduct=0268
[ 1420.202521] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1420.202528] usb 1-1.5: Product: PLAYSTATION(R)3 Controller
[ 1420.202534] usb 1-1.5: Manufacturer: Sony
[ 1420.419818] input: Sony PLAYSTATION(R)3 Controller as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/0003:054C:0268.0006/input/input5
[ 1420.420314] sony 0003:054C:0268.0006: input,hiddev0,hidraw4: USB HID v1.11 Joystick [Sony PLAYSTATION(R)3 Controller] on usb-3f980000.usb-1.5/input0
Under Main Menu->Controller Settings->Input P1, the PS3 controller does appear so I guess that means it's paired?
Disconnect controller from USB, #1 LED stays lit (paired?) but controller never works
If I shutdown Recalbox, the PS3 controller shuts off
I have seen a lot of posts about problems of different kinds with PS3 controllers but didn't find a solution for mine.
@paradadf Ok so I guess arcade scrape is out for now.
I checked a few of the Atari 5200 ROMs, SHA1 values matched those on SS. There's data there, descriptions, box art, etc. and the total number of ROMs from No-Intro's set is the same as the total number of games on SS, 107 games. Maybe my directory name should be different?
Thanks.
Just tried this yesterday, worked very well but had a few problems.
atari5200 and supergrafx had no successful scrapes. ROMs are from No-Intro set.
FBA had almost no successful scrapes, only 154 out of 4156 worked, that number should have been several hundred right? Or should it be almost all of them?
I thought maybe the directory name causes it to scrape from different sources so I tried fba, fba_libretro, and mame, same results for all. ROMs are from the set called FBA v0.2.97.38 .
Maybe there is still a problem with mamedb causing so many failures?
