Zombeaver

@cZ8tL So far that that assumption has held true - all the ones that did work when converted to G64 format via nibtools are working natively in micro64 and all the ones that didn't aren't. That, in and of itself, is impressive though. I have to say, micro64 looks pretty impressive so far, albeit not particularly user-friendly; which isn't helped by seemingly zero documentation for anything other than a changelog and a forum that's almost entirely empty. It's basically a barren wasteland haha. The longest thread is a guy asking "Where's the manual?" and the developer saying there isn't one, but maybe at some point (and it's from 5 years ago...). The amount of video options is quite impressive (the most extensive I've ever seen in fact) and the video and audio accuracy seem very good. It definitely seems like one guy's side-side-project though. Granted, the same could be said for CCS64 but it's got 20 years of development behind it.

Fair enough; that's not one I have any experience with. They don't work with Hoxs64 though (or VICE or CCS64 for that matter), and Hoxs64 is what's used in the video. And my assumption is the ones that do work in micro64 are probably the same ones that work when converted to G64 format, which, based on my testing, isn't a whole lot of them. I'm kinda curious about micro64 now though, I'll have to check that out. I've still got my original nibs and conversions that I used for testing so I'll do a comparison. Huh? I'm not entirely sure what you're asking here. If you're referring to the fact that it's called "Amiga" instead of "Commodore Amiga", that's just because of how it's listed in the LBGDB. You can change it to whatever you want in your own library if you prefer something different, and just tell it to "Scrape As: Amiga".

You'll get out of it proportionately to what you put into it, like anything else. I've already done the actually hard work of researching, testing, experimenting, more researching, more testing, digging through obscure multi-page forum posts and Github and Amiga programming wikis until the wee hours of the morning... and then assembled all of that in a precise, step-by-step package that walks you through everything you need to know and do, including all the things that you might need to know and do even if you don't realize it yet. Short of me coming over to people's houses and setting it up for them, there's not a whole lot more I can do. If watching and following instructions in a video is too much work, then by all means don't. Only you can determine whether or not it's worth it to you.

I've used quite a few different ones over the years, like FRAPS, Xsplit, and awful junk like Camstudio, Camtasia, and Xfire Video Recorder. I like both OBS and Nvidia Share quite a bit. I probably end up using Nvidia Share more commonly just because it's a bit more streamlined but OBS can deal with situations that Nvidia Share can't and it does have more features (that may or may not matter to you); and obviously there's the fact that you can use it with non-Nvidia cards. They're both really good though.

That all sounds fine although... how are you planning on handling the Amiga stuff? Those aren't as simple as just dumping everything in like the other platforms. If you need help on Amiga, take a look at the tutorial I did over here.

Amiga, Vic-20, and C64 are definitely all separate platforms. I'm not familiar with the Plus-4 honestly, but it's certainly something separate.

Well as I said, I don't know why you'd split them into separate platforms - they're all going to the same emulator, with the same command line parameters, and they're all C64 games. I'm not sure why you'd need/want them split up, in any practical sense. Again, in case I wasn't explicit enough about it - do not import PP (nib) files into your library. They DO NOT work in emulators. You can delete them or use Nibtools to convert them to G64 and test them out (and you'll find most of them don't work). I would dump all the C64 and C64 (Tapes) into your library at the same time, and indicate that both of them are Commodore 64 games. You can make them separate platforms, but as I said I don't know why you would. There might be some duplicates (typically No Intro is good for avoiding that but I'm not sure if they have duplicate versions of the games in both disk and tape format). This might be something that the new auto-combining feature will help with. It'll depend on how they're named.

There are a couple problems with that tutorial. 1) It doesn't make any mention of cartridge format games (honestly this isn't a huge deal but the video seems to imply that your choices are just tape or disk, which isn't accurate) 2) "PP" stands for Preservation Project. These are 1-to-1 dumps of original, official C64 disks, including all of the original copy protection. The intended purpose of these files is to have a backup of the original game disks which can be duplicated onto new physical diskettes via transfer tools that were simultaneously released for that purpose. Nib files do not work in emulators (edit: other than micro64, and only some of them even then). I have no idea why you would want these in your library. They do nothing within this setting. I know these are commonly distributed on a number of well-known emulation sites, but I've never understood why - unless you plan on breaking out your spare 1541 disk drive and some blank 5 1/4 floppy disks, this isn't going to help you much. There are conversion tools (called Nibtools) that will convert them into an emulator-usable format (G64) but even if you do that only 30-40% of them will actually be usable because of the copy-protection. These are the supported file formats for VICE, Hoxs64, and CCS64; the three most common/best C64 emulators out there. You'll notice that .nib isn't supported by any of them. To my knowledge, no emulator does (edit: other than micro64). VICE Supported File Formats X64 (preferred) or D64 disk image files; Used by the 1541, 2031, 3040, 4040 drives. G64 GCR-encoded 1541 disk image files P64 NRZI flux pulse disk image files D67 CBM2040 (DOS1) disk image format D71 VC1571 disk image format D81 VC1581 disk image format D80 CBM8050 disk image format D82 CBM8250/1001 disk image format D1M FD2000/FD4000 DD disk image format D2M FD2000/FD4000 HD disk image format D4M FD4000 ED disk image format T64 tape image files (read-only) P00 program files CRT C64 cartridge image files Hoxs64 Supported File Formats FDI D64 G64 T64 TAP P00 PRG CRT CCS64 Supported File Formats CRT PRG P00 T64 D64 TAP G41 G64 The format that I would recommend people use is D64 or G64 (disk formats) followed by TAP or T64 (tape formats). Disks formats are definitely preferable if you're using CCS64 because of the (really awesome) Maximum 1541 Speed feature, which only works on disk formats, but it doesn't really matter one way or the other on VICE or Hoxs64. Beyond that, I'm not sure why you'd want to split them up into separate platforms in your LB library considering they're going to be directed to the same emulator with the same command-line parameters regardless, but it's not going to hurt anything I suppose. I've been in the process of working on a CCS64 tutorial video for the last couple days, but it's probably still a week off at this point.

Thanks! Still not quite sure what I'm gonna do with any of this stuff yet.

The PSO one should work. The Star Wars Arcade one is a little bit too spread out/vertically-oriented. You're not going to get a whole lot in the horizontal slice of the clear logo. Doom is better but you're gonna be left with either just Doom Guy by himself or the demons below, not both.

I'm assuming by "Bust a Move" you mean the Japanese version: "Bust a Move: Dance & Rhythm Action" and not actually "Bust a Move" (Puzzle Bobble) right? That would be a very weird combo otherwise haha Jet Moto 2 Championship Edition is one of the few instances where a Greatest Hits edition was actually different from the original release. Championship Edition has fewer racers on each track but it runs a lot smoother. Great game! Sorry... random tangent... carry on.

Sure, that's no problem. I'll add it to the to-do list.

Yeah I added my entire emulation folder to my Avast whitelist a long time ago because of this kind of crap.

Love it dude! I'd love to do some game artwork. Right now it's just some framed movie posters for me. My cat likes to "help" while I'm working on stuff.

@JJLR when you say that it's not starting a game and it's showing "just the emulator" is it actually showing the PCSX2 UI when you try to start a game? Because that shouldn't be possible with --nogui in your command line parameters...

The dev versions are fine too, I'm not debating that, all I'm saying is 1.4.0 definitely works via Launchbox because that's what I'm using and telling someone to use a different version as if that's going to fix it doesn't make much sense to me; especially since 1.4.0 is working for him outside of Launchbox. @JJLR I'll still need to see the Launcher section of that game entry in your library.

You don't have to use the buildbot version. I'm using 1.4.0 stable and it works just fine...

Can you show me the "Launcher" tab for that game as well please?

My assumption is it's just putting them in alphabetical order (and "b" is before "u"). As far as doing it automatically, I'm not sure - but worst case scenario you could change the default by going into additional apps, going to the (usa) one and pressing "make default".

Ah I see what you're saying now - they're actually in the install directory. I thought these were some kind of extras like the Avatars, Manuals, etc. that you can get from their site. Having to actually install everything to get the .icos is kindof a nightmare I've got about 250 games on GOG but probably only 40ish installed. Yep I tried it and I see what you're saying. That's unfortunate. IrfanView is a great bulk image converter but this is kindof a weird situation and it seems like it's only pulling the smallest image. I actually tried opening one in Photoshop out of curiosity but it wouldn't even open it - it doesn't seem to know what to do with it. I'm wondering if maybe it needs an additional plugin or something to open them. Hmm...

I think that's pretty rare though - honestly I think I'd probably just enable that on a per-need basis via custom command line parameters rather than just applying it to everything (especially in my case since I'm using custom command line parameters to indicate a game config for every game anyway). To each their own though.

I'm not sure - it looks normal. Here's what mine looks like and a game that's using it. I'm using custom command-line parameters in the last screenshot because I specify custom configs for every game. The --fullscreen and --nogui parameters are correct though. I'd have to see screenshots for these same sections for your setup to see if I see any problems but what you've shown so far looks normal.

I just tested and it worked I used Bard's Tale which was 3 files, separated as (Disk 1 Side A), (Disk 1 Side B), and (Disk 2 Side A).

Okay, no problem. I'll test it tonight and see what happens Like I said though, it doesn't really matter (in the case of the C64 anyway) because nearly all multi-disk games won't actually start unless they're started with Disk 1 Side A (so an additional app for additional disks doesn't really do anything in that scenario). I usually just recommend that people only import Disk 1 Side A because it's the only one that'll boot. This should, however, help people not have a huge mess of duplicate entries on their initial import even if they don't pick and choose to only import Disk 1 Side A though, so that's still nice!