Zombeaver

Yep, that kindof confused me too the first time it happened. It basically refreshes when you change platforms.

This has been discussed before and it's been denied before. The reason being is that the general consensus is that we don't want LB to mess with filenames for the (obvious) potential issues that could create.

You can change it. Just right-click on the game you want to change and go to edit. You'll see the platform listed in the upper right side of the metadata. Just click the drop-down and change it to something else. When you change platforms in LB it should be in the one you changed it to and no longer in the one you had it in previously. I'm not sure if you can do this in bulk as I've never tried, but you can definitely do it for individual games as I've had a few instances where I accidentally imported something as either the wrong platform or with no platform and changed it after the fact.

Okay, here you go. This is pretty darn close.

It should be noted, however, that you will very likely not be able to see it regardless once it's actually in BB because it's going to be scaled down.

If you use Photoshop you could just make one that looks like that using pattern overlay. I can make one if you want.

Yeah, #1 it will only auto-fill if your emulator entry is using the specific name that LB is looking for which, in this case, is just "Retroarch" not "Retroarch NEC" etc. and #2 even when it does auto-fill, the cores it uses aren't always correct (they're outdated). Any time you add a new platform that you want to use RA with, you need to verify that the correct associated platform is in the associated platform tab and that it's using the correct core dll.

You still need to specify it for TurboGrafx-CD. You can't just have an associated platform of TurboGrafx-16 and it just work for both. You have to tell LB which core to use for which platforms (even if it's the same core between them). You have to add in an associated platform of NEC TurboGrafx-CD and then put the core dll in (and add that as the emulator to use for the relevant games in your library). Then it will work.

Still need to see a screenshot with the core for TurboGrafx-CD specifically. Your other one only showed TurboGrafx 16.

What @DOS76 said too. Gotta make sure you don't have a platform of TurboGrafx-CD and an associated platform of NEC TurboGrafx-CD or something.

@shinra358I don't see TurboGrafx-CD in your list though. Scroll down so I can see it. Mednafen PCE Fast should work for both TG16 and TGCD though.

@mssngr just FYI, I will be trying out those settings for The Getaway and, assuming everything's okay, will include them in the next batch of configs. I've just had a lot of stuff going on IRL the last couple days so I haven't had a chance to work on these.

They definitely work. It's probably a problem with your core dll in the associated platform tab. Post a screenshot of your associated platform tab for RA.

Not sure how I hadn't heard of AURORA before, but I really dig it.

The assignments in CCS64 itself you don't need to mess with. The A button (on a 360/Xbone controller) will be fire by default. I'm not sure about an F310 but I believe it uses Xinput so it should be similar. I use AutoHotkey to assign some CCS64 functions to the controller. I linked that above, but here it is again.

It does: That's exactly what it's telling you. If you don't have an associated platform in the associated platform tab, it doesn't know what platform(s) the emulator can be used with. In case anyone is confused about this, for future reference:

No. It blanks out the associated platform if you do it first. You need to fill out the first tab first, then associated platforms.

Yeah, you have to add an associated platform on the associated platform tab. Otherwise it's not going to know what platforms are relevant for that emulator. No, as I said, it does not matter if it's in the list or not. All those are are suggestions. The error you're receiving is because you're not specifying an associated platform in the associated platform tab. You need to add Commodore 64 and check the box for the default emulator. This is shown in my screenshots above.

No problem! CCS64 is a fantastic emulator. It's really not bad to setup. Don't get hung up on having to place the emulator in a specific place or having it show up automatically in a list - one of the great things about Launchbox is how flexible it is. You can put your emulators wherever you want and name them whatever you want when you make an emulator entry for them in Launchbox. Launchbox just has a list of known emulators that it kindof auto-fills parameters for, but this isn't a be-all-end-all. If it's an emulator that isn't one of these previously known ones, you can still add it manually. All you have to do is browse to the emulator's exe, add any default command-line parameters if necessary (none are necessary in the case of CCS64), and add in the relevant platform to the associated platforms tab (Commodore 64 in this case). You can also check the box to make it the default emulator for that platform in the associated platform tab.

Also, don't watch that tutorial. It's got a good deal of bad information in it to be honest with you (like importing .nib files which do absolutely nothing in this context). It's not complicated. Make a new emulator entry in LB, browse to CCS64's exe, name it CCS64, add Commodore 64 as the associated platform. That's it. You're getting hung up on the fact that it's an emulator that LB isn't already aware of and doesn't have a link to download the emulator or default parameters to go with it - this is true for plenty of emulators. There are certain ones that are already known/suggested in LB and plenty of others that aren't. If they aren't, there's nothing stopping you from adding them by hand.

@C64Crazy You can put the emulator wherever you want, but you'll need to create an emulator entry for it in Launchbox. It doesn't have to be one "known" to Launchbox beforehand. Some emulators have some default parameters if it's one that's already known but, if not, you can still add it anyway. Just name it whatever you want, add whatever parameters you want, and direct it to the emulator .exe. I use CCS64 myself. My entry for it looks like this in Launchbox: You don't have to add anything to the AutoHotkey Script page, but I've added some commands to allow certain CCS64 functions to be mapped to a 360/Xbone controller: I've got more details on the full script here if you're interested.

New configs: Alter Echo Sphinx and the Cursed Mummy Vexx Whiplash

I think it may be an issue with a scaling setting in Windows. This should be addressed in a later update to the plugin, but currently it's designed for 100% scale. You have to set it to 100% and then log out and back into Windows. You can also just use Y or N keyboard keys in the meantime for "Yes" and "No" respectively.

New configs: Legend of Kay The Mark of Kri Rise of the Kasai We're past the 150 mark now