@ase1981 said in PS3 connected by USB on RPI4 running most recent Retropie:

However I am confused about the "plug and play" sync when using USB. Once it is synced, will I be able to disconnect the USB wire and still use the controller?

For a simply USB connection, the controller doesn't need to be 'synced', you can just press the PS button and it will start working, i.e. you can configure it and it will be available for the emulators included.

I don't want to be tethered to the RPi.

Using USB, it won't be 'tethered' exclusively to the Pi, that happens only when you pair it via Bluetooth.

I see there are bluetooth syncing options available, but it looks complicated and I would rather avoid that if possible.

It's really not complicated and I think you should give it a try.

Also is it possible to have more than 1 ps3 controller synced and running at the same time for 2 player games?

Yes.

@mitu

I've already done that, a number of times.

There's something more complicated going on here.

I attempted a completely fresh install to track my progress better step-by-step.

It's here: https://retropie.org.uk/forum/topic/34489/continued-sound-issues-some-kind-of-bug

There seems to be:

A bug somewhere in the RetroPie audio script since 4.8 (whatever update coincided with the ".asoundrc is no longer being used" message).

Why would raspi-config generate .asoundrc when we should be using /etc/alsa/conf.d/99-retropie.conf? Why multiple config files for the same thing?

Something kind of bug or interaction with omx player.

I think most of those who are posting with lvl0 volume mixer issues who aren't helped by your guide are stumbling because they have omx player enabled.

It looks very nice and I hope it will be possible to have this in RetroPie. Without being a developer, I think it is unlikely that we will see the latest version of this emulator in RetroPie, because of the minimal requirements set by the developer.

You can't change the name of the controllers, at least not the ones that show up in the selection script. They come from the OS and cannot be controlled from userspace. The input_device_display_name option is useful just inside RetroArch (shows just a friendly name for the device), so that won't help in the selection script.

So yesterday I had a weird error. I thought why don't I put the nvme mount with option exec into /etc/fstab. I did that and after that it would only boot into emergency and I couldn't recover anything. I tried adding the shell to cmdline.txt but nothing helped. So I decided to completly redo my retropie setup. After redoing everything, I tried again to build kodi with all the options and it just worked fine.
No errors nothing, it just went up to 100%. I installed it with sudo make install and it works.
:D As stupid as this seems it probably was some bad configuration which still existed from my first tries.
I want to thank you for your help, after I remounted my drive I thought what a godsent it would have took me atleast weeks to come up with this if ever. :D
So this thread can be closed now.

@Lolonois
This did work, thanks :)
I don't know what I did, but I made a fresh RetroPie flash again, then run the install twice and it worked

@louis1987

I don't have any lag with a Pro 2 without a dongle. (Edit: I also use two simultaneously)

First things first: Update your firmware. Use the 8BitDo application from their website.

Next: make sure background is selected under Bluetooth options to keep it initialized.

Which selection (SADX) do you have underneath your controller? Is it configured properly?

Here is a cfg with D input that should work well.

And here is the cfg I use with X-input.

Make sure it is showing the pop-up that the configuration has been added when you start a game. Sometimes I've noticed lag when the controller was working, but was autoconfigured in some way by RetroArch rather than using the cfg file.

If you are still noticing serious lag it may also be due to your case. Drill some holes in it. (not joking. had one of those shmansy metal cases and couldn't get Bluetooth working right with the controller basically on top of it. Then bought an NESPi case that had an SSD slot and the unshielded SATA connector really screwed with the Bluetooth / wifi- an RPI4 a dinky 3d printed plastic case with a good heatsink / fan is your friend)

Get all the basic thresholds and everything working right in the cfg to your liking as close to perfect as you can before you start adding layers of hardware and configuration complexity. Adding complexity to your system configuration outside of retroarch etc. will also likely be lost / not salvaged if you attempt a reinstall.

More hardware, more changes = more headaches down the line.

Keep it simple, focus on basics.

Good luck.

@dmmarti Ok then. Thanks! I'll use the mouse for MYST :)

Normally you'd compile it manually and add it as a separate emulator, but the current version doesn't compile on current RetroPie (Pi3/Pi4). You may wait until the new version of RetroPie (based on the Raspi OS bullseye) is released and the standalone flycast will be installable.
I've started working on a RetroPie module to integrate it, but due to some rendering bugs and the aforementioned incompatibility, I didn't add it to RetroPie proper yet.

@mitu you, my friend, are a genius (and this is really a stupid bug)
Yes, the hostname was Inwin as that particular system lives in an Inwin mini-ITX case. Changing the hostname of the system fixed it!

It's ok, I figured it out, the problem was that the roms where in folders. This thread can be closed. Thanks.

Hm, this is a RetroPie dedicated forum. You may want to try a forum for PS3 console owners ?

@jamesnj ...just getting back around to the forum.

Hmm, not sure why the override files in /opt/retropie/configs/atari5200 aren't working. They should be the last ones loaded.

Strange.............you could try looking at the runtime log in /dev/shm and see what Retroarch is loading (and in what order). If I remember right, the file is: runcommand.log

May not help since I’m using mine with Dolphin (not as a lightgun) and in x86 but maybe it’ll give you something to think about.

But I had to make a file called 51-gcadapter.rules and place it in /etc/udev/rules.d. The file contains the following

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="057e", ATTRS{idProduct}=="0337", MODE="0666" SUBSYSTEM=="hidraw", ATTRS{idVendor}=="057e", ATTRS{idProduct}=="0306", MODE="0666"

The usb device is for the GameCube controller adapter so you could ignore that. But the hidraw device is my dolphinbar which is what I had to do to get it to work with Dolphin.

Once again this was to get my wiimotes to work with Dolphin so may have absolutely nothing to do with a lightgun setup.

@rasp_renegade What are you using for an image ?