@mitu

This fixed the issue. I was under the false impression that a clean install from an imaged I downloaded would be the latest version.

Thank you for your help.

Press F4 in Emulation Station to go to the command console. Then enter:

sudo apt clean # clears the update cache sudo apt autoremove # removes installed packages that are no longer needed by other packages (so-called dependencies) exit # exits the console back to Emulation Station

@mitu Yes, it works with the select button, so it is fine, and defnitelly it does not worth to take so much of your time. Thank you very much for all that help.

All what I can say is for sure it used to work with the home button but since some update it stopped working anymore. I wonder if there is a difference between the xbox one controllers. The two controllers I have are the ones with the USB B connector, not the newest one with USB C.

But yes, I guess I can call it a day and use as it is. Thanks again!

I use a Pro Controller with the Pi thanks to those instructions. It works wired and wireless.

Did you have any error messages while installing either the HID module or the userspace driver?
How are the lights on the controller behaving when you connect the cable? Do they start blinking "side to side" quickly? If they do, did you press L + R to pair?

@vodkanakas I think the [A] means it's an alternative version

@sleve_mcdichael sorry yeah that's what I meant to ask but didn't word it properly lol I'll try this today and see how it goes, and I've no problem shaving a few GB off if it means saving my build lol

I have found the holy grail in this repo line:
https://github.com/meleu/RetroPie-joystick-selection/blob/master/jsfuncs.sh#L345

Basically in order to change the index, we should just edit /opt/retropie/configs/all/retroarch.cfg at this line:
input_player1_joypad_index = "some_index_number"

or whatever input player you want. NOTE: i didn't tested it yet, but this might work.

@louf Sorry for the late response, I am currently not maintaining Kodi packages since Kodi 19 does not support H265 HW video decoding on RPi 3/2, which are the ones that I still use for Kodi.
About your problem, I can't really tell, never happened to me and I never anyone complaining about something like that. Can you reproduce your problem and post a Kodi debug log? A photo/screenshot may also help.

Please provide some info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

An EmulationStation crash, as you're experience it, usually means the controllers are disconnecting during the initial scan. Are all joysticks plugged in directly into the Pi ? Are you using a good power source for the Pi ?

How exactly did you check the memory? Fake cards report a bigger size than they actually are. You'll only notice it after you write more than their actual size to them, as the exceeding data will be lost, often without any error messages if the fake card was done well.

If you can boot to RetroPie's command line, you can try to install the tool f3 and test the card with that:

sudo apt install f3 # install the tool cd # change to home directory makedir test # create a test directory f3write test # write 1 GB sized test files until the card is full f3read test # read the files' test patterns rm -r test # remove the test directory

It will test the actual amount of data that can successfully be written to the card and read again.

@ezra84 Not sure what error are you seeing. You should have deleted just the site from where you downloaded the image, not the rest. The post is ok now.

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