@fredthelifeguard said in Audio Issues HDMI:

Built From: Image found on Raspberry Pi SD Card Imager

Which image are we talking about - RetroPie or RaspiOS Did you install any additional drivers or run additional scripts for the PiCade hat to work ?
Please post your /boot/config.txt file.

@mitu I only rememebr following the instructions that came with the box. But yes, I defintely ran all the updates.

@mitu Thank you! I will try these solutions. Hopefully that fixes it.

@dankcushions said in Mame 2003 Retroarch controls for 6 button games:

it's added complexity and in my experience users struggle enough with "just use 0.78 + mame2003", never mind "use 0.78 and mame2003+

I would tend to agree with @barbudreadmon. Even mame2003 is starting to "drift" with changes (albeit small but still no longer the static set it used to be--a few additions here, a rom set rename there). You might as well go with mame2003+ for the most part.

If you can get the ROM management concept down for those minor changes in mame2003, that is if those games interest you, then mame2003+ isn't that much more work.

I would have rather seen mame2003 hold a hard line on its set and let mame2003+ be the dynamic set with additions, deletions and corrections.

I think mame2003 is much simpler to understand and configure (mainly the interface) but mame2003+ is more progressive. They do have 3 folks doing quite a bit of work currently with some worthy additions.

As barbudreadmon pointed out a majority are the original rom set but some updates improve accuracy (like Bubble Bobble) and some additions are recent emulation code, hence more accurate. When you think of the target platform of low spec hardware it's a worthy core. I have a great base game set on the Pi 3 that I'm happy with, and the Pi 4 provides some nice 'oomph' for other cores.

@Spinjunkey-0 said in Picade Sound stuck at Max Volume:

[..] I actually get nothing. My .asoundrc file is exactly like Ultra-Magnuss' and have even renamed and deleted the file. Nada. Volume is still 100% even if I edit with the PICADE on screen controls. [...]

Post your $HOME/.asoundrc.

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!