JoeViking245

Try this instead PluginHelper.LaunchBoxMainViewModel.RefreshData();

Do you have the Custom Command-Line Parameters set to "-input-system=rawinput"?

From what I read, seeing an ID of 5 and 6 is probably correct for your guns. "...as lower ones are usually allocated to the standard devices." Running "supermodel -config-inputs -input-system=rawinput" is probably where got the 5 and 6 from. When you launch a game you will also need to use "-input-system=rawinput" in the command line for it to [keep] work[ing] as separate lightguns.

Short answer, bulk download the latest romset. Long answer (and method), to use the update packs you'd have to use Clrmamepro. Also, to get to the current 0.221 from 0.209 you will need every update pack from .209-->.210 thru .220-->.221. So that's like 12 update pack sets.

If you have your MAME 209 and 221 in separate folders, make a backup of the mame64.exe file that's in the 221 folder. Now copy the 209 version of mame64.exe into the 221 folder (just the exe). Now run that and see if your bezels work as you saw with 221.

Not tested, but my notes do mention the "Super CD_ROM System..." (scdsys). So this all makes sense now. But you wouldn't need to add it to each game individually. In your MAME emulator under Associated Platforms for "NEC PC-Engine / Turbografx 16 CD-ROMs" (or whatever name you gave it), set the Default Command-Line Parameters to... pce -cart scdsys -cdrom .. and you're good to go.Thanks @DOS76 The Atari 2600 cassettes is similar in that it needs the Arcadia (Starpath) "SuperCharger" loaded as well.

@isamu Thank you very much for the kind words! Questions, thoughts, input, opinions and suggestions are always welcome. The 2 options are for how it sets up (Imports) the rom file location into LaunchBox. So depends on how you plan to emulate them. If you are planning to (attempt) to run softlist chd's with MAME as your emulator, definitely choose the 1st option. MAME launches the games using the [short] zip filename (just like Arcade), then (because it's smart) it knows to look for the chd to actually load and play. For Other emulators that are able to run the MAME chd's, they need to know the full chd file name. (A request was made during early development to add this option [full_file_name.chd v.s short_MAME_name.zip]) Both options will give the proper Title so LaunchBox can scan for metadata (the original intent of this plugin) 1st option "MAME" 2nd Option "Other"

*New v3.0 - New Audit Feature. Compare your existing softlist Platform against the MAME hash.xml. Will cross check Title and Rom names. - Select the respective hash.xml and Platform - Click Audit (last page) - Any differences along with a brief description will be shown. - Option to select files (if any) and have them removed from your LaunchBox Platform. - Will check main Titles as well as Additional Apps (if you imported them separately). This does NOT check rom integrity. That's between you and Clrmamepro (or related utility).

Not familiar with MAME Plus. But in "Edit Emulator", try un-checking both "Don't use quotes..." AND "Use file name only....". Also, you sure the - [dash] is required in the command line?

skip_gameinfo is under "CORE MISC OPTIONS". ("1" to turn it on) You won't find a skip_disclaimer setting. You need a special build of mame64.exe for that. Myself, never heard of the the skip_validitychecks.

@Lennygundam14 So glad it helped!!! And Thank You for taking the initiative to search the forums for answers to your issue.

Correct. It's a 'Windows seeing 3rd party software attempting to access special folders' thing. It might also be a LaunchBox seeing this [type] folder location and saying "I'm not even going to try." Hence, no prompt. You'd see the same thing if you placed them in "C:\Program Files\" and several others. What I've done is created the folder "C:\scratch\". In there I'll put roms for testing, programs to try out, etc. I have too much shtuff on my Desktop already (a personal problem ) but also a shortcut to my scratch folder. Of course when testing roms in LB, you need to point to the actual folder and not the desktop [shortcut] one.

Thanks. But I don't think this is going to happen. Not by me at least. Too many little nuances to do it properly, but I have found some checks and balances I can add in that will [hopefully] help. - If they're simply adding new roms, the plugin already covers that. - If they change the Game.Title, you'll end up with 2 Titles pointing to one rom. (Blockbuster, Block Buster) Delete the old one. - If they delete a rom altogether, manually delete it from your Platform (and roms folder). Or not. - If they rename a rom, my proposed checks and balances may cover that. May need to delete something as noted above. - If they rename a rom AND rename the title AND re-associate a rom AND add a rom (see "Connect 4" example in previous post), my proposed checks and balances may cover some of that. May need to delete something(s) as noted above. but I make no promises. After adding in the 'checks and balances' (and assuming they work), I may add in an audit feature that will display differences between the hash.xml and LB's Platform.xml mainly covering discrepancies between Titles and rom names. Again, no promises. Worse case scenario, delete the Platform and import anew. You'll need to re-import the metadata, but not the media (assuming no changes in the Game.Title).

OK. That one is all messed up. lol But I think I see how you ended up with 21. The Game.Title (description) was the biggest killer (as you mentioned). And the Connect 4 series didn't help matters either... old new <software name="connect4"> <software name="connect4o" cloneof="connect4"> <description>Connect Four (8021)</description> <description>Connect Four (8021 version)</description> sha1="971f9117dc809f7b9796134208b47ea34990ae71"/> sha1="971f9117dc809f7b9796134208b47ea34990ae71"/> <software name="connect4t" cloneof="connect4"> <software name="connect4"> <description>Connect Four (TMS1100)</description> <description>Connect Four (TMS1100 version)</description> sha1="e93d848784205ab49234ad26718e04d267b776ed"/> sha1="e93d848784205ab49234ad26718e04d267b776ed"/> As you can see by the hash #'s, the Parent became the Clone, and the Clone became the Parent. So if someone merely copied the update pack into their fullset without running crlmamepro 1st, they wouldn't have connect4o and their connect4 wouldn't be the actual parent. connect4t wouldn't be seen and I guessing none of it would work in MAME. So I am actually looking into the logistics of fitting in Update scenarios. Not sure how pretty or not it's going to be (the code OR the outcome). We'll see.

Ya, 'updating' is beyond the original intent of the plugin. But is the next logical progression for a version 4.0. I'll add to my "I'll think about it" list. I'm curious to look into your 3 - 15 -18 - 21 - 17 files/games example. I guess it's more of a morbid curiosity. Which sofltlist set was that in?

Your Playlists are saved under ../LaunchBox/Data/Playlists So I'm pretty confident that you can simply copy the one (or the whole folder) over to the other machine, start that LaunchBox (because LB was not running when you copied them ) and be good to go.

Dude!!!! It's designed to import! Not update! Now that I've got that out of my system.... Here's how it's setup... "Copy AND Import" - the Copy roms part: A - It will copy AND overwrite (replace existing) all roms as per your selected criteria. All. No clones. No prototypes. No non-supported games. Or a viable combination there of. B - It does not and will not look to see if an existing rom no longer exists (is obsolete) in the current [updated] set. Theory: Part A - Say a game was updated but the rom's name didn't change. You'd want the original overwritten (replaced) by the new one. Part B - Don't want to delete something that is 'obsolete' per MAME, but the end user wanted to keep. "Copy AND Import" / "Import Only" - the Import part: Importing separately - If the Game Title does not already exist in the platform you're importing to, import it. Importing additional Apps (Clones) - If the clones' parent already exists in the platform you're importing to, AND the clone is not already an additional app to that parent, import it. Your First Situation. Hmmm.... I think "Yes." If the file to copy doesn't exist in the Source folder, it skips it and jumps to the next one "in the list". So if your Source folder is your Update Pack folder, I suppose the Copy process would actually go a lot faster. Nice one! I like it. Hmmm... unless you do the clrmamepro process 1st. 🤔 Second Situation. Unfortunately any subsequent changes you make to your LaunchBox Platform in this manner will not be addressed with a new (eh hem.... update) Import. The process to scan all existing Parents and all existing Additional Apps associated with each Parent to see if a game to be imported is listed as a Parent or an Additional app would, in-the-end, utilize quite a bit of resources and will definitely increase Import time. Ain't happening. Easy fix 'taint so easy. NOW.... if the games in question were not in your update pack Source folder, I t h i n k you'd be OK. One sure way to find out. lol Plan B, edit the hash file before importing and note those files as clones. Example: change this <software name="cpm8607"> to <software name="cpm8607" cloneof="cpm86"> When updating (as much as can be) be sure to update your hash files as well for Importing. (Though "common knowledge", I try not to take things for granted) Yes. Funny thing is I thought I had done this. But I guess if you only have a couple Emulators and the 1st one on the list is "MAME", it would appear that way. lol I've added this to my to do list. As Always, thank you for your love and support. Keep the comments, concerns and suggestions coming.

@Tripno Short answer, Yes. The LaunchBox UI/program/Front-End does not install anything outside of the folder you installed it to and uses (mostly*) relative paths from where the executable file (LaunchBox.exe) is located. So if you install it in C:\LaunchBox\ and copy that to E:\LaunchBox\, the UI will work just fine. The caveat is in where you install the emulators and roms. If you initially install them in say, C:\Emulators\ and then copy this and C:\LaunchBox\ folders both to E:\, LaunchBox (executed from the E:\ drive) will look for the emulators using the *absolute path.... "C:\Emulators\". The simple fix is to install the Emulators and roms within the LaunchBox folder structure. (i.e. C:\LaunchBox\Emulators\) LaunchBox will then store them as relative paths an all will be good when you copy the LaunchBox folder to somewhere else. "The simple fix" only accounts for part of it though. If the Emulators themselves aren't "portable", well... back to the drawing board. LaunchBox won't fix that. That's a loaded question. Barring the fore mentioned caveats, Yes. Will it run well? That, I cannot answer definitively. When you talk about running off a USB 'stick', you run into concerns of read/write data access speeds and possibly a mess of other things beyond me.

Glad you figured out "the button" to avoid.

Yes and No. As of Dolphin release 5.0-12038, you are able to load save states from the command line. But the Dolphin Triforce branch needed for MK GP2 cannot. Take a look at the Dolphin wiki for this game and apply the patches listed. I believe those are all that's needed [now]. As in you don't need the save state.

You mentioned creating an AHK script. Not sure if this would work with it starting in full screen, but as a start you may be able to finagle something from it. Sleep, 3000 ;wait 3 seconds (more time?) Send #+{Left} ;Send Win+Shift+Left (or change "Left" to "Right" as necessary) Return

How are you bezel creation skills?

tc4.zip in with your regular MAME rom set. It works but you need the stencil your own playing field and score board on your monitor.