@ultra-magnuss I haven't looked at this in a few days. For now I have remapped my buttons to not use the start and coin up button. I leave a putty session open to turn the volume down if someone hits it but I would like to figure out how to fix it. It's not as urgent for now since I have a kind of workaround but I would like to figure this out. I'm sure it's a configuration somewhere but don't know where.

It should work after configuring inputs in ES. What arcade core are you using?

@classicgmr definitely improved

@xu-xiaolan omg I actually got it working, tyvm @mitu or I would've been very confused xd, I cloned the github, went to configs and allowed the safe hdmi option then I switched the HDMI port from 1 to 0 (right to left) if anyones wondering how i did it

Is it possible to change the keymapping in retropie?

FIXED
The script from installing the HAT had inexplicably forced the HDMI signal to the other port whilst running emulationstation !
I switched ports and all good !!

Just configure the controller in EmulationStation and that should be all.

From what I see, Egg has the 4 control buttons mapped like this:

1 (RetroPad Dpad-Up) 3 (RetroPad B) 2 (RetroPad Dpad-Up) 4 (RetroPad X)

To re-map them to other buttons, you need to have to have something like this in the system's retroarch.cfg

input_remapping_directory = "/opt/retropie/configs/gameandwatch/" input_player1_up = "w" input_player1_down = "a" input_player1_b = "s" input_player1_x = "d" #include "/opt/retropie/configs/all/retroarch.cfg"

In the example above, I remapped all buttons to WASD on the keyboard and it seems to work fine. I think RetroPad L (left shoulder) and RetroPad R (right shoulder) are used for the Game A/Game B selection, if you wish to remap those.

Since this is a specific game config, you can add the input_... options in a special ROMNAME.cfg file next to the .mgw file and the input configuration will be automatically applied, only for that ROM - see https://retropie.org.uk/docs/RetroArch-Configuration/#example-per-rom-override-retroarchcfg.

@lupsyn This post can be close solution can be found here : https://retropie.org.uk/forum/topic/24544/reicast-mapping-controllers-2020-version-stuck/20

It works!
TBH this project required a little more than that. Had to uncomment a line in a config file to make the screen come to life. Had to change default keyboard layout (I'm using US keyboard, couldn't type "|"). Had to localize system. Had to install gamepad driver and configure input. Mount system on my network. And of course install a romset in the proper directory. Still... WORTH IT.

Thanks for your help.

@mitu

I don't know why that error occurs, I don't think RetroArch uses directly this env var - may be a Wayland/screensaver warning.

So I fixed that error regarding XDG_RUNTIME_DIR, maybe RetroArch does use it after all. I was mistaken when I said it flashed up when launching, it actually flashes up when exiting! Same for the CD-ROM warning.

To solve it, I did the following:

run:

sudo sudo -V

scrolled up a bit to see which environment variables are preserved. XDG_RUNTIME_DIR is not one of them.

I then had to edit the sudoers file (sudo visudo) and add the following in:

Defaults env_keep += "XDG_RUNTIME_DIR"

Save and exit, you can then run 'sudo sudo -V' again and you'll see XDG_RUNTIME_DIR is in the list of environment variables to preserve. Reboot the system and the error should go away when quitting Retroarch.

For whatever reason, sudo does not preserve this environment variable, and i'm guessing because Retroarch launches from the Retropie menu with root privileges, it cannot see or have access to this environment variable. Adding the above in preserves it, suppressing the error (after a reboot).

The CD error still pops up though, but not much that can be done about that at this time it seems.

FYI, this error only pops up when you quit Retroarch after launching it on its own from the Retropie menu - it doesn't come up when quitting out of a game. I guess this is because games are launched as the 'pi' user, rather than with root privileges.

My question would be, is there a reason Retroarch needs to be launched with root privileges from the Retropie menu? Maybe I am misunderstanding how it launches, but that is what it looks like to me.

Cheers!

@grant2258 Hi Grant - yes I think I've realised that this is the problem. The default RetroArch setup creates a virtual gamepad and binds both virtual gamepad and keyboard. I think the problem with Defender is that these mappings overlap - so the virtual gamepad is triggering as well as producing a keypress, and these are both bound to different things (eg thrust AND fire).

Thanks for your help!

@tinybilbo Take a look at https://retropie.org.uk/docs/RetroArch-Configuration/#example-default-per-system-retroarchcfg. You'll need to edit the /opt/retropie/configs/atari2600/retroarch.cfg file (also available via file shares at \\retropie\configs\atari2600\retroarch.cfg) and change the mappings for input_player1_<button_name>.

The defaults are

input_player1_a = "x" input_player1_b = "z" input_player1_y = "a" input_player1_x = "s" input_player1_start = "enter" input_player1_select = "rshift" input_player1_l = "q" input_player1_r = "w" input_player1_left = "left" input_player1_right = "right" input_player1_up = "up" input_player1_down = "down"

@gizmo90 you could also put them in the arcade folder. The arcade folder let's you select from multiple different arcade emulators (libretro mame, advmame, fba etc) it's used for organizing if you have multiple romsets and you want to keep them all in the same place.

@Run-the-Jewels If you have the Pimoroni controller (X Hat) then you should do what I did, see above. Some additional information is on the Pimoroni forums, see https://forums.pimoroni.com/t/x-hat-retropie-coin-button-exits-game/9633.

If you have another controller, then this might not be the same problem. If this is the case, then I suggest you start a new thread, with detailed descriptions of your hardware, software versions, log file entries etc.

I tried commenting out both, like you suggested, but the dimming is still happening. I’m thinking this is just a default behavior in EmulationStation.