@BuZz Ok, so I tried it last night with my existing Pi3 image. It didn't make it past the 1st boot (kernel) screen. I got a number of error messages such as these: Recovery4.dat not found Recover.dat not found startup4.dat not found Error: 000044 Then there was another message stating that this Pi needs an updated version of the software. Is there a way to do the update of SD card offline by mounting it?

Get a SDcard testing tool (like H2testw or F3X) and check if your card is ok. If not, then you'll need a different SD card, otherwise try again to re-image. You can also have issues from the power supply - the 3B model needs a 5V, 2.5A power supply - if you're using a simple charger I strongly advise to get a proper one.

@fullauto2009 An upgrade in place is not recommended, as it's not supported even by Raspbian. Note that attractmode is not compatible yet with the Pi4.

Translated by google Thank you very much for the guidance, it is 0:15 am here (city of Cabo Frio RJ / Brazil), I am replying to you from an RPi4, tomorrow I will record a Retropie image on the sdcard to use on the RPi3 and try / study the guidelines ok? I'll be back here to post the results. . . Again, thank you very much for your attention. Muito obrigado pela orientação, são 0:15 hs aqui (cidade de Cabo Frio RJ / brasil ), estou te respondendo de um RPi4, amanha gravarei uma imagem do Retropie no sdcard para usar no RPi3 e tentar / estudar as orientações ok? Volto aqui para postar os resultados . . . Novamente, muito obrigado pela atenção.

@mitu Thank you. That's all I needed to know.

A lot of this functionality is built in eg. on your ubuntu machine sudo ./retropie_packages.sh crosscomp setup stretch then on the rpi3 just install distcc, configure it to use Ubuntu machine. for building: PATH="/usr/lib/distcc:$PATH" MAKEFLAGS="-j4 PATH=/usr/lib/distcc:$PATH" ./retropie_packages.sh etc note settings the PATH for makeflags is needed for some modules to use distcc. retropie also includes the facility to build raspberry pi binaries on an x86 Ubuntu machine using an emulated chroot and the distcc on the host. see the "builder" module.

@mitu Thanks for your reply. I finally figured it out the problem was PEBKAC!!! I had the joystick plugged into the wrong 5 pin port. I thought there was only the one and I was wrong. Totally my bad but thanks for the help. I'm going to leave this up since I could not find any solutions to this problem anywhere and it might help someone.

I'd love to be able to use the attractmode with OSMC, but I think it isn't possible I use OSMC for KODI and installed RetroPie via RetroSMC, which now works perfectly with Debian Stretch now that RetroPie has been worked on for Stretch I've even tried custom scripts I found that add the attract options to emulationstation so you can switch between the different modes via the emulationstation menu but that doesn't work either as the modes don't appear on the emulationstation menu. At least not with OSMC as no menu options appear and I've never seen the 'Configure Splashscreen' option either with OSMC

@mitu thank you!! Solved my issues!

@Impman66 how you set up your speedlink controller? I have SL-6566-BK xeox pro analog gamepad-wireless-black, retropie detected it but when i press&hold A to set up nothing happened.. please help

Solved. Had to access emulator settings for the one second the game was booting and disable "Fast Memory (Unstable)". Boots fine now.

@psw757 If you want to bypass the desktop, you can install the standalone version of Chromium from the RetroPie Extra Repository. Once it's installed, you can edit the chromium.sh script so that the last line reads: /usr/bin/chromium-browser iscored.info

Hi Clyde, Thanks for the reply. I've decided to test a few things out and see if I can get it going on my own. If I do, I'll post how I did it here. If not, I'll post the specific info you asked for above. Thanks again.

@rion Perfect! Now it works. Thank you. I recently faced crashes on Driver by select "Try Mission Again" after I fail a mission. Any idea how to fix that?

Thanks for that elaborate answer. I need to step through this now.

Ok so I hooked the pi up to a wired connection this morning. I continued my testing with Fable and was able to play this morning for about an hour with no problems even with Netflix going in another room. Later tonight I'm going to change the moonlight launcher script I wrote to see how it runs at a full 60fps rather than the 30fps I started testing at. Over all I'm very impressed with it.

Yup confirmed, it was rumble. After turning off rumble in game's option no more issue.

I have sorted it, anyone else with the same problem needs to do the following: sudo nano /boot/config.txt And scroll down to the bottom. If you see a line that says: dtparam=audio=on Disable it by putting a # in front. Then add: dtoverlay=hifiberry-dacplus on the next line. Save the file. Next create /etc/asound.conf with the following content: pcm.!default { type hw card 0 } ctl.!default { type hw card 0 } Then go to: /home/pi/.reicast/emulators.cfg and change it to this: reicast-audio-alsa = "CON:/opt/retropie/emulators/reicast/bin/reicast.sh alsa %ROM%" default = "reicast-audio-alsa" reicast-audio-oss = "CON:/opt/retropie/emulators/reicast/bin/reicast.sh oss %ROM%" Save and reboot and enjoy! Also has anyone managed to get reicast to change to 16:9 aspect ratios? maybe i'll start a new topic for this.

Why didn't you install RetroPie on the PiDrive? All you need to do is install BerryBoot on the SD card, add the retropie image to the USB drive and install it via BerryBoot.