[ex]

thiemok, when you copied the config file for you xbox controller, what did you name the second file? I am trying something similar with a PS3 controller so that I can use two PS3 controllers while keeping the option to still use my SNES USB.

[ex]

Correct me if I’m wrong here because its been a few weeks, but isn’t the name of games handled by the gamelist.xml? The scraper does indeed pull metadata from the roms hash and uses that to generate the gamelist file. If you edit this file for the specific console you can change things.

I for example was too lazy to run the scraper myself to avoid wrong naming of roms. I instead just let it auto-run and then corrected the errors myself by editing the gamelist file. You can name the rom whatever you would like in there. You can also easily correct improper images and what not. This was simpler/quicker for me than individually scrapping thousands of games.

Floobs video will help you scrap info for MAME and pifba! I actually used his method myself. Same thing applies to mame with the gamelist.

[ex]

Pretty sure your problem is due to this:

[Joystick]
# Get codes from "jstest /dev/input/js0"
# from package "joystick"
input_player1_joypad_index = 0
#player 2 button configuration
input_player1_joypad_index = 1

You have both configs set as player 1. Change one to player 2.

[ex]

Hmmm. I previously had a PS3 controller synced with bluetooth. I try to remove that because it is the only bluetooth device displayed in hciconfig. Could this be the problem? Having a PS3 controller synced before? I try to remove it and get hit with this:

pi@raspberrypi ~ $ bluez-simple-agent hci0 00:02:72:D6:9E:96 remove
ERROR:dbus.proxies:Introspect error on :1.1:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.10" (uid=1000 pid=5609 comm="/usr/bin/python /usr/bin/bluez-simple-agent hci0 0") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=2270 comm="python /usr/sbin/sixad-dbus-blocker ")
Traceback (most recent call last):
  File "/usr/bin/bluez-simple-agent", line 102, in <module>
    path = manager.FindAdapter(args[0])
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.10" (uid=1000 pid=5609 comm="/usr/bin/python /usr/bin/bluez-simple-agent hci0 0") interface="org.bluez.Manager" member="FindAdapter" error name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=2270 comm="python /usr/sbin/sixad-dbus-blocker ")

I can’t remove the PS3 connection. Anyway to remove it completely and do a clean install of the DS4?

Here is what hciconfig outputs (This is my PS3 controller MAC which I no longer have, not my DS4 MAC):

pi@raspberrypi ~ $ hciconfig
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 00:02:72:D6:9E:96  ACL MTU: 1021:8  SCO MTU: 64:1
        UP RUNNING PSCAN
        RX bytes:2363 acl:0 sco:0 events:88 errors:0
        TX bytes:1403 acl:0 sco:0 commands:78 errors:0

Edit: Your English is more than good!

[ex]

Just tested it out and ran into two issues.

The DS4 was found and the mac address displayed. After that it never goes to a soft blue it just keeps blinking. I then ended the command. If I don’t end the command and let it continue, I get this message:

[bluetooth] Unable to connect to detected device: Failed to set operation al mode: [Errno 107] Transport endpoint is not connected

Also, what file are you editing in the /etc/init.d directory? rc.local?

[ex]

I am definitely going to try this! Someone I spoke with tried this a while ago with older drivers and said it was so laggy it was unusable. I will give this a shot and report back.

[ex]

Thanks for the response. I actually figured out what was happening.

My PS4 controller was increasing save state slots with each save. When loading it would seem to cycle backwards and attempt to load the wrong state.

I actually changed over to a PS3 controller and it fixed itself. This is what made me go back and figure it out because it was bugging me.

[ex]

Ahhh thats what I figured! That’s what I get for trying to be lazy.

Where is the gamelist.xml file generated by es_scraper? I used sselphs scraper for SNES and it places it along with the roms. ES_Scraper seems to place it somewhere else.

Edit: Nvm! Found it!

[ex]

Just wanted to add that I do see the save states in the proper folder (ex. Mega Man X (E).state1 in /home/pi/RetroPie/roms/snes).

[ex]

@mikedpitt

Have you configured the controller settings for MAME4ALL and Neo Geo? They don’t use retroarch and require you to enter individual settings for them.

Also, ES looks for images and descriptions from thegamesdb.net. The site has been down more often than not the past few days, so this could be the reason for problems your having.

[ex]

RetroMarine is correct. The correct romset is 0.37b5. I can confirm most games from that set are working fine with the default MAME from the 2.3 image.

[ex]

PSX has been working fine for me. If your BIOS was wrong you should get a quick yellow flash of text when you load any rom that lets you know you’re missing and BIOS file and to expect errors.

Seems to me like it might be you actual rom file. With just the BIOS placed in the bios directory and the .bin file placed in PSX roms mine are working.

[ex]

Im not 100% on this but it looks like you switched to the alternative MAME emulator. By default, retropie uses MAME4ALL. The es_systems contains the alternative emulator (usually an alternative because it doesn’t run as well for most people as the default set emu). Looks like you switched to the alternative emulator which would explain your performance decrease.

[ex]

Using a program such as winscp would be much simpler. Drop the bios file where bobbyt mentioned and you are good to go.

Winscp will also allow you to transfer roms over.

[ex]

I got some heatsinks with my case and have been running on medium. Some games still have audio blips.

Mobel B+ with 256 mem split.

[ex]

First off the scraper works great! Pulled about 90% of my titles with no problem and I have a ton! Thanks for your work!

The only issue I am having is with unzipped .md roms. It seems to flag an error because of the file extension. Is there any workaround for this?

[Author]

Posts