@shavecat said in Raspberry PI4 Couple of Q ?....:

"You can backup ROMs and configs and copy them back. It's not a long process really.

"
Will take a couple of good hours or more .....

It depends on your setup and how you want to do it.
-If you have a linux machine then you can just plug the sdcard into your computer and copy them over at USB 3.X speeds.
-If you keep your roms/settings on an external usb drive (this is how I do it), then you can just unplug the usb stick/hdd/ssd and plug them into another computer to copy/backup.
-If you are going over the network through something like WinSCP, then yes, that is painfully slow. Ethernet connections on both the pc and Pi make this a more tolerable experience.

You can also follow this guide:

https://retropie.org.uk/docs/Running-ROMs-from-a-USB-drive/

This is meant to set you up to run roms externally, but it will also copy your entire Retropie folder to the usb drive. Then just unplug it after it is done and plug it into a computer to copy over. Just make sure to preformat the drive to be readable by whatever OS you plan on reading it.

Hope this helps a little.

Yes, after comparing the SNES bezels *.png names with all SNES roms and swapping the roms with the correct versions I also realized the bezels are about 95% for USA versions and rarely for Europe or Japan versions of games.
Thanks!

I think that's because the 1 PS4 controller appears to generate 2 input devices, so the numbering is skewed. Try the workaround proposed here.

The file should be /opt/retropie/configs/all/emulators.cfg - if you've chosen from the Runcommand launch menu an emulator for a ROM, then this is where the association is saved.

Its not removing any configuration the devices are named the same what you need to to is wire them up the same and you only need to set it one time will work for both players as its configured per device.

@Clyde @mitu thank you for the help i really appreciate the feedback and found a solution that seems to be working. For my computer i use a small booster and so i tried putting it on the 2gb_EXT as a test last night, i just woke up and started using and having my phone as a wifi monitor and so far no disconnects.

Copy that. Thanks anyways, appreciate the response.

@F4CEpa1m your retropie is out of date. Did you update? You probably need to start from a 4.5.x image.

Hard to advise without details of your setup.

Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

Ok so a Xbox /Playstation type of control, got it. Thanks guys

@dmmarti Bah. Thanks for the info.

I don't know how the video describes the installation, you can try ask the author of the video for guidance.
If you'd like to the try the on-going development branch for PI4 managed by RetroPie, then you'd need to perform a manual installation using a Raspbian Lite image and the fkms_rpi4 branch of the RetroPie repository. You'll need to use the command line to do that, so if you're not familiar or comfortable doing that, then you should just wait until a Pi4 supported image will be released.

It is Pi 3 b+ and RetroPie 4.5.3 (according to RetroPie Setup Script).

TLDR; -- map your USB encoder to match USB console pads

REYANN ENCODER appears to work best as
0:B, 1:A, 2:R1, 3:Y, 4:X, 5: L1, 6: L2, 7:R2, 8:SELECT, 9: START

Did some more work with this. The joysticks work great when (when mapping of multiple are the same - as discussed). There was an issue where I started to need to remap per system if I was using USB console-like controllers.

It started out to be fine, then started to become a pain - especially once I found and started to use this GEM by @meleu
https://retropie.org.uk/forum/topic/740/having-more-than-one-player-1/18

Since one set was remap, and the other wasnt, the graceful fallback didnt work.

I rewired the USB encoder pins and its all working great. PIN:BUTTON layout at the top. LOVE I

@quicksilver Thank you very much and have a great weekend.

If it's a generic USB Xbox clone, then it should be handled by the xpad driver. Can you run - from the command line - cat /proc/bus/input/devices and then post the output ?

Thank you @mitu

That worked, I needed to throw in a --disable-x11 too:

CFLAGS="-O2 -march=armv8-a+crc -mtune=cortex-a72 -mfpu=neon-fp-armv8 -mfloat-abi=hard -ftree-vectorize -funsafe-math-optimizations" ./configure --prefix=/opt/retropie/emulators/retroarch --disable-sdl --enable-sdl2 --disable-oss --disable-al --disable-jack --disable-qt --disable-pulse --enable-opengles --disable-videocore --disable-vulkan --disable-wayland --enable-kms --enable-egl --enable-floathard --enable-neon --disable-x11

I may have got rid of the --prefix bit, I can't quite remember now.

Appreciate the help.

Mr Lightgun

TLDR;

Works; Is awesome; Fallbacks to default/dedicated gamepads; [Con] appears to honor the custom system kep-remaps which (in my case) dont align for the dedicated USB encoder, but are correct for the gamepads.**

2019-NOV convo on this tool:
https://github.com/meleu/RetroPie-joystick-selection/issues/31

** Solution may be to adjustmy USB encoder to align 1:1 with gamepads

@Metatron When you run the rom go into retro arch menu/ options/overlays then manually select the game bezel folder/relevant system for rom and select the bezel for the game you are running. This is caused by not having the rom names saved in a conformed way. I had this problem with my psx ROMs the other day.

Forgot to mention make sure save configuration on exit is on.