Still looking for a solution on this issue if anyone has any advice.

@bdpyle Word of advice - don't use 'Reset Configuration' in RetroArch, the defaults it creates are not best suited for a Pi/RetroPie installation.

@bdpyle duplicate of https://retropie.org.uk/forum/topic/31061/psx-and-psp-games-won-t-start-after-adjusting-retroarch-settings ?

@br23z please fill out https://retropie.org.uk/forum/topic/3/read-this-first

including relevant config files (/opt/retropie/configs/all/retroarch.cfg and the one for the system in question) and verbose log.

@mitu I just want to confirm that everything has worked perfectly now, just some minor things that will require manual tweaking, but overall, everything worked and managed to scrape everything nicely.

Thanks mitu and sleve_mcdichael

I ended up just using the rsync command from my first post.

I didn’t expect it to work but, Everything seems to be back to normal now.

Although I didn’t know I could merely just reinstall the RetroPie manager.

Thanks @mitu!

@rip I had the very same issue and could not find any good solution posted already so I will post mine here (Z button was never an issue for me , Z button is also my hotkey)

Once configured as screenshot above and after first launch with n64 emu the following configuration was generated into /opt/retropie/configs/n64/InputAutoCfg.ini

; SWITCH CO.,LTD. Controller (Dinput)_START [SWITCH CO.,LTD. Controller (Dinput)] plugged = True plugin = 2 mouse = False AnalogDeadzone = 4096,4096 AnalogPeak = 32768,32768 Mempak switch = Rumblepak switch = C Button U = button(9) L Trig = button(4) C Button D = button(1) button(0) #C Down gets mapped to button(1) which is really B Button and button(0) is the actual C Down button DPad U = hat(0 Up) DPad L = hat(0 Left) C Button L = button(3) Y Axis = axis(1-,1+) X Axis = axis(0-,0+) DPad R = hat(0 Right) Z Trig = button(6) C Button R = button(8) R Trig = button(5) DPad D = hat(0 Down) Start = button(12) A Button = button(2) # Lack of mapping for button B at all ; SWITCH CO.,LTD. Controller (Dinput)_END

I then used jtest to actually view which button was what hence my conclusions above with jstest /dev/input/js0 then I edited the file nano /opt/retropie/configs/n64/InputAutoCfg.ini with the following

; SWITCH CO.,LTD. Controller (Dinput)_START [SWITCH CO.,LTD. Controller (Dinput)] plugged = True plugin = 2 mouse = False AnalogDeadzone = 4096,4096 AnalogPeak = 32768,32768 Mempak switch = Rumblepak switch = C Button U = button(9) L Trig = button(4) C Button D = button(0) DPad U = hat(0 Up) DPad L = hat(0 Left) C Button L = button(3) Y Axis = axis(1-,1+) X Axis = axis(0-,0+) DPad R = hat(0 Right) Z Trig = button(6) C Button R = button(8) R Trig = button(5) DPad D = hat(0 Down) Start = button(12) A Button = button(1) B Button = button(2) ; SWITCH CO.,LTD. Controller (Dinput)_END

Hope this might help someone else with same setup, cheers

/a

I fixed it, but it is very weird. I connected it to another monitor, standard office FHD, 60Hz monitor and it now works (only on that monitor), it also works on out TV, which is 4K, 120Hz. I don't really understand, what's going on, that it doesn't work especially on my monitor (1440p, 165Hz).
Pls devs, fix it =)

For more information on supported chipsets:
https://wiki.debian.org/WiFi

For more information about supported brands and models (linked also from above site):
http://linux-wless.passys.nl/query_hostif.php?hostif=USB

TL;DR chipsets Ralink, Atheros, Atmel, Prism are mostly well supported. Realtek: depends on model, to be avoided: Broadcom. But do search the internet about Linux compliance before buying a specific model.

I use a Netgear A6210 (USB ID 0846:9053) which depends on firmware mediatek/mt7662u.bin. Listed here as mt76 flavor: https://en.wikipedia.org/wiki/Comparison_of_open-source_wireless_drivers (this is also the most accurate list to my knowledge)
Depending on which model you pick, you will have to install the package firmware-linux-nonfree, see also first link above.

HTH

@mitu Thank you so much! I'll check this out the next chance I get.

@pinokiooo do you mean to "double click" the input combo or using 2 controller devices as a combo?

Just in case anybody has the same issue, been able to solve it by:

checking that when the BIOS directory was set, the game wasn't loading. Removing it made the games load, with the warning about setting BIOS directory; went to the BIOS directory and realized that I was so lazy that I had like 20 repeated PSX BIOSes, removing them and leaving only the ones expected by the core did the trick.

Now I am able of reducing by 10 GB my PSX set and enjoying Retroachievements for PSX !

Thanks a lot, @mitu ! =)

This is still somewhat confusing as it has you editing files that may not even exist and aren't accessible by the default samba shares. Also, leaving out that chmod step was very bad. I may need to write my own better guide if nobody else has made a simple one.

Anyway, I did this over ssh to make es_systems.cfg accessible so I could open it in Notepad++ on Windows

sudo cp /etc/emulationstation/es_systems.cfg /opt/retropie/configs/all/emulationstation/

I also had to do

sudo chmod -R 0777 /opt/retropie/configs/all/emulationstation/es_systems.cfg

in order to allow me to edit it. This is not easy stuff for dum-dums. It needs a script really. People who just want to play Pico-8 games cannot understand all this arcane wizardry.

Also had to switch to using pico8_dyn

I shouldn't have to choose between running the pico8 cartridge directly versus running splore. I should be able to do either one, anytime. How do I fix this?

(later edit) More recent guide here: https://retropie.org.uk/forum/topic/30736/how-to-install-pico-8-on-a-raspberry-pi-3-or-4-for-dummies-2021-version?_=1627524066426

To anyone having the same issue, I needed to cut the HSYNC trace on the vga666 board for the csync to be strong enough to control the PVM

@mitu Oh, gotcha. I'll try that out.

@hellothere I guess that the usb drive is formatted with a file system that doesn't support Linux file ownership, e.g. FAT32, exFAT, NTFS or the like. Hence the errors when mvtries to transfer the files' ownership to the new location, and maybe also the nonresponsive controls, as the ownership might be important for some of the files or directories in /opt.

You can check the file system with this command:

df -T | grep usb2

(df -T lists all mounted file systems, and grepfilters its output to just the lines that contain usb2.)