Thank you for the replies....it was one game so I decided to just start from my last game save and catch up to where I was...

@quicksilver oops! Yeah I certainly wasnt trying to tell you that. 😂

@goobatroopa It is in the updated core.
"Quick Menu" - "Options"(/"Core Options"; if they were frugal about labeling settings). "PSX cpu clock (default 57)"

@echotech26 probably wrong romset. You need to read through the arcade documentation.

I remember a topic a month ago with a similar problem - the pairing of Xbox controllers worked, but they acted as a single controller. The solution was to install an alternate driver for the controller - xpadneo (https://github.com/atar-axis/xpadneo).
If you want to give it a try, the installation is quite easy:

Remove any Bluetooth controller from the RetroPie script Bluetooth configuration. Remove the xpad driver from the RetroPie setup script, from the drivers package section. Install xpadneo (run this from the SSH session): git clone https://github.com/atar-axis/xpadneo.git cd xpadneo sudo ./install Reboot and then redo the Bluetooth pairing for the controllers.

See if you get 3 devices (/dev/input/event[0-2]) and Emulationstation detects all your controllers after the installation.

Sadly, not as cut and dried as hoped. I thought I'd bite the bullet and unpair my watch, but try as I might it didn't make a difference.

Boo.

I updated to version 4.4. from 4.1 aswell and i have the same problem.
Sometimes when a game starts (every emulator) i must wait 10-20 seconds before the controller responds
(for example "press START to start Tetris or Super Mario Land").
But the green text, that appears when i start a game, on the botton left appears and says "Controller Xbox 360 worked".

Sometimes the controller doesn't work in a game.
On 4.1 everything was fine.
Thats probably the same problem that FuerDrauka has.

I dont belive that we are the only ones with this problem, that must be an update issue and i dont know how to solve this.
I reinstall the xbox driver but nothing helps.
Maybe someone has a solution sometimes.

Now i'll create a new partition and reinstall 4.1

@Efriim yes that is where it goes. You change the line to:

emulationstation --no-splash #auto

@SmackAttack86 Please add more info about your system, as requested in https://retropie.org.uk/forum/topic/3/read-this-first.

EDIT: make sure the usbromservice is installed, on a PC is no longer installed automatically, you need to install it first from the optional packages section.

Thank you @mitu for all help. I almost finish my image from other posts you helped me to solve. In the case of the game pads I write a solution worked for me, just in case someone is lost and can be useful. This is the solution:

Finally I could make work two 8bitdo SN30 Pro 2 game pads. I used the firmware V1.2 and worked pretty with this same technique. However, I wanted to try with the latest V1.3 firmware to see what happens and I could make work. Fighting with the retro arena setup and also retropie setup both versions in the bluetooth script, it just worked for me the first time and after the first time is impossible, at least for me, to pair again by the horrible error Already exists bluez.org. Something is stored in the cache or somewhere after the first pairing but I could not find information in any place. Most of posts run from a real solution and they mention “my solution was begin with a fresh image and problem solved”. I made that but if you have a mistake, like in my case, is an endless loop over and over again and no solution. Then this is what I did:

First I made a copy, to have safe the original file “/etc/dbus-1/system.d/bluetooth.conf”. Then I replaced that file with this:

https://pastebin.com/LufCYWy9

Then I made this procedure to pair:

1.-sudo service bluetooth restart

2.-agent on

3-power on

4.-scan on

5.-scan off

6.-pair “mac address of the gamepad”

7.-connect “mac address of the gamepad”

At this is step it will pair although and is possible it can says cannot connect. No matter this is not a thing to be afraid. If it doesn’t connect or says fail to connect in specific: Turn OFF if it is ON the game pad. Turn ON again normally the game pad and type again step 7 (connect with the mac address command).

It can says a couple (2 or 3) times is not possible connect but no matter it will do. Simply is turn OFF the game pad and ON again and give the “connect” command again. Once say successfully connected is give this command:

8.-trust “mac address of the gamepad”

9.-Return the original file “/etc/dbus-1/system.d/bluetooth.conf”, deleting the one of pastebin above described. Just in case. I used the pastebin temporary just to pair, after pair there is no sense to keep it.

If in the step 6 of pairing says already exists bluez.org or simply never connected in step 7 then is type first to see the devices paired:

devices

After that is check if i there the game pad. If it’s there then is give now:

remove “mac address of the gamepad”

One is successfully removed is back to step 5.

Once is paired, and connected, because It will pair for sure, also will be detected ALL the buttons by emulation station. I have two gamepads and both were detected including after reboot and latest firmware. I tested this like 10 times to be sure, including making tests downgrading and upgrading firmware in the game pads and always worked at the end. I write this just in case someone has a problem as me and want time and loss time beginning from fresh image and is wanted to save time.

The error is no longer showing up.

@Efriim said in Error when starting netplay host:

@saccublenda
Perhaps there is the same setting somewhere within retroarch.

Indeed there is. Under Settings -> User -> Username (it sets the "netplay_nickname" in
retroarch.cfg). With this matching the hostname I can start the netplay host from retroarch menu.

It is a peculiar thing, I remember it working without configuration, I had a hostname so I don't really understand it.

Same here. I used to have a netplay nickname different from the hostname, and it didn't matter. Weird.

These are the installation steps for the program I'm using (different from mpg123):

Press F4 in emulationstation and type the following:
sudo apt-get install python-pygame
(You’ll need to type “y” when prompted)
mkdir -p ~/PyScripts
wget -O ~/PyScripts/bgmusic.py http://pastebin.com/raw/KpUaZuSz
sudo nano /etc/rc.local
Insert “(sudo python /home/pi/PyScripts/bgmusic.py) &” (without quotes) on any line before the “exit 0” line
Press Ctrl+o, Enter, then Ctrl+x to save changes and exit the editor
Connect through Windows to \retropie\roms\ and create a folder called “music”. Place your mp3s in there.
If you want to edit the script you can use this command to edit:
nano ~/PyScripts/bgmusic.py
When finished you can press Ctrl+o, Enter, then Ctrl+x to save and exit.

(In the file called bgmusic.py there is a list of emulator names. A few are missing (for example the PSP emulator). This means that the music does not stop playing when starting a game in such an emulator. But that is solved easily by adding the name of the emulator to the file. To find out the name of an emulator, start a game in the specific emulator, then open Winscp (or a similar program) on your computer, connect to the Pi, open a terminal and type 'ps -A'. With this command you see all the processes running on the Pi. )

It's a very nice little program. Music plays randomly and it fades in and out in between games and, in the bgmusic.py file, you can set a song that always plays when booting the Pi (I'm using the PS1 intro music)

It worked, Thankyou

Well I found a sollution from 2016 that worked for me, in this example it´s the snes that made trouble but it works for other emulators too

BuZz ADMINISTRATORS 24 Aug 2016, 17:19
@Robust

Please try the following.

From a terminal please do rm /opt/retropie/configs/snes/retroarch.cfg or delete the file over windows networking
Go to Emulation Station -> RetroPie and do Update RetroPie-Setup script
Go to Manage Packages -> Main section > lr-snes9x-next - and choose "Update from binary"
and all should be good.

No, you don't need to format the card before installing RetroPie.

@dankcushions said in Any Difference in performance using 0/1 img on Pi 3B+:

another issue is compiler flags. the 0/1 have a different generation of ARM cpu, without some of the features of the 2/3, so they have binaries compiled without these features that would presumably run less efficiently on a 2/3 than with the right flags.

That is perhaps the strongest argument to use the correct image for your device. For example, the Raspberry Pi 0/1 does not support NEON instructions, which are used by many emulators for speed. The Raspberry Pi 2/3 does have NEON and also have a different processor with faster instructions. All of that can only be taken advantage of if the binaries are compiled for them. Running a RPI0/1 image on an RPI2/3 basically does not take advantage of any of these optimisations and will just underuse the better aspects of these devices.

@Efriim thanks for that info, i'll try it when i get back home later.
i'll report back.

@davidgrohl

Learn how to use SFTP or Samba-Shares.
https://retropie.org.uk/docs/Transferring-Roms/#sftp
https://retropie.org.uk/docs/Transferring-Roms/#samba-shares If using SFTP, go to /opt/retropie/configs/all/atari5200/retroarch.cfg, or if using Samba-Shares, go to configs/all/atari5200/retroarch.cfg. Add core_options_path = "/opt/retropie/configs/atari5200/retroarch-core-options.cfg" to the retroarch.cfg above the #include "/opt/retropie/configs/all/retroarch.cfg" line.