sundogak

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

I would try this: 1) setup another MAME emulator as a test (so don't mess up your working MAME). Call it MAME_MESS or something like that. 2) Associate this MAME version with Entex Adventure Vision. Under default command parameters put "advision" with no quotes. See second screen shot 3) Under the Edit Emulator panel make sure to check the "use file name without file extension or folder path" (it will gag MAME if has file path or "zip" in the name used to launch). See first screen shot 4) What MAME is wanting (and seems to deviate from the normal -cartslot method) is a command like "mame.64.exe advision defender" 5) I tried launching via command line with full path and doesn't work for some odd reason (works with Apple and other computer software lists so not sure why deviates). It needs to just be the simple rom name and not path (see last screen shot).

@Valkie71 Would double check settings as noted in the two screen snaps since have no issues. Double check pointing to the Steam executable and not the PinballFX3 executable. Also cut/paste in the code under the Default Command Line: -applaunch 442120 -table_

@cleverest Most of the space hogs are movies since ripped all my blu-rays (and a few UHDs) for Plex. My arcade "active" set is on a 5 TB drive that I try to keep pruned so it fits on portable hard drive. I keep a backup of that on the NAS, so not pulling from it for play purposes. A 4 drive NAS is nice setup and with the higher density drives can get a lot on them.

@starfiretbtI made a playlist for arcade games and have it filter for any MAME genre that contains the word "mature" and it will pick them up if you use the MAME importer since the genres are pulled in. You can then select all and hide those games so don't have to delete. In BigBox it will not show a playlist if all the games are hidden. If set a PIN in BB then they cannot unhide and cannot exit (normally). The limitation is that you cannot hide a playlist in LB (was a feature I was hoping would get higher on the poll but didn't make the cut). So the playlist will still show if rooting around in in LB side and obviously the files themselves along with art are still on the drive. So it isn't high security but does keep from stumbling across when in BB. The only other alternative is to duplicate your LB and keep a kid friendly import version and then master.

Its a bug with Zen if you have both Mars and Attack from Mars on FX3. At one of the pinball sites noted to do the following: Duplicate the "mars.pxp" Rename the dupe to "Nars.pxp" Then link to the "Nars" file for the "Mars" table within LB the same way you do for other tables. I have done that and launches the correct one.

@LordmonkusFor the media, so media has the same name as the ROMs rather than arbitrary -01 etc. Edit: Actually..sorry misread the original thread! TheMan8631 was talking about ROMs....ignore everything I said...I was referring to renaming of media to ROMs.

This feature was on the recent feature poll, but sadly it didn't make the cut (last item in the "round 2" list). I have wanted this feature for awhile as well, particularly for MAME. But it is not likely to be priority at this stage until other things are crossed off the higher ranked items in the list.

@cleverestI have an 8 bay Synology with 2-drive parity disks (64TB usable). For large disks, it takes a long time to rebuild (~48 hours for 10TB depending on usage of system concurrently). So at least for RAID 5, large number of bays, if you have another drive crump while the disk is rebuilding, then unhappiness. Rebuilding puts a lot of stress on rest of disks so if something is wonky, likely that will happen then. Unlike UnRaid won't be able to easily recover data off the others if parity disk(s) and another fail. When had a 4-bay ReadyNas only ever used 1 disk parity since sucks up too much space otherwise. Have used WD Red Drives and now using Seagate IronWolf drives since the delta in pricing between two started getting a bit much. Have had some 5 plus year old Reds start throwing errors but never outright failed before replaced them. Never had any issues with Synology but they are fairly "proud" price wise of their systems. It runs 24/7 with Docker apps doing various things along with data serving. Definitely UnRaid gets a bigger bang for buck and flexibility/features whereas you pay for Synology to make more appliance like (plug and go). In the end, don't depend entirely on RAID. Backup key items (Nice CloudSync feature in Synology apps for example). I have never (knock on wood) had a catastrophic drive set failure but Murphy is always waiting to slap us upside the head!

Did you log into EMUMovies?

If you want to only have one cover type you have to remove the other versions. So if want only the UK version, remove the US, Japan, etc. There is no way to set a cover as default on per game basis at this point.

I have this same behavior as well. Seems to have popped up somewhere in the last few versions since that was not how worked in the past. As noted it is limited to the details fields whereas the tab fields work as expected. Also noted the "version" field works fine so looks like anything that is drop down exhibits the issue.

I have FP, VP, TPA, and FX3 all installed and working within Launchbox but you have to go through some hoops with most to get them working well. In most cases, it isn't LB problem but just the nature of the Pinball programs that nothing is quite as simple, particularly when it comes to mass setup. The other time suck is lack of central repository for media that makes it easy to map to your install and lack of table naming convention. Media setup took a huge amount of time since LB DB isn't of any use for pinball. So depending on how media crazy you want to get can take some time even for something as basic as getting clear logos. If you want to do a full on pinball setup with multiple screens (table, backglass, DMD) then LB isn't likely the best suited for such setups. I have a two monitor setup with the main screen in "desktop" mode and the second where the pinball program will allow, as a backglass and LB works fine in that use case. I was hoping LB would get some additional pinball love but based on recent threads that appears it won't happen anytime soon. So was holding off on any sort of "how to" but may revisit since nothing is changing now. If you setup just a "curated" pinball setup things can go pretty quick but if you want a bunch of tables then it takes a lot of time to setup, particularly for FP and VP and add to that media setup time. But the short(er) version is this in somewhat order of difficulty in setting up in LB (and in general) from easiest to most fiddly: FX3: You have to have the cabinet mode turned on by getting a code from them. This allows you to launch to a specific table in LB or it is like TPA and won't launch to specific table. The advantage is that with the code you don't need another program. I have found the Williams tables in "classic" mode seem to be pretty good physics wise. Their goal there was to replicate real tables unlike the "new" tables. The one thing I like about FX3 is that it "just runs" without a lot of fiddling around. I do have a back glass setup which isn't quite as fancy as FP, and VP in particular but works for my purposes. TPA: you can integrate into LB but to allow it to launch directly to a table you have to use TPAFreeCamMod. This also allows changing of the camera position but I only use it for its ability to let you launch a specific table in TPA from a command line. By itself, TPA will launch in LB but just goes to the front end menu table view and not direct without the mod. Otherwise, setup is pretty straight forward. Future Pinball + BAM: Future Pinball as noted isn't developed anymore but BAM changes the game in that regard. BAM adds many features including lighting and physics adjustments that couldn't be done in FP and BAM is updated frequently. With BAM, it fixes a lot of the issues with FP. FP was the first pinball setup I did but wound up doing major revamp when I installed BAM, mostly to fix the things I ignored the first time. For FP and VP, you have to come up with some consistent naming convention and stick with it or you will go insane with the different versions of tables and the various files needed. Naming will also help with media later on as well. In my case, I went with the "Table, Maker, year" name so that "The Addams Family (Bally 1992)" is what stick with for folders, table names, and the associated physics xml (if there is one). One key thing that helps here is that contrary to almost all the setup guides, you can put all you FP files for each table in an individual folder. This helps a lot with BAM and keeping track of versions since you can put the table, sounds/media (which have no logic to naming and you cannot change them easily), XML physics file, and other scripts in one folder rather than all files dumped in tables folder in flat file organization. The big advantage with BAM is that you no longer have to have different exe files for different physics. You just change the XML file (which is name exactly as the table and in same folder) and the physics is adjusted or you can customize it within BAM. One problem I noted with some sets you get off the internet is that the XML physics files are not always present so the table will be "Physics 2.6" but the XML will be missing which makes for really wonky physics since most times you will setup BAM to default to 1.0 physics (FP vanilla). If your ball is sluggish or the plunger seems to not launch the ball, then double check the table physics version and likely don't have the correct XML. I also stuck in most cases with "one version of table" setup. I have about +750 tables but didn't setup the zillion different variations. Where possible, I went with the most recently updated and http://www.pinsimdb.org/ is an invaluable resource both to see what the physics for the table is along with checking version. After messing with tables for awhile found best to put a text note in the folder with the physics and version and then I could name the table to its main name and not get into "The Addams Family Ultimate 1.02" naming in LB. A example is below: Within LB, it will pickup name prior to the ( ). This can be a problem with some tables since there are originals with same name as a recreated table. There are also some tricks (using the Microsoft Compatibility Administrator tool) to use to set it up so you don't have to get the ADMIN elevation warning in Windows. FP wants admin rights which is a pain for front end like LB. I have FP pretty much setup with almost all media except still missing a number of videos but I do have logo, backglass, and table view media for all 750ish. VP: I avoided VP for a long time simply because of the mess of different VP versions and table compatibility coupled with the whole VPinMAME aspects. But took second crack after got the others above figured out. My first thing was I decided to only go with VP X only. Since many of the popular tables are or are being updated that seems to not have been a limitation. VP is typically the easiest to get setup in LB since doesn't have any other programs needed and seems to play well with Windows overall (i.e., no admin like FP requiring a fix). VP is also under continual development. VP seems to me to be geared towards the full on pinball setup with DMD, table, and back glass setup. For that it has lots of powerful features in particular the ability to have custom back glasses that can be lit with different flashes if setup in B2S. However, the back glass feature took a lot of time to setup in relation to FP where it was relatively quick. Of course you don't have to do a back glass so that simplifies if just want to run a table. Getting the DMD/VPinMAME setup took me some time and you run into issues with then having to find the ROMs for the DMD in addition to the VP table. Not all tables use VPinMAME but most of the "recreations" do. The one thing I really don't like about VP is that it is a pain to change the camera view. Whereas in the others above you can map to your controller clicks to change the camera angle, with VP they make it an exercise. With VPX tables you can setup "POV" files which alter the camera view but it isn't a simple "click" of button. Also some tables come setup for a full pinball machine setup rather than desktop so it means fiddling around with the table code to "fix" it. Many of the lighting for tables is also "dark" to my eyes so again have to fiddle with table code on table by table basis to fix it since no "global" fix like you can do in FP. I have about 425 tables and have about 100 working the way I want in LB with backglass running and DMD positioned correctly. I decided to take a break for awhile from VP before tackling the rest including media hunting. VP can also be setup by folder for each table (like screen below for Addams Family) although I found its gets fiddly if using B2S. The one other nice thing with VP is it seems to work with the LB Pause Screen feature where as the others above have various issues. As far as physics, with FP+BAM I don't notice much of difference but then I haven't had VP up and running long enough to do cross comparison extensively. Anyway, hope gives some basic frame of reference on setup of each. To a large degree, getting a table running for each in LB isn't too bad if do a small curated list of tables.

It looks like your window that is on the bottom is drug all the way up to the top. If I take the red circled window bar in LB and drag up it looks similar (although you snap doesn't have any text which is odd). See if you can go to the top and drag the window back. If cannot grab, try a double click as close to the top edge in LB as possible and see if it will snap the window large enough to grab the gray bar and drag back down. Not sure where the window dimensions are set so if that doesn't work will likely be a Jason question. If I drag window almost to the top.