Yup, that did the trick. You def need to have it in Android mode and not Windows to get it working with Retropie (for me anyway). Thanks!

@saiki20 said in Using RetroPie For My Own Software:

Do I have to do anything special when programing it to account for these new USB signals?

Can you be more specific ? How are you using the USB ports - just using a regular controller/gamepad or you have a another device type of device that connects via USB and you'd like to act as a controller ?

I'm having the same issue,
i have 4 controllers, 2 nes(clone)(usb), 2 genesis(8bitdo)(usb wifi dongle).
they share the same name,"USB Gamepad ", vendor 0079, product 0011.
They both use "USB Gamepad .cfg"
I've been trying to get around this for a while now.

(8bitdo m30 2.4g)
cat /proc/bus/input/devices
I: Bus=0003 Vendor=0079 Product=0011 Version=0110
N: Name="USB Gamepad "
P: Phys=usb-0000:01:00.0-1.4.3/input0
S: Sysfs=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4.3/1-1.4.3:1.0/0003:0079:0011.0003/input/input2
U: Uniq=
H: Handlers=js1 event1
B: PROP=0
B: EV=1b
B: KEY=3ff 0 0 0 0 0 0 0 0 0
B: ABS=3
B: MSC=10

(generic usb nes controller clone)
I: Bus=0003 Vendor=0079 Product=0011 Version=0110
N: Name="USB Gamepad "
P: Phys=usb-0000:01:00.0-1.4.4/input0
S: Sysfs=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4.4/1-1.4.4:1.0/0003:0079:0011.0005/input/input4
U: Uniq=
H: Handlers=js2 event2
B: PROP=0
B: EV=1b
B: KEY=3ff 0 0 0 0 0 0 0 0 0
B: ABS=3
B: MSC=10

(8bitdo m30 2.4g)
udevadm info -q all -n /dev/input/event[1]
P: /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4.3/1-1.4.3:1.0/0003:0079:0011.0003/input/input2/event1
N: input/event1
L: 0
S: input/by-id/usb-0079_USB_Gamepad-event-joystick
S: input/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4.3:1.0-event-joystick
E: DEVPATH=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4.3/1-1.4.3:1.0/0003:0079:0011.0003/input/input2/event1
E: DEVNAME=/dev/input/event1
E: MAJOR=13
E: MINOR=65
E: SUBSYSTEM=input
E: USEC_INITIALIZED=5712528
E: ID_INPUT=1
E: ID_INPUT_JOYSTICK=1
E: ID_VENDOR=0079
E: ID_VENDOR_ENC=0079
E: ID_VENDOR_ID=0079
E: ID_MODEL=USB_Gamepad
E: ID_MODEL_ENC=USB\x20Gamepad\x20
E: ID_MODEL_ID=0011
E: ID_REVISION=0105
E: ID_SERIAL=0079_USB_Gamepad
E: ID_TYPE=hid
E: ID_BUS=usb
E: ID_USB_INTERFACES=:030000:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usbhid
E: ID_PATH=platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4.3:1.0
E: ID_PATH_TAG=platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_4_3_1_0
E: ID_FOR_SEAT=input-platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_4_3_1_0
E: LIBINPUT_DEVICE_GROUP=3/79/11:usb-0000:01:00.0-1.4
E: DEVLINKS=/dev/input/by-id/usb-0079_USB_Gamepad-event-joystick /dev/input/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4.3:1.0-event-joystick
E: TAGS=:uaccess:seat:

(generic usb nes controller clone)
udevadm info -q all -n /dev/input/event[2]
P: /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4.4/1-1.4.4:1.0/0003:0079:0011.0005/input/input4/event2
N: input/event2
L: 0
S: input/by-id/usb-0079_USB_Gamepad-event-joystick
S: input/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4.4:1.0-event-joystick
E: DEVPATH=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4.4/1-1.4.4:1.0/0003:0079:0011.0005/input/input4/event2
E: DEVNAME=/dev/input/event2
E: MAJOR=13
E: MINOR=66
E: SUBSYSTEM=input
E: USEC_INITIALIZED=93696483560
E: ID_INPUT=1
E: ID_INPUT_JOYSTICK=1
E: ID_VENDOR=0079
E: ID_VENDOR_ENC=0079
E: ID_VENDOR_ID=0079
E: ID_MODEL=USB_Gamepad
E: ID_MODEL_ENC=USB\x20Gamepad\x20
E: ID_MODEL_ID=0011
E: ID_REVISION=0106
E: ID_SERIAL=0079_USB_Gamepad
E: ID_TYPE=hid
E: ID_BUS=usb
E: ID_USB_INTERFACES=:030000:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usbhid
E: ID_PATH=platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4.4:1.0
E: ID_PATH_TAG=platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_4_4_1_0
E: ID_FOR_SEAT=input-platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_4_4_1_0
E: LIBINPUT_DEVICE_GROUP=3/79/11:usb-0000:01:00.0-1.4
E: DEVLINKS=/dev/input/by-id/usb-0079_USB_Gamepad-event-joystick /dev/input/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.4.4:1.0-event-joystick
E: TAGS=:seat:uaccess:

This script is to make ResilioSync an always running service so any changes made are automatically uploaded to your master repo.

Run the commands, make the changes and then restart the service. I made my initial repo on my master server and added my main retropie to the sync group, waited for 100% sync and then added the rest of my devices exactly the same way.

Open the resilio gui by going to retropieIP:8888/gui/

wget -c https://download-cdn.resilio.com/2.6.3/Debian/resilio-sync_2.6.3-1_armhf.deb sudo dpkg -i resilio-sync_2.6.3-1_armhf.deb sudo systemctl enable resilio-sync sudo nano /lib/systemd/system/resilio-sync.service sudo sed -i "s/rslsync/pi/g" /lib/systemd/system/resilio-sync.service

sudo nano /lib/systemd/system/resilio-sync.service

Go in and edit the file and change out this line
ExecStart=/usr/bin/pi--config ${SYNC_CONF_DIR}/config.json

to

ExecStart=/usr/bin/rslsync --config ${SYNC_CONF_DIR}/config.json

sudo systemctl daemon-reload sudo systemctl restart resilio-sync

When u go to make the sync, I used /home/pi/RetroPie/roms

I can get to the core options using select&start anyway. (Those two are the only buttons that function) I couldn't find the option at first (because one would think that would be in the Controls menu...) but I found it and it now lets the joysticks work, at least. I have to check the buttons on a different game (because pacman has no buttons). I'll set it at the Core level once I test it out. So far, so good.

EDIT: I think it's working properly at this point. Thanks!

@BuZz said in Retropie On Debian:

@NY152 you will need to run retropie under the desktop on your system. Please post logs for any error you got installing as @mitu mentioned. Thanks.

Astonishing ...

NO error during installation.

The problem with Debian is that you can not run EmulationStation in console mode (it does not detect a display)

Under ArchLinux, no worries without any desktop environment. EmulationStation starts and runs the emulators itself without any problem.

So saying that an office environment is mandatory is a totally false.

I will look for myself since without thinking more than that, the office environment is for you indispensable, you consider this as normal, not me

thanks anyway

Sorry, I will... many thanks

Hi, I'm also in the same situation... I did an installation from source an leave alf day and night, it tooks almost 6hs :o :/ and is not working on my Pi Zero W. I never tried to install from binary... Is the only way to get it work?

Thanks for all your help.

@A-big-nerd https://github.com/retropie/retropie-setup/wiki/Nintendo-DS

Bummer that there seems to be no way to do this.

I don't plan on cutting power without doing a normal shutdown regularly, but accidental unplugging is definitely a risk in my use case.

Thank you for the help!

@VictimRLSH

I tried:

EMS=true
XMS=true

Still didn't work :(

@mitu Yeah the original process of the game is there's a key you hit to start when the audio track prompts you to, so the game and the audio track are sync'd up. I'm not 100% sure but I doubt the spectrum ever had a microphone add on.

@showstopper no that location will not be overwritten. You will have to manually update that file from now on if you add new systems to emulation station.

@archie456 note that mame4all is redundant on pi3. see https://github.com/RetroPie/RetroPie-Setup/wiki/Arcade#step-1-choose-your-arcade-emulators

@Eims said in [PSX] Convert various source files into a single *.pbp:

@mitu Well, I have the .bin and .cue files currently available and would like to process them further.

OK, so you should be able to convert them to .pbp - isn't this what you intend to do ? If the .cue file is correct, then that's all you need.

Note that some CDs don't have only 1 .cue + 1 .bin, if the CD has both a data track and multiple audio trackes, you'd have multiple .bin files.
For instance, In the Hunt has alot of audio tracks, so the .cue should be accompanied by multiple .bin files - http://redump.org/disc/7676/.

Awesome! I set up open box to start with 1280x720, verified it via the log, and it worked perfectly with the threading set false. Looks way better than it did set true, has better response/less lag, and of course the screensaver doesn't kill it after 10 minutes.

Thanks so much for your help with my problem.

Sure you can. Check the docs.
You can find overlays and launching images for many arcade classics in my Repo.