Hey!

Many thanks to both of you for your feedback!

In the end, it was the Raspberry Pi Imager tool that got the job done - excellent!

Unfortunately, the weekly builds link didn't work for me, the same problem continued. I also, out of curiosity, tried Firefox (as was trying Safari and Chrome) and pressed the resume function every time the download failed along the way - that method completed the download.

Anyway, thanks again for your help re the Raspberry Pi Imager help! :)

@90sgamer Good to hear!

@retrofdi

So, you get the same results on fresh install...And just spit balling per say, how many video ports do you have? Additionally, have you tried any other displays? My thoughts would be the next thing to look at the communications via HDMI (Assuming you are using HDMI based on the hardware). I would use a known/good HDMI cable, attempted another port, and another display is possible.

@mitu
Thanks for all the help, I finally figured it out. There was a directory config overwriting in the folder with the bios config, when I removed that one my own configs worked and everything is now perfect.

@mitu I've managed to get audio working now, I just needed to add the "-audio default" command to the below. Hope this helps someone else. Now just to solve the DPAD issue :) Thank you!

/opt/retropie/supplementary/moonlight/moonlight.sh stream -verbose -config - audio default "/home/pi/RetroPie/roms/steam/Steam.ml"

@sleve_mcdichael Just my 2 cents here but a USB keyboard should always be set up as well for times like this. Whenever something happens you can reconnect the USB keyboard and have a backup control to fix the other issues. Then unplug it when you're done with it. :)

There's a virtual keyboard on my end when using Netplay, no physical keyboard needed.

I guess first try updating to the latest Retropie version along with Retroarch as well.

@thewillrussell did you configure the controller first in EmulationStation?

@mitu @all
I switch to lr-puae and to lr-vice and it works great now.
Thanx for your help.

Currently the themes installation menu shows (installed) next to installed themes:

01966fb0-e9b7-47ce-bbe8-06dfa2ff2527-image.png

As for the error during install, the only thing I see being an issue is the internet connection - is your Pi system connected to the internet ? If you run an update of the RetroPie-Setup script, does it work or it errors out ?

@roslof Thanks! That may work. They'd just have to disable the port 3 and port 4 inputs if the 2600daptor selection were picked for the second port I guess. The suggestion I had was similar: have a core option "Paddle Type" for port 1 and port 2 that switches between unique controllers and 2600daptors. That's essentially how lr-vice handles inputs for Commodore 64.

An issue that is not yet resolved is the presence of one fire button per paddle. A single port would need an additional fire button in order for the 2600daptor to fully work.

You can update from source to test the latest if you'd like. It doesn't seem to affect anything else. Currently, the control types listed in the RetroArch Controls menu don't have any bearing on what happens in game. Stella's auto-detection still overrides that completely.

Speaking of the 2600daptors, have you tried mapping those in EmulationStation? I still need to go back and mark which paddle is which, but one moves the X-axis and the other the Y-axis of an analog stick according to ES. The two buttons are read as buttons 0 and 1. I am having trouble mapping via the EmulationStation GUI because of how the analog movements are read. I'm thinking I'll just have to manually map those in a config file. The lack of ES configuration means that the paddles don't get auto-configured when RetroArch launches. You can still map them in the RA menu while in game, and they'll work (very well), but we still need to figure out how to bridge that gap.

@mitu said in awk runtime error at launch any games:

What's different in your old install ? Did you change the locale from the default (en_GB) ?

Nothing different. Resolved uninstalling and reinstalling runcommand from Retropie-Setup script. Now it seems to work like a charm.
Thanks @mitu for replying me.

Resolved restoring Keyboard settings.

@gomisensei Yes, I'm aware of that. What I'm concerned with is getting it working. It doesn't run in lr-bluemsx, lr-fmsx doesn't run anything at all, lr-fbneomsx doesn't support MSX2 and lr-mess runs it but neither keyboard nor joystick responds.

https://retropie.org.uk/docs/Updating-RetroPie/#updatinginstalling-individual-packages

@natesroom So i figured it out, I needed to update the RetroPie Setup Script or whatever that name was in the screen first then run the install option packages.

In the Documentation that should be noted (unless it is and i just missed it)

@mitu I actually figured it out myself. I updated retropie and it’s all good now. I actually wiped out my entire retropie burning the Sinden light gun image on my sd card. I can’t figure out how to do this without wiping everything out.

@sleve_mcdichael something something gift horse in the mouth :)