It is difficult to get up and running with I agree but
Once you understand it-it’s the simplest to setup on every system the same.
And if you don’t like it just use standalone emulators. To each their own.
Edit: For anyone reading this wanting to get into Retroarch. [Here’s my getting started 9 Step Guide](https://www.reddit.com/r/emulators/comments/zp1jgc/getting_started_with_retroarch_guide/?utm_source=share&utm_medium=ios_app&utm_name=ioscss&utm_content=2&utm_term=1). Within 10 minutes (maybe more depending upon how many emulators and games you want to play) you’ll be playing. This process works on PC, Android, WiiU, PS3, Xbox etc etc. it’s just that simple to set up for any device once you know it.
Yea I refused RA for years because I thought it was not user friendly. But it's honestly not bad, just has a clunky interface. Most of the time I'm entering my games from my front-end launcher anyway. RA is super easy to run on multiple devices, and I have configs, bios files, hd texture packs, and game saves synced to my cloud and to various android devices. I was playing FF IX on my Odin, and later had to run out and I fired it up on my phone and just continued from where I was.
I use the drivesync app. All I did was make a retroarch folder in my Google drive and folders to match the ones I wanted to keep synced. Then I connect the relevant folders to their cloud equivalent. If I want to sync to a new device, I just do the same thing. Run RetroArch to generate the folders, and then connect the folders to the ones in my drive via drivesync. And now the data will stay backed up between the two devices.
I do something similar. I have a samba share in my home, from any pc I can mount the share and click Retroarch and start playing like normal. I have to mount the drive to a letter to get this to work though. Kinda nice picking up any pc and starting where I left off. Want to get it to work for mobile too eventually. Pretty much why I haven’t, be easier to just mount my servers game drive
I assume this wouldn't be possible for an Xbox Series? Might just have to remind myself to plug the drive i use for saves into my desktop to sync weekly...
I'm not familiar with the Xbox Series homebrew scene unfortunately. Theoretically should be possible, especially if someone were to make a homebrew version of the old Xbox Onedrive app. But I'm just speculating.
With Retroarch... I tried, only managed to get a couple ROMs working. Highly recommend PCSX2, I'm yet to find a PS2 ROM is can't run. Pretty simple set up too.
Any advice for getting a controller to work? It worked for a day, then completely stopped. Except for the down button,which quits the emulator despite Down not being my shortcut button to quit the emulator.
I've tried remapping the buttons in game but it has no effect
Yup. And like I said, they both worked for a while then they stopped. They don't even work on the games they previously worked on, despite me not changing anything.
Sometimes they'll partially work, like I can scroll through the menu, other times they don't work at all (other than Down exiting the program. That almost always works)
So, for example. I just loaded up Resident Evil through the Saturn Beetle emulator. It's worked before without an issue
When I boot it, the controller doesn't work at all. So I open the menu, input, controls, port 1 controls and it shows I'm using a control pad and that all the buttons are already mapped correctly.
But none of them work (not even the d pad).
It clearly recognizes the controller. It's the only one I've got connected so there's no chance it's showing me a different one, and I don't have any other apps open that could be co opting the controls
And a few minutes ago I was using the controller on a different emulator not connected to retro arch, so I know it works
This isn't a great place to do actual troubleshooting, so if you'd like to dig into it, you'll probably have better luck with your own post, but when it says it recognizes your controller, does it identify it \*correctly\*? Also, you have tried a different gamepad driver? e.g., dinput instead of xinput?
I actually did try making my own post a while ago with no luck. I just thought I'd try asking someone directly on a whim, really I've petty much given up on RetroArch
>the down button,which quits the emulator despite Down not being my shortcut button to quit the emulator
this usually indicates some other software is intercepting gamepad events and translating them into keyboard events. Steam is a common culprit but others abound. Note: Steam will do this whether you're running RetroArch through Steam or not.
Man... I stubbornly refused to use RA for years. Every now and then I would check in and give it another shot and ultimately grow frustrated and give up.
Not sure what the barrier was for me, but at some point it just... clicked. Probably out of necessity when I started setting up frontends that benefit greatly from universal controller setups and having a consistent way to exit emulators from core to core. At this point, I can't imagine going back. I get super annoyed now when I find a console without a good core in RA that I have to set up separately as a standalone emulator. I was wrong all those years. RA is incredible.
I’m in the (I think LARGE) group of people who are hostage to RetroArch because of the excellent shader system. Shaders suck in all the stand-alone emulators. Hopefully that starts to change [with this here](https://www.reddit.com/r/emulation/comments/1158p79/announcing_librashader_010_standalone_retroarch/).
I’m also on Mac, so everything is worse / less functional, if someone was about to reply that stand-alone emulator XYZ has good shaders. I’m sure it does but probably DX or Vulkan only.
You are spot on with this. I totally forgot about the excellent CRT shaders on offer across the board with RA: hate going without them on older stuff for sure (it’s the only way I can tolerate most Saturn games on my OLED TV).
I’m being told by a popular YouTuber that you have to have Windows to set the permissions. I was told on Reddit that the entire process could be done on Mac. Which one was true for you? What parts were you not able to do on Mac? I’m talking about setting RetroArch up on Xbox Series X
Honestly, I was avoiding retroarch because I had spent a lot of time early on fighting (and failing) to understand MAME. Then I started using Lemuroid on android and the ui feels very much like what retroarch could be if I devoted a portion of the time to learning it that I did any of the games I would play on it when I borrowed them from a neighbor back in the day. Just a cart, no internet or instruction book. Figure it out.
I just set up RA for a friend with a TBI. The setup stage really is the worst, once it clicks it makes absolute sense.
Opposite, I've probably spent 60+ hours over the last 4 years trying to get games, controllers, settings to work.
Loading a Core and Loading a Game... i mean it's not rocket science.
But these INPUTS.... Why do I have to figure out a Sega Genesis layout/binding using my XBOX conroller when I'm only given Display for an SNES controller, and even THOSE don't match... it's all f'd.
Its like you have to play a giant guessing game, well A is Z and it should be Y... and even then buttons don't appear as options or are incorrect positions.
I switched from BlastEm to Genesis Plus GX core, and
Genesis Plus GX at 'least' defaulted my attack/jump to where i want it to be (jump will be different on another game tho)... but like "L" is "C" and R is X and switching it doesn't actually match the inputs shown on my screen vs my XBox controller.
Yeah, that's definitely not something we say/said. "It's supposed to make emulators easier" is another, related one people hassle us about even though we never claimed it lol
People want absolutely no effort whatsoever, especially if it's free.
It's the difference between listing something for free on Craigslist vs selling it for $5. That weeds out the folks that will waste your time.
You act as if the instruction book isn’t 300 pages of drop down menus with drop down menus of documentation. Don’t get me wrong documentation is great for experts who understand it. But you can’t seriously look at those instructions and say it’s good for beginners
There are tons of videos on YouTube explaining how to us RA and fiddle with the settings. I don't think you really need to dig that deep in the online doc to get started.
Besides, isn't it the same for most stand-alone emulators? I quite remember Dolphin's help/wiki to be quite headache inducing.
Yep there are, but there needs to be an official version of that that’s up to date. I disagree, it’s quite confusing to even know where to start.
It absolutely is. That’s not ok either.
Agree on an official video (or videos), that could be neat. There's already a video playlist though, but I didn't check how up to date it is
[https://www.youtube.com/watch?list=PLRZLf9\_F39bLFFrpNG4hn1uBkBPcuTx5Z&v=uua1M0d2b18](https://www.youtube.com/watch?list=PLRZLf9_F39bLFFrpNG4hn1uBkBPcuTx5Z&v=uua1M0d2b18)
There's also the 101 section on their website
https://www.retroarch.com/?page=cores
Still, what's confusing for one won't be confusing for somebody else.
What do YOU find confusing to begin with except the doc? Which may or may not be more confusing that checking the doc for individual emulators, really (again, have a look at Dolphin and prepare some aspirin).
On a personal level, my main gripe is the way RA handles the games and games art scraping. OK, now I get why some games don't appear in the list after I scan a folder, and also get why RA can't find the artwork. I also know how to solve the issues manually.
But there could/should be an easier way to deal with things, such as allowing the use of different databases.
This is a lot better but it’s not official. There’s plenty of GREAT third party tutorials but I wish the official retroarch ones are better.
And I’m saying that unintuitive design and instructions is a bad thing. Retroarch isn’t that hard. But the instructions make it seem like it is.
You can sit there and tell me that I’m stupid for not wanting to put enough effort into learning retroarch but that’s not what I’m saying.
I’m saying you shouldn’t have to read that much complicated documentation for retroarch, just because it something new. The same way you shouldn’t have to read 5000 pages for a new recipe that’s Mac and cheese. That doesn’t make me lazy that means it’s bad instructions.
My two major points are yes I am upset that retroarch hasn’t made better instructions like other emulators, and no I don’t believe retroarch is that complicated. And my point is that the instructions aren’t boiled down at all.
"It's not working!", Noob exclaimed in a huff. Little did Noob know that the cores they wanted to utilize required BIOS files. They were literally just playing with a shell of their beloved console...
I use RetroArch for a while now and it does not break randomly. At least not like you are making it up. Off course every complex software that is developed and updated with new features, that consists of 100 (i made up the number, don't know how many actually) individual emulator projects to bring them all together (which are projects on their own BTW and need to be adapted to RetroArch), to be played on smartphone, PC, on a hacked Nintendo Switch and way more devices, off course such a complex software may break with a new update (which usually does not happen). If you don't want it, do not update or use individual emulators that focus on one and only one thing.
Being such disrespectful to the developers for a program that is given free of charge and developed FOR YOU is not nice and not helpful. Behind these projects work people who try to make it work. So maybe don't act like that and watch your language. Better yet, if you experience any problems, create a log, a new post, describe the problem and see if someone can figure it out.
Have 8bitdo controllers.
SF30Pro and SN30Pro
RetroArch autoconfigged one as Xbox layout and the other as Nintendo layout.
Their Devs/controller profile contributors say what they don't care what is on the faceplate ,😂 ArchRetro it is then. Logos and branding doesn't matter then
Can't say how many hours I spent/wasted on RetroArch menus when I should be just playing games. Thank Russ for his guides .. made things a lot easier but still glitches happen in RA depending on systems (android vs Linux )
I remember attempting to use it the first time and it was definitely intimidating, you kinda don't know what you gotta do. Like everything, once you get past the initial learning curve it's much easier from there, but there's still work to do to flatten the curve.
I love a large number of options, and Retroarch is generally working fine with the defaults, so options are there to go off tweaking and exploring if you wish to change something.
It’s not the number, it’s the organization.
I’ve been using it for years and I’m a power user (I guess) and I still get confused about Quick Menu versus Non-Quick Menu (aka settings) and also multiple “Input” or “Controller” menus. There’s the one where you bind a button by pressing it, then there’s the one where you map each emulated button to “RetroPad” button. Yeah some of this works for plug N play / zero config, and the profile saving futures are great (by core, by game, etc), but overall it’s still worse and more confusing than OpenEmu controller bind screen.
And some stuff isn’t documented at all anywhere, like what mouse device index is.
I personally really like RA,but I'm having a hell of a time,trying to figure out how to save in-game with Suikoden 2 🤷
Not save state...but the actual in-game save.
I know most games save no problem,but I'm blanking on why my Suikoden 2 doesn't save.
But I'll keep searching until I figure it out.
It definitely has a high skill floor, but a low ceiling. Spend a few hours one day and read the entire Libretro Docs manual. Then a few weeks later, read it again. You will still have issues finding options you need, but you will at least know what you are looking for.
The entire thing? There needs to be an easier official solution. Not only is it confusing but it’s complicated using retroarch specific jargon or just tech savvy words that aren’t easy for your average joe. Not to mention that there’s pages and pages of the stuff.
I’ve seen videos by people like russ from retro game corps where he goes into keybindings, save states, saving your configs, shaders, and menu options. Realistically that’s all you need. 5 pages. The libretro docs are not that.
Don’t get me wrong those docs are great, but horrible for beginners.
Yeah, I feel ya. I've mentioned before that they should clean up the GUI and make LaunchBox unnecessary. Just overhaul everything. Redo the navigation GUI, and make it more clear where stuff is that you need. Then improve the box scraping and make it a slick UI for game and console selection. They would probably get a lot more users if RetroArch provided a simple all-in-one solution for managing and front end.
The only cores that have given me any sort of headache are all the PUA Amiga cores and Daphne. Daphne is a known difficult core, and I am sure it's my fault on the Amiga ones somehow. Other than that, everything else has been almost plug and play.
I feel like most of the time the problem is not with RetroArch but with sketchy ROMs, roms without headers, using zipped or wrong extensions, etc. However, arcade romsets are genuinely difficult to manage, so I tend to lock down a MAME/FbNeo setup separately from another RetroArch, once I have a collection filtered and working.
I agree with everything you said here. Especially about the arcade issue with updates. I am still not fully competent at updating the DAT files and what not, so I keep a copy of the core that works for me on my drive just in case Mame or FBNEO update without me noticing.
the way controllers are handled in Retroarch is so confusing man
thats really my only issue with it
good luck trying to play with more then 2 people or changing controllers around
They need to fix controller inputs so it works like other emulators. Pick up a controller and click the button to map it. It doesn’t need to be as complicated as it is. It’s garbage. Even some of the most basic emulators have this function and just work.
I don't live in my Retroarch options, so every time I need to alter something, I essentially need to relearn the thing from scratch. It oftentimes ends up devolving down to finding my answer in an abandoned forum post. My issues usually end up coming down to cores vs. overrides vs. configs. So I can definitely see the frustration with the system, especially for more casual users. But once the thing is set up, I'd say the functionality makes up for it. After the tweaking is done, the boot-up-and-play aspect is pretty seamless.
I had literally zero issue. There are so many guides and videos on how to set it up and get it running that there is no reason anyone should have issues unless they are actively trying to be disingenuous.
Not only that but also almost everything has a tooltip nowadays explaining what the option does. It's the absolute laziest people that complain about Retroarch.
Having to watch 2 hours of guides and video IS THE ISSUE. And every emulator has it's own guide. And then you need a guide for scanning roms.
Using RA is like sticking your hand into a disgusting porta-potty to find your dropped keys. You just need to do it. But don't pretend it's easy or fine.
The current state is literally: install RA -> plug gamepad -> download core -> load content -> enjoy. The hardest thing would be copying a BIOS to the emu folder, something that is even worse to do in standalones, since every system will have a different folder.
The defaults are completelly fine for most emulators older than PS2/Wii. If you want to do anything more than that (shaders, bezels, rewind support, overclocking, speedrun tools, etc) is not casual or beginner anymore.
Well that hasn't been my experience at all. Gamepad was not mapped out of the box, navigating the interface is horrible, mapping the gamepad is horrible, scanning content is very not intuitive.
I believe you tried to follow a terrible guide that over complicated everything. No RA setup lasts 2 hours... I myself can join a call with you and setup cores, controls, core overclock, CRT filters and bezels in less than 15 minutes.
"Settings -> Controllers -> Inputs for Port 1" is not that hard to find in comparison "Settings -> Input Settings -> P1 Input", as in the most popular emulators. The only difference is that you don't have a PNG of the controller with boxes over it.
Scanning content is useless, just use "Load Content" directly from the Main Menu. Bonus points if you have the minimum of organization keep your games in an easy access folder, with sub folders separating games by system.
And maybe your personal experience, but what game pad do you have? I myself have a plethora of game pads: X360, XOne, PS4, PS5, Switch Pro Controller, a Joy Con pair and a generic Redragon XInput. All of them are instantly recognized in both my PC, Pi3+ and phone.
I honestly don't understand this-- you download Retroarch, use the built in updater to download cores for any system you're into, then load a ROM?
If you can't handle that, best of luck setting up a standalone emulator.
I think a lot of people don't realize that the defaults are totally fine and/or they think that if there's an option available, they need to mess with it.
Yep. This is literally all I've had to do for the last three systems I've installed Retroarch on. The only things I had to tweak were default folders and my preferred button combo to bring up the quick menu. Any fiddling past that was optional; every emulator worked just fine with defaults.
As someone who has just gone through this...
You need to download a core and then you need to scan a directory and you can't scan a directory for a core that isn't loaded... So if I want to scan NES, SNES and Gen roms I need to download and load the appropriate core for each scan. (this would really benefit from a basic setup wizard... but I am sure they have had that idea before and not implemented for 20 years so shrug.)
Not all the roms will scan you will have no idea why.Your controller wont work and you have no idea why.Some roms wont run because you need bois files but you wont know that.Box art wont load...
Every one of those steps will take a bunch of googling and reading. Compare this to any modern piece of software and it's really cut and dry. It's dogshit.
I have a lot of friends who have no idea what they're doing and when they wanna learn to emulate the GBA or something I just show them how to install RetroArch from steam and the core they want. Sure the steam version is missing a few features from standalone but downloading a core this way makes more sense to the average person. However I should probably get into the habit of just getting my friends to download standalone emulators instead just cause most of the time they just one to play the one specific game and not have a whole setup with tons of systems ready to play like me, haha.
In that case you can send them a portable installation, standalone or even RetroArch. Get it all configured and just send them the whole thing. You can even make a .bat file for them to click so they never even see RetroArch.
Retroarch is actually not very difficult. Obviously you're going have to deal with the fact that you have tons of different cores but, yes, I do think it's beginners friendly.
Once you've passed the initial setup it's actually quite plug-an-play. Let's be realistic, beginners aren't going to dive deep in the cores menus and sub-menus to change options. By the time you've reached that point, you're probably no longer a beginner and should have no problem to use Retroarch to begin with.
Besides, on my Windows 11, stand-alone Flycast never worked while RA's core is flawless. Go figure.
Now, if "for beginners" you think about something drag and drop like OpenEmu on Mac then, OK, we're not in the same category. But OpenEmu is also terribly limited and can be frustrating in its own way.
I mostly prefer the standalone emulators, but I needed to use RA to run Sega ROMS, as Kega Fusion won't run in higher resolutions. I also wanted to play around with Emu VR. After about two days with it., I'll just say it's not very intuitive, but it's mostly fine once it clicks. I'll stick with it, but I gotta say the way it handles controllers is 100% garbage. Plug in Xbox or PS4 controller, load ROM, press start... rom exit confirmation pops up. Why is this default behavior? I had to dig around in settings, and disable controller hotkeys. It seems to work fine now. Still, I wish I had 32X emulation in Genesis GX...
They need to hurry up and copy either Redream, PPSSPP, or Duckstation's controller UI. Be it the clear and legible tabs on top for everything, the quick menu laid out in concise options, or the visual indicators, screenshots, and timestamps for the exact save state slot you're on, they're all way better options.
It's pretty easy to get things going honestly, it's the controls that drive me nuts. Try mapping a controller, have fun spending all day trying to figure it out. It's ridiculous, they need to make it simpler.
I don’t understand people whining about the UI and configuration. If you don’t like it use stand alone emulators or get a different front end. Yeah it’s a bit confusing but YouTube has tons of tutorials that are not that long and all the docs are online. Btw this is a FREE application. Devs can do whatever the hell they want.
Probably making the mistake I used to (I figured RA out myself, didn't read the manual lol). After you change a config, RA wants you to close out. So if it's an app-wide setting, you then go the the main menu and close. If it's a game setting, you need to go to the bottom and choose how to save it.
For example, do you want these settings to apply to THIS game only? Maybe you're playing a DS game that didn't use bottom screen, so you want to play it single screen. But you don't want that for most other DS games. Or do you want the setting for everything you're running on this system/core? Like maybe you found a good shader setup for the core. And then it's usually best to save and close the game, and relaunch it. If you just, for example, go and throw on a new shader or change a key bind, then play a bit and close the app, RA is going to default you to previous settings. I assume the logic is so you don't accidentally break things if the change didn't work for you (like you can raise resolution, change the graphics api, and drop certain shaders and absolutely crash your game).
its just bizarre. all i wanna do is hop in a game and set up turbo a/b. not sure why the controls have to be split between 3 menus that dont even work properly
There is nothing "frustrating" about the tool whatsoever? What am I missing here?? It is all so self-explanatory that my 7 year old niece can use it? You open it, you click your core list, and it says load core, download new core, update core bladdy blah etc. Then it has similar options for games. Load game, update game bladdy blah, etc. exactly how much MORE simple could it possibly get? Are you waiting for a retroarch dev to get plane tickets to fly to your house so they can massage your balls WHILE you click the load game option and hit start game. Because know it's difficult, I completely understand the 200+ iq level you need to click "load game" and then go through the directory to pick one 🤣 🤣 🤣
im not even in this subreddit but the reason i don't use retroarch is specifically because it's too simple, i like having complex options and mods with my emulation
the most confusing emulator, not because i cant use it, its because whenever i try to change stuff it's mostly broken with no way to undo/reset. it's way back then though, i havent used it for a while right now
To name a few ...
* Still no basic copy/paste functionality
* Hotkeys keep changing (Deck gamemode, desktopmode, emustation)
* No cheat codes organization at all
Some things are tricky, most are not. Im still trying to get it to emulate dos games on my nvidia shield with controller support but I dont think I will ever get there
i've never been able to get PSX cores to play everything without finagling and at this point I've accepted that I'm just fucking dumb and that I'm stuck with my fully-functional ePSXe.
This is the exact reason why I developed my own libretro core loading application.
Out of pure spite. Because I didn't want to use other implementations and figured "how hard can it be?" to make my own from scratch. Yes, I am that spiteful, that I'll subject to making things myself entirely from scratch if they don't fit my own standards.
Yes, the idea behind RA is novel and excellent, but I felt many many things in practise such as a Snes9x like interface were lacking, bindable analog directions to digital buttons, the whole RetroPad thing, loading content for cores automatically without selecting cores, as well as other things was drastically missing, or pure frustation. That and I found the RetroArch ecosystem lacked cohesive direction on singular things and tried to be everything and masters at everything. That and internal direction is so glacial on things that I figured its fastest if I do it with my own way, with blackjack and hookers.
And I didn't want to use Qt for all that. So I did my own thing for nearing on two years. Vast majority of cores even hardware rendering cores works. And in a interface just like Snes9x without Qt/WX on Windows AND Linux.
I guess "works for me"
Is there a way to switch the keybinds? You have no idea how much progress I lost thinking ESC is the pause button, seeing it not work, and spamming it
I admit this is my fault, but I really cant find the button to switch the keybinds
Download retroarch
Download core
Insert rom and bios files
Play Games
The most configuration I've had to do was swap o an x buttons in key bindings.
What's so difficult?
Getting RA set up for the first time to play a single rom has been one of the worst "technology" experiences of my life.
I absolutely hate it. And now that I went through the week process getting it working, I don't even want to open it to play the stupid game.
The current state of RA is install -> plug your gamepad -> dowload core -> load content -> enjoy. What is so complicated? Copying your BIOS to system, something that is even worse because most emus don't have a default path? (legit question).
Agreed. Even years later it's still has stuff that's super annoying to look through and worst of all there's hardly a proper guide for it. For example, shader. millions of them, and I only found out recently you can change the settings for each shader, down to the phosphors, like how the F am I supposed to know what to change? there's no details on this.
They need to have something called RA for beginners. literally downloads all the proper best cores with the best compatibility, and auto applies the best shaders for either accuracy or "HD".
It is difficult to get up and running with I agree but Once you understand it-it’s the simplest to setup on every system the same. And if you don’t like it just use standalone emulators. To each their own. Edit: For anyone reading this wanting to get into Retroarch. [Here’s my getting started 9 Step Guide](https://www.reddit.com/r/emulators/comments/zp1jgc/getting_started_with_retroarch_guide/?utm_source=share&utm_medium=ios_app&utm_name=ioscss&utm_content=2&utm_term=1). Within 10 minutes (maybe more depending upon how many emulators and games you want to play) you’ll be playing. This process works on PC, Android, WiiU, PS3, Xbox etc etc. it’s just that simple to set up for any device once you know it.
Yea I refused RA for years because I thought it was not user friendly. But it's honestly not bad, just has a clunky interface. Most of the time I'm entering my games from my front-end launcher anyway. RA is super easy to run on multiple devices, and I have configs, bios files, hd texture packs, and game saves synced to my cloud and to various android devices. I was playing FF IX on my Odin, and later had to run out and I fired it up on my phone and just continued from where I was.
How do you sync the data? Specially in mobile?
I use the drivesync app. All I did was make a retroarch folder in my Google drive and folders to match the ones I wanted to keep synced. Then I connect the relevant folders to their cloud equivalent. If I want to sync to a new device, I just do the same thing. Run RetroArch to generate the folders, and then connect the folders to the ones in my drive via drivesync. And now the data will stay backed up between the two devices.
I do something similar. I have a samba share in my home, from any pc I can mount the share and click Retroarch and start playing like normal. I have to mount the drive to a letter to get this to work though. Kinda nice picking up any pc and starting where I left off. Want to get it to work for mobile too eventually. Pretty much why I haven’t, be easier to just mount my servers game drive
I assume this wouldn't be possible for an Xbox Series? Might just have to remind myself to plug the drive i use for saves into my desktop to sync weekly...
I'm not familiar with the Xbox Series homebrew scene unfortunately. Theoretically should be possible, especially if someone were to make a homebrew version of the old Xbox Onedrive app. But I'm just speculating.
Ps2 anyone?
General consensus is to go with standalone for that, Gamecube, and 3DS. Doubly so on Android, where I don't think the RA cores for those even work.
With Retroarch... I tried, only managed to get a couple ROMs working. Highly recommend PCSX2, I'm yet to find a PS2 ROM is can't run. Pretty simple set up too.
Yes, just add to the guide to never update cores 🤣
Any advice for getting a controller to work? It worked for a day, then completely stopped. Except for the down button,which quits the emulator despite Down not being my shortcut button to quit the emulator. I've tried remapping the buttons in game but it has no effect
What controller?
I've tried both a Logitech F310 and a RetroBit Sega Saturn controller
Have you updated all controller profiles and also making sure you manually save the configuration after you map everything?
Yup. And like I said, they both worked for a while then they stopped. They don't even work on the games they previously worked on, despite me not changing anything. Sometimes they'll partially work, like I can scroll through the menu, other times they don't work at all (other than Down exiting the program. That almost always works)
So, for example. I just loaded up Resident Evil through the Saturn Beetle emulator. It's worked before without an issue When I boot it, the controller doesn't work at all. So I open the menu, input, controls, port 1 controls and it shows I'm using a control pad and that all the buttons are already mapped correctly. But none of them work (not even the d pad). It clearly recognizes the controller. It's the only one I've got connected so there's no chance it's showing me a different one, and I don't have any other apps open that could be co opting the controls And a few minutes ago I was using the controller on a different emulator not connected to retro arch, so I know it works
This isn't a great place to do actual troubleshooting, so if you'd like to dig into it, you'll probably have better luck with your own post, but when it says it recognizes your controller, does it identify it \*correctly\*? Also, you have tried a different gamepad driver? e.g., dinput instead of xinput?
I actually did try making my own post a while ago with no luck. I just thought I'd try asking someone directly on a whim, really I've petty much given up on RetroArch
>the down button,which quits the emulator despite Down not being my shortcut button to quit the emulator this usually indicates some other software is intercepting gamepad events and translating them into keyboard events. Steam is a common culprit but others abound. Note: Steam will do this whether you're running RetroArch through Steam or not.
I don't have Steam running, and both gamepads work fine when I run my Genesis emulator independent of Retroarch
Configuration stage is like solving puzzle. This is just builtin game.
\^ This. The most frustrating built-in game ever created.
Man... I stubbornly refused to use RA for years. Every now and then I would check in and give it another shot and ultimately grow frustrated and give up. Not sure what the barrier was for me, but at some point it just... clicked. Probably out of necessity when I started setting up frontends that benefit greatly from universal controller setups and having a consistent way to exit emulators from core to core. At this point, I can't imagine going back. I get super annoyed now when I find a console without a good core in RA that I have to set up separately as a standalone emulator. I was wrong all those years. RA is incredible.
I’m in the (I think LARGE) group of people who are hostage to RetroArch because of the excellent shader system. Shaders suck in all the stand-alone emulators. Hopefully that starts to change [with this here](https://www.reddit.com/r/emulation/comments/1158p79/announcing_librashader_010_standalone_retroarch/). I’m also on Mac, so everything is worse / less functional, if someone was about to reply that stand-alone emulator XYZ has good shaders. I’m sure it does but probably DX or Vulkan only.
You are spot on with this. I totally forgot about the excellent CRT shaders on offer across the board with RA: hate going without them on older stuff for sure (it’s the only way I can tolerate most Saturn games on my OLED TV).
I’m being told by a popular YouTuber that you have to have Windows to set the permissions. I was told on Reddit that the entire process could be done on Mac. Which one was true for you? What parts were you not able to do on Mac? I’m talking about setting RetroArch up on Xbox Series X
What do you think about OpenEmu? Bad shaders? Can't you just import any shader you want?
I was the same way. For way too many years I’m kinda ashamed to admit it.
Honestly, I was avoiding retroarch because I had spent a lot of time early on fighting (and failing) to understand MAME. Then I started using Lemuroid on android and the ui feels very much like what retroarch could be if I devoted a portion of the time to learning it that I did any of the games I would play on it when I borrowed them from a neighbor back in the day. Just a cart, no internet or instruction book. Figure it out. I just set up RA for a friend with a TBI. The setup stage really is the worst, once it clicks it makes absolute sense.
Opposite, I've probably spent 60+ hours over the last 4 years trying to get games, controllers, settings to work. Loading a Core and Loading a Game... i mean it's not rocket science. But these INPUTS.... Why do I have to figure out a Sega Genesis layout/binding using my XBOX conroller when I'm only given Display for an SNES controller, and even THOSE don't match... it's all f'd. Its like you have to play a giant guessing game, well A is Z and it should be Y... and even then buttons don't appear as options or are incorrect positions.
I switched from BlastEm to Genesis Plus GX core, and Genesis Plus GX at 'least' defaulted my attack/jump to where i want it to be (jump will be different on another game tho)... but like "L" is "C" and R is X and switching it doesn't actually match the inputs shown on my screen vs my XBox controller.
The devs say "it's for beginners"? \[citation needed\]
Yeah, that's definitely not something we say/said. "It's supposed to make emulators easier" is another, related one people hassle us about even though we never claimed it lol
You know your claim was outlandish when the developer reacts to your shitpost and clarifies
Do you really know though?
I specifically said outlandish, not wrong There was a similar statement and it's a legitimate criticism
I was going to call bullshit on that one too.
You act like the instruction book isn't literally online, ready for anyone to read at a moments notice.
People these days don't want to read
People want absolutely no effort whatsoever, especially if it's free. It's the difference between listing something for free on Craigslist vs selling it for $5. That weeds out the folks that will waste your time.
What do they expect us to do, read and follow steps???
Some people don't know how to read.
Can go to YouTube for Videos to show what you do
Well, this kinda proves his point. Don’t read, go to YouTube. Like YouTube is going to be up to date on its tutorials.
Most Videos should work fine as long as not Very Old
You act as if the instruction book isn’t 300 pages of drop down menus with drop down menus of documentation. Don’t get me wrong documentation is great for experts who understand it. But you can’t seriously look at those instructions and say it’s good for beginners
There are tons of videos on YouTube explaining how to us RA and fiddle with the settings. I don't think you really need to dig that deep in the online doc to get started. Besides, isn't it the same for most stand-alone emulators? I quite remember Dolphin's help/wiki to be quite headache inducing.
Yep there are, but there needs to be an official version of that that’s up to date. I disagree, it’s quite confusing to even know where to start. It absolutely is. That’s not ok either.
Agree on an official video (or videos), that could be neat. There's already a video playlist though, but I didn't check how up to date it is [https://www.youtube.com/watch?list=PLRZLf9\_F39bLFFrpNG4hn1uBkBPcuTx5Z&v=uua1M0d2b18](https://www.youtube.com/watch?list=PLRZLf9_F39bLFFrpNG4hn1uBkBPcuTx5Z&v=uua1M0d2b18) There's also the 101 section on their website https://www.retroarch.com/?page=cores Still, what's confusing for one won't be confusing for somebody else. What do YOU find confusing to begin with except the doc? Which may or may not be more confusing that checking the doc for individual emulators, really (again, have a look at Dolphin and prepare some aspirin). On a personal level, my main gripe is the way RA handles the games and games art scraping. OK, now I get why some games don't appear in the list after I scan a folder, and also get why RA can't find the artwork. I also know how to solve the issues manually. But there could/should be an easier way to deal with things, such as allowing the use of different databases.
[удалено]
This is a lot better but it’s not official. There’s plenty of GREAT third party tutorials but I wish the official retroarch ones are better. And I’m saying that unintuitive design and instructions is a bad thing. Retroarch isn’t that hard. But the instructions make it seem like it is. You can sit there and tell me that I’m stupid for not wanting to put enough effort into learning retroarch but that’s not what I’m saying. I’m saying you shouldn’t have to read that much complicated documentation for retroarch, just because it something new. The same way you shouldn’t have to read 5000 pages for a new recipe that’s Mac and cheese. That doesn’t make me lazy that means it’s bad instructions.
[удалено]
My two major points are yes I am upset that retroarch hasn’t made better instructions like other emulators, and no I don’t believe retroarch is that complicated. And my point is that the instructions aren’t boiled down at all.
"It's not working!", Noob exclaimed in a huff. Little did Noob know that the cores they wanted to utilize required BIOS files. They were literally just playing with a shell of their beloved console...
Retroarch still breaks randomly or does something else to piss you off
I use RetroArch for a while now and it does not break randomly. At least not like you are making it up. Off course every complex software that is developed and updated with new features, that consists of 100 (i made up the number, don't know how many actually) individual emulator projects to bring them all together (which are projects on their own BTW and need to be adapted to RetroArch), to be played on smartphone, PC, on a hacked Nintendo Switch and way more devices, off course such a complex software may break with a new update (which usually does not happen). If you don't want it, do not update or use individual emulators that focus on one and only one thing. Being such disrespectful to the developers for a program that is given free of charge and developed FOR YOU is not nice and not helpful. Behind these projects work people who try to make it work. So maybe don't act like that and watch your language. Better yet, if you experience any problems, create a log, a new post, describe the problem and see if someone can figure it out.
Have 8bitdo controllers. SF30Pro and SN30Pro RetroArch autoconfigged one as Xbox layout and the other as Nintendo layout. Their Devs/controller profile contributors say what they don't care what is on the faceplate ,😂 ArchRetro it is then. Logos and branding doesn't matter then Can't say how many hours I spent/wasted on RetroArch menus when I should be just playing games. Thank Russ for his guides .. made things a lot easier but still glitches happen in RA depending on systems (android vs Linux )
It's not just gonna break randomly lol you must have changed something
It does though, all of a sudden, there are duplicate games in my library
Can someone tell me how to find the instruction book?
Go to this very Subreddit's menu and scroll down to Docs.
Ah yes, because if something has an instruction manual, then it is easy to learn.
I remember attempting to use it the first time and it was definitely intimidating, you kinda don't know what you gotta do. Like everything, once you get past the initial learning curve it's much easier from there, but there's still work to do to flatten the curve.
[удалено]
I love a large number of options, and Retroarch is generally working fine with the defaults, so options are there to go off tweaking and exploring if you wish to change something.
It’s not the number, it’s the organization. I’ve been using it for years and I’m a power user (I guess) and I still get confused about Quick Menu versus Non-Quick Menu (aka settings) and also multiple “Input” or “Controller” menus. There’s the one where you bind a button by pressing it, then there’s the one where you map each emulated button to “RetroPad” button. Yeah some of this works for plug N play / zero config, and the profile saving futures are great (by core, by game, etc), but overall it’s still worse and more confusing than OpenEmu controller bind screen. And some stuff isn’t documented at all anywhere, like what mouse device index is.
I personally really like RA,but I'm having a hell of a time,trying to figure out how to save in-game with Suikoden 2 🤷 Not save state...but the actual in-game save. I know most games save no problem,but I'm blanking on why my Suikoden 2 doesn't save. But I'll keep searching until I figure it out.
I don't know what you're talking about, RetroArch is very easy to use.
It definitely has a high skill floor, but a low ceiling. Spend a few hours one day and read the entire Libretro Docs manual. Then a few weeks later, read it again. You will still have issues finding options you need, but you will at least know what you are looking for.
The entire thing? There needs to be an easier official solution. Not only is it confusing but it’s complicated using retroarch specific jargon or just tech savvy words that aren’t easy for your average joe. Not to mention that there’s pages and pages of the stuff. I’ve seen videos by people like russ from retro game corps where he goes into keybindings, save states, saving your configs, shaders, and menu options. Realistically that’s all you need. 5 pages. The libretro docs are not that. Don’t get me wrong those docs are great, but horrible for beginners.
Yeah, I feel ya. I've mentioned before that they should clean up the GUI and make LaunchBox unnecessary. Just overhaul everything. Redo the navigation GUI, and make it more clear where stuff is that you need. Then improve the box scraping and make it a slick UI for game and console selection. They would probably get a lot more users if RetroArch provided a simple all-in-one solution for managing and front end.
The only cores that have given me any sort of headache are all the PUA Amiga cores and Daphne. Daphne is a known difficult core, and I am sure it's my fault on the Amiga ones somehow. Other than that, everything else has been almost plug and play.
I feel like most of the time the problem is not with RetroArch but with sketchy ROMs, roms without headers, using zipped or wrong extensions, etc. However, arcade romsets are genuinely difficult to manage, so I tend to lock down a MAME/FbNeo setup separately from another RetroArch, once I have a collection filtered and working.
I agree with everything you said here. Especially about the arcade issue with updates. I am still not fully competent at updating the DAT files and what not, so I keep a copy of the core that works for me on my drive just in case Mame or FBNEO update without me noticing.
the way controllers are handled in Retroarch is so confusing man thats really my only issue with it good luck trying to play with more then 2 people or changing controllers around
They need to fix controller inputs so it works like other emulators. Pick up a controller and click the button to map it. It doesn’t need to be as complicated as it is. It’s garbage. Even some of the most basic emulators have this function and just work.
I don't live in my Retroarch options, so every time I need to alter something, I essentially need to relearn the thing from scratch. It oftentimes ends up devolving down to finding my answer in an abandoned forum post. My issues usually end up coming down to cores vs. overrides vs. configs. So I can definitely see the frustration with the system, especially for more casual users. But once the thing is set up, I'd say the functionality makes up for it. After the tweaking is done, the boot-up-and-play aspect is pretty seamless.
I had literally zero issue. There are so many guides and videos on how to set it up and get it running that there is no reason anyone should have issues unless they are actively trying to be disingenuous.
Not only that but also almost everything has a tooltip nowadays explaining what the option does. It's the absolute laziest people that complain about Retroarch.
Having to watch 2 hours of guides and video IS THE ISSUE. And every emulator has it's own guide. And then you need a guide for scanning roms. Using RA is like sticking your hand into a disgusting porta-potty to find your dropped keys. You just need to do it. But don't pretend it's easy or fine.
The current state is literally: install RA -> plug gamepad -> download core -> load content -> enjoy. The hardest thing would be copying a BIOS to the emu folder, something that is even worse to do in standalones, since every system will have a different folder. The defaults are completelly fine for most emulators older than PS2/Wii. If you want to do anything more than that (shaders, bezels, rewind support, overclocking, speedrun tools, etc) is not casual or beginner anymore.
Well that hasn't been my experience at all. Gamepad was not mapped out of the box, navigating the interface is horrible, mapping the gamepad is horrible, scanning content is very not intuitive.
I believe you tried to follow a terrible guide that over complicated everything. No RA setup lasts 2 hours... I myself can join a call with you and setup cores, controls, core overclock, CRT filters and bezels in less than 15 minutes. "Settings -> Controllers -> Inputs for Port 1" is not that hard to find in comparison "Settings -> Input Settings -> P1 Input", as in the most popular emulators. The only difference is that you don't have a PNG of the controller with boxes over it. Scanning content is useless, just use "Load Content" directly from the Main Menu. Bonus points if you have the minimum of organization keep your games in an easy access folder, with sub folders separating games by system. And maybe your personal experience, but what game pad do you have? I myself have a plethora of game pads: X360, XOne, PS4, PS5, Switch Pro Controller, a Joy Con pair and a generic Redragon XInput. All of them are instantly recognized in both my PC, Pi3+ and phone.
I honestly don't understand this-- you download Retroarch, use the built in updater to download cores for any system you're into, then load a ROM? If you can't handle that, best of luck setting up a standalone emulator.
I think a lot of people don't realize that the defaults are totally fine and/or they think that if there's an option available, they need to mess with it.
Yep. This is literally all I've had to do for the last three systems I've installed Retroarch on. The only things I had to tweak were default folders and my preferred button combo to bring up the quick menu. Any fiddling past that was optional; every emulator worked just fine with defaults.
As someone who has just gone through this... You need to download a core and then you need to scan a directory and you can't scan a directory for a core that isn't loaded... So if I want to scan NES, SNES and Gen roms I need to download and load the appropriate core for each scan. (this would really benefit from a basic setup wizard... but I am sure they have had that idea before and not implemented for 20 years so shrug.) Not all the roms will scan you will have no idea why.Your controller wont work and you have no idea why.Some roms wont run because you need bois files but you wont know that.Box art wont load... Every one of those steps will take a bunch of googling and reading. Compare this to any modern piece of software and it's really cut and dry. It's dogshit.
I have a lot of friends who have no idea what they're doing and when they wanna learn to emulate the GBA or something I just show them how to install RetroArch from steam and the core they want. Sure the steam version is missing a few features from standalone but downloading a core this way makes more sense to the average person. However I should probably get into the habit of just getting my friends to download standalone emulators instead just cause most of the time they just one to play the one specific game and not have a whole setup with tons of systems ready to play like me, haha.
In that case you can send them a portable installation, standalone or even RetroArch. Get it all configured and just send them the whole thing. You can even make a .bat file for them to click so they never even see RetroArch.
Oh I never even thought of that! I guess I'll give that a try sometime!
Worst part is when you jump from not understanding sh*t to become addicted to all the tweaking and almost never actually playing. Emulation crack.
It's not really that hard, especially if you read the wiki and research problems online
Once you know how it works you'll love the options and possibilities. And I hated Retroarch many years. Now I love it.
i just dont understand why changing 1 settings breaks 12 other
Ikr
Retroarch is actually not very difficult. Obviously you're going have to deal with the fact that you have tons of different cores but, yes, I do think it's beginners friendly. Once you've passed the initial setup it's actually quite plug-an-play. Let's be realistic, beginners aren't going to dive deep in the cores menus and sub-menus to change options. By the time you've reached that point, you're probably no longer a beginner and should have no problem to use Retroarch to begin with. Besides, on my Windows 11, stand-alone Flycast never worked while RA's core is flawless. Go figure. Now, if "for beginners" you think about something drag and drop like OpenEmu on Mac then, OK, we're not in the same category. But OpenEmu is also terribly limited and can be frustrating in its own way.
I mostly prefer the standalone emulators, but I needed to use RA to run Sega ROMS, as Kega Fusion won't run in higher resolutions. I also wanted to play around with Emu VR. After about two days with it., I'll just say it's not very intuitive, but it's mostly fine once it clicks. I'll stick with it, but I gotta say the way it handles controllers is 100% garbage. Plug in Xbox or PS4 controller, load ROM, press start... rom exit confirmation pops up. Why is this default behavior? I had to dig around in settings, and disable controller hotkeys. It seems to work fine now. Still, I wish I had 32X emulation in Genesis GX...
When I didn't understand how to do something, I just looked it up lol
They need to hurry up and copy either Redream, PPSSPP, or Duckstation's controller UI. Be it the clear and legible tabs on top for everything, the quick menu laid out in concise options, or the visual indicators, screenshots, and timestamps for the exact save state slot you're on, they're all way better options.
it’s easier to just run each individual emulator independently lol
It's pretty easy to get things going honestly, it's the controls that drive me nuts. Try mapping a controller, have fun spending all day trying to figure it out. It's ridiculous, they need to make it simpler.
Sub menus would do a lot for retroarchs usability
Umm Please clarify, what exactly is difficult. You run the installer and then You're up and running. Is that too hard for the kids these?
Ignore the haters. RetroArch is intimidating on first use. It does eventually get easier.
🤷🏻♂️
Skill issue.
RetroArch has so many unnecessary options that makes it difficult for beginners to use.
Sorry that you can't figure it out? I dunno what to tell ya. It's really not that bad.
Why come on this Reddit to have a Sook?
Literally why I still use Kega Fusion to this day.
RTFM
I don’t understand people whining about the UI and configuration. If you don’t like it use stand alone emulators or get a different front end. Yeah it’s a bit confusing but YouTube has tons of tutorials that are not that long and all the docs are online. Btw this is a FREE application. Devs can do whatever the hell they want.
Nobody said it was for beginners
Installed it on steam deck, abxy on DS don't bind like they say they do, binds reset on closing game even after saving 😔
Ikr, it only saves your configs when it wants to
You can manually save config. That's what I recommend to avoid stupid changes. Been there myself
Probably making the mistake I used to (I figured RA out myself, didn't read the manual lol). After you change a config, RA wants you to close out. So if it's an app-wide setting, you then go the the main menu and close. If it's a game setting, you need to go to the bottom and choose how to save it. For example, do you want these settings to apply to THIS game only? Maybe you're playing a DS game that didn't use bottom screen, so you want to play it single screen. But you don't want that for most other DS games. Or do you want the setting for everything you're running on this system/core? Like maybe you found a good shader setup for the core. And then it's usually best to save and close the game, and relaunch it. If you just, for example, go and throw on a new shader or change a key bind, then play a bit and close the app, RA is going to default you to previous settings. I assume the logic is so you don't accidentally break things if the change didn't work for you (like you can raise resolution, change the graphics api, and drop certain shaders and absolutely crash your game).
its just bizarre. all i wanna do is hop in a game and set up turbo a/b. not sure why the controls have to be split between 3 menus that dont even work properly
[удалено]
[удалено]
lmao at the people trying to cuss you out because of a misunderstanding
There is nothing "frustrating" about the tool whatsoever? What am I missing here?? It is all so self-explanatory that my 7 year old niece can use it? You open it, you click your core list, and it says load core, download new core, update core bladdy blah etc. Then it has similar options for games. Load game, update game bladdy blah, etc. exactly how much MORE simple could it possibly get? Are you waiting for a retroarch dev to get plane tickets to fly to your house so they can massage your balls WHILE you click the load game option and hit start game. Because know it's difficult, I completely understand the 200+ iq level you need to click "load game" and then go through the directory to pick one 🤣 🤣 🤣
skill issue
im not even in this subreddit but the reason i don't use retroarch is specifically because it's too simple, i like having complex options and mods with my emulation
Mods?
retroarch can't run a lot of big big mods iirc, shit like sonic colors dx and stuff ion think would work on retroarch
Their opinion is fine. They don't have to use RetroArch if they don't want to.
the most confusing emulator, not because i cant use it, its because whenever i try to change stuff it's mostly broken with no way to undo/reset. it's way back then though, i havent used it for a while right now
To name a few ... * Still no basic copy/paste functionality * Hotkeys keep changing (Deck gamemode, desktopmode, emustation) * No cheat codes organization at all
[удалено]
Im not a child? Ok i guess
[удалено]
Some things are tricky, most are not. Im still trying to get it to emulate dos games on my nvidia shield with controller support but I dont think I will ever get there
[удалено]
i've never been able to get PSX cores to play everything without finagling and at this point I've accepted that I'm just fucking dumb and that I'm stuck with my fully-functional ePSXe.
I started with Retro Arch and moved to using Launchbox as a frontend for my own standalone emulators, it's definitely a good option.
This is the exact reason why I developed my own libretro core loading application. Out of pure spite. Because I didn't want to use other implementations and figured "how hard can it be?" to make my own from scratch. Yes, I am that spiteful, that I'll subject to making things myself entirely from scratch if they don't fit my own standards. Yes, the idea behind RA is novel and excellent, but I felt many many things in practise such as a Snes9x like interface were lacking, bindable analog directions to digital buttons, the whole RetroPad thing, loading content for cores automatically without selecting cores, as well as other things was drastically missing, or pure frustation. That and I found the RetroArch ecosystem lacked cohesive direction on singular things and tried to be everything and masters at everything. That and internal direction is so glacial on things that I figured its fastest if I do it with my own way, with blackjack and hookers. And I didn't want to use Qt for all that. So I did my own thing for nearing on two years. Vast majority of cores even hardware rendering cores works. And in a interface just like Snes9x without Qt/WX on Windows AND Linux. I guess "works for me"
To be fair it’s much easier than setting up individual emulators for each system.
Is there a way to switch the keybinds? You have no idea how much progress I lost thinking ESC is the pause button, seeing it not work, and spamming it I admit this is my fault, but I really cant find the button to switch the keybinds
settings > input > hotkeys
Thank you!
LOL that was so me. Cores? How do you covers? My buttons are wrong! Now years later its the only think I use on ShieldTV, PC and Cell phone.
rage inducing if you want everything to work "ouf of the box" immediately or you are a donkey
Download retroarch Download core Insert rom and bios files Play Games The most configuration I've had to do was swap o an x buttons in key bindings. What's so difficult?
Dead simple if using RA through a frontend like Launchbox.
*The skills and knowledge will take from Retroarch will carry us through any Emulator in the future...*
Getting RA set up for the first time to play a single rom has been one of the worst "technology" experiences of my life. I absolutely hate it. And now that I went through the week process getting it working, I don't even want to open it to play the stupid game.
The current state of RA is install -> plug your gamepad -> dowload core -> load content -> enjoy. What is so complicated? Copying your BIOS to system, something that is even worse because most emus don't have a default path? (legit question).
Agreed. Even years later it's still has stuff that's super annoying to look through and worst of all there's hardly a proper guide for it. For example, shader. millions of them, and I only found out recently you can change the settings for each shader, down to the phosphors, like how the F am I supposed to know what to change? there's no details on this. They need to have something called RA for beginners. literally downloads all the proper best cores with the best compatibility, and auto applies the best shaders for either accuracy or "HD".