SpaceMidget75

List seems perfect dude and thanks for working on this again! I know what it's like working on evening projects and finding the motivation to continue work on them once the spark has been lost, so well done. (As we discussed at length, my 'lil feature request would be if you could have an option to specify a folder which will then copy the filtered images to that folder and point LB's XML to them instead of the source MAME image folders.)

Yep, a great UX is one of LB's strongest points and it wouldn't be wise to complicate the back-end configuration further with multiple folders IMHO. Maybe the following: Launchbox should be aware if images are from it's own default folders or an external source. Launchbox should warn you if you attempt to modify/clean images only if in an external source. When adding images for a system it should ask if you want to copy the image to LB or link to it. (third party apps could also ask a similar question and either copy & set folder path or). That way we're protected from accidental deletes, people can chose to maintain their images within LB or not (on a system by system basis) and I'm guessing it's not quite as a big change for LB and could be added to the roadmap easier than multiple/working folders. Just brainstorming guys

Yes, this is completely understandable. LB needs its own image folders that it controls and maintains. The only real conclusion to this is that a) IF people have pointed to external collections, sufficient warning is put in place and b) for the most part images from external sources should be COPIED to the default image location for the given system in LB. As I said, this takes up a bit more space but allows LB to manage what it considers it's own setup. @Jason Carr When you add images via the "Add Image" dialog (not download) does it keep the browse path or copy the image to LB?

@Antropus Just one quick point, in case you wasn't aware. Cleaning up the images in LB actually deletes the original images from the MAME extras folders. Bleeding obvious that it would when you think about it, but also a problem given that people tend to get their MAME artwork from outside of LB which means torrenting them down again. Wonder if it might be better to copy the artwork required for the custom list to a folder specifically for use in LB? Takes up more space, but at least it keeps peoples MAME data safe. Just a thought.

Long time C# dev here. Both solutions are great so you should all be pleased with what you've achieved thus far. Thank you. @Antropus for what it's worth LB running with a Mame Set imported via your tool seems perfectly fine speed wise, running an i5 6600, SSD & 16GB. Maybe drive speed is the issue here? I'm also guessing that the XML changes should be minor, but after 15 years in the business I'm not going to assume anything without seeing the code, and as this is a personal project I completely understand that you need to determine when (and if) you're willing to make those changes. Someone else could always pick-up the project for you if real life does get in the way. It could even be integrated into the Launch Box Mame importer @Jason Carr Keep up the good work! I love the frequency of new features and personally haven't seen it cause a negative impact on performance or stability yet.

Hey man, no need for anything so drastic as pulling the link! I know I had a few issues further up, but they both have workarounds (as posted) and other than that the program appears to be working great (for me at least).

Fixed it. Just so others are aware, there's two small "features" ;) that might catch you off guard... 1) Running through Lightspeed again doesn't change paths. To fix this you either have to delete the Arcade platform from LaunchBox and re-import or Edit the properties of the Arcade platform and manually change the paths. 2) Be careful running the LaunchBox "Clean up Images" feature. This will delete all your MAME extras. I know that's sort of stating the obvious, but unlike other box art in LB, MAME Extras aren't dedicated just to LB, so people maybe surprised when they find their MAME Snaps folder empty.

Hi Program worked great. After importing I decided I would prefer Titles instead of Flyers as the front covers so I re-imported, selecting Titles in the Flyer path instead. This made no difference and the Flyers remained in Launchbox. So I deleted out the arcade games from Launchbox and did Tools | Clean Up Images (said it removed loads of images). I then tried another import (selecting titles the Titles folder) and the roms imported again, but now I have no images for front covers at all. Very strange. Any ideas? EDIT: I've just noticed after going back into Lightspeed that it's now not showing snaps in the output tab whereas it was before.

DOS76 said Do you see the line in the associated platform that says Sega Genesis in LaunchBox are you using Sega MegaDrive as the platform or Genesis? If your platform is called megadrive that is why it isn't working. You can either change that to be the same as your platform name or you can create a completely new line if you plan on using Genesis as a platform also. Awesome thanks! I must have changed it to Mega Drive (UK/Jap fanboy here) a while back and forgot to test it immediately after. I've renamed the platform to Sega Mega Drive and it's all working fine. Thanks again.

This is an odd one. I had a few Sega Master System games and a few Sega Megadrive games setup in LB using Retroarch. I tried to load the Megadrive games and now nothing happens. No message, nothing but a very brief hour glass. Here's the thing... the Master System games are still working and everything still loads fine via RA itself??! Cores are up to date. Everything seems to be setup the same for both systems in LB. Any ideas? I've attached some shots: