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

@mitu got it. sounds like I need to upgrade my GPU then

@newmanph said in When launching a game, emulationstation switches to desktop, then back to the menu:

Is there any way to make emulationstation work within the desktop? I know it's recommended to just use the raspberry pi to launch emulationstation, but if it's possible I'd like to use the pi for other things as well.

You can still use the desktop, start if from EmulationStation - see https://retropie.org.uk/docs/FAQ/#where-did-the-desktop-go - and not the other way around.

Thanks again.

I found how to fix it, in case anyone stumbles upon the same problem:

xset -display :0 dpms force on

enabled my hdmi monitor again.

Going to reinstall retropi again, see if it breaks again and if I can fix it like this again.

@Weatherby said in Pi4 default resolution won't work:

The Pi3 runs smoothly at 4k though, it just gets hot as hell.

Pi3 doesn't support 4k, it's probably choosing 1080p as the best display resolution.

I am not sure what the deal is with the audio not working on the HDMI1 port

That's the default. You can switch it from the Audio menu.

@Libation

thanks you :)

@warchant RetroPie on the RPI is designed to run from the console. Not under X. Don't use xinit.

Check your port forwarding settings on your router. You maybe able to restrict the port forward to specific external IP address(es) or MAC address(es). If so you can whitelist your friends IP/Mac address.

Awesome, thank you!

Ran the test and determined only the standard 4 buttons are registering. The additional buttons from the 6 button pad do not appear.

I did have this working on previous RetroPies, and also just tested it on my PC and confirmed that all buttons are being registered there. Perhaps I'll reach out to RetroUsb and see if there's a recent compatibility issue.

Appreciate the help.

@DavidDraper I'm sorry to hear that it is not working for you.

First off, you definitely shouldn't edit the .bak file, stick with only the .cfg file. Sorry if I wasn't clear there. I'm not sure what the .bak even does, or how to revert it.

Second, remember to only overwrite the button mappings. For example, in the .cfg file there are 2 lines above the mappings that I left intact. For me it reads:
input_device = "SealieComputing N64 RetroPort"
input_driver = "udev"

This of course would change depending on what controller you are using.

If you've done all of the above correctly, then the only other thing that I can think of is that it might be because you are using a "Generic USB" controller rather than an original N64 controller with an adapter.
Perhaps this means your buttons are in a different order, or are labeled differently, I'm not really sure as I don't own a Dragon Rise controller to test with.

Still, if you'd like, feel free to copy what your original dragon rise.cfg file was (prior to copy / pasting my info), and I'll see if I can translate it into something that may work for you.

Otherwise, good luck, and I hope that other solution works for you!

Good to hear, and thanks for sharing the outcome, as even "I overlooked something" can be an important hint for others. 👍

Sorry took so long but thanks it worked amazing you are the best.

@psyke83

Thank you a ton, your advice worked perfectly for Sigil. I actually am interested in having individual launcher files for Brutal Doom for all of the Doom versions just because I like the simplicity of being able to select each game version separately, even if it is more work. But it isn't working like Sigil did. I created another folder under the doom folder called "brutaldoom," just like with Sigil, then edited the emulators.cfg file with the addition of an emulator called brutaldoom. This new entry had /addon/* changed to brutaldoom/*, the same as I did with Sigil.

I placed the doom wad in that folder, and the brutal doom .pk3 file. I set up a "Brutal Ultimate Doom" launcher directing the location of the doom.wad file in the doom/brutaldoom folder. It launches it perfectly fine when I set "brutaldoom" as the default rom launcher, but for my launcher for the normal Ultimate Doom it will then be set to use the brutaldoom launcher as the default rom emulator as well. If I change the normal ultimate doom launcher back to lzdoom to play vanilla doom, the default emulator for the brutal doom launcher will then automatically be changed to lzdoom as well. So changing the emulator for one ultimate doom launcher changes it for the other, whether its brutal doom or vanilla. I assumed that was because I used the doom.wad file in the brutaldoom folder without changing the name, so what happened to one "doom.wad" changes it for the other because they have the same name, despite being in different folders.

So I tried changing the name of the doom.wad file to brutaldoom.wad in the brutaldoom folder, and kept the original vanilla ultimate doom in the doom folder unchanged, but then it won't even launch the brutal doom version. So it seems to have to keep the original wad name. Since what I did what worked for Sigil I'm lost as to what it is making the two doom.wad files, in different folders, linked. You know so much about how it works, is it obvious where I went wrong? I feel like it must be something small that I just keep missing.

on arcade games in its intended resolution there is black bars at top and bottom because its on 1280x1024 when I try drop the resolution lower on launch options the game wont load up for some reason, just the sound and a black screen.

I can go into option during the game with the 1280x1024 and change the screen to fit but I have to do that for all games it's a bit annoying.

Retropie 4.6 on a raspberry pi 3B with a 128gb Card.