• 5 Posts
  • 712 Comments
Joined 8 months ago
cake
Cake day: January 24th, 2024

help-circle










  • 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.



  • 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.



  • it lets you look like a clown

    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.

    I’m afraid

    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.


  • Lol fuck off. I’ve been in the emulation scene since long before this absolute garbage became recommended by you drooling 12 year olds. It’s not a matter of “newbie”, it’s a matter of shit design that looks and functions worse than PCSX2 did circa 2013.

    This is a shitty, fuzzy program that tries to do everything but does nothing. It’s useless for arrogant morons and otherwise non-technical people like yourself without emulationstation or some hundred hour youtube tutorial, and it’s useless for actual devs and technical folks like myself who want a clear simple model of program flow and interaction between all the settings so we can quickly troubleshoot whatever issues arise and get on with our lives.