sundogak

No, subsequent ones beyond the originals Viking did are in the thread only in most cases.

@C-BeatsNo pattern that I can tell, so randomly.

On Beta 13: Running a Metadata update to games that have a valid max number of players and play mode entered in the DB results in inconsistent update results to the max player field. If select a game individually and do a meta data update will update correctly. If you rerun the metadata update it tends to fix it but not always. In some cases, at least in audit view, you can see it update some and others it actually removes the max player data (even though it is in the DB). At first thought it was just an audit window issue but happens outside that tool. Example 1: This was an audit view window after doing a full metadata update replacing any metadata that was missing (recommended option). Note the Single Player items and no entry in the max player. This was after two update runs of entire ~130 ish games. If do a few at a time (~5) or individually (see Examples 2 below) then the max player data "sticks". Example 2A: This is example after ran metadata update on Intellivision console. Note the Max Players field is empty/missing although Play Mode is filled in as single player and a metadata update was run prior where others were filled in but not this one. Example 2B: This is same window as above, if click the "X" box at top right and do a manual search, it properly fills in the Max Player field. This always works. It just seems to be the batch metadata updates that are hit and miss if, particularly when in >20 at time updates. I did about 5 console platform updates (mostly for release types) and results in same behaviour so didn't seem to be an issue with a particular platform. The easiest way to see it is is pick a platform and run audit view, do metadata update, then sort by play mode and look for missing MAX players field.

Centauri would approve

@JoeViking245yeah, through the settings gear icon, and then the synchronization options box you can set for variety of ways for how you want it to treat files on the "left" or "right" side by clicking the icons. So for example the "update" box if do selections right is similar to the XL for Robocopy (only newer files). Takes some fiddling if get complicated but can save the settings and paths so just click and go the next time. File list input for syncing is one thing I wish it would add to features (didn't see it buried in features), so still stuck using batch files for things like in this thread where doing an initial copy.

@codetvirus Rom/Bios packs cannot be shared here. But here is the listing and the checksums. Google is friend with the checksums. Some of these are also in the current MAME packs but as recall there were a few from older bios packs so you need to verify checksums before copying to Retroarch system directory under ..\Retroarch\system\neocd Name CRC32 File Hash 000-lo.lo 5A86CFF2 (in current MAME set inside Neogeo.zip) front-sp1.bin CAC62307 (front loader) neocd.bin DF9DE490 neocd.srm 5C2AAB47 ng-lo.rom E09E253C top-sp1.bin C36A47C0 (top loader, don't need both) uni-bioscd.rom 0FFB3127 (this is version 3.2 renamed)

@JoeViking245 Thanks for sending, very helpful. I had been playing around with a more robust batch file last night as wells as Robocopy which less familiar with command wise. I typically have been using Freefilesync to keep my Mame files in sync across a couple computers and my main PD set. Like you noted, the whatsnew.txt file is good enough in my book to find the occasional new rom/chds popping up.

Beta 9 10 or 11 didn't address that issue noted in the other thread with Space Invaders which is more priority of parent/child related versus beta/prototype.

Understood, typically try to do same with MAME set and was pretty space constrained up until my recent upgrade. If have to update down the road, the above web link to http://adb.arcadeitalia.net will help with total brute force approach since it outputs a rom name and "real" name in text file by rom set and bios. I used it to double check I got everything, particularly for CHDs. Easy or hard way, whatever works is what matters ultimately.

Went through a similar gyration this weekend focusing on the Naomi side. Did similar where pulled in full set of Mame with working/non-working. But like you, it pulls in a ton of stuff that have to wade through. Particularly since the Naomi sets (1, 2 and GD) were only 12GBs total inclusive of the CHDs fit seemed excessive to manage all those other ROM entries. So I went the copy the ROMs via batch file to another directory route (i.e., Sega Naomi, etc.). There are a couple older threads here on the forum with batch files to copy from MAME to another directory and there is a GIT posting (ver 0.215) as well that does similar. However, I wanted a current set with 0.223. I did look briefly at DAT with CLRMAME Pro but decided to just work a batch file. A great site resource for helping with this is here. The options are not quite intuitive but it does allow you to sort by source/bios and then you can export out via multiple formats (XML, TXT, DAT). So first item is to select Additional Filters, then Driver Tab. Then you can use the required BIOS entry and although it isn't a drop down box it is a "smart" box that will type in closest match. So you can type in Naomi for Naomi hardware, Naomi 2, etc. Once you do that and hit search it will display rom set matching. It also allows you to select by ROM set (i.e., 0.223, 0.222). Then if you go to Options and Export the Results it gives you a variety of export options. I chose TXT and then used those to generate a crude batch file set. Once figure it out it was easy to generate other files. For plain old ROM only entries works relatively easy to use the file names to make a copy batch set. For CHD files can be somewhat of a pain with a bit more manual matching. An example TXT output is attached for Naomi Bios and a few of the Batch files I created. I didn't get fancy with trying to do file list inputs to batch file so relatively crude. I REM'd out any prototypes. I am sure there are more elegant solutions but this worked for me and I was able to get the Naomi sets and Atomiswave hardware in to LB using Flycast for Retroarch or Demul. I chose to duplicate the roms into separate folder simply since was easier to import into LB. The downside is using more drive space and also separate MAME set for maintenance. Again, I am sure there are much better ways but after doing some Googling nothing popped out that wasn't using older ROM sets. I find sometimes that I spend more time looking to find a cooler way then it would take to brute force it. 0.223 NAOMI MAME search - ADB.txtMy_223_naomi.batMy_223_naomi2.batMy_223_Hikaru.bat

Suspect there may be others but I haven't really looked/ran into them. Just noticeable for something "famous" like Space Invaders. Jason would have to weigh in on question of fixing. I did see in the beta thread he mentioned looking at how betas/prototypes get prioritized in additional apps where betas get set as default. But that wouldn't necessarily fix this issue since related to parent versus clone priority.

At least on a World or North America import, LB picks the clone Cosmic Monsters as the default for the large group of Invaders games rather than Space Invaders. Going to the additional Apps and setting as default fixes it. So next import, look for Cosmic Monsters and then under Additional Apps should see it. Looks like it is picking alphabetical versus the parent for some reason in LB.

Similar to @wallmachine on Bigbox issue noted in post above. The themes (at least Refried and Redux) are breaking since notes in error log of having issues finding path via the ...\Launchbox\Core\Themes shortcut/link. Same error for both, snap below is for Redux.

You can try one of these three with the last one being more targeted if comfortable editing XML: 1) Use Tools "restore" feature and restore from LB autobackup. LB/BB does this on LB and BB shutdown and startup. If do the restore of the startup of Bigbox it would return you to before your made the change (along with all other settings both in BB and LB). Alternatively, look at the date/time stamp and see which one is most recent before you made change. 2) Go to ..\Launchbox\Data\InputBindings.xml and move it to temp location (outside the data folder). LB/BB will regen the input bindings file back to default. Note this will also remove any other custom changes you had for both LB and BB as far as input selections (everything else is untouched). 3) Open up the Inputbindings.XML and search for the key that got changed. Likely look at the BigBoxBack or the BigBoxSelect button entry and modify accordingly back to what you had originally.

Emumovies is working on my end (Beta 9). You might check your antivirus didn't block something and do a reinstall. At least on my setup, Norton was being more difficult then usual blocking LB/BB initially on internet access and/or removing DLLs, until I excluded the processes.

Unfortunately, Flycast requires the CHD folders and files beneath that to be co-located with the MAME roms (see the Flycast wiki) and it is part of how the core looks for things. 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 Each core is its own self contained setup so how the MAME core works (and the MAME.INI) will have no bearing on other cores. Also LB won't have any way to override how the core wants things unless it is a command option within the core. Might be good feature request/enhancement to post here. I have my CHD files and ROMs separately in different folders which for me is easiest way to keep updated based on where sourced. But was similar issue in that Flycast won't work since expects the CHDs as above. DEMUL does allow option to set multiple directory paths for bios, games, etc. So worked in my case since pointed one path to CHDs, the other to ROMs/Bios. Not sure it would work if pointed to path with all merged, but may be worth a look. Otherwise, if want to use Flycast, stuck as far as I know with using path roms and folder/CHD structure.

@handsome1987 While you are working the video angle, for most themes, whatever your prioritize as far as screenshots/titles will show if there is no video available. So if you look in LB under Options and priorities, it will pull the image(s) in the order you have listed in this priorities selection. In my case I have it pulling Title, Gameplay, Select, etc: In case of Future Pinball, images go here ....\LaunchBox\Images\Future Pinball So for example this table Battle of Britain, I don't yet have a video so it shows "title" screenshot since that is the first priority I have indicated and I have an image that matches the the table name. I place the Backglass Images in the Title screenshot folders, desktop table game field images in "GamePlay" and full table images in "Select", but you can place wherever you want and prioritize whichever way you would like:

Wasn't entirely clear on if you wanted multiple or combining the two images? Also those images are not very high resolution so a bit jaggy. Anyway, here is stab at what wanted:

@Johnny T It is community thread and not anything official, so feel free to post/share. More selection is always better.

Beta 9: still getting this error if running full setup on Beta 9 and checking the box to install desktop links:

@as905 Here you go.

@JoeViking245 There is a LB glitch in audit view consistency after some further fiddling and noted in post after Neils. This is why I thought it was plugin based issue originally in that two platforms (coincidentally SL) had 5 MAME related columns whereas Arcade had 11 "new" MAME related columns. Thus, it appears to be bug in LB beta based on them adding in new fields. 11 columns versus 5. I nuked Atari 800 by deleting all games and did full re-import thinking it was something related to newer imports. However, same results 5 columns of "new" audit info as snipped above. A full MAME import still results in 11. Sorry I posted that it was plugin related, it is not.

Forgot to attach this ALT that is similar to some others did prior.

Here is a quick one. Not many quality logos for Dual so used top one you attached.

Appears to be an inconsistency in how LB is doing things in the beta. This is the view I have in MAME which didn't use the plugin (more fields than you have). Seems like all these fields would be common to both your view and to the others where this plugin was used (i.e., anything where MAME importer process used either via plugin or built in). Maybe a minor bug in the beta then.