@mitu That worked perfectly - thanks!!

@mitu ah ok good to know. I ended up using luma oled drivers that dont depend on the adafruit driver and they are working out nicely as screensavers for the oled screen. I will eventually have to revisit this issue because of the plans i have for the project but this has been very helpful. I now need to figure out how to launch a clear command for the screen just before shutdown to prevent burn in. The script i originally needed help with launches shut off commands for the multiple led hats and devices when the screensaver starts , including a 30min auto shutdown command. But when the pi shuts down though the oled keeps the pixels it was displaying last so lets hope the service im going to write works. Again thank you for your help as always

found...)

Can you do this with autostart.sh?

/opt/retropie/configs/all/autostart.sh:

emulationstation #auto

As a quick test I added an "echo" command so the file now reads:

emulationstation #auto echo Are you there?

Then I pressed ctrl-D to start EmulationStation and quit with F4. The terminal asked "Are you there?" before displaying the retropie_welcome message and command prompt.

Note: this worked when using any of ctrl-D, exit, or logout to end the current bash login and call the autostart script. It did not work when just running the emulationstation command by itself.

So I think if, instead of an "echo" command, you used the startx (start the desktop) command, it might do what you want? Boots to EmulationStation on login and then, when ES quits, go to the desktop.

/opt/retropie/configs/all/autostart.sh:

emulationstation #auto startx

After trial & error, I have pcsx2 libretro core up and running on Ubuntu 20.04
Hopefully somebody can turn this chaos into an unofficial script.
Keep in mind that I'm rusty with retropie configs.

Okay so.. Here we go.

sudo apt remove gcc-9 g++-9 sudo apt install cmake g++-10-multilib libaio-dev libasound2-dev libcairo2-dev libegl-dev \ libegl1-mesa-dev libgdk-pixbuf2.0-dev libgirepository-1.0-1 libgl-dev libgl1-mesa-dev \ libgl1-mesa-dri libgles-dev libgles-dev libgles2-mesa-dev libglib2.0-dev libglu1-mesa-dev \ libglu1-mesa libglvnd-dev libglx-dev libglx-mesa0 libglx0 libgtk-3-dev libgtk2.0-dev \ libharfbuzz-dev libllvm10 liblzma-dev libpango1.0-dev libpcap0.8-dev libpulse-dev \ libsdl2-dev libsamplerate0-dev libsoundtouch-dev libwxgtk3.0-gtk3-0v5 libwxgtk3.0-gtk3-dev \ libx11-xcb-dev libxext-dev libxft-dev libxml2-dev portaudio19-dev zlib1g-dev ccache sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-10 10 sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-10 10 sudo update-alternatives --install /usr/bin/cc cc /usr/bin/gcc 30 sudo update-alternatives --install /usr/bin/c++ c++ /usr/bin/g++ 30 git clone https://github.com/libretro/pcsx2.git && cd pcsx2 && mkdir build && cd build cmake .. -Wno-dev cmake .. -DLIBRETRO=ON -DCMAKE_BUILD_TYPE=Release make -j$(nproc) cd ../bin

If everything goes right, there should be a "pcsx2" folder in the "bin" folder of the root folder.

Make a "lr-pcsx2" folder in "opt/retropie/libretrocores" and move the "pcsx2_libretro.so" into it.

pcsx2-libretros bios seem to be hardcoded to one spot.. otherwise segmentation fault.

Make a "pcsx2" folder in "Home/Retropie/BIOS" and move the "pcsx2" folder from the "bin" folder into it.

Yeah its weird.. the folder tree should look like:

"Home/Retropie/BIOS/pcsx2/pcsx2/bios"

And of course have all your ps2 bios files in that last folder.

Now if you have pcsx2 stand alone installed..

Go into "opt/retropie/configs/ps2" folders, otherwise make one.

Edit your "emulators.cfg" and paste this:

lr-pcsx2 = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-pcsx2/pcsx2_libretro.so --config /opt/retropie/configs/ps2/retroarch.cfg %ROM%"

Make a "retroarch.cfg" and paste this:

system_directory = "~/RetroPie/BIOS/pcsx2"

Now load a ps2 game, be sure to set your runcommand to "lr-pcsx2" and cross fingers.

gcc-9 will be installed whenever you update your retropie emu's.
So you have to go through the compiling procedures above any time you want to update pcsx2-libretro.
Actually after a few times it seems gcc-9 and gcc-10 are installed.

Keep in mind these are alpha builds and purely x64 so no software mode.

Edit your es_systems.cfg to accept .chd in the ps2 section.

If someone can make an unofficial script out of this. It would be appreciated.

@nullfx said in Ipega 9083S Blutooth Controller with RetroPie 4.5:

I know this is way late, but I actually found a way to use the Ipega 9083S on my Raspberry Pi 4 running Retroarch. After the initial Bluetooth setup, manage your drivers and install the sixaxis driver. When that finishes, go to the configuration that shows up and enable third party controllers. Worked like a charm for me.

Also late to the party, but I'm making a Pi 4B powered handheld
and wanted to use this controller for my project.
But before I buy this controller, I wanted to be sure if it would work.

So as long as I install the sixaxis driver, this Android only controller will definitely work ?

Thanks in advance.

@brutaljess sorry we dont support other party images. if recalbox has a forum try asking there.

@unknown nah the memory is emulated, don't think a proper emulator could read the data from a real memory card; that would be cool though.

Thanks for your responses.

@sirhenrythe5th said in Command to edit file permissions (solved):

run into another issue: when i change settings (language, continues) in the atomiswave-servicemenu and push "save & exit"

I mean, yeah. You've just made the nvram read-only, and now you're trying to save changes to it. That ain't gonna work. You'd have to do all that before you locked the file, while it was still writable.

Oops! Missed the part where you said it even happens without changing the permissions.

@greenhawk84
I remember reading in the github page somewhere there was an update involving the joy2key package and you may need to manually update this package.

EDIT: Found the related thread:
https://retropie.org.uk/forum/topic/31092/controller-no-longer-works-in-retropie-setup-launching-menu-es-themes

@soogs retropie on pi is not supported within any desktop - only running from raspberry pi os command line, with the desktop not running.

@twalls

Hello....
Your thread is probably one of the closest that I can find online for my issue. Any help would be great...

I've built 20 or so arcade 1ups with raspberry pi 3b+ and ran into this problem on the latest NBA Jam build with 4 players. Probably 50% of the time the arcade boots I get a message directly after the emulators load (right when it says done) that emulation station crashed. Talks about changing the theme and if it's the first time loading retropie, etc. Screenshot_20210917-210224_Photos.jpg

I use the same image for every one of my arcades, 4 player and 2 player and have never ran into this problem. I've changed out everything....usb cables, encoders, raspberry pi, surge protector, tried a different outlet, changed the theme, etc. Nothing helps. Sometimes it boots normal and perfectly, but I'd say half the time I get the crashed message. I've tried doing one encoder/joystick at a time and it works fine...all the way up to 3 encoders/joysticks, but when 4 are connected that's when it randomly does it. I've noticed that after I turn on and one of the encoders flashes (red light) instead of staying on is when this happens. And it's random each time of which encoder flashes. Like I've said though, I changed out all the encoders, cables, pi, surge protector. I'm at a loss here and is driving me crazy. Any help would be greatly appreciated. Thanks in advance!

@exarkuniv , sounds good…thanks.

@yarongo said in Pi3B, Xbox Wireless Controller not connecting:

A few questions to @mitu :

Should I uninstall xpad driver first?

No, it's not needed.

Should I install xpadneo directly from Github and not via the menu?

You can try, but the menu installation pulls the latest release tag from the xpadneo Github repository anyway, so I don't think it will make a difference.

@sleve_mcdichael should be fixed now, thanks again for reporting.

@mtlhd1011 said in Psx emulator controls not working:

@dankcushions I can understand that. Maybe a link to the bios section after mentioning it briefly in the first installation section would be helpful I think, kind of like it does with the roms. I didn't realize the bios were proprietary as well, so mentioning that somewhere would help first timers like me understand that better too I think. Thanks for the info, I saw the location section but thought maybe it was something that has to be installed as a program (thinking computer bios) vs. a file drop. I'll see if I can find it and get it going.

I also have an additional question related to my new install. I have one of those nespi+ cases with the fan on it. I was reading their scripts don't work right anymore with the new version of RetroPie. Is that true? I saw someone made a work around with some generic code, but I don't understand it fully.

Update on this, I copied over the bios for each of the emulators that were on my machine previously. Once I did that it broke my PSX emulator again. What I found was that there were a few bios on there that were not supported by the version of the rearmed emulator it currently uses. So I think it picked a bad bios which broke functionality. Once I pulled those unsupported bios from the folder, it functions normally once again. This must've been what happened when I updated my system previously. I also see commodore 64 is broken currently too, probably the same thing there I'll need to dig into. I did manage to get the nespi-case script installed also, I will monitor it to see if that portion has issues.

@dankcushions As it turns out, it was looking for a specific file from a secondary Shock Troopers ROM. Not much to say beyond, "I didn't do my due diligence." The filename in the verbose log was so similar to one already in the ROM that I didn't realize it was actually missing. Also new to me is a Neo Geo game requiring a secondary file. I've dealt with parent and clone ROMs in the past, and even have experience with CHD's and secondary files with CP System III stuff, but this was a new one for me.

I appreciate the confirmation that I had it wrong. Between that and Googling the crc I was able to find the missing file and get this running.