sundogak

My take when adding is that if it is rated by a ratings board of some country, then generally there can be an equivalency to ESRB. I don't think it HAS to be an ESRB rating. Europe and Japan ratings can (mostly) be equated to ESRB, as an example by looking at their wiki's. To me an 18+ PEGI is easily equatable to a Mature, which can be validated if the game was issued in USA and Europe. Japan ratings can get wonky because they slice the ages in more groupings in earlier years. So the "10+" type ratings can get a bit odd for different countries. But overall the Everyone, Teen, Mature, and "Kids" have comparable levels in all the ratings systems. Even the early ESRB ratings changed from "K-A" to Everyone over time. Additionally, if the game "self rated", which you can see on some Atari 2600 "adult" carts, or particularly the 3DO/CDI adult CD games, then I definitely add that in as well since the developer determined the rating and most assuredly they are "adult" by most people's measures. But earlier than 1990s, then most times it will be "not rated" in my mind. If it was never rated by any independent country level board (or the company), I don't put my "opinion" rating, which is what I see some folks do. If I run across, I will change it. Obviously, we all have the ability to rate or place games in playlists if we want to have our family level ratings for our own setup regardless of what is in the DB. But my take on what is Mature or Teen for a non-rated game my not be the same as another person's take on things (hence the challenges with boards in general). My 2 cents FWIW.

@HansS You have multiple files that are duplicates (anything with (1) info files). So LB will not prune those out if duplicated if told it to pull in *.info files. LB doesn't have enough information in what is named above to match anything. It either needs the file name or the directory name to match (excepting MAME). So LB will be completely confused on what you have in your screenshot. See #2. It appears the set you have in the screen snap is a WHDLoad game set that was unzipped from the source *.lha files. Those are managed differently and will not import directly. See info at FS-UAE site. FS-UAE uses a matching system to compare the games using checksums (very slick). The screen shot below shows a WHDLoad set I have. Notice they are all still zipped (in *.lha extension). If you look inside the zip you see an Info and Folder. Looks to me like these were all unzipped which is why have a zillion *.info files. FS-UAE manages them in compressed form (think like MAME does). See this LB thread on how to take FS-UAE pointer files generated by its launcher to import into LB. Other emulators will be different..... 3. What is referred to above by Lou is an ADF set. That will look like this (see snap below). So those will import as noted above since typically either the name of directory or the name of the game is enough for LB to match. If for some reason they are not, then you are in for a long slog to rename the files to what the game is by title if not using a checksum method like in #2. Ultimately for any import set (excluding MAME) it needs enough of the name in the file to be able to match. I would try and make sure your emulator your are using (wasn't indicated in post) that you can run the files you have outside LB first and then import after you sure your set is working and in correct directory path. Edit. If have a MAME Software set, then the Amiga files are (mostly) in ADF format (with some IPF) within the zip files.

So you backed up the file and deleted it like suggested?

If talking keyboard bindings rather than controller, then go to Launchbox\Data\BigBoxSettings.xml and either manually edit (scroll through and look for key you want to change), or backup file and delete it.

See here on instructions for Flycast core. For games that need CHD files you need them as well and they need to be in path structure that the core wants to see. Snip from the instructions: How to play NAOMI Games:¶ Run NAOMI games stored in MAME format zip files by following the same process as standard Dreamcast games Run NAOMI GD-ROM format games stored in MAME zip + chd format by running the zip file through RetroArch. The zip file should be stored in your roms folder with the chd file in a subdirectory of the roms folder named after the mame ID. Example (MAME ID=ikaruga) - [ROM FOLDER]/ikaruga.zip - [ROM FOLDER]/ikaruga/gdl-0010.chd

See attached example. Goes in your MAME\ini directory. Just change any plugins you want to "1" and any you want off to "0". # # PLUGINS OPTIONS # cheat 1 cheatfind 0 console 0 data 1 discord 0 dummy 0 gdbstub 0 hiscore 1 layout 0 portname 1 showcp 0 timer 0 plugin.ini

See this thread below for attempts to make it work. Highlights: 1) One issue is the RA core is version 1.8 of Hatari and standalone is up to 2.2 2) tos.img file needs to go in the Retroarch\system directory. 1.02 (CRC32 = D3C32283), others may work but that is what have. 3) Some have noted that needs hatari.cfg file in Retroarch\system directory. I have found RA will run regardless as long as tos.img is in system directory. The path to the image directory is driven by RA. But if you do have it in the system directory, doesn't "hurt" anything. Note that the paths are normal Windows path format not the Linux format used in the instructions. See example attached. Note: Hatari loves to stick things (nvram, and autosaves for example) in the Users\###\AppData\Local \Hatari folder by default (for 2.2). The RA core one likes to stick things in Users\####\.hatari So if hit F12 when Hatari is running (as well with RA core) will see where paths are set as well as other emulation settings. If you hit save cfg in the F12 screen it will dump a full CFG file similar to standalone. Haven't played with it enough in RA core to see if it will take all those settings or not. 4) .st extension files seem to work for me. However, I and at least others in the thread below couldn't get the .ipf files to work. Core says it works with them but all games I have tried get stuck at white screen and will not boot. Again, might be some combination of settings but suspect it is just an old version not playing well. 5) End result: Standalone is easier, works relatively quickly out of box, and is updated. I have Steem and Hatari working. I prefer to use RA where possible as well, but when you get to the computer emulation they have lots of issues and the benefit of unified controller is less of an issue since most times you are stuck with hitting the keyboard at some point. YMMV. I hatari.cfg

I added the new ScummVM as a separate emulator. If use the pointer files in this thread it will get you 90% there. I didn't do for every version/game but you get the idea. I used EpicFails launcher prior but he would also need to update plugin since his DB internal to the program doesn't pull all the codes for the new games. One advantage (like the internal LB method) is that it works with Pause Screens which is what originally sent me down the path since wanted access to manuals in pause. Pause screens, at least on my setup, never worked if using the batch file method. The other is that this will also work with Retroarch with no changes since pointer files have GameID files in the text file as well.

take a look at this thread as well for MAME setup.

If using a "common" directory structure the following zip file has the text pointers formatted correctly for RA and LB. If you have different directory naming then won't be as useful but can see what text files look like and/or drag into the appropriate folder. Once they are in the directory you just tell LB to look for any file with *.scummvm in name and import those only. If setup the ScummVM emulator as noted above then it will launch the games using the text file game ID. ScummVM LB Pointer Txt Files in Directory Structure.7z

The version that comes with LB isn't updated yet to 2.1.0 (after all ScummVM was just finalized today). Additionally, the built in settings within LB will need to be updated to reflect the new codes that are supported in 2.1.0 which is why you don't see them in LB. LB wouldn't know which codes they were or what games were to be supported until ScummVM folks finalized things. Since you are not using batch files you can go another route in the mean time. Basically, you do as follows: 1) Add the new ScummVM emulator EXE path like any other emulator (version 2.1.0 downloaded from ScummVM site). 2) make sure to to check "don't use quotes" and the "use file name only without extension..." 3) In the default command line parameters insert command that points to location of your scummvm.ini which can be anywhere but in my case I keep with the EXE location rather in my User directory so it is portable: ScummVM -c "G:\Emulators\ScummVM\ScummVM\scummvm.ini" --no-console -f the -f just tells it to go to full screen. All other settings are taken from your INI file. 4) Go to the directory with a new game and make a text file with the name of the Game ID. In the case of Blade Runner, it is bladerunner-win. The extension can be anything but I use scummvm since that is also what Retroarch likes. If you open the text file and also insert the game ID (i.e., the same as title without extension) then Retroarch will also work in addition to normal emulator installed above. 5) Then add the "rom" like normal within LB by pointing it to the bladerunner-win.scummvm file. See below example. 5) If you want to find the game IDs for other new games just open up the ScummVM emulator and go to the game after you added it and click "Edit Game" and will see ID on first tab. Setting a dummy text file with the name will allow LB to launch the game with the above settings.

Assuming you are talking game themes, go to the LB folder under videos and then whatever platform name you want to add to. Then under that platform add the videos in the "Theme" directory. Example below for MAME. If you are talking about themes for LB itself then you can put videos under the specific LB Theme (as one option):

...all whopping $3.02 of it which brings my total haul to $13.09 (got $10.07 last year). The original claim per the class action was "up to $65". For those who may not recall/or were not around for the whole ordeal see link here: https://www.cnet.com/how-to/ps3-other-os-settlement-claim-how-to/ Now I wasn't delusional that would get the much (if anything). However, I always find these class action settlements "educational" from perspective of how long the legal system takes to work through all this. This claim form was submitted in October 2016. Sony was sued in 2011 and the final settlement was in 2017. I think I bought my "fat" PS3 ~2009 (which still have). For the original claim (~2014), I had to submit a scan of the boot disc showing it was used for multiple OS capability. Of course, that was a hilarious requirement since you could just label any old CD-R disc and scan it to "count". Ultimately the judge threw out the original claim process saying it was too complicated and that there wasn't enough money (originally $55) going to claimants. The 2016 era settlement required you show your serial number (or PS3 gamer ID) and "attest" you knew/used the OS function. Obviously, the lawyers burning through 9 years of billable left little left for the settlement. I was never that worked up with Sony on this since I treated the other OS capability as a curiosity. But it is an example of how these cases are meaningless from compensation to end users (witness the abomination of the Equifax settlement). Anyway, off to go pickup a "King Size" KitKat with my additional bounty, just in time for Halloween. ?

1) Easiest: Just directly install LB on external drive. Then it will download media there and don't have to go through all that. I have mine on external "G" drive. So all LB files are on G:\LaunchBox\... If concerned about caching speed (i.e., internal is SSD, external mechanical) then there is way around that. There is a thread here that shows how to keep the LB cache on C drive via virtual links and free utility. If both your external and internal are mechanical drives likely not worth messing with the cache location. 2) Alt: Adjust paths in edit platform to external drive location. It will then download to wherever you tell it. You will have to manually adjust each platform initially but will not have to do after the first time. Could do via XML file with search /replace rather than the platform window to speed it up.

@kidshoalin Region log os go in playlist folder like noted below and as path noted in the linked screenshots. They don't go in separate region folder since LB just treats them like any other playlist.

@kidshoalin on your question on where these go, look here for discussion and screenshots (click on "sundogak relied to a topic" link). and here

@kidshoalin FX3 is already made, look at thread page 22.

I would uncheck the Wikipedia box when importing initially, it will pull in unrelated items as you saw depending on how roms are named. Particularly for the computer based systems. Wikipedia doesn't have much in way of Atari 800 info for specific games so it pulls in next best thing which tends to be Commodore or Apple II media (assuming it gets game name right). The LB DB is relatively sparse on the Atari 800. I have added maybe 15 or so games for Atari that were "popular" games at the time. So less popular ones likely going to have to hunt down media. Atarimania web site has the most media but they annoyingly watermark much of the media (also contributing to why not as much in LB DB).

Works fine in my setup. Might check that your playlist is pulling the same exact name platform name as in your setup as well as the region names used:

Many of the Laserdisc games are not working in MAME. In particular, Dragon's Lair is non-working. See here We are stuck with Daphne at moment if want working Dragon's Lair game. Additionally, MAME looks for specific checksums for the various files it needs, so you have to make sure whatever you convert via CHD is a source file that MAME was looking for, not just by name. CLRMAME or other ROM managers will validate if files you have are what MAME expects to see.

@Jason Carr Beta-3 solved the above issue for me. ? Running the Scan for Added ROMs now doesn't pop up the games that were already imported.

wow, cool. Will give it a whirl when beta comes out.

I have had this pop up on occasion and in my case always when imported game is an Additional App. It is odd because it seems to only happen with certain games and for no obvious reason (i.e., special character in name vs others that import fine). Deleting and re-adding doesn't fix the problem ones. Until I made my Sony PS1 dual disc games into one file PBP, it popped up there as well on few games (so not emulator/system specific). So two that I know for sure that this still happens are under the Nintendo GameCube system. These two games: Lord of the Rings, The - The Third Age (USA) (Disc 1).gcz Lord of the Rings, The - The Third Age (USA) (Disc 2).gcz Resident Evil - Code Veronica X (USA) (Disc 1).gcz Resident Evil - Code Veronica X (USA) (Disc 2).gcz LB will always try to re-import the 2nd disc again no matter how import even though the settings are fine and adds to the additional app as expected. It is like the Scan for Added Roms feature just doesn't see it. So here is a run through with Resident Evil game above. 1) Deleted game from LB. Here are the two files on drive: 2) Re-added both games with combine checked. All looks good 3) Looks good after import (not two separate files) 4) Double check the additional apps. All added okay. 5) Both look fine and will run as expected. 6) Now run the Scan for Added Roms and it pops up to add it again even though it is in the Additional Apps listing. A manual Edit Application and re-linking files once game added also won't fix. Sometimes I found a slight name change to both files will fix but that doesn't work all the time. In the case of Resident Evil above, I deleted the "dash" in file names and adjusted the Additional Apps and will do the same thing (try to reimport disc 2 after both are added). I remember looking at the XML files once trying to figure out what is different but couldn't see any pattern but nothing jumped out. Anyway, odd to be sure. Edit: tried a couple other things. Tried swapping Disc titles (i.e., Disc 1 is now Disc 2) to see if something peculiar with the file. Will still pick up "Disc 2" even though it is physically the Disc 1 image. Other thing tried is making the names "Disc A" and "Disc B". Same thing, now just keeps trying to re-import Disc B.

You might double check no space between dash or correct entry for NES and associated platform title is the same. The setup is the same for NES as the others: nes -cart You also shouldn't uncheck "use file name only..." or "extract ROM.." for any of them if using the -cart flag in the default parameters. These two screen shots work with NES, Genesis.

I shouldn't post when it is late, particularly for MAME... so ignore what posted earlier. This will work for what you want without setting up another instance of MAME (which works but why have two?). The software list command dump doesn't seem to have the correct flag. "-cart" is the correct one for both advision and genesis. With that flag then you can leave MAME setup to use the full ROM path. SO here is the correct MAME settings in LB for both Sega Genesis and Advision. You need this in the command line parameters for Advision and Genesis, respectively: advision -cart genesis -cart I had used the wrong MAME flag when tried last night thinking it was "cartslot" and "mdslot" (which are what is listed in MAME command -list dump). Anyway, the above should get you going with normal MAME setup. You can use the non-flag version like I originally captured (i.e,. without the -cart) for both but then it has to be with no path or extension, only the ROM name and likely not how you have your original MAME setup to do. The full path with -cart flag is what I was trying to get to yesterday, so what I would suggest. One other thing when messing with software lists is to also consider using a specific INI file if options are different in MAME.ini. In my case for Arcade games, I use save states but prefer not to for most other things. In that case need to either add command switch in LB in same line as the "-cart" (i.e., -noautosave) or add that to a "genesis.ini" and "advision.ini" in INI directory. Just depends on what you want/have in your MAME.ini. Alternatively, you can add "-statename %g/%d_cart" if want the save states by machine and then game. If using a machine specific INI, say for Genesis.ini it would be added in as: autosave 1 statename %g/%d_cart