Antropus

@flores9, can you post a screengrab showing the contents of your "SupportFiles" folder under the Lightspeed installation folder as well? I also noticed something unusual in your setup, but I don't know if it might be related: All your paths are set to "E:\EMULADORES\EMULADORES\" except your Roms and Softlists, which are pointing to "E:\EMULADORES\". They should be all at the same level, for example: ROMS, Flyers, Snap folders should be all inside of the mame root folder.

Thanks Cid! Do you mean the date is not correct or not present at all? You mean the date in Launchbox, not at the Lightspeed listview, right? Or both?

@JCSRT05, please try this version and let me know if the file corruption still occurs. I isolated the routine to affect only the platforms supported by LS and leave anything else alone: Version: 0183_Beta2 Date: 2/27/2017 10:55am https://drive.google.com/file/d/0B23vaxsfSk1yQUQ1aXZpSThpbUk/view?usp=sharing

@JCSRT05, I was able to reproduce it and I found the problem. It's duplicating the .xml games info on platforms not supported instead of simply bypassing them. I will have a new version with a fix today. Thanks for reporting! The version posted should work on any brand new library, but if you have a library already populated with other systems, this will definitely cause headache. I will remove the download link for now. Thanks again!

@JCSRT05, not sure what happened in there. Is it related to something Lightspeed did? I ask this because Lightspeed doesn't support Nintendo 64, so there's no way it would corrupt the Nintendo 64.xml file O_o @Johnnydement, very true. I added support to .zip files inside artwork folders, so these should be recognized now. But for obvious reasons (HUGE hit in performance), those .zip files are not being verified and Lightspeed only trusts that you will have the right image inside of it. I wrote code to verify if the file is indeed in the .zip (or .7z), but as I said before, this is more of an audit thing, because depending on the size of your library, this can take hours (clrmamepro is a good reference when it comes to unzipping/zipping files. It's super fast, yet it takes hours...). About the merged set, it's not ideal, but it *should* work. Exactly like what happens with the GUI present in the official mame, that does not recognize the children roms as present, because it doesn't deep scan the .zip files, Lightspeed doesn't either. So, although the games will be fully playable, if you try to force your list to contain only the present ROMS, a lot of them will be missing, so make sure that option is off! @flores9, I did a fresh download/installation in a different folder, pointed to the correct paths (Softlists out of the ROMS folder, just like you have it), restarted Lightspeed and had no problems. Could you please post some screenshots of your paths tab, filters tabs, option tab and platform tab? Or even better, a copy of your .ini file?

Finally a version you guys can try: Version: 0183_Beta1 Date: 2/27/2017 12:40am EDIT: Found a bug that's causing Lightspeed to corrupt .xml files for systems not supported by it. Working on a solution. It shouldn't take long. Thanks! Please test and report anything not working. I will write some more tomorrow, explaining some of the new features a little more in-depth. -Kris

About the zipped artwork, would it be useful if I made Lightspeed consider .zip files inside of artwork directories as artwork themselves? I could unzip them to verify if artwork was present, but that would be more of an audit thing, because if I did this on startup, depending on the number of files you have in your collection, that could take a long, long time. Let me know if simply supporting .zip without unzipping them would work for you guys. -Kris

Here are some highlights of the features I am currently working on: Main focus is being the Copy/Move Files Utility at this point and I am about 75% done with it. As it stands you will be able to: - Copy or Move Roms/CHDs and/or Artwork that matches your filtered list, creating a "clean set" with no leftover junk - Search and rename Artwork files matching either the ROM name or the Description of the game (parenthesis and brackets being removed automatically). A "Fuzzy" search feature is being planned, to help finding files named not so carefully. - Remove from your source folders anything that doesn't match MAME.xml - Remove from your source folders anything that doesn't match your current output list - Generate (by copying) artwork for clones from their parents. As for destination folders you will need to inform the ROMS, Software Lists (which can be the same as the ROMS, if that's the way your library is set) and Artwork. All processed files will be created under separate folders matching MAME's naming convention: Snap, Flyers, Marquee etc. If you are removing files, you will need to inform a backup folder as the destination. Again, the files will be organized under their respective folders during the process. There are two options so far: - "Use LaunchBox Folders": This will switch between exporting to the folders of your choice or point to the Launchbox folders. If Using Launchbox folders, all artwork and files will be exported under their respective Platforms and organized as if you had done it using Launchbox. - "Copy/Move Bios and Parents": will move/copy those files along with their relatives during the process. Another requested feature was the clones view, similar to Don's, where you will be able to select and add certain clones to either your filtered list (for further tweaking) or straight to your output list. To see all related parents and clones you just need to right click any game in the list: To get to this screen: An import filter that was missing was the parents filter. You had the clones filter available, so you could remove them, but you could not remove the parents if you wanted to generate a clones only list. Now you can: A feature request I got in another forum was an Audit tool that could scan and report any missing artwork with the ability to export a list/report showing those files, so I ended up creating this: Lastly, my previous way to check for pre-existing entries in the LB library wasn't very good, so I re-wrote that whole chunk of code and it now really reads all platforms currently imported into LB, loads them into memory and compares with what is being exported. If a rom of same name is present in a platform of same name, this game will be bypassed and not imported again, no matter if it was imported previously with Launchbox or Lightspeed. There's a catch though: an overwrite that you can use to export a clean list instead of merging it with existent. If overwrite is used, you will have an extra option showing up, were you can tell Lightspeed to set all paths to point to Launchbox's folders instead of MAME's, which can be very useful if you are going for a portable setup and you are using the copy/move utility to create a matching clean set in the same folders: Things are coming along. Still no date for release, but those things take a good amount of thinking to get right. Cheers, -Kris

@Plaidlgoo, yes indeed. You can filter the roms, export your list to LB and get the artwork from there.

You just need to point to the root of your Launchbox folder on the bottom left corner of the export tab and Lighstpeed should be able to find and modify all necessary files for you.

Ran into something tonight and had to delay the release yet again. Since I am at it, I might as well add the move/rename/cleanup artwork feature that was requested multiple times before the release. Sorry guys. I am on it! -Kris

Hi guys, I mentioned a few messages back that the app has issues at this point, so if you can wait a bit I will have a new version coming up soon, very possibly tonight. Since RC3 I've found a number of things not hooked up correctly, causing some roms to not be affected by the filters, mismatch between what Lightspeed said it exported and what was actually exported, lack of a better way to check for games already in the library and bypass them, notes with a blank lines at the beginning/end, among many other issues mentioned by users. I managed to fix the vast majority of those and worked on a much improved memory management system, so it doesn't hog RAM anymore. In the past, LS would need 700mb at startup and could go to over 1.2gb when dealing with large xml files. Now it constantly flushes memory after each operation and instead of 700mb, once started it occupies only 7mb or less in memory and although it will go to larger numbers, it always resets itself before it starts any major operation, making sure that RAM is not an issue anymore. A user in other forum complained that it was running out of memory when generating the xml, so that should be handled now. It's hard for me at this point to even try to come up with workarounds to fix your current problems, because my working version is quite far in terms of bug fixes from the version you are current using and I believe a big chunk of your problems will be solved with the new version, so stay tuned and hold on for now Thanks! -Kris

So sorry for all the issues guys! As I said, this was almost a complete redo after all. Please wait a few days and I will have a new version up. I've read all comments and test results (thank you SO MUCH for the feedback and for testing it!!!) and I've got all those issues sorted already. I decided to change a core area of the code because I wanted people to be able preserve their current library entries to make Lightspeed add games to existent libraries created by Launchbox, making the merging of data more previse than currently, which works better as a clean import. So I am writing a little parser module to collect the info from all current platforms and emulators and if a game of the same ID is found, that game/plat/emulator will not be created again, unless an override is used (useful if you want to change paths, for example). This way you will be able to freely add/remove stuff from either Launchbox or Lightspeed and both should be able to pickup the changes, at least that's the hope. So please hang in there, because I am working on it! -Kris

I delayed the release because I got carried away by a little project, which is the reporting of missing Artwork/CHD/ROMS. I added a new tool which is now reporting anything missing and exporting as lists for now, but the intention is to add many new tools to it, like removal of orphan artwork, renaming of artwork from description (with tags or not) to rom name and vice versa, creation of clone artwork from parents and even a mini-scraper to get missing artwork from emumovies from that very same little interface. I am planning to make those missing lists exportable to launchbox as well, so you will be able to, for example, export all games missing snaps to launchbox and use it to scrape only what's missing, if you prefer LaunchBox's more robust scraper. I am also planning to add a function to move/copy all related artwork when you copy/move ROMS, but this will come a little later. Some tools might seem redundant with what Launchbox already does, but this program is targeted to users of other front-ends as well. -Kris

Fixed!@Pacman56 not at all! Thank you so much for testing and catching this! There was an override I added by mistake, so every time you had the "Launchbox DB" box checked it would remove the tags. I fixed it just now. Please feel free to report anything else you find. Just bear in mind that I found a couple of bigger problems that I fixed for the next version, which I plan to release soon, but not before I fix some other minor things. Next version will pack a lot of bug fixes and I am excited for you guys to try it soon. Thank you again for taking the time! -Kris

@CriticalCid, thank you SO MUCH for really testing it! Very much appreciated. This is the only way we will get the bugs fixed. 1. Fixed! 2. Fixed! 3. Extra-Info is not present in a great deal of games. That info is actually extracted from the game description, which many games don't have. Otherwise, VerAdd and Sub-Genre info seem to be fixed now! I will be releasing a new version tomorrow. I added a switch to reverse the folder matching filters. This way you can now filter by games missing snaps, for example, or games missing any type of artwork in fact. I will add a few tools in the future for manipulating the artwork, moving it around to match the lists, generating artwork for clones from their parents etc. -Kris

I found a bug that was preventing the filters to run correctly. Fixing it now, so hold on before you update anything.

If it happened during the installation, then this is completely unrelated to Lightspeed itself. I wonder if it's some glitch caused by something in your computer. Maybe an anti-virus or something like that? Yeah. Just uninstall it either through control panel > Programs and Features or by double-clicking the uninstall icon in the installation folder. It should remove everything but Lightspeed.ini and Ratings.ini, which are created after the installation, so those files will be preserved. -Kris

@Drybonz I am curious about this issue. I cannot reproduce it on my computer, but reading it again, seems like the issue that you had happened in two very distinct places, is that correct? I mean, one was during the installation of the program itself and the other time was after the program was already installed and loaded and you were trying to configure the paths. Is that correct?

Latest Version: 0.181a_RC3 Updated on: 1/15/2017 @ 2:20PM Download: https://drive.google.com/file/d/0B23vaxsfSk1yQUQ1aXZpSThpbUk/view?usp=sharing - The GUI elements are now preserved on displays using custom DPI (scales different then 100%). - To avoid further problems with the GUI not being accessible for whatever weird reason, for now only the window size is going to be saved, but not its last position. For the same reason, from now on the GUI will be automatically centered in the primary screen on startup. - Fixed a bug that was causing the favorite icon (heart) to only work if clicked twice. - Improved memory usage by flushing many variables when not in use. Lightspeed is still a memory hog though, but there's no way out of it, because data for over 68.000 games, from multiple files is being kept in memory for fast interaction. I prefer that to have to reload arrays and variables all the time, which would slow things down quite a lot. - "Rom Of" column added. I don't know how I missed it before. - Overall code cleanup, removing a lot of unused, legacy code. Please test and report any problems you mind find. Thanks, -Kris

You are welcome

Good! I will do something to fix that issue. Are you using a multi-monitor setup? Can you post a screenshot of the way you want your paths to be configured? Does Launchbox recognize those paths with no issues? I want to make sure I can narrow down to the core of the problem if it's coming from Lightspeed specifically or something about your setup in general. Thanks!

Thank you so much. I really appreciate your words. It doesn't suck to be able to make a living out of the things one loves doing, that's for sure! I am lucky, but it came through long hours of hard work

The path issue is concerning, no doubt. I know that Jason wants to keep all paths relative, as much as possible and I want to make them absolute, as much as possible, because I don't trust that the mailman will know the address by following clues. I rather give the mailman the full address, to make sure he knows where he is going About the video you just posted, I think I get what's going on. I can tell Lightspeed is up and running by looking at the bar. What's happening is that it's out of your desktop area and is VERY probable that this is related to the way Lightspeed saves the GUI window size and position. Size and position are captured on exit and saved in the ini file (last 4 lines). If this happen again, instead of deleting the whole .ini file, please simply remove the values from those last 4 lines. Keep the keys. Only remove the values, save the ini and reopen Lightspeed and let me know if that works. If it does, the problem might be related to multi-monitor setup, for example and if that's the case, I think I can work around it to fix the problem. Edit the last 4 lines to look like this: Width= Height= PosX= PosY= Let me know if it works. Thanks!

Alright, lets hope nobody complains about the use of "their work"... Here are the platform wheels I am using for all those systems supported by Lightspeed: https://drive.google.com/file/d/0B23vaxsfSk1ydkwxakRxVmNXTUU/view?usp=sharing Cheers!