Couple reasons:
RetroDeck is a flatpak and EmuDeck is basically a script that installs a bunch of custom stuff directly and configures it. I like the flatpak ecosystem and it makes more sense to me to do it that way so it’s self-contained. Seems like it’d be cleaner to remove/update/move the installation and less likely to break due to a SteamOS update
EmuDeck is working on Windows/ROG Ally support, while RetroDeck is just for Linux and dev priorities are still fully focused on the Deck
RetroDeck supports a couple fewer systems than EmuDeck, but they both cover all of the ones I care about personally.
RetroDeck is also more closely partnered with EmulationStation-DE
@entropicdrift is retrodeck ready for use? I haven’t really heard of it compared to emudeck.
IMO it is. They put a bunch of “oh it’s still early days” kinda warnings on their page but for me it was pretty much plug and play
@entropicdrift okay, I’m having issues with the rom transfers. The way I have my rom set up is that each game has its older folder. So, RE2 folder has .cue 1 and .cue 2 and the .m3u file. I put that folder in the psx folder and now retrodeck sees it as separate files and the .m3u file won’t launch. Actually , no Psx game launches.
@entropicdrift i wish someone did a walk through. I don’t know much about the process involved for retro deck.
