sundogak

Depends on which core you are using, and you didn't specify. NeoGeo CD core: No command line parameters FBNEO core: --subsystem neocd

Answered above saying that that resolution won't work for Daphne. You will get an error. Also noted above: The fullscreen and ignore aspect commands will make game full screen and stretch no matter the original resolution of the media and is discussed above in relation to the batch file command: -fullscreen -ignore_aspect_ratio

No, it is within your batch files you call to launch Daphne from LB. Highly unlikely you are putting the entire command line needed in LB to run. See G22's example above.

If you are putting stuff in the RA directory for MAME then you to have all bios and software (i.e., cartridges) there as well unless you tell RA to look for ROMs outside normal RA path. With AES you are not only using neogeo bios files but also software carts. So it isn't a "normal" arcade" setup with point to a ROM and go. It needs two pieces plus the HASH folder which is the "map" for MAME to know which software carts/files go with particular bios. However, there is a setting that allows you to avoid duping your ROMset into the RA folder. See below. With an option setting in RA, you don't have to put your ROMs in the RA directory. However, you do have to do certain folders, particularly the HASH, samples, and INI folders. ROMs can be pointed to in a normal setup outside RA. These are the only folders in my MAME RA folder (Note looks like MAME folder but substantially truncated and no ROMs): The MAME ini folder will have a dumbed down version of a normal MAME.ini file. The key here is you have the paths to your "normal" (non-RA) MAME folder with all your ROMs and full software set. This special RA version of MAME.ini basically is only used to point to ROM paths outside of RA. So don't just copy over your normal MAME.ini into RA, you have to adjust paths. See example below but you will have to adapt to your paths. Make sure your Rom path and SWpath point to a full set MAME rom set and software rom set. Anything in the paths below that says it is in the "retroarch" folder path has to be in RA folder (it won't work outside RA because of glitch in the MAME core). Then in the RA config folder under MAME, have a mame.cfg file with: game_specific_options = "true" Then also in the config folder a file called MAME.opt (this contains the options settings in RA): The key ones are: mame_mame_paths_enable = "enabled" <<< this is the one that allows option for RA to use paths outside normal structure. But it was coded incompletely and documented poorly. It ONLY works with ROM and Software paths outside RA. They have never bothered to fix it to work with other paths. These others are also key, particularly the CLI enabled one. mame_boot_from_cli = "enabled" mame_boot_to_bios = "disabled" mame_boot_to_osd = "enabled" You can set these in the RA interface but find it easier to do in the config files. This is why setting up MAME in RA is pain, because you are overlaying a complex MAME setup, with a jury rigged RA version that has parts that must be "RA way" and others that have to be "MAME way".

@ElhoraMAME and RA overall are a headache, particularly when using software MAME set. But if using the MAME RA core here is how setup for AES: "aes -cart \"%romfile%\"" This is an example for MAME RA emulator settings. It is different than a normal MAME RA Arcade set up so I setup a separate instance of RA and called it "Retroarch_MESS" (you can call whatever). It still points to same exact RA setup as your main, it just tells LB slightly different launch commands: Using Art of Fighting as example, LB just points to the normal zip file (AES cartridge) for that game within a regular MAME software set (i.e., the cartridge "software" is not in the arcade set for MAME).

The fullscreen and ignore aspect commands will make game full screen and stretch no matter the original resolution of the media and is discussed above in relation to the batch file command: -fullscreen -ignore_aspect_ratio Keep in mind this just blows up the video and stretches it. There is no "upscaling" within Daphne and most definitely not at 4K. There are some enhanced Dragon's Lair and Space Ace video files that are actually upscaled using AI at 1920x1080. But in most cases these are 480p generation games, so none are truly wide screen. If not using full screen option, then the screenres command tells Daphne what resolution to use via command line or batch file. You can see examples above. In theory, you could set the resolution command like below, but you will get an error within Daphne since it will not recognize that high of resolution: -x 3840 -y 2160 -fullscreen Daphne is an old emulator so 4K isn't going to be option. So best you are going to do is use wide screen resolution like: -x 1920 -y 1080 -fullscreen But again, this will stretch almost all the Laser Disc based games. The easiest is just to use the fullscreen command (without any specific screenres setting) and let the emulator size realizing it will have black bars on the sides.

LB won't import something if it is already there unless you check import duplicates. However, MAME full-set importer has a different import process than all other LB game imports since it uses the MAME meta data. Pac-Man (USA) is a clone of Puck-Man (Japan/international). Depending on what options you used when you did the full-set import (i.e., if selected "import clones") and what region you selected will determine what LB imports for MAME and also what it defaults the clone/main game to. If you selected import clones, then you will see all versions when you right-click on the game (see snap below, with USA region as priority and all clones imported). Then you can run that version. The "Japan set 1" is the Puck-Man Japan version. If you select "Edit Game" with right click, then you will see the various versions in the Additional Apps section. If you want to always default a particular version (say Puck-Man and not Pac-Man) you can select and select "Make Default".

No, you have to go back and fix your error assuming it was not caught/rejected at moderation (don't assume it was).

Those two games are not emulated in MAME. This is good reference to determine what is and isn't working as well as ROM names.

Yes, you can use both a standalone (not the built-in version within LB) of ScummVM and the RA core in that I have this setup this way. But it takes a bit of work initially in that you have to add a dummy pointer text file with the ScummVM GameID for all to work. I did this several years ago now but here are basic steps: Setup a normal ScummVM instance and make sure it works outside LB with your games. Your ScummVM.ini file shows your gameIDs if wondering what they are and where to find. It also is in the ScummVM control panel (standalone). You should have folders with each game in it with the various files that ScummVM needs In each folder, you place an empty text file with the gameID as part of the file name. This is what we will point LB to when installing the ROMs/Games. The extension of the dummy file can be anything, but I used an extension of *.scummvm. The key is the extension is consistent or will be headache when trying to import into LB. In LB, setup the ScummVM standalone emulator. See Figure 1 and 2 below. Note the setups in Details and Associated Platforms portions. I also have a eXoScummVM version in there but ignore that. The path in quotes must match your specific setup to where you keep your working scummvm.ini that is installed as part of standalone. -c "G:\Emulators\ScummVM\ScummVM\scummvm.ini" --no-console -f Figure 1 - ScummVM Standalone Figure 2 - ScummVM Standalone 5. For Retroarch your setup in LB looks like this for ScummVM core: As an example, using the game Backyard Football 2002. Notice that LB is pointing to football2002.scummvm which is the dummy text file noted above with the gameID of "football2002". Again, the text file is empty and is just being used to tell program which ScummVM game ID to pass to the emulator. The second snap is of the directory of the game and the text file. Note this HAS to go on the root of each game folder (unfortunately) or things won't work without a lot of other things to manage. if all is well, then in LB you should see this which gives you option of which emulator to use: In the Retroarch directory under System you should have a scummvm.ini file. Make sure the paths to the games match. My recollection is the scummvm.ini for RA was different versus what standalone uses. Test RA by launching RA outside of LB then going to the scummvm text file pointer and selecting that to run. If this runs and ScummVM standalone runs outside of LB, then reduces troubleshooting if something is not working. ScummVM is particular about where things are located so best to get that squared first. If both ScummVM standalone and RA are working then you can do a normal LB import where you tell LB to import all *.scummvm files as "ROMs". Unfortunately, another step is you have to match the LB entry manually to the LB database. Some might connect if folks have put in an alt name in DB. So as can see not simple to do, but once you get one game working it is just wash and repeat and have flex of using RA or standalone. Any new games that come up you do the same thing so you only have to do the drugery of placing the text file and manually matching one time.

Might try this video: Also, Exo has a discord that can get help as well.

Tiger handhelds are part of normal full MAME set (I am assuming you are not trying to use Retroarch). So, if you are getting incorrect lengths then you likely have a mismatched ROM set relative to your MAME executable version (likely by a lot). They made a lot of improvements in two years with handhelds, so if for example using a newer MAME version and older ROM set then can cause issues (Google "pleasuredome mame set" and will find current sets). The SVG file is what MAME is using to generate the background graphic of the handheld game (like tbatman.zip which is Batman Tiger Handheld game with SVG snap below). MAME will not run if the checksum and sizes don't match and/or the file is corrupted. Also, you should have an SVG file in the Tiger game zips. If not, older set. Example below is the Batman MAME file for Tiger with a binary and the SVG.

Plus this thread: Also note that no current emulator (MAME or RA) will play games that require the CDi digital video unit (games like Mad Dog).

If you are referring to matching the game to the LB DB then for most part, you will have to manually match (override the name, then click the "Search for Metadata" button). For some Daphne Arcade games, users have added alternate names in the LB arcade database to aid with matching (i.e., like Cliff Hanger = "cliff" alt name) but that is hit or miss. For MAME, LB "knows" the ROM names and can match when using the full set importer since it is using the MAME internal database to help. But with Daphne, nothing similar is in place. Fortunately, only ~30 games to work through and once linked to LB DB should not have to mess with it again.

The issue you find with "media sets" with VPX and Future Pinball media, particularly with LaunchBox, is the lack of standard naming convention and no pinball "media categories". Coupled with the LaunchBox database not being conducive to pinball in general, it makes for quite a slog to make a pack that (mostly) works for others. Most packs you will see outside the LB universe are like "Attack from Mars (Bally 1995)" and that is the format I use. LB ignores anything in brackets, which is 90% of time good (except for games of same name with different release years/companies). However, LB has a penchant for renaming media to "Attack from Mars-01" so that is also a headache when working with pinball media. The various MODs, table versions, and originals (some of which are really MODs of "recreations") add even more to the naming fun. PB dedicated frontends like Pinball Popper and PinballX have better options media management and launching, but still prefer LB for "overall" game management. For my PB setup I have VPX (~1,100 tables) and Future Pinball media (~700 tables) and have most of key media (logo, table screenshot, marquee shot, docklet, adverts), but there is always "one more addition to fix". Only the FX3 and Pinball Arcade are "complete". Media for pinball is a definite time suck!

Do you have under the "Clear Logo" folder name? Also, did you do a "refresh" of the platform images within BB under Options?

Might try this: make a backup, then open up the XML file in the \\LaunchBox\Data\Platforms\NAME_OF_YOUR_PLATFORM.xml and search for the game name. Under <Application Path> entry you can then edit the file name to the changed one. The metadata should all then be the same. Media "should" match unless media was matched to the ROM/File name (typically LB names media via game name). Note: When messing with DATA XML files, make sure the backup XML is NOT kept in the Data folder or can cause LB weirdness. Only the actual Data XML files LB needs should be in that folder.

For others, in case question comes up on how to do, you can put in "model3.cpp" in the Driver tab under "Source File" for the Sega Model 3.

That is because you have to go to Additional Filters, then put in Naomi into the Required Bios section. You are telling it to look for games named with Naomi which is why you only got one result.

Here you go:

I have never quite been able to track this issue 100% and like JoeViking245 said, sometimes alt tabbing eventually fixes. But I have had some that something is obviously "pulling" the DMD back behind the main screen window. Option 1: there is a pup pack utility that can use to z-order the running DMD back to top (don't have to use PUP Packs, but it was designed to help with same issue there). I have had "mixed" success with this and can be non-intuitive to setup initially. Option 2: This option always "works" to fix DMD not on top. If willing to put in some minor table editing, you can fix the code in the table to embed the DMD as part of the main table display. The main thing you lose by embedding the DMD is if you are using Freezy's DMD and/or full color mods because you are using Visual Pinball's built in DMD process versus an external DLL. The embedded VP DMD is also limited in color flexibility (4 options). Once you figure out, the general principals apply to any table you want to embed the DMD into the desktop. Oddly, this coding is present in many tables, but the authors have tended to "undo" much of it on assumption most are not running in desktop mode (even though there is code to say "embed DMD on desktop, else turn off". Step 1: Open table in editor. In this case I will use the table 24 by Stern. Click on the icon that looks like a pinball table that toggles to backglass view. Most times, you will not find the DMD text box, or they have drug off screen. To make one go up to "INSERT" in the menu. Click insert "Textbox". You can quickly place it anywhere/drag size (don't worry about placement, will fix later) Step 2: Now make sure you click on the text box so highlighted (shows below in shot below). You will see the "position" options at the right. I typically just use 25,25,290,84 or something similar to place DMD on upper left. You can adjust but most DMDs are similar size once get hang to it. The most important item here is that at bottom right under "STATE" you will want to type "DMD" (no quotes) in the box labeled text. Basically, that tells VP that the Textbox is to be used as a DMD. Now you have told VP where the DMD is placed so next is to adjust some code. If you look at tables done by JPSALAS he almost always uses the proper embed "DMD" code since he is on desktop. So, you can use them as examples as well. Also, you can adjust the "brightness of the DMD by the option on the right called "Text color" . Setting at higher than 1.0 makes brighter DMD. Also, if want DMD to be colorized, need to click on the little box in the Text Color option and make white (most times it is "orange"). If like orange, can just leave it as is. Sometimes just doing the above will work since the code is in the table, just the text box DMD was purposely removed. In the case of 24, most versions I have seen have the code already in it so don't have to change/add. If run table and don't see DMD, then proceed to next step. The code that is doing the embedding is the text below in red for 24 (click on Scroll icon on left panel to bring up script window). Step 3: In the case of the table 24, all of this code is already in the table. But for others, if the block isn't present at all (do search for "DMD") then typically add near the first 100 lines of code (i.e., beginning) after you see the first set of "DIM" variables. I would work on a duplicate of your table so in case mess stuff up can go back. Below basically says set variables for (DIM commands) then if in desktop mode display DMD, if in cabinet mode, don't display DMD. Dim UseColoredDMD Dim VarHidden If DesktopMode = True Then 'Show Desktop components UseColoredDMD = true VarHidden = 1 Else UseColoredDMD = False VarHidden = 0 End if Sometimes have found that some tables will only work if substitute all references to UseColoredDMD variable with one of the following (in order of what found typically works): UseVMPDMD UseDMD UseVPMColoredDMD After you do the above, the DMD is fixed on the desktop and cannot be moved around but also will not move under the main window. It is part of the main screen. The other benefit is that if you use JoeViking245 video plugin for VPX that it will record the DMD as part of the video.

Yes, you also have the option of dragging and dropping the ROM file into LB under the platform you want to add to and it will start the process to add. For adding a few that works quickest/easiest. If have a full MAME (arcade) set and are using the "Import, MAME Arcade Full Set..." import feature, then you do not use the scan for added ROMs feature and/or remove ROMs or it will cause issues for most situations depending on the set type you have (i.e., merged, split, unmerged). Correct. Full set importer is basically just pointers and really doesn't "import" anything like for non-Arcade ROMs. The advantage is that LB does the work to know where ROMs are and understands how the MAME naming convention works so metadata is (mostly) correct. The assumption is that you have a full set. The set is only modified by your selections on import (i.e., region, skip casino games, etc). If don't have or don't want a full set and only one offs then don't use the fullset import feature. But then it is up to you to know how MAME works well enough to know what ROM to import and typically you will have to "help" the metadata search in LB DB since the DB won't know how to parse the zip ROM names (looks for the actual game name in DB). The fullset importer features uses MAME backend files created by the MAME developers, so LB "knows" what the MAME ROM names are and what MAME (per the MAMEDev group) named the game. That is distinct/separate from the LB database. You can tell this in that the genres that MAME uses are hyper granular compared to what is in the LB DB. So, if the game was just added in MAME the game will still import and have a name with limited metadata even if not in the LB DB. If no one has added it in LB DB you won't get images and any additional data beyond what the MAME Developers included.

For this the easiest I have found is using FreeFileSync and then periodically updating the other PCs from a "master". It can mirror the setup, or you can pick and choose (which would be lengthy process first round). It has a save function so you can replicate what folders/files you want to copy. LB is still locally installed on each of the "child" PCs (particularly the image cache) for speed purposes. Somewhat depends on the intent of the child PCs. If they are full copies and similar capability (i.e., can run all same emulators) then relatively straight forward. The mirror function only copies changes/updated files after initial pass. The key is making sure all the paths and drive letters are the same on each (either for local drive or for NAS). The "Data" folder for LB is where you have to be careful and not mirror to other child PCs beyond the initial if the child PCs have significantly different setups (or you will lose the customization on those PCs). If using a NAS, then don't have to mirror games (but can come with speed hit if have slow network and depending on emulator). For example, for the "kids" setup it was a massively stripped-down version of my master setup. I mirrored over initially a LB setup from master and then on that local PC stripped out the emulators not used, deleted games, etc so only included what want. Brute force approach, but really didn't take that long. At that point only sync is done on the games folder and media but not the LB data folder or other emulators not used. Rarely do I update that computer since it is mostly very small set of MAME games, and cartridge-based games (PC is too slow for CD based). Basically, this is what you described, copy over, delete what don't want. Even for the cabinet, my experience is once you get that running, you REALLY don't want to mess with things that much. I use that cabinet copy as "it works" if I mess up something on the Master (my main gaming PC). Plus for cabinet, you usually have different setups for things than on PC (controls, screen, etc). Again, found it easier to master over the whole thing, get it setup to cabinet specs and then setting FreeFileSync to only copy folders like media, roms, game files and not touch emulation folders and LB data side.