@Used2BeRX
Is it possible to configure gamepad for second player?
By the way, -joystart seems not working for Master System (it is only for Game Gear).

@EctoOne Oh, that's a real bummer. I thought the package with the "-Linux-64Bit.tar.gz" in the filename from the releases page, which is build with PyInstaller would solve issues like that in the future. I get a fontconfig error with it on my current system and it can be a local issue on my machine. Not very encouraging, but maybe you could try to run that.

But well, it contains binary files, so from security standpoint I can understand when you don't even want try that.

@mitu said in Possible fork of 32bit RpiOS?:

hence the presence of the 32bit compatibility OOB

Thanks for the clarification! And I would have sworn that after my migration to XPx64 the change in Ubuntu was troublesome in the 1st incarnations of 64bit but later it was pretty easy (maybe because all apt* gets where referencing 64bit installs), but still I remember using certain geo-scientific apps (edit: deb packages) that where 32bit (and wheren't updated since ages) only under ubuntu 64bit... but I am really not sure whether I installed a layer similar to WoW64 or simply used in that time something like "linux32 <appname>", but what I am pretty sure in my memories is that in early ubuntu 64bit versions I've stepped back from migration because they where 64bit World only and just a few distros later it was alike (in my memory) to the windows world :/ Well, Memories.... But to add one last statement, after XPx64 (which really wasn't supported/pushed by M$ from start and the users of it learned pretty fast how to use Orca or the Windows SDK AppVerifier to get apps installed) and the early hazzards of 64bit OS', I've never had any trouble of running 32bit Apps on my Desktop PC Systems (on various 64bit OS)... So I am really troubled by the notion of the concept 32bit ain't running under 64bit OS', as my experience is strictly opposed to that :/

Though I may say, my thoughts aren't really helpfull within OP's topic ... Sigh...

Just updated a bug in the RetroPie installation script, which did not take into account the move to the new carbon-2021 theme from RetroPie v.4.7.19 and onwards.

Should work now for both newer and older RetroPie versions. Sorry for any inconvenience.

@Endprodukt
Retrieved my file (SVG vector format); unfortunately the parts outside those needed for the backdrop still need some finalizing. Anyway you can now download it from here.
Don't look at the preview it shows there, the cardboard does is complete.

I made an ARM64 build of dosbox-core:

https://github.com/realnc/dosbox-core/releases/tag/latest_build_linux_arm

I don't actually know if it runs, since I don't have an ARM machine. In theory, it should run fine on RPi 4 since it's built on arm64v8 Ubuntu 16.04.

In addition to the system detection in system.sh, where you specify the detection method and the capabilities, you'll need to decide which distro (and flavor) you support and set the debian/ubuntu_ver. The platform flags in system.sh also have to be able to differentiate the platform so that different packages can be built with the proper make/cflags/ldflags parameters. Some emulators have makefiles that take into account the SBC platform and set compiler options themselves (i.e. Amiberry).

You should also take a look at _mapPackage in helpers.sh to make sure that kernel headers package are properly detected and installed. Armbian has a different naming strategy for kernel package names than Ubuntu/Debian and they also provide different distro options for the same SBC (Debian/Ubuntu flavor).

Lastly, you'd need to check what packages should be enabled via each package's flags and make sure they're working properly.

Not possible, the Pico is a different type of device which is not suited as a general purpose computer, like the Raspberry Pi.

@mitu I tried to install the RetroFix theme
It was confirmed that the function of the theme was not supported normally.

First, the system does not seem to support video output and path {random}.

Second, since the minimum size of the image cannot be specified in the grid view, the size ratio of the image is not constant. Moving the selection cursor changes the size of the selected ones, but I hope to ensure a consistent size from the beginning.

There are other minor issues.

@windg It will be included when we are ready - https://github.com/RetroPie/RetroPie-Setup/pull/3486

That’s right. Retropad abstraction. . . Thanks for the reminder about that terminology.

None of this is actually a problem—it’s just a matter of development solving the needs of everyone AND configuration solving the needs of an individual project.

It has been a while since I was deep into these details as I tend to come and go with other projects/hobbies getting in the way. Someone gave me a Pi4 which is the first in my collection, so naturally, I put it into the arcade build and setup a fresh image of RetroPie 4.8. Now, I have LOTS of work to get it going again, so I am re-learning the controller configs, transcribing some stuff from 2003 to 2003 plus etc., not to mention getting some of my GPIO inputs working again, dealing with different HDMI cords, USB-C, and on and on.

There is actually what I will call a second generation of nostalgia in all of this nostalgia!

@Lolonois: Thanks. I have already updated my Pi3b and Pi400 using the official released Retropie version from Midwan. I also compiled myself releases since around Christmas 2021 and reported all bugs I found on my old Pi3b to Midwan, which were all fixed up to the v5 stable release.

@nemo93: Update process was quite smooth. Just compile or copy official zip package and copying over some files to the right Retropie spots and you are good to go. As I switched around last Christmas from ADF to WHDLoad, I can‘t report much on .uae files, as I do have no real need for them anymore . For compatibility I created an A1200 profile and saved that as default.uae.

For WHDLoad games I recommend setting up Port 0+1 with two game controller and enable the mouse/joystick auto switch feature under Input to switch mouse and Joystick by simply pressing left mouse or fire button. This allows to play Bubble Bobble or Blood Money with two Joysticks and still enable trainer etc. by simply clicking LMB on WHDLoad workbench screen and fire button once game is loaded.

In addition I would recommend to set whdload_quit_on_exit=truein .uae files, respective set default_whd_quit_on_exit=yesin amiberry.conf. This forces WHDLoad games to call AmiQuit when quit WHDLoad games via F10. Without this option, user may get trapped in the AmigaDOS prompt, from where you could enter AmiQuit + ENTER manually to go back to ES menu.

@psyke83 Hi, I was away since a long time.
I'm installing the latest Retropie version on an Rpi 3 and wanted to try the sixaxis driver with a SHANWAN PS3 clone controllor.
I was able to pair the controller but not to connect, the led on number 1 turn on solid red for less than a second and then disconnects.
Sometimes happens that while doing it, Emulationstation crash.
This is the messages on bluetoothctl

Agent registered [<span style="color:blue">CHG</span>] Device 00:26:5C:5D:BD:00 Connected: yes [CHG] Device 00:26:5C:5D:BD:00 Name: PLAYSTATION(R)3 Controller [CHG] Device 00:26:5C:5D:BD:00 Alias: PLAYSTATION(R)3 Controller [CHG] Device 00:26:5C:5D:BD:00 Connected: no [CHG] Controller B8:27:EB:75:21:27 Powered: no [CHG] Controller B8:27:EB:75:21:27 Discovering: no Agent unregistered [DEL] Device 00:26:5C:5D:BD:00 PLAYSTATION(R)3 Controller [DEL] Controller B8:27:EB:75:21:27 retropie [default] Agent registered [CHG] Controller B8:27:EB:75:21:27 Powered: yes [CHG] Controller B8:27:EB:75:21:27 UUIDs: 00001801-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 UUIDs: 00001200-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 UUIDs: 00001800-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 UUIDs: 00001801-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 UUIDs: 00001200-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 UUIDs: 00001800-0000-1000-8000-00805f9b34fb [CHG] Controller B8:27:EB:75:21:27 Alias: BlueZ 5.50 [CHG] Controller B8:27:EB:75:21:27 Name: retropie [CHG] Controller B8:27:EB:75:21:27 Alias: BlueZ 5.50 [CHG] Controller B8:27:EB:75:21:27 Alias: retropie

There is something I can try to solve the problem ?
Thank you in advance.

@prince_rakeem said in Raspberry Pi 4B 4GB and the Sega Saturn:

Do you know if there are there any plans to introduce official lightgun support into yabause?

It has been on my todo list for 1 or 2 years

@mitu said in Game Mode on/off via CEC? ARC?:

@Dochartaigh said in Game Mode on/off via CEC? ARC?:

My question is if we can make the Pi turn on "Game Mode" on our TV's with CEC or ARC? (then off when we're done playing it?)

I'm not sure if that can be done dynamically, but you can set 'game mode' via config.txt - https://retropie.org.uk/docs/Input-Lag/#set-tv-to-game-mode

Thanks for the link! Tried that on my Zero 2 W and RP4 and didn't work so don't know if that's an issue with the software or whatever.. or I also researched my TCL TV which has a history of firmware updates messing with some CEC protocols... so who knows. I would test it on another flatscreen I have but that's a TCL brand too ;)

@2Play Yeah - I will sort this.