mcfilmmakers

Hold up... this seems to only be happening in this one platform... I wonder why. Might have something to do with the update issue I mentioned earlier? I was editing in this platform at the time. I'm thinking having to force quit might have corrupted something... Importing a backup doesn't resolve the problem though.

HUGE BUG After updating to 11.9 Launchbox thinks that all my games have 0 images. However, the images in the launchbox folders are still there. You don't immediately notice but go into the edit window in the images section and it shows 0/0 or press F5 and the images disappear. When adding new images, Launchbox isn't recognizing those either.

Found a glitch on update window... I opened Launchbox, selected a game and opened the edit window. Then went into additional apps and clicked to edit an app. That's when the popup to ask if I wanted to install the update appeared. Rather than click Yes or No or close the popup, I wanted to finish what I was doing in the additional app-edit application window and then install the update, so I simply clicked on the additional app-edit application window. I was able to edit the application command-line parameters as I intended to do but then none of the buttons was responsive. Can't select OK or Cancel and can't close the window with the X on the top right. Because the update popup is considered as belonging to the main launchbox window rather than it's own, I can't return to the popup, which is what I know the edit application window is not responding for. Only way out is to ctrl+alt+del and force quit Launchbox.

Would this help? https://github.com/libretro/mame2003-libretro/pull/348 I don't really use retroarch so I can't say for sure but I hope it leads to something useful.

This guide is wonderful but I did have aa couple issues. 1) I had to change the unmount script by launcherbox to --remove_all. Other might want to try that if they have issues with that. 2) the -F0 "full path to user disk" doesn't work. I always have to go into the menus in Unz to insert the user disk manually. Does anyone know what the correct commandline for this is?

Yeah, just select the specific games and tools->download media

While the topic is fresh, a deselect all button would be SUPER appreciated on this screen.

I am crying with joy. Thank you!

I'm trying to get an IBM 5170 game to launch through launchbox but am having issues. The game requires a harddisk, flop1 and flop2. I can do this with no issue in IBM 5150 with the following commandline: ibm5150 -skip_gameinfo -harddisk1 "F:\Launchbox\Emulators\MAME\ibm5150hd.chd" -flop1 "F:\Launchbox\Emulators\MAME\software\ibm5150\msdos33.zip" -flop2 However, the same commandline in 5170 doesn't work: ibm5170 -skip_gameinfo -harddisk1 "F:\Launchbox\Emulators\MAME\ibm5150hd.chd" -flop1 "F:\Launchbox\Emulators\MAME\software\ibm5170\msdos33s.zip" -flop2 The above line will not open MAME at all. I have to modify it to this: ibm5170 -skip_gameinfo -harddisk1 "F:\Launchbox\Emulators\MAME\ibm5150hd.chd" -flop1 "F:\Launchbox\Emulators\MAME\software\ibm5170\msdos33s.zip" -flop2 "F:\Launchbox\Emulators\MAME\software\ibm5150\4dboxing.zip" At this point, Launchbox opens MAME with the correct harddisk but the game is set in both floppy drives. I want the msdos disk in drive 1 and the game in drive 2. What make it all the more perplexing is that it loads perfectly fine in Negatron (I use it to create the harddisk). Negatron shows me this commandline: ibm5170 -bios rev1 -ramsize 1703936 -isa1 ega -isa2 fdc -isa2:fdc:fdc:0 35hd -isa2:fdc:fdc:1 35hd -isa3 comat -isa3:comat:serport0 logitech_mouse -isa3:comat:serport1 "" -isa4 ide -isa4:ide:ide:0 hdd -isa4:ide:ide:1 "" -kbd pcat -floppydisk1 msdos33s -floppydisk2 4dboxing -harddisk "F:\Launchbox\Emulators\MAME\ibm5150hd.chd" Even with that exact commandline in launchbox, it still puts the game in both floppy drives. How can I resolve this?

I can't find any concreate information about this. The only info I find is that MAME emulates this but I can't find any guide as to HOW to get MAMe to emulate it. I'm only interested in running the floppy disk set with mame. If I set launchbox to "fmtownsux -flop1" I only get a loading screen which according to google means that the system is not setup. If I set it to "fmtmarty -flop1" then I get the FM Towns Marty boot screen but none of the disks loads. Can anyone share their MAME settings for FM Towns?

just create a playlist.

I've seen nothing but massive improvements.

I can FINALLY reproduce an earlier issue I had with an error popping up in the edit window. Video below. Highlight text and drag = error. Happens mostly when I click a nanosecond before I stop moving my mouse over the title field with the intention to type in the field. 2021-01-05 17-27-03.mp4

Hello to all! 2020 has been an absolutely downer of a year and I aim to make 2021as great as it can be. I want to do my part by contributing tot he community as best I can and so far, that has meant making theme videos. I've noticed that some contributors have their own patreons and it's something I've always hesitated to do myself so I was wondering if this is something that the community would be willing to support? Starting a patreon is a commitment I don't take lightly and if I were to start one, I would absolutely ensure all patrons would get something worth their patronage. The net benefit being that the commitment through patreon would ensure a constant stream of new material for the community at large while providing extra bonuses for the patrons (a thought: custom theme videos?). Please, let me know your thoughts.

Whenever Jason decides to hold one. He said it would be after the top 20 of the last poll are integrated.

I hear you. You know the process better than anyone! In that case, providing the supported version on import is a great 1st step. Allowing a power user import option is an excellent step from there, all it would take is a mention of filenames required and asking the user to make sure the files are all in the same folder, ask the user to point to the folder and done. I think it sounds like a very simple process (from a UI standpoint). Yes, collecting the files might be inconvenient but the user wanting and using this feature wouldn't be complaining about it anyway and frankly, isn't foreign to anyone who bothered collecting roms in the first place. The files required for the import don't carry the same legal or availability hurdles as the very roms being imported anyway. Heck, Launchbox may even be able to point users directly to progretto (or elsewhere) to get them.

Totally fair. Notifying users of the supported version will go a long way of helping users to avoid potentially updating too far. It would certainly help on support issues by simply pointing out "you aren't importing a supported version of MAME, you were told that when you imported the roms". I do think though that a reasonable compromise for power users would be to allow import of the rom with the Game's title based on the Mame.exe hash (which JoeViking noted can be extracted from the exe). This way, users won't have to pull a bunch of files from everywhere, just the mame.exe I'm fairly certain more than just the game's title can be pulled from that too. With the user's understanding that the import is basically just a straight import of the roms without sorting them or filtering. User's basically would use the power import to let them import 100% of what they selected, with the correct title (and potentially other possible metadata) for MANUAL sorting after import. At first, anyway. Anything else that can't can be relegated to "please wait for the Launchbox DB to update then run the metadata wizard" if necessary but at least users will be able to set up (and play) in the meantime and get collecting on their images/videos. Perhaps an ability to "flag" your platform during the import process to have Launchbox notify you when the Mame version is updated would be an asset here (to avoid questions of "when will it be updated?"). The check can be made when launchbox launches at the same time that it checks if a new version of launchbox is available. Just a thought.

As suggested, I will continue the thought brought up in the 11.17 thread here. The catver.ini on progretto snaps is in fact currently updated to 226 while Launchbox appears to still be at 224. Because Launchbox does not communicate this discrepancy to users, it is a problem, especially when the intent is to update Launchbox's files a couple of days after each Mame update. The point here is simply to highlight that users are being asked to wait un unknown amount of time to update to unknown versions of Mame at irregular intervals independent of Mame updates. In short, the crux of the issue is users can't import ALL the roms they want. if the user is at 225 but Launchbox is at 224, the user will never know that the 225 games did not import (unless they paid attention). It's only worse if you're trying to import 226 as you'll never know about either 225 or 226 missing roms. The only alternative that permits the import of ALL the roms they want, is to import without Mame as the emulator, but then the games' titles match their filenames, which is useless and a HUGE time sync to rectify manually. There has to be a compromise possible. The suggestion is to 1) communictae the currently supported mame set in LBDB and 2) allow users to use their own dat files, at the very least to import ALL the roms they want using the dat file's titles. The rest of the metadata can wait for the launchbox DB update if necessary (though a lot of the info should be in the dat file anyway). This can be done in the mame importer (before it asks if you want to skip certain types of games) with a screen which states what the current LBDB version is with a field asking if the user wishes to proceed using the LBDB version or use their own dat file. The software list plugin does a good job doing this for reference.

That's what we're getting at - users who want to keep mame up to date have to do so by updating through every version between their current set and the latest set. Without a way of knowing what the current launchbox supported set is, users have to guess. Most of that time, the guess would be wrong. In this case, Mame is at version 226 and launchbox would appear to still be at 224. If a user updates to 225, such as I did, they can't know that they went too far without running into this problem I experienced. That's where letting the user use their own dat file comes in handy. I don't want to have to update through 3 iterations of mame updates at once. I also don't want to have to guess when to do it either. It's an issue.

I doubt the file is that large... Perhaps I am not using the right terminology. The user should be allowed to use the file they use with clrmamepro. Mine is 68MB. They likely are, it is the update set. I have that assumption, that LBDB isn't up to date (two versions behind?) which is why the user should be given the option. I don't think launchbox should be bearing that responsibility in the first place to be honest... just make the user use the dat file on import.

When i select a different emulator and a different platform (Temp 2), they finally import... but now the names are wrong (obviously). Is there no way to import EVERYTHING from mame whether they work or not? The user should be allowed to do this. My guess is launchbox DB hasn't updated to the latest mame hence part the issue (for the names anyway + finding at least new working games)... But why rely on launchbox DB updating to the latest set? Launchbox should be looking at the user's mame hash file to compare against the user's actual mame set. It should at least be a choice provided to the user. I'll submit a feature request on this. I mean, I expect that when I import using mame metadata but tell it NOT to skip unplayable games, it should import everything, but it doesn't. If I import without using mame metadata, it will import everything but I won't have any of the names that mame recognizes. Surely there is a way to import everything, working or not, using mame metadata...

Except they should import even when I tell launchbox they are NOT mame roms but they don't.

With all due respect, a user can name their platform whatever they want. It should never prevent a rom from importing. If it does or even might, it's a problem. The same for the scraping as. Also, I already explained that I've tried scraping as arcade without any greater success. If they don't work in MAME, that's fine. I want to import them anyway. I should add that some of those 30 games that are imported are identified as not working in the first place (such as a couple of electromechanical roms) so it still doesn't make sense. I've tried importing as non-mame files and they STILL won't import. I'm not sure why we're focusing so much on mame when they won't even import at all. But to answer your question, I am importing the 225 update roms. I have ALWAYS imported the update roms into a Temp platform to cross reference against my existing MAME platform to merge new clones as there is no native way to "update" mame in Launchbox. This issue has only comue up with 225 and 11.7 so i'm stuck on being able to update my platform. I cannot simply reimport the platform as I would lose HUNDREDS of playlists and apparently, games, because Launchbox isn't letting me import everything in the first place.

Yes, but it doesn't change anything. Even set to arcade it doesn't import them and it shouldn't matter what I import as anyway, that's just to find metadata, not for actual importing. I left it as none to eliminate it as a possible reason is didn't import but the result is always the same.

I really don't like that it's called MAME fullset importer... I don't have a fullset so it throws me off every single time. That said, the fullset importer imports 0 games. So i HAVE to use the regular import: Import as roms Platform: Temp Scape As: none Emulator: MAME Use file sin current location Search for game info in LBGD checked Import all media Force import duplicates Import all clones Skip nothing Finds only 34 out of 130 roms. If I drag the files into launchbox and import as none of the above using the same settings as above, I get the same result. Disabling search for game info gives the same result.