@mitu

It was in fact that I had not updated retro pie on installation - I can’t believe I did not think of that.

The rom was also no good, I did try the correct one earlier, and it didn’t work so I went searching for that one.

But the rom is working now!
Thank you very much.

@mitu Like my 8bitdo gamepads (on pi3 or pi4), my DS4 never reconnect after a system reboot. They stay connected only on EmulationStation reboot.

@OM3GAZX

Just sort Hypseus.

FYI anyone reading.

I added a sleep 1 to the ydotool script at launch and a sleep 1.5 to my emulationstation auto launch script for a more stable result.

@mitu
I think I must have hit the audio settings script module several times. with a healthy amount of reboots before it did anything in the way of successfully setting up ALSA

I'm still lost on this one. I know a clean install after installing retropie it did have audio, somewhere i lost audio updating and configuring pretty early on. I gave up on it several months back only to come back to it today.

I'm starting to lean towards it being some issue with argon one HDMI daughter board. But in the end it is working now, and i admit it is very unlikely that my "fix" did anything.

I just remembered I installed Kodi, from optional packages, somewhere in this attempt too. I feel really dumb, but at least there is always something to learn

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