Is switching to Retroarch a good idea?

[AxelTerizaki]

Hello there.

I have somewhat a complex question regarding Retroarch.

Currently I use a lot of different emulators for different systems. Thanks to Hyperlaunch/Rocketlauncher, it's fairly easy to configure and get an overall good user experience even if I run into small problems here and there. So I'm wondering is Retroarch is something for me or if I should stick with my current setup that, well, just works. And as I work in IT, I learned the hard way that, if it's not broken, don't fix it.

I'm not interested in Retroarch's superior visuals/shader system for emulators. This is just not for me.

For controls, I've setup a standard Xpadder profile for my two gamepads, and configured emulator keys accordingly for each emulator. I understand Retroarch would kind of simplify the task but how exactly? how is it different from using Xpadder and setting up each emulator ? The Retroarch wiki isn't very helpful, I see it is compatible with Xbox 360 or Xbox One pads, how does that work ? How can it be better than my current setup ?

As for cores, I'm using MAME, MESS for a lot of vintage systems, Mednafen for PSX/PCEngine and a few others, SSF for Saturn, Nestopia for NES, etc. My problem is that I fail to see the exact state of emulators/cores for Retroarch. How compatible are they? Do they work well with Daemon Tools when it comes to ISOs? Which core should I use for which systems?

Which features of Retroarch really do work and are useful for a cab/arcade machine? (apart from the filters and such.)

From someone who doesn't follow Retroarch much, I see a lot of questions on the forum, which makes me think it's not easy to get it working (despite that excellent noob guide I saw the other day), and that people are having lots of random problems with it.

In other words, can someone sell me Retroarch? As in, convince me it's the emulation software I need?

[dougan78]

It is easier to have fewer emulators to update. That is why i started moving my stuff over to RA. I am not a shaders person either. Once you get the hang of RA it is rather easy to setup. Just takes some learning. That was the selling point for me anyway less moving parts. More uniform. Good luck.

[SIMPLYAUSTIN]

Currently I use a lot of different emulators for different systems. Thanks to Hyperlaunch/Rocketlauncher, it's fairly easy to configure and get an overall good user experience even if I run into small problems here and there. So I'm wondering is Retroarch is something for me or if I should stick with my current setup that, well, just works. And as I work in IT, I learned the hard way that, if it's not broken, don't fix it.

Soo true. and to be honest there is no right answer for this. Many people think that it does offer better emulation, some differ. To be honest it depends on the system. Some do better and some dont... although with many, you wouldnt notice. One thing I would say... its smooth. I know that when Im running from RA that the fade will blend right in, and then when I wuit I will fade right out as smooth ast butter. No flickers etc, black/white screens, popups etc. Also one you have it runnig, its just a few clicks to add all systems.

I'm not interested in Retroarch's superior visuals/shader system for emulators. This is just not for me.

True... although they are amazing for some systems. Again like the topic above. Its a resolution thing for me. I have screen flickers. I also like the scaling and the way I can choose where and how much of the screen I want to use. With or without bezels, its perfect for this.

For controls, I've setup a standard Xpadder profile for my two gamepads, and configured emulator keys accordingly for each emulator. I understand Retroarch would kind of simplify the task but how exactly? how is it different from using Xpadder and setting up each emulator ? The Retroarch wiki isn't very helpful, I see it is compatible with Xbox 360 or Xbox One pads, how does that work ? How can it be better than my current setup ?

Unless you want to use the Dolphin bar with real Wiimotes, I see no reason to use Xpadder at all. It gets rid of all the Emu's that require it as default. Set it up once and its generic on all systems, unless you want to rebind any others by choice.

As for cores, I'm using MAME, MESS for a lot of vintage systems, Mednafen for PSX/PCEngine and a few others, SSF for Saturn, Nestopia for NES, etc. My problem is that I fail to see the exact state of emulators/cores for Retroarch. How compatible are they? Do they work well with Daemon Tools when it comes to ISOs? Which core should I use for which systems

With the current module, all cores will be setup or should be setup by default. There are a few options for systems, but to be honest theres usually only one choice and its default. Saturn... well to be honest your better of with SSF still, RA uses Yabusse or whatever it is... it has issues. I still use MESS and MAME, I like the visuals on those. For me RA is best for 99% of console games that require a cart and also PSX. the rest is swept up by, dolphin, PCSX2, MAME, MESS, MODEL 2, SUPERMODEL, PPSSPP, WinUAE, NullDC and a couple of others.

Which features of Retroarch really do work and are useful for a cab/arcade machine? (apart from the filters and such.)

Controls are a big major part. Having no need for Xpadder is amazing! But its just the way it plays, you dont have to use filters or overlays etc... but that does not mean you dont have to play with the GFX on each system. Its hard to explain, but its just much more smoother, no flickers or issues.

From someone who doesn't follow Retroarch much, I see a lot of questions on the forum, which makes me think it's not easy to get it working (despite that excellent noob guide I saw the other day), and that people are having lots of random problems with it.

It sounds more complicated than it is. But for the core systems like NES, GB, GBA, MEGADRIVE, SNES etc etc etc it plays almost out of the box. Problems is when you try to get MESS or some of the more obscure disc systems to work..... than you can get issues.

In other words, can someone sell me Retroarch? As in, convince me it's the emulation software I need?

Im not saying its the digs dinner, but I will say that it is the best way to go. Even if its just for the core systems. Its worked on daily so emulation just gets better. Yes, it has a long way to go, but it has great foundations. You dont have to get rid of your old Emus, just add this one woth them. More emus the better. I like to add this for everything I can and then if any systems aint covered but it or games have issues play it on another Emu. Systems like N64 need every emu they can get at the moment to get everything to run.

[Styphelus]

"I know that when Im running from RA that the fade will blend right in, and then when I wuit I will fade right out as smooth ast butter. No flickers etc, black/white screens, popups etc. "

My fade screen flickers just before it starts a game in retroarch. I always assumed it was the screen switching resolutions. So this is not normal?

[SIMPLYAUSTIN]

Not at all no?? It does my head in and I have never had any issue with flicker with RA. Hmmmm that is interesting... I run mine at Core resolution standard, but then I "custom resolution" to make them fit screen/bezel.

[AxelTerizaki]

Thanks for your answers dougan and austin!

I agree that less emulators is better. I like using MESS for a lot of vintage systems as it's easy to setup.

So if I understand correctly, controls are the best selling point. I'll have to take a look into it.

As for systems it works with, I should consider everything that works with carts to be okay, but not systems with CDs?

Also, how do you update cores individually? For instance there's a new MAME version, how do I upgrade just that core? in the Libretro.com site's download section I only see the whole cores package, but there is no repository anywhere (or I didn't look close enough?)

[SIMPLYAUSTIN]

For CD based systems, I only use it for Playstaion. Saturn does not emulate properly and it can be fussy about file types on ISOs. So to be honest I do not bother. For MAME... I use MAME. Its emulation in perfect so I dont want to mess with it. I have never tried it in RA so to be honest I couldnt comment.

You can update cores from their nightly builds if you wish, or wait for released full releases. I tend to keep the cores as they are unless major releases come out. As my cart emulation is perfect bar N64 Im happy to keep with my cores until a major update is released. Only time you nrealy need to update cores is if they get something working. Like for example, Amiga is emulated in RA.... but I dont know anyone who has it running hehehe. When that core is updated and stable I will just drop that one in and give it a try. its that easy

[Styphelus]

Not at all no?? It does my head in and I have never had any issue with flicker with RA. Hmmmm that is interesting... I run mine at Core resolution standard, but then I "custom resolution" to make them fit screen/bezel.

That's weird. I run mine at core resolution as well and it still flickers. Now this will be bugging me until I find out why it's doing this.

I switched to retroarch for most systems as well, mostly for simplicity and controls. It's so easy to get hyperspin up and running. However note that as far as I know there's no way to switch disks yet for games that require more than one disk. This is true for 3DO, Sega CD, PS1 and so on...I'm sure there will be a future fix for this but for now I don't know how you would go about playing multi disk games.

For Mame I use Mame. For Neo Geo AES, Intellivision, Colleco Vision, Atari 5200 and 7800 and a few others I use Mess simply because Retroarch does not save states when using the Mess core (at least it didn't 2 months ago).

For Sega Saturn, you have to use SSF. Don't use retroarch for that.

[marxkemp]

I agree with all of the above posts

[Fromlostdays]

I get better performance out of RetroArch than I did with espxe or project 64 / mupen. But I think it's really hard to say that that will be uniform across the board, maybe because of different hardware/software. My inclination is to say yes, switch, but I also agree if you're like 100 percent set up and happy currently, the above posts are absolutely correct. Having said that, RetroArch is an emulator that is worth having anyway, even if just as an alternate, so I'm going to go ahead and conclude that you should indeed set it up, but maybe not switch everything to it.

In terms of the above posts about flicker, there's three things you can check:

Try Launching in Fullscreen Windowed

Set RetroArch to launch at your native desktop resolution

Lastly, there's a way to turn off the command prompt window (I think its in core options) that may eliminate the flicker.

Edit: I want to amend that it might not be the best TIME to start messing with RetroArch. Lots of changes. You may want to wait until v1.1 if you decide to at all.

[Awakened]

I switched to retroarch for most systems as well, mostly for simplicity and controls. It's so easy to get hyperspin up and running. However note that as far as I know there's no way to switch disks yet for games that require more than one disk. This is true for 3DO, Sega CD, PS1 and so on...I'm sure there will be a future fix for this but for now I don't know how you would go about playing multi disk games.

You can easily swap discs in PS1 by creating an .m3u file with each disc's .cue filename inside, loading that instead of the .cue, then using the open disc drive and swap disc hotkeys during the boot screen or when prompted to switch discs by the game. The process of creating .m3u's is described on the wiki here: http://wiki.libretro.com/index.php?title=Beetle/Mednafen_PSX#Usage

[suspendedhatch]

Wait for v1.1? That's going to be a long long wait. It was expected to be out in December, not much word since then, but they've started a new project that is a front end called Lakka that looks like PS3. Why finish existing projects when you can just keep starting new ones?

I'll be happy when they fix key binding on the Mac version.

There's no reason to delete your existing emulators. You leave them set up, then set up RetroArch as an alternative emulator. If it works out for you, set it as your preferred emulator and leave the others as backup. That's my current set up.

[Styphelus]

Try Launching in Fullscreen Windowed

Thanks. That fixed it. Much better now!

[DrMaxwell]

I have everything setup for testing purposes. I use UME (MESS and MAME together) in the GroovyUME build (switches resolution and refresh rates to accurately emulate the system you are playing whether it is arcade/computer/console based). I test out new systems that I've added to my custom AHK in the MESS environment if emulation is firstly supported, then GroovyUME, then finally I'll add this to the UME core in RetroArch.

I use RetroArch for my windows 8.1 laptop and GroovyUME for my windows xp 64 Taito Egret 3 candy cab with arcade monitor.

RetroArch is great for its intended HDTV audience. GroovyUME is more accurate for its CRT audience.

I completely agree with awakened on the Nintendo 64 emulation being better in RetroArch than the standalone P64/ Mupen64 emulation.

TLDR: set up both, test, then leave it and play.