JoeViking245

Me? Hardly ever. But the moment that [hypothetically] gets changed to a Yes/No only option, someone's going to say... "When I'm viewing my playlists and I want to remove a game from my collection, I have to remove it from my playlist, then switch to platforms view, go to that platform, find the game and then also delete it from there. Why can't I just be able to remove it from my collection when viewing it in the playlist?"

Good choice. Note, as of release 0.284: There are 644 MAME Arcade CHDs Of those, 361 are Parent ROMs Of the 361, only 57 are considered "Working" That said, I recommend always checking the Arcade Database first before messing with CHDs. Example: CarnEvil

Most likely you don't have the [also] required CHD file for it, or MAME can't "find it" when launching. When a game is loaded, can you press "5" on the keyboard to 'load a coin'? Then press "1" to start the game?

Having it "just remove it from the paylist" without any type of message confirmation is asking for trouble. So a popup message box is necessary. The current message that comes up is two-fold. (though not explicitly stated) Do you wish to remove game "xyz" from the playlist? No. Press Cancel Do you want to also permanently remove the game from your collection? Yes. Press Yes The game is removed from your collection and is removed from the static playlist. No. Press No The game is only removed from the playlist To have it only confirm removing it from the playlist, you'd see only two [button] options (instead of the above 3). Yes The game is removed from the static playlist (same as pressing No above) No Same a pressing Cancel above With the current setup, the are no extra button clicks to accomplish the end goal. Just one extra option.

Not a fix nor a workaround (especially if it doesn't prove well ), but a test of sorts... Tomorrow (or the "next day"), before doing any "Search", run Tools < Download < Force Update Games Database Metadata... and see if that process is any better (faster). When that's complete, then do your searches.

Then LaunchBox is not seeing the images [in the folder] for that game. In the left panel, select a Platform (not a Platform Category). Right-click the Platform and select edit. In the Folders tab, are the Folder Paths pointing to the same folder your images are in for the respective image types?

Yeah, the auto import [for PS3] will work with games you've installed into RPCS3. But manually adding games and selecting the Use Folder Names has only ever grabbed the folder immediately above the ROM file.

The folder the ROM file (EBOOT.BIN) is in is "USRDIR". Which is in "PS3_GAME". Which is in "3D Dot Game Heroes (USA)"

To clarify, when you Edit a game and look in the Images section, the images are not there? Even though the images are in their respective folder(s) for that platform/image-type. Also, in the left panel, are you selecting a Platform (vs. a Platform Category or Playlist)? Is this images-not-there debacle happening in several Platforms? Or just in one?

I think it's time to pass this on to the developers by filing a Bug Report. (top of this page under Help & Support) It looks like, for Big Box, it might not be saving the pre-launch high scores to be able to compare against when the game exits. But that's just a guess based on what my unknowing eyes see in the logs. "Unknowing" in that, I didn't write the app (LB/BB) and don't know inner workings.

What steps are you doing to [daily] update the metadata? I presume you're talking about the updating of the local Games Database Metadata. Which should only update if you do something that accesses it. e.g. Force Update it or are adding new games or Update Metadata and Media for selected games. Or maybe I'm mistaken and it does do some automatic daily update in the background (or not so in-the-background as you're seeing) that I've never noticed.

What folder? When you edit the game and look in the Images section, does it show the images there? Can you share some screenshots of what you're seeing (or as it may be, not seeing).

You may be looking for Image Group. Although you can't specify the image on a per game basis, you can add (or remove) image types and set their priority, globally per Group. Tools < Options < Media

It's possible the GitHub services (where the MAME emulator is downloaded from) was temporarily down. Try the import/add emulator process again and let us know if it's now working or you're still getting an error. Thanks.

Based on the info you provided, I'd say create a special folder for your Link Cable games' save states. e.g. M:\LinkCableGamesSaveStates\ (I like to use camelCase for file names and folders to help reduce errors with spaces in the names. But feel free to name it to your liking.) You can probably put this in that same folder... Create a custom config file to direct where the save states should be save when "this" config file is loaded. Call the file e.g. LinkCableSaveStateFolder.cfg. In it, add just one line. savestate_directory = M:\LinkCableGamesSaveStates Now add to your custom command-line parameters --appendconfig M:\LinkCableGamesSaveStates\LinkCableSaveStateFolder.cfg (Depending on your folder and file names, you may want to add quotes around the "/path/to/your/config/file.cfg") [still] Not tested, but looks even better 'on paper' than the last one did.

It's a couple years old, but may still be relevant.

Since LB adds the game you're launching to then end of the command line, RA [probably] loads them in that order. Using LB's built in parameters, you could use something like this to place it (Blue) before the other (Red): -L ".\cores\sameboy_libretro.dll" --subsystem gb_link_2p "%romfile%" "M:\Pokemon - Red Version (USA, Europe) (SGB Enhanced).gb" A quick search shows you can use the parameter --savestate "/path/to/custom_state.state". (not tested, but looks really good 'on paper') This should work internally with RA, but how LB sees/addresses/uses that save state in its save states feature may be a different story.

I can't attest to manually adding PSVita games, but if using the Vita3k emulator you should be able to just add the games in the emulator itself (thus creating its virtual hard drive [which I believe is key to having them work in the emulator]) then add the emulator to LaunchBox. The auto import feature (if enabled) should then scan the emulator and auto import "its" games. Originally implemented in version 13.15 and "fixed" in 13.19.

I recommend posting on that other thread your issues as the OP is still active in the community and may have some insight for you. That, or it may have been covered in amongst the 6 pages.

Apologies. I totally missed you previously stating that. I've always associated DLC's to Steam games and so went the wrong route. My bad. Hopefully the developers are already aware of this or someone else has already filed a bug report for it (making them aware).

According to the video in the attached link, to launch game with a custom config file, you set the game-specific config file as the game's application path rather than the game ROM itself. Though the tutorial was started in 2016, it appears to still be relevant and active (at least as of last June). Grab a cup pot of coffee, your reading glasses and enjoy.

I indicated Windows (Steam) importing is different from other platforms. What I do know is for Steam, LaunchBox will search for a Steam install on your system (via registry?) and add "games" that Steam says it has installed on your PC. This is an-aside to using your Steam credentials to parse Steam for what games you "own". Did the 2nd Disable ROM Auto-Import fix the issue? Granted newly added games [now] won't get imported. After thought: Look in Tools > Manage > Storefronts. Check that None is selected for Steam. En leu of the above, that "should" stop the auto-import. (Sorry. I should have thought of this before.) Another after-thought is, instead of one or the other (or both?) of the above, delete the DLC's that got imported, from your LaunchBox collection. These should then get added to a "blacklist" so they won't auto-import again. You can read more about Storefront management here: Managing Storefront Games in LaunchBox - LaunchBox Note the section about blacklisted games under the section Re-Importing Deleted / Blacklisted Storefront Games in the above link. With how LaunchBox uses your installed Steam app to import "installed" games, I don't know if there's a way to distinguish between an installed "game" or "DLC" (that's beyond my knowledge). With that, I'd say it's not a beta issue. But rather a "bug" in general. Again, assuming the distinguishment can be made between the 2. It may be better suited in a bug report (or a feature request to "ignore DLCs when auto importing"?). (top of this page under Help & Support) However, the blacklist feature may be the answer.