Genesis/master system same core

[paulwillingham]

trying to set up master genesis_plus_gx core for master system/genesis in retroarch so i can set a different onscreen overlay for each but since they both use the same core i cant seem to do it. does anyone know how?????

[DOS76]

You will have to setup two emulators for Retroarch configure the one to use Genesis overlay for the genesis_plus_gx core and the other to use the SMS overlay and then if you wanted a Sega CD and Gamegear overlay you would have to set up 2 more emulators. I know it isn't really the greatest solution but its pretty much all that we got at the moment.

Edited September 2, 2017 by DOS76

[neil9000]

Yeah, unfortunately this is just a limitation of the way retroarch currently works, there is no real good way around it apart from duplicating your retroarch and adding it to launchbox under a different name. Or you could use the picodrive core for the other system.

[paulwillingham]

Just been trying this and it dosent work since they are still using the same "CORE"

[paulwillingham]

12 minutes ago, neil9000 said:

Yeah, unfortunately this is just a limitation of the way retroarch currently works, there is no real good way around it apart from duplicating your retroarch and adding it to launchbox under a different name. Or you could use the picodrive core for the other system.

i cant believe whoever programmed this core never put a system in place so you can do this this is just ludicrous!!!!!

[DOS76]

yeah its either per core or per game no per system for multi system emulators it would be a nice addition for features like this but really the RA guys aren't really concerned with you using the program outside of their UI ie with LB

 

Edited September 2, 2017 by DOS76

[Charco]

Not really, you have a particular use case. ekeeke created Genplus GX to be an emulator for all these systems and the Libretro core is that emulator.

If you set up two instances of RA you can do exactly what you are looking for. Simply point LaunchBox to RA install number one for Mega Drive and set it up the way you like it and point it to RA install number two for your Master System set up.

Edited September 2, 2017 by Charco

[neil9000]

This method works just fine, here is how you do it. Download a fresh RA or just copy and paste your current one, then go to manage emulators in Launchbox and add a new emulator call what you like then point to the second Retroarch .exe. Then go to your assoiciated platforms tab and make sure it has the correct core for the system, then click your master system in the left bar click a master system game then ctrl a to highlight them all, then right click and choose edit. In the first dropdown choose emulator, then the second box choose your second Retroarch. You will of course have to set your options and overlay and save the core override like like i described in your other thread.

[paulwillingham]

29 minutes ago, neil9000 said:

Yeah, unfortunately this is just a limitation of the way retroarch currently works, there is no real good way around it apart from duplicating your retroarch and adding it to launchbox under a different name. Or you could use the picodrive core for the other system.

i cant believe whoever programmed this core never put a system in place so you can do this this is just ludicrous!!!!!

 

12 minutes ago, neil9000 said:

This method works just fine, here is how you do it. Download a fresh RA or just copy and paste your current one, then go to manage emulators in Launchbox and add a new emulator call what you like then point to the second Retroarch .exe. Then go to your assoiciated platforms tab and make sure it has the correct core for the system, then click your master system in the left bar click a master system game then ctrl a to highlight them all, then right click and choose edit. In the first dropdown choose emulator, then the second box choose your second Retroarch. You will of course have to set your options and overlay and save the core override like like i described in your other thread.

have done this and is now working thanks guys!!!!!

[Zombeaver]

There's no reason to duplicate the entire RA folder, that's total overkill. As I said in the other thread, I've got instructions on how to do this here (click on the "Zombeaver replied to" part to go to the right comment):

Since then I've expanded this to cover Genesis Plus GX and FBA too.

[JABlekken]

Is this also possible trough Rocket Launcher?

[LogicalEgo]

On 9/2/2017 at 9:29 AM, Zombeaver said:

There's no reason to duplicate the entire RA folder, that's total overkill. As I said in the other thread, I've got instructions on how to do this here (click on the "Zombeaver replied to" part to go to the right comment):

Since then I've expanded this to cover Genesis Plus GX and FBA too.

This is actually a really awesome work around and solution since you can literally drag and drop your configs every time you update RA.

[Zombeaver]

2 hours ago, keltoigael said:

This is actually a really awesome work around and solution since you can literally drag and drop your configs every time you update RA.

Yep. I don't have to update anything in LB with that. I don't even update any paths in LB because I always keep my current version of RA in a folder of "Retroarch", then when I need to update to a new version, I make a backup copy in a folder of "Retroarch v1.[whatever]" and just copy (and overwrite) the new .exes into the existing Retroarch folder. That way nothing changes in LB at all whenever I update.

[LogicalEgo]

Normally I do the same, but wanted to test the newest version of RA and its features since I was far behind. Happy to say I was able to bring over all my configs files and everything works. Moving forward I will be doing the same of backing up and updating .exe's in the future.

[gStAv]

Old topic but I ran into this problem aswell, was looking at the cores used from the associated cores and found one "Genesis GX Plus" which was assigned to both but dropping down there was also a "Genesis GX Plus SMS" so using this you get two of the same core = separate control mappi g and bezel for the core. Don't know if this is a lunchbox feature or RetroArch, didnt found anything about this SMS version on Google. Works great though

[neil9000]

4 minutes ago, gStAv said:

Old topic but I ran into this problem aswell, was looking at the cores used from the associated cores and found one "Genesis GX Plus" which was assigned to both but dropping down there was also a "Genesis GX Plus SMS" so using this you get two of the same core = separate control mappi g and bezel for the core. Don't know if this is a lunchbox feature or RetroArch, didnt found anything about this SMS version on Google. Works great though

Retroarch has "content directory overrides" these days for such use case, it will save the changes you made to the games that are loaded from the same folder as the currently loaded game. So as long as you have separate megadrive/master system/game gear rom folders, which you should, then the content overrides is what you want.

[gStAv]

Cool, sounds even easier, thanks. But do you know the differens with the SMS version ot the Genesis GX Plus core? Still thinking the sms is more suitable for SMS due to the naming. Would be neat to know if there's any difference from the standard Plus version 

[Zombeaver]

I want to say that it was actually just created specially for the sort of use case you're using it for before content directory overides were a thing. As in it was just split off to provide an alternate core for core overrides for a different platform, not because of any actual differences in the core itself. I know they did that a while back, I don't know if they're still otherwise indistinguishable now (they probably are though).

[gStAv]

Thabks for the elaborated answer Sir. I actually took the SMS core route, easier to see the setup later on as I manipulate config files per system + games with remaps. Feel it's better to hard code stuff when having a cab

[Zombeaver]

One isn't any easier or better than the other. They're effectively the same thing. It's creating a .cfg either way, it's just creating one in one folder or another. If you used a content directory override it would create one at config\[core name]\[folder name].cfg. If you used a core override it would create one at config\[core name]\[core name].cfg. The backend is identical, it's just a different name/location depending on what you're using.

The only time when content directory overrides aren't really viable is if you're in a situation where all your games are in their own subfolders (because the overide matches, as the name implies, based on the folder that the content is located in), which most people typically only do for disc-based games if anything.