sundogak

Make sure you your associated platforms is setup now that you replaced the RA version. Also that your associated platform name is exactly the same as what you have in your LB platform listing (left of screen in LB main window). Screen snaps help here, so snap your Details and Associated Platforms tabs.

No, point to actual exe, not a shortcut. You said you have a working setup outside LB and the cores work there. Point LB to the retroarch.EXE in Emulator Application Path to that working directory and RA where you can see your cores, etc. Basically, if you downloaded a duplicate copy of RA somewhere, then there is no cores in that copy.

If you already have the RA exe then you shouldn't need to download anything in LB. I suspect what has happened is you downloaded an additional copy and that is what LB is pointing to versus the one where you have a working setup. Go to Tools menu in LB and then Edit Emulator. Look at the Retroarch entry and validate the path shown is to your working setup. Use the "browse" button to point to it just to double check.

Interesting, always good to have more resources for media. Thanks for the link/info. Another alternative I have used same reason you capture above (plus have clear logos and banners) is the SteamGridDB site. They are uniform quality and size at 600x900 resolution. If the original Steam Assets are available (most newer era games) there will be a button at the landing page for the game. The Steam Assets are of high quality, although the user creations are pretty good as well (mostly). In your example that is here and click on "View Original Steam Assets" button at left of screen for cover art (just right-click, save as image for 600x900). A bit larger and taller aspect ratio than IGDB but disadvantage is SteamGridDB will only have those games that are sold on Steam (i.e., no Blizzard/Epic Games for one).

I went down this road as well at one point. I wasn't worried about the storage but just preferred to pull from one master set. You can convert the MAME zip files into a iNES/NES 2.0 (*.NES) format using UCon64. The problem is the "on the fly" portion. To convert, you have to provide some key data such as mirroring and mapper type to UCon64 so it properly sets up the header that most non-MAME emulators expect to see. That data could be put in a batch file after unzipping the MAME file but to my knowledge there is no easy way to auto lookup the data needed without doing some code. The MAME NES HASH file actually contains much of the per game information you need for UCon64 to convert to NES. If using MAME as NES emulator it looks inside the zip, goes to the Hash file and compares the checksums and uses the data within the Hash to figure out how to properly run the game with the PRG, CHR, etc, components. Basically, the HASH replicates the header data for NES format. For MAME it makes sense they do it that way since fits there overall model of how dump ROMs, but does make sharing MAME ROM sets with non-MAME emulators problematic (or vice versa really). But with all that, like you said, if you have a full No-Intro set it wouldn't be worth all the gyrations to get from the MAME set to the NES format in that you would need to work custom batch files per cartridge to call Ucon64. I have done a few one-offs from MAME set to use for non-MAME NES emulator but it would be crazy time consuming unless you were a coder.

@twobucksI had swapped motherboards on my PC with working FreeCamMod setup but then after I was having similar issues. At the time I just assumed I messed something up even though had backups with the exact same setup. I was only using FreeCamMod for the single table launch feature so tried an alternative tool since couldn't get it back to working status. If that is case for you, you might want to look at this tool: "Pinball Arcade Loader". If do google search should be the first entry. That seemed to fix my issues with screen focus (even though it did work). Also it fixed some minor issues I always had with FreeCamMod where it would sometimes not launch to table on the very first instance as well as just a complete clean launch into the table. FreeCam seemed to stop at the main screen briefly and move the mouse around then launch (which may be the issue with the screen focus). So if only using the single table feature here is my setup with Pinball Arcade Loader: The key with Launchbox is you need to point to the PinballArcadeLoder.exe as the "emulator" but also have in the Default Command-Line Parameters the full path to your PinballArcade11.exe. The launcher will then take whatever "ROM" (text file pointer) and launch from that. Here is my dummy text pointer to ACDC. Similar to FreeCam the names of the pointers are specific to each game. The "HIDE TEXT" command tells Pinball Arcade to not bring up the intro text, if you want that just leave only the game name pointers. You can do via CMD batch files but I always find it easier and LB seems happier (with Pause Screen) if keep direct to the launcher exe. Make sure you have the "Don't Use Quotes" and the "Use File Name Only" check boxes checked in the emulator screen if using the pointer text file method. I have attached my pointer text files for reference so you don't have to hunt down the table names that the launcher wants to see. Launcher Text Pointer Files.zip

Here you go:

As rough idea for a full set for just ROMs (no CHDs and no software set): Split: ~ 72GB Merged: ~70 GB Non-Merged: ~128 GB The following are "add-on" sets (they need one of the ROM sets above plus the add-on set files): Arcade CHD set is an additional 553 GB. These are typically later era arcade games that had hard drives or CD ROM full images besides ROMs. So quite a bit larger, but you don't have to have the CHD set if looking at early era arcade games only. The website link I gave above will have a flag if game needs a CHD (when you start getting into later 1990s games like Street Fighter III 3rd Strike). A non-Arcade "Software List" set is an additional ~79 GB (this set includes computer type non-arcade emulation software like for home game consoles with cartridges, Apple II, Commodore 64, etc). Software List CHD set ~2.5 TB. This includes CD ROM and disk image sets for non-arcade emulations (like IBM PC CD ROM software, home consoles with CDs, etc).

Correct, unmerged is largest file size in that has all parts and pieces for each game within each zip (so child/clone zips will run if the parent isn't around). Split sets tend to be the most common, however. So you could download a split set, use a ROM Manager to convert the zips to unmerged and then pick and choose. For split sets, the child/clone zip only includes the different parts from the parent, but none of the parts from the parent ROM. So splits can be where you can get into missing parts. Merged meshes all the parents/clones into one zip and is the smallest size for a set but (historically, not so much anymore) some frontends had issues with merged sets in how to parse the merged zip. MAME itself as frontend doesn't care (merged, split, unmerged). But really with moderate speed Internet connection (these days), if you have access to one or other full set pick the one set you know you will use as primary in that it does take some time for a ROM Manager to recombine things into another set type.

Also should have pointed out that need to be careful on how you download sets. Look up MAME "Merged, Split, and Unmerged" rom sets to get more info. You can use a ROM manager like clrmamepro or ROMVault to "remix" one set type to another but still to have all the source parts. If you mix and match set types then you will likely wind up with MAME complaining it is missing ROMs in that some components needed may be in the "parent" set vs the "child" set. For example, Pac-Man is a "clone" of "Puckman" which is the Japanese name and considered the MAME parent. If you are North America based you might just go and download the Pac-Man rom set and depending on where you got it, may miss vital parts from the Parent Puckman rom set (see snap below from above web site that indicates parent/child relationship). Unless you have a poor internet connection (or really only want a few games) you are much better off downloading a complete ROM set and then taking parts away (or convert to an unmerged set) using a ROM Manager. Otherwise it can be frustrating in that MAME will stop and say it is missing XYZ component.

this website will allow you to sort by year, genre, etc. It is updated through current MAME set 0.234. There are also various lists people have put together of favorites and "all killer/no filler" type deals (some on this site). So just depends what you looking for. http://adb.arcadeitalia.net/lista_mame.php

No, there is no priority setting as of current version so you would need to remove the others if don't want random selection.

Maybe not exactly tracking on issue, but when you are in window where you use "Ctrl-A" to select all you can use CTRL mouse click to to toggle unselect and/or SHIFT mouse click to select all between highlighted selection to mouse click selection. Still some work but don't have to do it at the end right before import.

If the files you downloaded are named accurately then you can do a couple things. First is anything you copy to ..\\Launchbox\Images\<Platform NAME>\<Image Type> or if videos via the \\Launchbox\Videos\ then LB's fuzzy naming will pickup anything in those folders. Make sure refresh your view via F5 by selecting the games so it looks for the new media. LB will match anything in the title or the name of the ROM if media is named similarly. So for example, you have downloaded a bunch of game snap videos for SNES. Then you would place those videos you already downloaded into \\Launchbox\Super Nintendo Entertainment System\ The key is that the videos have to be similar to what you have in LB for the game title or rom name. Also, LB doesn't "read" anything that is in parenthesis or brackets, which is by design. So if you have "Alien 3 (1983).mp4" as the video name then LB will match with any game you have imported with "Alien 3" and ignores the year. I originally did what you are trying to do since I had most of the media. You can get about 90% to import straight off with minimal troubles. However there will be some that will not match in that the names are different (usually a regional difference) to which you have to match manually (or rename the media so LB will see it). Second method is you have media in a set of organized folders and you don't want to duplicate it into the LB folders, then you tell LB to look at a specific folder besides the default. Go to the platform list on left of LB. Select and right-click on the platform name and select "edit", then click on "folders" tab. It will bring up this window: You can then point the folder for that media type to where you have your folder with EMUMovies data. You are still held to the fuzzy naming logic described above. Edit: one caution on this option is that LB will merrily rename files if you open up the game and do any sort of editing (i.e., Alien 3-01.mp4...it would nuke the year in example above). So if you point to a folder where you have a very specific naming process that you want to keep, then might want to stick with first method above.

@Unrealcpu If the Setup.Exe files are all in folders with title of the game, then the easiest would be to run the import wizard within LB. Then do import of files and select "Setup.EXE" (or whatever is the common file you have in the folder setup). Then when you come to this option select option to use the folder name rather than the "Setup.EXE" for doing media searches and naming. Then it should pick up the media based on folder title versus whatever file you imported. The dummy text file method (or batch file) is useful if for some reason you don't have consistent folder names. Whatever the text file is named is what LB will import for search purposes. I use this method for Daphne for example and some other platforms using batch files.

@balrog57 Here is a PS Classic one.

Agreed. The next best solution is mapping a consistent drive across installs. For those few setups that are not relative path then doesn't break them. Annoyingly, pinball emulation (FP/VP) is still the primary holdout that loves to stick stuff in Windows registry.

@PurpleTentacle Not to my knowledge. It isn’t something supported in upstream emulator. So would be something the RA core developer would have to add.

@vegas4917Here are two, wasn't sure if wanted collection on it or not.

This is image from their PDF cover at the developer's web site. Uploaded to DB.

A cfg file should be in the folder Atari800 and in your case Atari5200. In LB you point via command line path to the cfg in 5200 folder. The emulator default folder is Atari800 so that is then your 8-bit cfg location. You should not have any cfg for the emulator in the root like you indicated. @Pineappleking Edit the file that is here (see snap) is a completely separate CFG file (don't mix it up with the others), that points to the BIOS/ROMs for the Atari800 emulator. So don't move/delete/copy to other CFGs. The CFGs I am referring to above are within the ..\RetroArch\config path. If you point correctly in LB to CFG within ...\Retroarch\config\ (see snaps above) then just set up the emulator within the RA interface vs trying to type in mods. If the CFG is set up correctly then when you do this it will only edit the one it is pointing to in LB command line path. Edit: also make sure in your "non-standard" folder (i.e., the non-Atari800 cfg folder) that your CFG has an entry pointing to the path for the option file in the non-standard cfg folder. So for example in your Atari5200 folder the CFG file has entry like (adapt path to your situation): core_options_path = "G:\Emulators\Retroarch\config\Atari800_XL\atari800_libretro.opt"

That screen shot doesn't really help much since all washed out and cannot see what is to the left of the Wii portion although suspect it is the Nintendo oval. So suggest using print screen or the built in Windows utility Snipping Tool (just type in Windows search box) vs a camera shot. Ideally, provide the actual PNG you want by going to the theme folder under images and and attach here. The Wii logo I used is the "official" Wii SVG file, so if the theme is using something different you will need to provide the PNG. The Wii Ware one looks to be standard so that is below.

Here is a stab at it, but if looking for something in particular easier if have example like Retro808 mentioned above.

You have to setup two RA CFG files and folders. One that was setup for the 5200 and one for the 8-bit. Then in your LB install you point to the specific CFG file within the "Extra Command Line Parameters" field like below: -c "config\Atari800_XL\atari800_libretro.cfg" When you point to a different folder then that folder contains the unique CFG and options and you don't overwrite them. So in my case above I setup the "normal" install folder with a 5200 option set. Then the second instance points to a separate folder for the 8-bit CFG. If you set RA up to save *.OPT files uniquely then you will see an Atari800.opt file in each folder and the key item within the option file being set to tell it which system to run: atari800_system = "5200" and in 8-bit folder Atari800.opt file has this: atari800_system = "800XL (64K)"

@moudrost here are steps I just used recently: Backup up LB XML files via Tools...Create Data Backup. Backups are stored in ..\Launchbox\Backups by date in zip. The install batch file will overwrite existing "ScummVM" XML file within ..\Launchbox\Data folder\ScummVM Your backup in Step 1 will keep a copy of your old version The install batch will merge media into any existing ScummVM folders within Images, Manuals, and Music. If you have setup a non-eXo version at some point you may want to consider renaming your old folders and/or backing up. The batch file will also replace your LB version with likely an older version. You can always reinstall LB back to version you last downloaded version via ..\Launchbox\Updates folder. I just "REM" the portion of script with LB unzip. Copy the eXoScummVM folders as follows or use a symbolic link to source: ..\eXoScummVM\Content >>>entire folder to root LB folder>>> ..\Launchbox\Content ..\eXoScummVM\eXo >>> entire folder to root of LB folder>>> ..\Launchbox\eXo if you have an eXoDOS setup within existing eXo folder it will merge the unique folders appropriately. The only thing you might get a warning from Windows during copy as a "dupe" is the unzip.exe in the ..\eXo\util folder which is fine to either either leave or copy replace. Setup eXoScummVM.bat >>> file to root of LB folder>>> ..\Launchbox\ You then launch the batch file and it will take awhile to copy/unzip and move things around. Remember if you don't REM out the LB unzip in the batch file you will likely need to rerun your most recent LB install setup. Your folders within the eXo side of things will look something like this. Note I have symbolic links to the two big eXo folders, so you won't see the "link arrows" for normal install. The files needed to run games all all stored within the eXoScummVM folder just like eXoDOS does. So don't have to worry about messing up your eXoDOs install. The scummvm exes needed for exodos are kept in separate folder than that from the full ScummVM install as well so no conflicts to eXoDOS.