sundogak

There are these.

It was never in the LB DB. The Shooter/ Gun" was likely coming in from the MAME import XML during your initial import if used full set import or told LB to use MAME metadata. If you ever update via LB DB it overwrites the MAME genre (and player modes).

Ahh..didn't check that it is in "Android" thread. Sorry about that.

These are the variables that I am aware of (no good place documenting so just picked up via change logs, etc): %romfilename% - Filename of the ROM WITHOUT extension %romextension% - Extension of the ROM file (ie, .rom) %romlocation_noquotes% - Path to the ROM without quotes %noromfile% - Replaced with empty string, suppresses rom file being added to end of the command line %romfile% - Rom name with extension Have you tried %romfilename% or %romfile% as this should work for what you are trying to do.

Beta 3. Disabled platforms not working uniformly. I had 7 platforms all checked with do not auto import and it is importing anyway. It took time to start the first time as turned on disabled, changed the platform folders, and nothing happened for about 15 minutes (as expected). But after I left and came 20 minutes later there was the pop info that it had imported 1,000s of files and downloaded media. All of which were in those disabled platforms. One platform as example was Sinclair ZX which was pointing to my main ROM folder and Disable ROM Auto-Import checked. There were a few games from prior I had manually imported from the folder but it installed the entire directory. It did it again after I exited out, restored to prior XML settings and restarted. Again after about 15 minutes or so it started importing the same 7 platforms all of which were checked to disable. One theory is that if you are pointing to a folder (even with disabled checked) and there are some games already installed in that platform within that same folder it is ignoring the disabled box (but haven't fully tested that). I didn't have debug logs turned on but will try it sometime tomorrow and see.

Is there is a list anywhere of what extensions auto import ignores?

Have no idea. I never let LB mess with my ROMs or move/copy so never use that feature. I only mentioned how you could fix the platform issue you described to adjust the rom folder path.

You named it Sega Megadrive and thus it picked that as platform exactly as you told LB. Platform and what you select for Scraper are completely independent. LB prioritizes what the platform name is for folder selection. Thus, you have two options: go to the edit Platform "Game" entry and browse to your Sega Genesis folder. Easiest but could be confusing down road. LB will look there for any roms for that platform. rename your Sega Genesis folder to Sega Megadrive. You will have to relink games but I believe with the new auto import feature on it will do that. If not you will have to reimport so path matches. You could also manually edit the Platform XML but make sure you have use LB backup feature first.

The auto import feature isn't working for files that have these extensions (this beta and 3.16): *.txt *.xml I tried on completely new LB install and cut and paste in a "ROM" file with same exact name and anything with above will not be seen by auto import. Variations of "*.t2t" work so suspect there was something added to ignore these extensions. As Emulators like TeknoParrot point to XMLs excluding these (if that was the intent) breaks importer for these type setups or where *.txt files are used as pointers. Less issue for txt files as could use another extension for text pointers. But not so much for XMLs as that is what TeknoParrot uses as the profile to run.

In their Discord eXo specifically discouraged changing to another DosBoX version this as they have tested the specific version of DosBoX with each game.

Something doesn't make sense on your paths. The third party folder is part of Launchbox install. ExoDos files are within the Launchbox directory (see snip below for working setup). Your Third party folder is in a parent folder of "ExoDos". Other than the issue you are having it will potentially cause others both with LB and ExoDOS. You are also using an older version of LB is up at 13.16 so would install LB first then merge in EXO files (he has info on how to do).

Yeah, during the beta I had the text point method prior as well. I do recall I had to nuke the platform and emulator entries and restart (similar with PS3) but was assuming it was a beta thing. Glad you got it sorted.

Updating MAME sets (i.e., #1 above) is usually easiest if using tool like TorrentCheck. You go to Pleasuredome Git Hub, download the Torrent file for your set type (you have to start a temp Torrent as they use magnet links, then stop torrent). Take downloaded torrent file and drop into Torrentcheck, point TorrentCheck to your MAME set and run it. It will rename (if tell it to) files if checksum matches, double check valid files and leave them, delete non-valid ROMs no longer in set (will backup if tell it to). Then you can rejoin torrent pointing to the folder and will only download deltas for that set. Easier than messing with CLRMAME Pro and update packs (for me). If you are completely downloading a full non-merged set each time and nuking your folder with fully updated then could do as proposed (with no Torrentcheck stuff). However, if downloading an UPDATE only set (i.e., not full non-merged) and overwriting your existing set will work MOST times. What you will get eventually is rom files that are stragglers. The reason is MAME does rename things so even with a non-merged set you could have an older ROM name in folder which won't get removed along with the new name. It won't hurt anything as these are fully standalone zip game files, but longer term could get confusing. Although bandwidth is less issue these days a split set tends to have less delta changes. For example, if un-merged and one driver change could cascade to multiple standalone zip game files whereas with split and to degree merged will be less zips to update. I also use split for both software and arcade simply because can easily see the clone zip files and it is slightly smaller than non-merged to download. If bandwidth and HD storage not issue and not concerned that have a lot more zip files (as shows all clones) then un-merged can be easiest. Scan for new ROMs should work assuming you have pointed your MAME platform folder to your ROMs directory. You can test by deleting a game in LB or putting a "new" dummy rom in your MAME rom folder. If do a scan LB will pick up that game zip and re-add it. If you have auto import turned on then LB will see the new dummy zip and add it. So you could do initial full set import, make your customization, then only depend on scanning for new ROMs for updates vs using fullset MAME importer tool. As for, "Scan for Removed MAME Roms" feature that should be avoided regardless of set as LB will delete CHD games and a few "no zip" games. LB puts in dummy rom pointers in pathing of the game for some CHDs without a corresponding ROM zip but the ROM doesn't physically exist (speaking ROM not the CHD file itself). If you scan for removed ROMs, LB simply looks to "is ROM there are not" and will suggest to delete the game as there is no zip file in the ROMs directory (it is the CHD file). There are some other oddballs like "Pong" which has no direct ROM file which will also get deleted if use this scan/remove feature. Example: all these games exist/work in MAME and shouldn't be removed:

Yes, blank folder or LB will wind up doing what you saw (to me should be some logic to stop this if auto import on but at moment not the case). For Vita3K and PS3 RPCS3 if using auto import feature LB uses the Vita and PS3 emulators to determine pathing. Thus it is a "must" to have games installed properly in the emulators when you open them. If not in there then LB will not pick up. If you point the folders to the rom folders then LB imports all the other files in addition to what it sees via emulator. Where the empty folder is located is immaterial but here is mine: Here are the other setup screens: This is Metal Slug 3 path that the auto import feature automatically places. Notice it isn't pointing to eboot file (by design) like the "old" way prior to auto import method. The key for that is the switch " -r" which tells Vita to run any eboot file in the installed path (hence why above game only points to folder) This needs to be checked to have LB use Vita (and PS3 RPCS3 which is similar setup) The key here is that for most part you never need to run "Scan" anymore as the auto import will pick it up. You can and if setup correctly as above it shouldn't pick anything spurious in the folder paths. Sometimes the auto import isn't immediate but will eventually do its thing (force a scan usually triggers). Side note (for non-Vita, RPCS3 emulators): The pointing to empty folder trick also works for platforms you do not want LB to do its normal ROM auto import thing. For example, I have Visual Pinball and do not point the rom folder in LB path to the VP tables or it will auto import EVERYTHING and it is a mess. Hopefully they will improve this at some point but originally was reason I avoided auto import feature.

There are two aspects here. 1) updating MAME with new sets 2) updating LB to reflect new MAME sets. For #1: the set type isn't as critical as long as consistent in type you are updating. I personally use a split set but for #2 (discussed below) LB doesn't care (merged, split, non-merged) as the Mame Fullset importer uses MAME's XML metadata to make pointers to the games as doesn't really "import" the roms like for other platforms (again assuming not manually importing and using LB MAME Full set Importer). There are ways to update the sets which can provide more detail if that was your question but assume it is more for the LB portion. For #2 (and this is assuming just Arcade set, not Software List MAME set): Always make backup of metadata via LB interface before doing import in case you have to revert The only "sure" way to keep customization is to do initial import via automated way, do your customization, then do manual per game import for any new games you want to add thereafter (i.e., drag and drop rom into LB window) and never using Fullset importer again. If delete MAME games from LB and do fullset import, all data will be back to "zero" and revert to MAME XML metadata provided by MAME team and all customization lost (and back to what you had where have to redo). To see the MAME metadata fields you can look in the Launchbox\Metadata\Mame.XML file. If do not delete MAME games from LB and import over top via fullset importer, any customization to metadata not in MAME XML will be retained as long as ROM file name stays same. Custom Fields will also be retained. Most times ROM names (at least for arcade) are relatively static so the ROM name changes are not usually a huge issue. Fields like Favorites, Hidden, Broken, Video URL, Star Rating, and Wikipedia entry will also be retained as not in the MAME metadata set. However, will lose changes to fields like Genre, Play Mode, Developer, Publisher, Version, Title with what the MAME team has in their metadata. For example MAME likes to put in names like "Aero Fighters 3 / Sonic Wings 3". If you change that and then do subsequent import it will revert back to the "MAME way". If file name of ROM changes then as far as LB is concerned it will be "new" and although it may match via LB DB entry (via name) any customization will be lost. If do import and then do a LB "Update Metadata and Media Wizard" then LB will look to the LB online DB and will replace data based on what you tell it. However, just like any changes you make if you then subsequently do a Fullset MAME import the LB online DB data will be overwritten back to the MAME XML metadata. Genre is perfect example, where you can see this as MAME uses genres like "Platform / Fighter Scrolling" where as LB DB will use one entry like Platform. Ideally what would be useful for LB is if we could "lock" fields and/or prioritize if data present do not change similar to other platforms (for various legit reasons it is different for MAME now). But for moment, metadata customization is problematic with MAME.

If these are Epic, Steam, Uplay games then LB now has a storefronts setup that is new since 3 years ago. Make sure you have gone to menu Tools, Manage, Storefronts and logged into applicable stores. You can have LB rescan the store to make sure they match based on drop down box selection. You might double check your platform for your PC/Windows is pointing to your folder (if manual imports) where files store. Lastly, if they are manually imported PC games then you might look at your Launchbox, Backups folder and inside that there are auto backups of the XML data files which are the pointer and metadata LB uses. You can go to Tools, File Management, and Create Backup to make a snapshot of what you have currently (just in case). Then you can close LB and look for the backup (they have dates on zip files) and under the Platform folder restore the platform XML for whatever you called you Windows/PC games.

The difference with Nocta’s situation and yours is you are still pointing to the ux0 directory. Point to completely empty directory (no sub directories).

Nothing with the wheel style of PinupPopper. However there is a vertical theme here: https://forums.launchbox-app.com/files/file/3925-vertical-vision/