Jump to content
LaunchBox Community Forums

SameBoy RA core not appearing as an option.


WraithTDK

Recommended Posts

3 hours ago, WraithTDK said:

     I've got the SameBoy core configured in RetroArch, but when I go into manage emulators > RetroArch > Associated Platforms and select GameBoy or GameBoy Color, the core does not seem to be appearing as an option. Am I missing something?

Just downloaded that core and it shows in LB.

Try going to the bottom of your list of Associated Platforms and adding Game Boy there and see if sameboy_libretro pops up when using a new cell.

Link to comment
Share on other sites

9 hours ago, WraithTDK said:

No luck. Even tried closing/re-opening LB and then adding Nintendo Game Boy to the bottom of the list again. Sameboy just isn't in the core list.

You have something strange going on here, i have always used the sameboy core, and of course it shows and works just fine here.

image.thumb.png.c612c2c4a59d62321bbd4918a8db6d04.pngI would check your Retroarch/cores folder to make sure the core is indeed there, the dropdown in Launchbox for selecting cores is just a list of what is in your Retroarch/cores folder. Also what version of retroarch are you using, as well as is it the zip or installer version?

Link to comment
Share on other sites

Quote

the dropdown in Launchbox for selecting cores is just a list of what is in your Retroarch/cores folder

OK, that helped me figure out the issue, and I think this probably qualifies as a bug. I changed the cores folder in RetroArch, under settings > directory > core. LB is still looking under the default directory. Once I copied the contents of what I'm currently using as my cores folder to the original default, and then restarted LB, SameBoy appeared as an option in the emulators menu.

 

      So I guess the work-around for now is to use the default cores menu. I guess in the long run that's probably better for performance anyway, the data folder I've been using is on a secondary 4TB mechanic drive, while the default location is on an m.2 ssd. I relocated the mechanical drive to everything retro-gaming; but the cores folder isn't that big; so no biggy.

Link to comment
Share on other sites

1 minute ago, WraithTDK said:

and I think this probably qualifies as a bug.

Thats not a bug, Launchbox has no way of telling that you changed the folder where your cores go. Also no one does that, its just you. :) Any reason why you changed the folder, as you are going to have issues with Launchbox now unless you use the default location.

Glad you figured out the issue though.

Link to comment
Share on other sites

If you were to type -L "DriveLetter\FullPathToCoresFolder\sameboy_libretro.dll" that might launch from where you had moved it to but I've never tested it so I'm not actually sure that if something typed in there would take precedence over the drop down or not but it may. While it isn't a bug if typing that in there doesn't supersede what is in the drop down then yes that may not be a scenario that LB is equipped to handle. I personally don't think I ever heard of anyone moving their cores folder so it is not something that probably would have been considered.

Link to comment
Share on other sites

1 minute ago, neil9000 said:

Thats not a bug, Launchbox has no way of telling that you changed the folder where your cores go. Also no one does that, its just you. :) Any reason why you changed the folder, as you are going to have issues with Launchbox now unless you use the default location.

Glad you figured out the issue though.

LOL!

 

The paths you set under directories have to be saved somewhere. I figured that they were stored in a config file that LB read from. I changed it for consistency. Like I said, I have a 4TB mechanical drive that I'm using as my "retro gaming drive." I'm keeping 1.65TB of assorted ROMS there, as well as a thousands of digital copies of various old-school gaming publications (Nintendo Power, Game Pro, etc.); and Launchbox (because I have an EmuMovies Pro account, and once I have everything set up to my liking, I'm going to download all available media for for everything in my collection, movies included). My system drive is only 2TB (the cost per TB of high-quality SSD vs. high-quality Mechanical is ridiculous), so I'm just keeping everything there. So I figured why not keep RetroArch's defaults there, as well. Plus it's nice having things like that on a second drive in case I ever need to reload the OS (which, to Microsoft's credit, I haven't needed to do in several years, which is a major improvement from the 9X/XP days, when I did it annually as a form of routine maintenance).

Link to comment
Share on other sites

LB doesn't have the ability to change the path from the default cores folder in the drop down its not a bug at all its just a very niche use case and it wasn't coded to consider it. An easy solution to get around it would be to not name your RetroArch emulator RetroArch in LB then it won't auto fill and you would have to come in and manually type in all of your paths to your cores folder using the full path from the mechanical drive.

Link to comment
Share on other sites

3 minutes ago, DOS76 said:

If you were to type -L "DriveLetter\FullPathToCoresFolder\sameboy_libretro.dll" that might launch from where you had moved it to but I've never tested it so I'm not actually sure that if something typed in there would take precedence over the drop down or not but it may. While it isn't a bug if typing that in there doesn't supersede what is in the drop down then yes that may not be a scenario that LB is equipped to handle. I personally don't think I ever heard of anyone moving their cores folder so it is not something that probably would have been considered.

Hmm. Well, IMO, it's something that should at least be considered. It might not be common, but at the same time, it's not like I'm doing something outside the scope of what RA was designed for, since there's an actual in-menu option to do this (it's an option under settings > directories). and I wouldn't be surprised if others did it. I figure that path has to be stored somewhere, right? I don't know the first thing about programming, so I'm not about to tell anyone their business, but it doesn't seem like it'd be that difficult to read whatever file that information is stored in.

Link to comment
Share on other sites

.

4 minutes ago, WraithTDK said:

I figure that path has to be stored somewhere, right? I

No LB allows RA to handle its directories the only path LB has stored is the path to your RA.exe then its set to automatically use the command line to call from the cores folder but that isn't stored anywhere it just assumes that you are using the default path in RA

Link to comment
Share on other sites

1 minute ago, WraithTDK said:

I don't know the first thing about programming, so I'm not about to tell anyone their business, but it doesn't seem like it'd be that difficult to read whatever file that information is stored in.

Launchbox doesnt read any config files for any emulators, it doesnt need to. All Launchbox does is pass the rom file to the emulator via a commandline and the emulator loads it and uses its own settings. Launchbox never reads or overrides settings of the emulator, nor should it to be honest. Launchbox is a launcher, it tells the emulator what rom to load and from where, nothing more.

Link to comment
Share on other sites

Okay with a quick test I have found that if you type in a different core next to the one in the drop down that LB will launch the one typed in over the one in the drop down.  So basically you can manually do what you want already in the program and type in the path to your cores folder no matter where it is located.

Link to comment
Share on other sites

8 minutes ago, DOS76 said:

Okay with a quick test I have found that if you type in a different core next to the one in the drop down that LB will launch the one typed in over the one in the drop down.  So basically you can manually do what you want already in the program and type in the path to your cores folder no matter where it is located.

Nice! Well, anyway; if anyone comes here saying their cores aren't in the right place, now we know the likely culprit. Thanks for the help. I probably would not have figured it out without the info about how LB finds the cores.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...