@sirhenrythe5th (…and others having issues with random custom splash screen videos)

After freshly upgrading to the latest retropi image on both my pi3b+ and my pi4, I ran into this issue again and had to add one more step.

After appending all the desired videos to the list (separate folders in the ‘opt/retropi/supplementary/splashscreen’ folder), disable the randomizer if it is already enabled, enable the randomizer, and select ‘Randomize /etc/splash screens.list’. Now when I reboot both the pi3 and pi4, a random splashscreen plays properly every time.

I did try this with the splash screens placed in /home/pi/retropie/splashscreens but could not get it to work reliably no matter what I did. This is likely due to me having retropie on an sdcard and roms on a usb drive… the usb is often not ready early enough in the boot process for the videos to work. No mods to autostart.sh etc worked either. If you are doing full usb boot, it will probably work keeping the videos in your home splashscreen folder (moving them to the opt supplementary folder is more work anyways).

@strohseph

I did the copy and paste from your entire list for the libretro cores.

It's kind of making a confusing mess of all things.

Is there a simple way to remove all of those symlinks?

I can use either PuTTy or WinSCP.

@sleve_mcdichael i did believe you i just wanted to know other opinions if anybody else could find another way of fixing it without having to start a new image, since theres no way other way around im giving up on this, thank you guys for the help!

@ama2021 said in Cloning SD card:

Win 32 Disk imager

Try Win 32 Disk imager to write it back. i do that and it work.

@rommell76 Ah, I didn't know that. Good to hear you did get it working, though.

@rasp_renegade thanks!

@silk You're using a very old RetroPie version. Use the latest image from retropie.org.uk/download.

@johnodon The driver status indicates that the game should be fully playable, however it doesn't prevent the possibility of regressions or other issues, that's your job as a user to report such issues to the emulator authors. Take the color/sound/graphics status in mame with a grain of salt, i know of several issues that i reported myself but it seems they weren't fixed nor had their status updated.

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