@hojo215
I know this is an old topic but I'm having exactly the same problem with reicast with exactly the same NUC and graphics, I'm running Ubuntu 18.04 and Retropie. I've tried to follow your instructions but am struggling. should I:

remove reicast using the retropie interface remove 20-intel.conf if it exists reboot Set HAVE_GL3 to 1 ?? someplace? reboot reinstall reicast, load the bios files in the BIOS folder reboot profit?

@mitu YOU DID IT! I LOVE YOU!!!!
donated

@mitu said in How to boot from USB pendrive:

@pscotto1234 said in How to boot from USB pendrive:

distro Android based on te USB pendrive.

I'm not sure how that works or if the bootloder on the EEPROM supports booting an Android image directly. Does the image work if you boot it from the sdcard ?

Yes, it boots fine.

@folly Will do!

@luedi thanks for suggesting this, will try it out when there is time... :)

@mitu

yes, I'm scammed.
I clearly ordered a 3b+ model and got a b+ model.
I'm sorry for bothering you with this stupid mistake.

Thanks for the help!

RetroPie - on the Pi models - doesn't use the desktop at all and it runs as a dedicated application (EmulationStation) from the console. If you want to use your Pi4 as a desktop enabled computer, perhaps it would be better to use Raspberry Pi OS and install the same emulators that RetroPie uses and run them standalone.
You can start RetroPie from the desktop environment, but it's not a supported configuration and not something we recommend.

I think this was fixed a couple of weeks ago in the dev branch of EmulationStation, make sure you're using the latest version by updating from source.

Or, if you need Windows compatibility without third-party drivers, use NTFS or ExFAT. Both are better than FAT32 and can be used out of the box in Windows and RetroPie.

Which features do you need the FS to have exactly?

@greenhawk84 advmame is usually the best choice for ST-V (sega saturn arcade) games on rpi.

@x20011I got that message the first time I tried to install desktop, pixel or the raspberry OS or whatever you want to call it, from retropie.
Fixed by re-burning the retopie image, Installing the Safe Shutdown and OSD Software on the PiBoy DMG.
After this I installed pixel and it worked.
But all this in my model 4.

@pscotto1234 said in Bluetooth RetroPie Setup Script Issues:

@spaceace said in Bluetooth RetroPie Setup Script Issues:

Hi, All.

Thank you for this thread. I found it AFTER I clicked the button to order my controller! I now have the 8BitDo SN30 Pro+ controller working flawlessly on a Raspberry Pi 4B, with RetroPie 4.7.1 on updated OS.

Before I attempted to pair, the pad was connected via USB to the Ultimate Software application for a firmware update. I also configured a Switch profile, with star(★) as turbo button.

I followed these steps before pairing, too. I consider these safe steps, as it only disables an unused SIM card driver and delays bluetooth start for two seconds at boot.

So, then...
$ sudo nano /lib/systemd/system/bluetooth.service
$ sudo nano /lib/systemd/system/bthelper@.service
$ sudo rm /etc/udev/rules.d/99-bluetooth.rules
$ sudo reboot
$ sudo /home/pi/RetroPie-Setup/retropie_setup.sh
Configuration / Tools -> bluetooth
hack OFF
power on controller by holding Y + start one second (Switch mode)
hold in pair button for three seconds
leds will rotate like knight rider
Register and Connect to Bluetooth Device
on "Searching" screen, pressing some buttons can help
choose "Pro Controller"
DisplayYesNo
Setup the udev rule
hold start three seconds to turn pad off
reboot
turn on controller
configure input
GOOD

I have the pad in Switch mode. To select the profile with turbo, press both sticks (L3+R3) and the heart/home button will light up. Hold a button and press star(★) to enable/disable turbo. It will stay in Switch mode with profile, so now all you have to do is hold the start button to turn it on or off.

Hope that helps. Cheers.

It works fine Smith DS4. Later I'll give it a try using a sixaxis controller.
@spaceace thank you so much!!!

Sixaxis works as well!!!

@alphabetapie I'm glad that worked out c:

Finally fixed this, and just in case anyone has a similar unconventional setup and the same problems, the solution was, on the pi, edit /etc/pulse/default.pa and change:

load-module module-udev-detect tsched=0

to

load-module module-udev-detect

@alphabetapie possible, the chd is a compressed file. It might take a tad longer to start streaming the CDDA. I have no experience with Chd, so no idea.
You can also put all the bin files with the cue in the main psx rom folder. Emulation station only looks for cue files, so the bin files don’t slow up.

@mitu Found it, and it works. Now I just have to locate the option to save this config for each individual game instead of every game...

@sleve_mcdichael said in 1on1 PSX Background issues:

@adambegood just so I understand...the solution was "fix the code and recompile your emulator from source" or am I reading that wrong?

Yep, change Line 35 of the scriptmodule to BUILTIN_GPU=unai and then Update from Source. Let me know if you need more detail on how to do that, I am no pro but could just about manage this!

@studboy1114 did you get it working already? interested in some old school gaming with modern day controllers (sturdy is key). Thanks for any info

@liveforeva it's generally best to start a new topic and not to resurrect ancient threads. However, you should take a look at this thread for the latest info for running SORR on retropie. I believe the vsync option works correctly now with the latest version of SORR but the fkms drivers on the raspberry pi 4 also seem to have some issues with screen tearing.
https://retropie.org.uk/forum/topic/23516/streets-of-rage-remake-latest-retropie-2019/100?_=1619185347574