Lordmonkus

Unfortunately right now they are having problems with their forums over on the Libretro site but I believe I have read about some of the same issues you are having over there before. If my memory is correct this is something they are aware of and working on, hopefully this is something that will be addressed in version 1.4.0. From my experiences with the nightly builds there does seem to be some work done on the controller side of things but of course I have no idea if they address the issues you are encountering.

No problem.

If there is nothing in the database you are going to have to add it manually. Right click each game and edit, the notes tab will be the description and you can add images into the appropriate folders within the Images folder.

No need to sync your folders one by one unless you plan on using the built in Retroarch lists and load games through Retroarch that way. In my setup I have a Roms folder will all the systems separated with all the roms for that system in their appropriate folder. Then in Retroarch in the Setting > Directory settings I set my File Browser Dir to my Roms folder. This way when I am quick testing my games I can simply load core, then load content and I am at my Roms folder quickly and from there it's easy enough to browse by system for my games.

I noticed n your video that you had all your roms in a single folder. Was this just for the purposes of the video or do you actually keep all roms for all systems in a single folder ?

Awesome job, love it.

no, you'll be fine

I have not had much luck with Reicast in terms of quality of emulation. It works for me just not very well, lots of glitches.

Ok, glad you sorted it out. As a side note though I highly recommend against using the Reicast core, Demul is a much better Dreamcast emulator along with NullDC if your system isn't powerful enough to run Demul.

Do your games work in Retroarch ? That is always the first place to start troubleshooting.

Yup. https://discord.gg/X3Cwsyw

What I did was mount the image using Daemon Tools, then opened ImgBurn and generated a cue + bin from that. Here is a video I did for Saturn games but the same should apply to Playstation games.

With music tracks that method should work but you may have to do all 70 one at a time, though there may be a way to do it automatically but I don't know how.

If you can mount the image with something like Daemon Tools you can re-dump the image to cue + bin using ImgBurn, I have done this a few times with success .

You can leave them in their own folders, I do it this way as well.

That's a feature to be added and I have been asking for it for a while. In the mean time though what you could do as a sort of workaround is create custom platforms for each region and import your roms from each region into them and have LB scrape them as N64. Not as neat and tidy though I know.

No problem.

Honestly I would just use Mame version 177 and see if that works with your rom set, it gives you great BGFX shaders and doesn't require the updated Capcom CPS-2 roms.

Ahh, cause the names shouldn't be messed up and need changing. I was just guessing at the Capcom CPS-2 games because with 178 they now require an update rom set that has .key files in them.

Are the games you are having problems with the Capcom CPS-2 games specifically ?

Don't feel bad, I was messing with my TV PC a couple of days ago and couldn't get my TurboGrafx and CD working. I forgot to add the .dll to the command parameter

No problem and welcome to Launchbox.

You can do this easily without RocketLauncher. You can either place a shortcut to BigBox in the Startup folder in your start menu or you can use a program to change your systems "shell". A program like bbSetshell found here: http://bb4win.sourceforge.net/bblean/ will do fine, it's free and easy to use. If you decide to go back to using the Windows shell, "Explorer" simply pull up the Windows Task Manager and run a new task and browse to bbSetshell and set it back to Explorer in there.

The only thing I can think of off the top of my head now is there is something messed up in the core config file like a bad video driver selected or some other setting that Retroarch is not agreeing with.