In RetroPie, the moonlight-embedded variant is used and it's installable only for ARM boards (Raspberry Pi in general). While it has more features, the -qt variant might not offer many advantages for Pi users.

Did you test it on a Pi ? Does it work better than the -embedded version ?

This looks like a feasible option. I expect my Pi400 to arrive later this day so I'll try this immediately.

Why not convert an old 8-bit ... https://retropie.org.uk/forum/topic/25090/commodore-plus-4-rpi4-build-ready?_=1604183646445

@julugamer said in Ouya games on Retropie:

But is it likely to happen that there will be something like such an emulator/interpreter on Retropie?

Unless there's already an emulator/interpreter that works, not likely to happen.

@h2805270 Really clever idea, looks a lot like Teletext, and clean layout too. My only reservation is that I'm not sure I'd want to spend too long looking a Teletext screen, as they're not the easiest on the eye. I was never a big user back in its heyday though, and others may well have a greater fondness and nostalgia for it.

@HipsterDuRocher Thanks for the offer. We wouldn't be able to link anything in with subscribers as I can't share any data with external sites.

Not sure what you had in mind, but even if it was possible I lack free time to do any sort of collaborative work. Sorry.

But wish you all the best with your site and thanks for your efforts.

Isn't it cleaner to use systemd / services in order to do so ?

It is explained here how to cycle between 2 services:
https://forum.kodi.tv/showthread.php?tid=288584

For kodi.service (configured as a user service not system wide service contrary to the above link) :

[unit] ... Conflicts = emulstation.service ... [service] ... ExecStopPost = /usr/bin/systemctl --user start emulstation.service ...

And for emulstation.service

[unit] ... Conflicts = kodi.service ... [service] ... ExecStopPost = /usr/bin/systemctl --user start kodi.service ...

Emulstation and kodi should not be services enabled/start by default at boot but rather
autostart.sh start the first service by something like:

systmctl --user start kodi.service

if kodi is configured to be the first one.

To go further we can also think about replacing the autostart script by a retropie service which is enabled at boot time. At start, it launches the first configured service. At stop it ensures that emulstation and kodi are stoped.

If the service is run as pi user (which is more secure), the pi user must be lingered to enable autostart of the service at boot even if the user is not logged in.

loginctl enable-linger pi systemctl --user enable retropie

Advantages:

All the services could be controlled, inspected, logged through the systemd tools Not need for automatic login It could be easily extended to any number of services not just 2.

@darrena092 said in Idea: Audio Device Selector in RetroPie-Setup:

I think it might be a good idea to add an audio configuration menu to RetroPie-Setup, which allows the user to select a default output device and automatically updates the ALSA config based on the user's preferences. This could also be added in EmulationStation to the RetroPie menu for easy access.

There is already an Audio settings menu in EmulationStation - in the RetroPie system. Right now it only works for choosing the audio output for the Pi's onboard audio - i.e. no USB/I2S sound card support. It should be possible to extend it to support other audio options.

The only issue would be the EmulationStation own Audio menu, where you can choose the Card and Device (volume control) - the ALSA name of the default mixer varies, depending on the audio card, but the list of Audio Devices is fixed (in source).

Not an option for me then since I use skyscraper when ever i add new games. I really hope they add this as a feature.

@duckmefast That only rotates the display 180 deg. - 90 or 270 deg. rotations are still not supported by the Pi4 via config.txt.

@p33te I built a bartop arcade machine. Like you said, building it was fun, really fun, but I don't have the space for it. The build process is what I'm really in for so although I at this moment think that some sort of small case and wireless controller would be smartest it doesn't sound very interesting. Right now I'm thinking about doing some sort of CRT build. That would add some extra challenge and the games we play on a Pi are all(?) originally meant to be played on CRTs.

@IanDaemon Thanks, Ian. This doesn't work on a CRT monitor (at least not with Pi2Scart). More here:

@jrb555 My main pc monitor is at 1440p and I use RetroPie on a separate smaller 480p. Love those pixels, part of the charm, but only if its sharp image. Your tv or monitor have to scale up the 720p to its native 1080p and that is where blurryness comes. If you play on a native 720p monitor, the pixels will be sharp.

@retropi19 If the problem is not specific to one Port, I suggest you open a new topic and add some details about your setup, including the info from https://retropie.org.uk/forum/topic/3/read-this-first.

@wintonson
Some compatibility lists exist.
MAME
Dreamcast
Look in the Docs for your emulated system. Also try searching the forums.
The lists aren't perfect, but can help set your expectations.

@mitu

Thank you mitu, I appreciate your reply, will go have a look into that.