This seems like what I wanted on my first rpi over a decade ago.
Install, add ~15000 games from archive.org romsets, maybe a few bios files.
Shit just works.
~1970-2000, done
This seems like what I wanted on my first rpi over a decade ago.
Install, add ~15000 games from archive.org romsets, maybe a few bios files.
Shit just works.
~1970-2000, done
+1. I’m a huge fan of RomM, they have been improving their solution constantly. Also, combine that with their Argosy launcher and you have a great combo of centralized repository and sync client. Edit: some fat-finger typos.
RomM looks really cool. I’ve had difficulty with getting the Retroarch container to play roms with acceptable latency and without crashing. Is RomM easy to set up and does it handle the heavy lifting in such a way as to not tax resources? I’m on an i5 thinkstation with onboard graphics. My system does not like Wayland at all.
In my use case, is just serving the assets as I’m usually using Argosy on my android device or the emulatorjs on other plataforms. Didn’t try yet the new functionality of “streaming” the emulator. But probably will not needed as I’m mostly playing 16/32/64bit era’s games. But probably my N100 with integrated GPU will not be the best choice for this feature 😅
Argosy has to be vibe coded because while the UI appears very polished it is the most confusing and inconsistent piece of software I’ve ever used.
I think they use claude in some way. Not disclosed the degree, however. So, not sure if it’s pure vibe-coded or just assisted (I’m not positioned on the topic and have a “debian-like” approach to it).
And I can understand that sometimes it can behave extremely randomly (modifying collections because in the client a platform is not synced, happened to me once).
But so far, the built-in emulator works really well for save/state sync, and now it can run 3DS (so it’s a one less emulator to install).