I found a workaround with the .srm files.

Open the game you want to use it on before copying over your saved data. Try to open a saved game. This creates a .srm file associated with the game file. Overwrite the .srm file with the desiredsave file.

I do not know why this works. It does though.

@barbudreadmon ding ding, thank you, I did not know about the parent rom. It works. Although I don't think this was on the NeoGeo system until 2 and 3 came out.

Hi again, I don't know what I did but somehow I managed to get it working finally! Thank you for the tips though :-)

After 2 hours of frustration with different controllers and even failing pairing with ps3controller driver, I decided to try a USB BT adapter (disabled the internal adapter) and only that lead me to the root cause.

I had forgotten a similar USB BT adapter attached to my HTPC nearby and it still had PS3 driver running.
I noticed this when trying to pair sixaxis driver with this same kind adapter in PI. First I was happy that the pairing found the device and seemingly successfully paired with it but controls wasn't working after unplugging the USB. Still the DS3 light showed that it had connected "with something". Only at this point I recalled that I might have another dongle still attached in one of the several PCs running nearby.
It was weird that it did not pair with this HTPC dongle when I was trying to pair it with PI internal BT radio, but only when using the similar dongle. Also, the internal radio did not ever found the controller but neither did the controller connect to that other USB dongle.

Silly mistake but further more I didn't think I'd have another dongle around as these controllers have been used for years with a Nvidia Shield and the original PS3 controller without a problem and with that forgotten dongle attached to HTPC all the time.

I verified that the sixaxis driver now works both with Pi3 internal radio and with the external dongle.

Thanks and sorry for being dumb.

Edit: Just to add, I successfully paired DS3 controller and a non vibrating original sixaxis controller. Thought to mention as while searching for help I found some discussion about wondering if the older controller type would pair at all.

Welcome to this forum. Please provide more information about your setup:

all the information that's asked for in https://retropie.org.uk/forum/topic/3/read-this-first What do you mean by "not the same"? Are the control settings different or gone? Does the effect happen in Emulation Station (the frontend where you choose the games) and/or in the games themselves? What kind of "a few things" did you try?

edit: typo

After the installation of Retropie, you can check this thread about Where to (legally) acquire content to play on RetroPie.

Please provide more information about your setup:

all the information that's asked for in https://retropie.org.uk/forum/topic/3/read-this-first the contents of /dev/shm/runcommand.log after running the game with verbose logging from the Runcommand Launch Menu How do you invoke the MAME configuration menu?

I tried adding this after I did a fresh install of the "retropie-buster-4.6-rpi2_rpi3" image... it won't load. I configured my wifi...is it the new build that needs an updated script?

@mitu alright then, thanks for your help, I'll update my system asap

Unless you're connecting your Pi using a composite cable to your TV (which seems unlikely, since that won't do 1080), NTSC/PAL is not an issue for TV's video resolution.
Use raspi-config to choose your desired video resolution globally or modify your /boot/config.txt according to the Raspbery Pi video doc.

Thanks everyone! I found @mitu's answer the most useful, but thanks for the suggestions!

@roslof - Nice, that looks right, I appreciate the screenshot.

@pjft - Thanks for the tip on AdvMAME I'll give it try this weekend.

Waiting for support the 8bitdos....all 8bitdo controllers supportet...
https://www.omgubuntu.co.uk/2016/08/update-8bitdo-firmware-linux
https://fwupd.org/lvfs/search?value=8bitdo+m30

@mitu yes that did it.
its kinda funny i thought i did change it to false before. oh well i have it working now. thank you

I don't think super glue would work because if it heats up anything over "kinda hot" it melts and starts to smell awful. Another bad glue to use is that stuff you use on fake fingernails. Smells bad without any heat or anything. It has toxic fumes. I once tried to attach a fan to a motor shaft with it. I turned the fan on and it started to blow a cloud of basically poison into the air. It was like hitting a wall. I started coughing, my lungs were burning, my eyes were watering, the whole nine yards. So yeah. If you need to fix your Pi with glue, hot glue is the way the go.

@mitu said in Unique config/controller mapping per Gamepad per Core:

If you're thinking of doing this for multiple joysticks/systems, then it might be easier to use an onstart script for runcommand. Instead of overriding joypad_autoconfig_dir, keep a list of desired configurations for a joystick and just copy it over to joypad_autoconfig_dir before the game starts. This way you'll keep one config per standard controller (like the SF 30 Pro) and you can have configs per-system for certain controllers.
...
Somehow this comes up as more complicated than it is and I can't help of thinking if there's a better way.

I modified your script so that it doesn't need to know the names of my controllers or use any new folders:

joypad_autoconfig_dir="/opt/retropie/configs/all/retroarch-joypads" # Put this script in /opt/retropie/configs/all/runcommand-onstart.sh # To support different gamepad autoconfigurations for a joypad in different # libretro emulators copy the current .cfg and rename it with _default added # to the end of the filename. # For each gamepad+emulator combination that requires a variation create # a new copy of the .cfg_default file, changing "default" to match the libretro # core that it applies to, for example .cfg_lr-picodrive. # Modify each variation as needed. This script will copy the variations # (or the default) over the orginal .cfg file as required each time an # emulator is started. # Log output goes to /dev/shm/runcommand.log echo "$0: looking for custom gamepad autoconfigs for $2 in $joypad_autoconfig_dir" >&2 for default_cfg in $joypad_autoconfig_dir/*.cfg_default; do [ -e "$default_cfg" ] || continue # stop now if there are no matches target_cfg_name=${default_cfg%.*} # remove file extention .cfg_default required_variation_cfg="$target_cfg_name.cfg_$2" if [ -e "$required_variation_cfg" ]; then echo "Using autoconfig variation $required_variation_cfg" >&2 cp -f "$required_variation_cfg" "$target_cfg_name.cfg" else echo "Using default gamepad autoconfig $default_cfg" >&2 cp -f "$default_cfg" "$target_cfg_name.cfg" fi done

All of the .cfg variations stay together in the /opt/retropie/configs/all/retroarch/autoconfigs directory, but with different extensions to indicate which core they are needed for. For example, autoconfigs has these files:

pi@rpi-tv:/opt/retropie/configs/all/retroarch $ ls -1 autoconfig/ 'Microsoft X-Box One pad.cfg' 'SWITCH CO.,LTD. USB Gamepad .cfg' 'SWITCH CO.,LTD. USB Gamepad .cfg_default' 'SWITCH CO.,LTD. USB Gamepad .cfg_lr-fbneo' 'SWITCH CO.,LTD. USB Gamepad .cfg_lr-genesis-plus-gx' 'SWITCH CO.,LTD. USB Gamepad .cfg_lr-picodrive' 'USB gamepad .cfg'

The .cfg_lr-picodrive is a symlink to the .cfg_lr-genesis-plus-gx that I made just to check if it would work.

I put some logging in to remind me what's happening if I forget that it's there.

Using joypad_autoconfig_dir in retroarch.cfg seems a bit more "standard", to me so I've stuck with that here. I thought the script could be useful to share though :)

@cedishappy said in Pi zero keeps freezing, please help troubleshoot:

Does this mean the rpi is not faulty?

Yes, if you don't get a crash it looks fine. You might want to try a manual install over the Raspbian image, make sure you disable the desktop auto-login first - https://retropie.org.uk/docs/Manual-Installation/.