mcfilmmakers

I'm running the latest Retroarch and have installed the Flycast core for Atomiswave (the tutorial on Youtube is outdated BTW). Anyway, I've got the emulator set up properly in Launchbox per the tutorial. The games are imported. Everything is pointed where it needs to. The only difference from the tutorial is I have to use Flycast instead of Reicast and naomi.zip instead of naomi_boot.bin (per the retroarch wiki https://docs.libretro.com/library/flycast/) It says I can use a MAME format bios, so I am. But none of the games launch. Launchbox just minimizes and nothing happens. When I try to load the game within Retroarch directly, retroarch says there are no contents within the zip file, which is not true... the zip files contain .ic## files. So what am I missing? Retroasrch says I should be able to use Mame files as they are so... why won't it work? Edit: The games all run in MAME so it's not my files causing the problem.

I have the same problem. Selected 23 files, Import as ROM files, select Force Importing duplicates but Launchbox will only recognize 4. If I select None of the above, launchbox will recognize all 23 files but then I have to bulk edit to tell Launchbox what emulator to use.

Milton Bradley Microvision... microvision.xml

I know I can click a playlist and see all the games within it, but is there a way to select a game and see all the playlists it belongs to? The right click -> add to playlist option appears to have two columns (there is blank space tho the left of the playlist titles) but there aren't any checkmarks next to the playlists I know the game is already in. The reason is I want to know what playlist game A belongs to so I can add game B to the same playlist... but I have hundreds of playlists so it isn't manageable to go through every playlist seperately...

Yeah, I updated via clrmamepro first. I'm just thinking of how the plugin grows from here and the natural path in my estimation is to enable updating. I ask because my source folder literally had 3 zip files in it. My platform before import had 15 titles. My destination folder had 18 files (I already did the update with clrmamepro so it was at 15 before the update: 15+3 = 18). After importing, launchbox had 21 titles (I expected to see 17 (I had manually removed 1 entry so 15 + 2 (remember, 1 of the new games is also a clone) =17)). Which means it didn't skip what wasn't in the source folder because if it did, it should have only added the 3 files resulting in 2 new titles. The culprit, as demonstrated, is the sole reliance on the game title during import which doesn't account for MAME changing the name of that title. As such instead of: "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. "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. It COULD be: "Copy AND Import" - the Copy roms part: A - Create a list of files where the filename in both the source and destination folders matches (aka find all same games based on filename). Let's call this GameMatches.txt... B - 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. C - It does not and will not look to see if an existing rom no longer exists (is obsolete) in the current [updated] set. <- that's cool. I don't expect the plugin to do this. "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, check if the filename.zip in the destination folder (or source folder... we could use either one) exists in GameMatches.txt. If it doesn't, import it (this is a new game); if it does exist, do not import it (the new game title is different from the old game title but they are the same filename.zip therefore, they are the same game) or, go a step further... prompt the user if they want to import anyway. We can show a prompt saying "Blockbuster and Block Buster share the same filename, would you like to import the game as a new title, rename the already existing title (edit the launchbox platform xml of the title to match the software list title), or skip importing this title?" with the appropriate options. 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. As is, the current solution to the problem is to delete the platform entirely and re-import it entirely. Implementing the above would save a large amount of time and effort for the user. Obviously, it may be beyond the scope of your intentions for the plugin and that's fine. I wouldn't expect the second situation to be implemented, but it is a dream scenario. The problem is that when you have literally hundreds of files you manually deleted, it simply isn't possible to edit the hash files manually every time you update MAME (once a month), hence the blacklist. The alternative here would be to keep the title in Launchbox and set it to hide. Not the end of the world, it's just an OCD thing.

lol. So now that 221 is out... what is the update process supposed to be after i've gone through the clrmamepro process? Dragging the files into launchbox results in Titles matching the rom names... which is garbage. The intention is to merge new roms with same names into additional apps of already existing games. The plugin can import the entire platform from the hashfile but I don't know how it behaves with updated sets... I'm afraid to move forward so I'm asking and suggesting at the same time... First situation: Am I correct in assuming that setting my roms source folder to my MAME - Update Software List ROMs (v0.220 to v0.221/platformIwant) folder and the copy my roms to destination towards the location of my software roms folder (launchbox/Emulators/MAME/software/platformIwant) then the plugin will import only the updated roms instead of the entire list for the platform? UPDATE: Answer: no. UPDATE: I ran a quick test with a smaller platform that had some changes: Milton Bradley MicroVision. I tried the above and the following happened: The platform game list went from 15 to 21. However, 221 only added 3 games (1 is a clone). As such, the expected game lsit should have gone from 15 to 17. Here's the rundown of what happened: - the game Blockbuster saw it's name change to Block Buster. Since the name changed, it was imported as a new title in Launchbox even though the filename hasn't changed. Suggestion: the plugin should check the filenames for potential same game matches. - the game Connect Four had 2 clones in 220 (connect4, connect4o, connect4t). When importing 220 (combine clones), the plugin preferred the Connect Four (8021) title. In 221, connect4t was removed. The plugin imported connect4 and connect4o as a new entry, preferring the title of Connect Four (TMS1100 version) base on the connect4.zip file... I don't know if this is because the name of connect4.zip in 220 was different. I'm going to assume that is the case since connect4t was removed. As such, the suggested solution is the same as above. - the game Star Trek Phaser Strike saw it's name change to Star Trek: Phaser Strike. See above suggestion. - I had deleted the game called Demo when I imported 220. Importing 221 brought that game back. Complex suggestion: It would require creating a new file for this to work, but the ability to create a black list per platform would be awesome to prevent this. Especially with larger platforms where I deleted in some cases HUNDREDS of magazine files, creating a blacklist on the Select a Computer/Console to import screen by selecting a platform, then highlighting the game you want to black list (ability to multi-select with shift/ctrl more than one at a time an added bonus) and then pressing on a blacklist game button would avoid importing those games the user doesn't want. A whitelist button would allow the user to undo their blacklist selections. - The two clones combined on import as expected, however both clones are new so I couldn't test how this interacts with pre-existing entries with matching titles. So, in this small set, I had to delete 4 entries. But we have to consider platforms with thousands of entries (such as Apple 2, Amstrad CPC, etc) where it isn't possible to go through the list manually. Second situation: Say you already have imported a very large platform (Apple II cracked for example). The set has MANY same game titles with different names (Zork I for example has 6: Zork I (release 26...), Zork I (Release 75...), etc). Naturally the plugin didn't combine these clones because they don't have the same names, nor would I expect it to. So I manually combine them into Zork I which places them as additional apps with one of them acting as the main entry. If I import the platform again, then it will re-import those combined games (since they have different names) and I don't want them to do that... or am I wrong and it will ignore them because they are found in the additional apps of another title? An easy fix here (if it is a problem), perhaps, would be to have a checkbox on the select how you want your roms imported screen under skip Non Supported games which would say skip all games in Additional Apps with a warning that it can increase importing time (for obvious reasons)... (it should check the file name, not the app title). CONCLUSION: Checking filenames in addition to game titles will avoid double entries where the title of the game was changed between Mame versions. It won't stop double entries where the game title AND the filename changed, but it'll stop 99% of those situations since it is rare both change at the same time. Allowing the creation of blacklists will also prevent having to delete already deleted roms when they are re-imported. I can see the suggestion to simply delete the zip file from the folder coming but what if you want to keep the file in case you might want to import it in the future? (for example, I want to blacklist a working game that isn't 100% emulated to my liking but in the future it is updated to a state I want). Deleting the file means I'll never see it again since it won't be placed in the update packs unless the rom itself changed). Also, another suggestion: is it possible to have the plugin auto select MAME as the emulator on the choose an emulator screen (as long as an emulator with that name exists)... just another QOL thing that reduces those clicks.... and another: the option to remove all text in brackets from game titles (nobody wants to see Connect Four (TMS1100 version) in the title, they just want to see Connect Four.... should accommodate for multiple instances of brackets (ie> Connect Four (TMS1100 version) (clean cracked)) I ask and suggest because I love. Your work has already made the unimaginable possible as is. I would help if I knew how... Thank you.

You said you have a script...

I'm new to updating CHDs... I'm going from MAME 220 to MAME 221. I know that clrmamepro doesn't pdate CHDs per se... is it really jsut a question of drag and dropping the update pack into my MAME roms folder? All the youtube videos completely ignore CHD updating so I have no idea if I'm doing this right... do i scan CHDs as merged or split? Does it matter?

Do you mind sharing your ahk script to press esc twice? Thank you.

lmao. sometimes I wish MAME would get over it's high horse and simulate those elements which cannot be emulated for obvious reasons... at least optionally. I mean, all they really need to do is allow for Overlays...

You are amazing! Curious, I've come across tc4.xml for Coleco Total Control 4 cartridges, however no such folder exists in the software list... am I missing something? (Mame 220)

Something is definitely wrong with your system. My launchbox is currently using 1.4GB ram and is in the middle of importing the N64 software list so there's no way on earth your system should be consuming that much ram.

My point is that it isn't Launchbox's fault. It's just a fact of life. My computer is 8 years old and running launchbox just fine... but I'm packing 24 GB ram.

Awesome. I didn't think it was anything serious. Just wanted to point out the error since it's a scary looking popup, lol. Feature request: auto populate the Launchbox application path based on either the location of the hash file (which is remembered), or setting a manual fixed root path which can be saved... it'll save quite a few clicks. 99% of users will be keeping their roms in the same basic directory as the hash file anyway and since we have to import each xml list individually, thats a lot of clicks to navigate to the same root directory. For example: Hash location: F:\Launchbox\Emulators\MAME 220\hash Software roms location: F:\Launchbox\Emulators\MAME 220\software (most other users might keep roms here): F:\Launchbox\Emulators\MAME 220\roms So based on the hash file, the file browser for the application path (select where to copy your roms to) should default to F:\Launchbox\Emulators\MAME 220\ rather than the C:\ drive. The difference means only needing to select the folder containing the roms and then scroll down to find the folder of the platform (two clicks), rather than select the correct drive and then the correct subfolders (6 clicks total) for each and every platform Ideally, and this would also encompass the minority of users who store their roms elsewhere entirely, they could store a manual root path to have an even better end result of having to simply select the one folder rather than click through their file tree every time (one click total). It's definitely a QOL thing, but when importing hundreds of platforms... those clicks add up fast.

8GB RAM isn't enough for most anything anymore. Windows 10 requires 1.5 -2.5GB RAM on average by itself. Launchbox uses an average of 2 GB RAM by itself for me. Firefox (and Chrome) will use about 1GB. That's about 6GB right there and you're not even running a game yet. I mean, to put things in perspective, modded Minecraft now requires 12GB of system RAM.

My personal hype feature is #26, the fact that a plugin exists means it can be done very easily now

c64_flop_clcracked.xml always gives me an error when i select it: just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index at System.Collections.ArrayList.get_Item(Int32 index) at System.Windows.Forms.DataGridViewRowCollection.SharedRow(Int32 rowIndex) at System.Windows.Forms.DataGridViewRowCollection.get_Item(Int32 index) at ImportMameSoftwareLists2.ImportWizard.Console_Refresh_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.ListBox.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll ---------------------------------------- LaunchBox Assembly Version: 10.15.0.0 Win32 Version: 10.15.0.0 CodeBase: file:///H:/LaunchBox/LaunchBox.exe ---------------------------------------- Protect Assembly Version: 2.0.22.14 Win32 Version: 10.15.0.0 CodeBase: file:///H:/LaunchBox/LaunchBox.exe ---------------------------------------- PresentationFramework Assembly Version: 4.0.0.0 Win32 Version: 4.8.4180.0 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.dll ---------------------------------------- WindowsBase Assembly Version: 4.0.0.0 Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- PresentationCore Assembly Version: 4.0.0.0 Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/PresentationCore/v4.0_4.0.0.0__31bf3856ad364e35/PresentationCore.dll ---------------------------------------- System.Xaml Assembly Version: 4.0.0.0 Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xaml/v4.0_4.0.0.0__b77a5c561934e089/System.Xaml.dll ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.8.4150.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.8.3752.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- Unbroken.LaunchBox Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///H:/LaunchBox/Metadata/Unbroken.LaunchBox.DLL ---------------------------------------- netstandard Assembly Version: 2.0.0.0 Win32 Version: 4.8.3752.0 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/netstandard/v4.0_2.0.0.0__cc7b13ffcd2ddd51/netstandard.dll ---------------------------------------- Unbroken.LaunchBox.Windows Assembly Version: 10.15.0.0 Win32 Version: 10.15.0.0 CodeBase: file:///H:/LaunchBox/Metadata/Unbroken.LaunchBox.Windows.DLL ---------------------------------------- Unbroken.LaunchBox.Plugins Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///H:/LaunchBox/Metadata/Unbroken.LaunchBox.Plugins.DLL ---------------------------------------- Unbroken Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///H:/LaunchBox/Metadata/Unbroken.DLL

It's still happening under the current version

I just updated. The sorting columns text disappears every one in a while in Launchbox. Not sure why. Changing platforms fixes the issue.

Weird, cause mine definitely did not do that and I did those exact same steps.

I've only done mame imports and it worked in the past. That said, it recognized 4 files for 2 games in my screenshots but only 3 imported for 1 game.

It's literally drag and drop. Select all 5 files, drag into launchbox, the wizard opens asking "What type of game files are you importing?". I select ROM Files. Then it asks for platform, in which case I select Irem M92, Choose Emulator: MAME. Use files in current location, search for info from games database enabled, select all to download images, select all to download from emumovies, select Force importing duplicate games, select combine roms with matching titles, then the MAME options screen appears:(I really wish that screen had a deselect all option....) I've done this literally the same way with everything else and never had an issue with unrecognized games showing the filename instead of a title under 10.14 but under the beta it's not working and again, doesn't explain why "2 games successfully import" but only 1 appears.

But that it how I am importing: drag and drop -> roms

In my experience, unrecognized games would still show up in the ist with the filename showing instead of the Game's name. That said, it doesn't explain why "2 games were successfully imported" when there is only 1.