@Seven71ne

It can be pretty daunting, but mitu explained very well the configuration autosaving schema for retroarch.

For retroarch cores, I will usually create configurations by-core. and these are mainly preferences, and not a lot that I do for optimization. These being like how i want to map a sega 6 button controller to my gamepad, or if there is some feature i like to use on this core.

Then there are certain games which may require something specific to be configured, or optimization as needed. And so I will create a configuration for that specific game. I've probably spent the most time configuring PSX games like this, some games not supporting dualshock/analog need to be configured to use digital pad, or vise-versa if you want to use analog on supporting games and digital is the default.

Depending what to consider optimization, there is a lot to take on, sometimes ive been driven to the point to learn a little bit of shell script to streamline an arduous task done by hand. I think mainly if you get stuck on something don't be afraid to ask in the appropriate channels. I got a lot of support and answers from searching all over the web about specific things that only one person was ever asking.
n.

@mitu

After some research i noticed that the .log was outputting:

Parameters: Executing: xinit /dev/shm/retropie_xinitrc -- vt1 -keeptty (EE) Fatal server error: (EE) Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again. (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" after 7 requests (7 known processed) with 0 events remaining.

So i headed to

nano /opt/retropie/configs/nds/emulators.cfg

where i saw that DraStic was using this command:

"XINIT:/opt/retropie/emulators/drastic/drastic.sh %ROM% kms"

changed it to:

drastic = "/opt/retropie/emulators/drastic/drastic.sh %ROM% kms"

Now works like a charm!!!

(Again for future reference - if anybody needs it - i'm using RetroPie under Twister OS 2.1.2)

@mitu One more question related to Drastic. Why is the menu of drastic "unusable"? I'm on an RPI4b. It just doesn't seem to 'register' the buttons correctly. Is there any fix regarding this issue? I'm guessing i'm not alone.

Thanks!

@arroyjose then it sounds like an issue with the USB adapter rather than a RetroPie/Raspberry Pi problem.

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.