this post was submitted on 08 Sep 2024
-31 points (21.8% liked)
Emulation
3569 readers
8 users here now
Community to talk about emulation & roms.
RULES:
1.) No bigotry
LINKS:
-
Emulation Wiki - Your source for everything emulation :)
-
[WIP] Emulation Links Wiki - My personal wiki for emulation links, please help contribute!
-
r/Roms Megathread - Megathread of Roms
-
RetroArch - RetroArch is the popular front-end to libretro which is a simple API that allows for the creation of games and emulators.
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I guess you were trying to say "it makes you look like a clown".
I'm afraid that's a C-, see me after class.
It is a shit design.
It's trying to do everything and ultimately does nothing very well at all. It's such a bad frontend, the only way through which it is really useful is if you use another frontend for it, but if you want to change any settings you're also SoL and might as well just use the standalones, since the way the RetroArch configs translate to individual cores is just a fuzzy mess where the actual dysfunction and if any - user error - will inevitably be obfuscated from the user.
I do not agree. I use RetroArch since years and don't want use standalone emulators every again. But I have to use them still, because they are no RetroArch cores for. There are million reasons why I prefer RetroArch over standalone, such as unified configuration and usability, or Shaders for all cores.
You seem not to value the values and features that RetroArch brings to you. And please speak for yourself if you say "which it is really useful is if you use another frontend for it", because clearly that is not true for lot of people including me. Either use a frontend or standalone emulators if you don't like RetroArch. If you want, try to be productive and don't shit talk and toxic, maybe talk what could be done better.
I have over 70 cores setup in RetroArch. They are all setup the same way, with some exceptions that need special attention. One UI, lot of playlists for all different games and emulators. Everything is updated in one system, all screenshots and files are in the retroarch directory.
And then I have standalone emulators PS3, yuzu and ryujinx, Cemu and Xemu. Some are installed through direct download (AppImage), some through specific package manager (Flatpak) and they have different file structures, configuration, different UI. Only 4 or 5 standalone emulators and they are all different and a mess. Compared to the RetroArch setup. Some can update itself from its menu (and I have to do this for every single emulator) and some need manual download and some are updated through the special package manager. Playing one game on an emulator will not put it in a global history file like in RetroArch. There are no user created custom playlists. I hate it.
Your gripes with standalone emulators are not invalid of course and I'm happy it works for you.
What's got my jimmies all rustled is that this is often recommended as the go-to by people online, making me constantly have to counter this.
There are many occasions where I've seen less tech-savvy friends, some far more intelligent folks than myself with a low patience for bullshit give up on emulation altogether, because they were having some issue or another, and it's always with RetroArch's peculiarities and troubleshooting issues in it to me feels unclear and fuzzy, requiring either dumb brute force or referencing at least several sets of docs, compared to a standalone emulator.
They don't have enormous setups, they just want to play that one game they remember as a kid once every 4 years.
If you're the type to know what [!] and GoodSNES mean with 70+ cores, then yeah, you could probably do worse than a nice set and forget configure-everything-once RetroArch install. I had just that on my Pi, for MAME exclusively, with ES thrown on top for good measure.
As for configs and updates I feel your pain. I never update software for this reason. If config is not in /etc/ or in ~/.config I uninstall immediately, if I see .conf.d - I uninstall immediately. Software exists to solve problems or be fun, not bloat out the system with complexity.
I only wish frustrated people wouldn't shit on RetroArch, like you did in your initial post. That frustrates me too, because it paints a wrong light of the software. See? Your latest reply here is exactly the tone it should have been and the exact problems you talked about, then you would be taken seriously day one. Nothing against critique and talk, nothing is perfect.
I think its not the softwares fault that people got the wrong recommendation or if people are not willing to learn how it works. And surely its unfair to the developers to be disrespectful. Some things are more complex than others, because they do complex stuff. And RetroArch does it in a way, no other software does. Not every software is for everyone. This does not mean its bad, just not for you or for those who struggled.
Fun fact: BTW my first experience with RetroArch was also through RetroPie 3b. And I do emulation stuff since mid 2000s I think and know what GoodSNES means (which is no longer needed, we switched over to NoIntro and TOSEC).
Yeah fundamentally it's an issue with the emulation community more broadly recommending RetroArch as a one-size-fits-all solution for all emulation, when actually it's kind of a niche software for emulation enthusiasts and developers to use as a base for some sort of more user friendly frontend. Hence why I am talking shit on the community hivemind more than the software itself.
For me personally I only emulate a few systems, but I tend to get pretty in-depth with various hacks, tweaks, mods etc. which can involve some basic debugging so I tend to prefer standalone emulators, it just keeps the overall stack much simpler, for these situations I also prefer to compile from source, so keeping things simple helps too.
deleted