I have read about a similar issue in the forum, and the solution was to install the pulseaudio driver.
Before you try, back up your setup!

sudo apt install pulseaudio pulseaudio-utils

You can change the gamepad buttons from the RetroArch menu for a specific emulator or game: https://retropie.org.uk/docs/RetroArch-Configuration/#core-input-remapping

@mitu Thanks

Could running on a lower resolution help?

"The real world is a special case."

FTR, the RetroPie version 4.8.6 onwards deploys the configurable platform information (peas.json). The upcoming Skyscraper release 3.14 will assess the RetroPie Setup version and will provide the hint on how to proceed if a older version of RetroPie Setup is found.

You can switch the theme from EmiulationStation menus, if that's what you want - closing/backing out from the menu will apply the newly chosen theme to EmulationStation automatically.

@DaniAngel said in Wireless dongle controller issue:

Does this observation help out?

Sort of, in the sense that it shows it's not a power issue, as I was suspected. If you have spare sdcard, can you install the latest RaspiOS from raspberrypi.com and see if you get the same behavior (i.e. dongles doesn't get detected during re-boot/power on) ?

I have been using a Seagate 8tb external hard drive for about a year now formatted to exfat and I'm constantly pounding on that thing and I have yet to have any files corrupt or any issues. Everyone's mileage may be different but I've at least had very good luck using exfat.

No particular error shows up in the logs, the 360 is detected but not initialized as a gamepad though. Nothing comes to mind on what's going on.
You may want to post in the Steamlink forums (https://steamcommunity.com/app/353380/discussions/0/) and post the link to your log there also. If any of the controller works by itself, then it's not a config issue and usually in situation like this I'd check if there's enough power for both the WiFi and USB at the time, but since they already work (simultaneously) outside Steamlink that can't be it.

You may want to use the Configuration Editor and choose to change the joystick order for the systems where you want the X360 pads to be player 1/2 instead of the arcade panel's 2 players.

Yes, I installed it from the imager and updated to the latest version. Thanks for the explanation.

@sugarfree Well, I wasn't quite sure what I did was right and I don't know the terminology too well, but I cloned the Raspberry Pi kernel, modified only the lines of code mentioned in the workaround (the file being vc4_v3d.c), then compiled and installed the kernel. It might have been just dumb luck that this worked, and my problem may have been something else entirely.

@mitu said in joy2key does not start in RetroPie dialog menus:

Isn't Java supposed to run on any system with a JVM available ? Which is the source of the package ?

Yes, but I tested it and it was not working. And I read it too, for example here.

I am going to test it on the newest Bookworm version tomorrow.

Thanks!

@LilaQ Option 2 adding the -ctrl2 joy to your command line should add the 2nd controller every time you load up a game.

@Folly said in Mesa Shader Cache - Can I delete this?:

@TPR said in Mesa Shader Cache - Can I delete this?:
You could rename the mesa_shader_cache first before you remove it.
Then you can always remove it later if you find that there are no problems.
Good idea ?

Yep. Very good idea. I'll rename it to see if there is any issues and if there are I'll just rename it back.

@JimmyFromTheBay

I read that most of these games are ported from MSX.
The story goes that in order to make porting easier the SGM module has a Yamaha music chip that is the same as used in MSX.

So why not run the original game on MSX ?

@Ranma doesn't log level 0 remove all text?

@umxp02 Hello thread from long ago :)

I ended up moving to Batocera with my Pi 4 and had no issues with screens at all. I eventually got a Pi 5 for Batocera.

My Pi 4... I repurposed it to run Plex, and don't need a screen since I can control it from my Mac.

Yeah this issue was a brain buster, so I'm happy I moved on.