gone completely

Remove package retropiemenuunder "core packages" in the retropie-setup utility.

Remove directory ~/.emulationstation/gamelists/retropie and everything in it.

Remove directory ~/RetroPie/retropiemenu and everything in it.

Edit /etc/emulationstation/es_systems.cfg and remove the "RetroPie" system entry:

<system> <name>retropie</name> <fullname>RetroPie</fullname> <path>/home/pi/RetroPie/retropiemenu</path> <extension>.rp .sh</extension> <command>sudo /home/pi/RetroPie-Setup/retropie_packages.sh retropiemenu launch %ROM% &lt;/dev/tty &gt;/dev/tty</command> <platform/> <theme>retropie</theme> </system>

If you have one at ~/.emulationstation/es_systems.cfg, make the same edit there.

I think that should about cover it? Now...

hoykey for retroarch

Edit your autoconfig file for your gamepad(s) at /opt/retropie/configs/all/retroarch/autoconfig/[gamepad device ID].cfg and remove all lines that look like these (your values will differ, and it may say axis where this says btn or vice-versa):

input_menu_toggle_btn = "3" input_reset_btn = "0" input_save_state_btn = "5" input_load_state_btn = "4" input_state_slot_decrease_axis = "-0" input_state_slot_increase_axis = "+0"

(Probably leave "enable_hotkey" and "exit_emulator" intact, or your players won't be able to quit, or will quit every time they hit Start.)

Use triggerhappy - https://github.com/wertarbyte/triggerhappy - it's already included in RasPI OS and you can just attach your PWM control scripts without having to deal with input processing.

@mitu Hi

Sorry for my late reply

In the reality I don't know how i solved it

but after many test i just update retropie and the error disappeared by himself ---

Mistery of the life :-D

Good day. After troubleshooting everything including the motherboard and usb cables I found out from the seller that the Dragonwise controllers will not work with the PI 4. FInd this odd, but that is what they said Only PI 3. Does anyone know of controllers you could recommend that are known to work with the PI 4? Tried every search combination but not finding any specifically stating they will work. Would appreciate any help.

@mitu I apologize for my lack of knowledge on this one. This must have happened when I loaded and compiled the MESS group of emulators, or when I added the Singe extension to Daphne.

At least now I know what's been causing me all the headaches. I didn't know there would be a difference in the two. The goal was to get as many emus working on my system...but obviously that created a small snafu I wasn't aware of.

So fixing this... I'll go through the RetroPie Setup repository and hopefully get back on track.

Thanks again for your help. Wow... I guess I really need to be more careful when I play around with all these fantastic emulators.

UPDATE: all is working great. I'm on the right repository, DosBox-Staging 77.1 is loaded and all is good. This can be closed.

@sleve_mcdichael said in N64 Controller Input Config:

The autoconfig only works for libretro cores;

Actually, the auto-config works for a few other emulators also, including Mupen64Plus (see here).

@Jay420 Please provide the info requested in https://retropie.org.uk/forum/topic/3/read-this-first, which should include the emulator you're using and what controller type do you have.

@colossal I think I figured it out. My retropie menu had all the folders listed as a <game> entry. I changed those to <folder> entry and now it works without an issue.

@iandaemon said in Do 3rd party joy cons work with Retropie ?:

They're just bluetooth controllers, right?

Yes.
If the wireless signal is exactly the same as the official Joy Cons,
then it should work, I suppose.
But no way to know for sure, unless someone has tried it before.

@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.