@Simberg190 you can open an issue here https://github.com/midwan/amiberry/issues

Use another front-end, maybe ?

@mitu
Thanks, save/load is working.

But strange, usb calbe keyboard is connected, also arrow-keys are working inside the retroPie, but in the Game-Menu no key is working, also no (i.e.) "5" to start the game.
I must use the virtual keyboard (select key). But OK ....

@Drakaen391 Pins #2 and #4 can be used to input power without usb power or run devices with usb power so you have two to choose from. There are even more grounds.

Pins # 1 and #17 are 3V power outputs. I used those instead of the 5V because they would run the fan slightly slower which meant quieter fans as I didn't like the noise.

@quicksilver

I also remember that on original N64 hardware that if the analog stick was pushed while the game was booting up the crosshair/selector would get stuck trying to go one direction.

I also remember this, very annoying. But once my N64 joysticks were worn out, I put the analog stick back a bit to not have to press it as much forward to have it react.

You need to remove then reinstall retropie manager from RetroPie-Setup.

You might also benefit from some RF shielding on both the Pi and the cable. The Pi throws off a huge amount of RFI , to the point where even a cable plugged right into it is going to catch some too. Use a grounded case on the Pi (or just put it in an Altoids tin with standoffs) and a grounded plug too. Don't forget to ground the Pi case to the car's ground too.

Self-Solving Problems Department: the trick is to put "cocoe" in the EMULATORS.CFG line rather than "coco"...

@dmmarti It was simpler than that - I'm a dumdum and I had so many folders with CoCo BIOS files in them from when I was trying to get it work that I'd added the Extended Basic ROMs to every folder except the right one :D

btw @mitu , I had been pulling my hair out for so long with this issue, I'm sure
I owe you a Paypal pint at least...

I want to add one thing to @BuZz' post: Please edit your post and give it a more explanatory topic. Imagine a forum filled with posts named "Newbie … Help!" and the like. Nobody wants to read every topic just to see what they are about.

Just a friendly advice. Welcome to Retropie and to this forum. :)

@robusco said in Multiplayer online and homebrews:

In order to do what interests to me, is the PI 3B also a good model?

Yes, but you might consider the 3B+ model released last year. The Pi4 is also out, but it's not fully supported by RetroPie yet.

Is there a list of which games of which systems can be played online?

It depends on the emulator used. The lr-.. emulators - Libretro Cores - that run through RetroArch can have Netplay ability - see https://retropie.org.uk/docs/Netplay/. You can consult the core page at https://docs.libretro.com and see if it has Netplay enabled (see for instance http://docs.libretro.com/library/mame2003_plus/).

The other thing I was asking about Homebrews is:
Wich version of Streets Of Rage Remake and Open BOR runs fine and have the almost game compatibility? I have to use two version of Open BOR to make the old and newest game both running?

I don't know about SORR and OpenBOR compatibility. In RetroPie, OpenBOR uses an old fork which is optimized for the Pi, could be it's not compatible with games created for recent OpenBOR games - there's whole topic for this with lots of details here.

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!