If I can add my contribution... I recently tried (like 2 weeks ago) to Update the RetroPie (I'm on 3B+ and had it since 2020 like you). I even had a message stating that my version (Stretch, I think I was on 3.8) was not supported anymore, but I still did it.

Unfortunately it took hours (building from source was the only option) and broke everything.

So I flashed and restarted from scratch (made a copy of my configs and bios/roms folder first), using latest image from the RetroPie website... now it looks like a charm but I need to redo all the custom setup I had. I use the configs backup only as a reference since configs parameters might have changed and didn't want to break things again.

I wish you luck :)

In this case, I think the last option (newer RaspiOS) is the one to try out.

Yes, I think the doc page is wrong and the buttons are switched on the libretro port.

@pinokiooo i had the same issue and i might be wrong but the mayflash dolphinbar only does one player and i ended up buying a 2nd mayflash dolphinbar. had them both on mode 2. nowadays i have 2 singen guns so i dunno if my previous setup still works.

@slug54 said in Need help getting analog sticks working in lr-mame2003 or any version of lr-mame:

If I choose the option for Left Analog Forced

It entirely ignores whether something is already mapped or not to the left analog stick, so i don't recommend ever using that crap. The non-forced option is supposedly safer in that concern, but i have seen reports proving otherwise from people using it.
I'm 99% sure there used to be a core option to map digital-to-analog-left and/or analog-left-to-dpad in some of the vintaged mame cores, but that doesn't seem to be the case anymore.

I'd recommend setting "Analog to Digital Type" back to "none" and using either MAME2003-plus (lr-mame2003-plus) or MAME (lr-mame), both seem to handle this safely out-of-the-box.

Tbh, i don't understand why retropie is still trying to push users toward lr-mame2003 in this day and age, lr-mame2003-plus is the non-arguably improved version of it, and lr-mame run fairly well on newer raspberry models.

Alternatively you could also use FBNeo (lr-fbneo) which also handles this out-of-the-box and offers interesting control alternatives for Battlezone.

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