Jump to content
LaunchBox Community Forums

Antropus

Members
  • Posts

    533
  • Joined

  • Last visited

  • Days Won

    4

Posts posted by Antropus

  1. In what format you have your images? Can you post a screenshot of your wheels folder? I just look at my code and it should find anything with the extensions: png, jpg, bmp, zip or 7z. Another thing you can look at is your  platforms.xml file. It's located under your "launchbox\data". Take a look and tell me if the paths are correct in there or pointing somewhere else.

  2. If you are downloading anything from a certain "dome", they should be all separated. It's up to you if you wanna extract the software lists into separated folders within MAME's roms folder or in a different root folder. Bear in mind that if you choose a separated folder, you will need to edit mame.ini (in your MAME folder) and include the new path in the rom path section of the ini, or else mame will not find the roms.

  3. I remember using clrmamepro to cleanup a similar problem I had in the past, but dealing with software lists is not the most straight forward thing with clrmamepro,  I can tell you that!
    Better to find a good torrent source and take a few days downloading the software to get things correctly. It's really not a requirement from Lightspeed, but rather the way MAME is structured, so Lightspeed respects that very same structure.

  4. But if you are talking about the arcade rom not showing up in the search results, it's because although the .zip names are exactly the same for the arcade and consoles, for the arcade version it's spelled "Battle Zone" (with a space), instead of "battlezone" all together.

  5. Wait a second... you are keeping both softlists and regular mame roms in the very same folder, at the very same level?
    If that's the case, this is definitely not the way MAME is supposed to work. As you can see in your listview search results, many roms will have the exact same name and for that reason they should be kept inside of sub-folders. Atari 2600 roms should be kept inside of a sub-folder called "a2600" and this folder should either live inside of the roms folder (based on your setup) or in a totally separated folder, as long as the folder "a2600" exists and its roms live inside of it. Can you try to create a folder called "a2600", copy that rom into there, reopen Lightspeed and see if it finds the rom? It should, as long as you have the right paths and the subfolder named after their respective software lists. The second to last column in your listview should tell you what is the expected name of your subfolder when it comes to software lists (except for "arcade" and "non-arcade", which are both related to Mame, not Mess).

  6. A new version is up with only two main fixes for now:
    - Release Date parsing now happens in 3 stages: 1) parses the date from History.dat, 2) parses the date from Launchbox database if present, 3) Searches one last time in the final notes and captures anything not captured previously due to "export release" versions.
    - Ctrl+C was mapped to opening the clone view and it was interfering with simple ctrl+c operations within the gui, like copy/pasting paths for example. It's now mapped to Ctrl+Alt+C. You can also access this menu by right clicking anywhere in the listview.

    Version: 0183_Beta4
    Date: 3/1/2017 1:22am
    https://drive.google.com/file/d/0B23vaxsfSk1ySUk0WTRwbDdjOGM/view?usp=sharing
     

    @CriticalCid, please test this one and report if you still see weirdness with the dates. Thanks!

    • Like 1
  7. 11 hours ago, audunv said:

    I have tried the beta 3 now and I can confirm that the content of emulator.xml is not deleted.

    I have some questions.

    1. How is the EmulatorID generated? LS5.PNG.2c6e6fd21731430ee4255c179bcdaeb2.PNG

    2. If I allready have an emulator named MESS, the importer creates a new one also called MESS. I guess that's because it uses a different EmulatorID. No problem, I can just delete the emulator I don't want.

    3. I you choose to use a custom emulator(2,3,4), the importer still creates an emulator named MESS or MAME, with the path to the custom emulator. This can be changed in Launchbox, so no big problem.

    LS6.PNG.7534ec5b85b586d6cf693a979731569c.PNGI guess all of this is the expected behavior of Lightspeed.

    What does the checkbox "Use Launchbox paths" do in "overwrite library"?

    LS7.PNG.a7aef260ea96c5205a582c3d87b6cadd.PNG

     

     

     

    1-2) The emulator IDs are fixed for both mame and mess. I only randomize game IDs to avoid conflicts. If you already have a platform of the same name and it already has a different ID assigned, LS will definitely create a new one. I can work on that and try to merge with whatever is present in the library.

    3) that falls into your previous request regarding the custom command lines for mess games. Those secondary emus should be their own thing, I will look at it.

    4) The "Use LaunchBox Paths" resets all paths to use LaunchBox's paths. It's useful when used in combination with the "File Match" button, that can also move/copy roms/chds/artwork directly to your Launchbox's folders, so it becomes portable.

     

  8. Just now, Malhavoc said:

    @Antropus used the last version linked above. I started from an already imported library. Some games were duplicated. Looking closer, I've noticed that the problem was some platforms were actually duplicated, due to slightly different names:

    toaplan-raizing
    toaplan/raizing


    capcom cps-3
    capcom cps3


    capcom cps-1
    capcom cps1


    capcom cps-2
    capcom cps2

    Oh, sorry about that! I tweaked the platform names slightly, so if you had a previous import you will definitely get some duplication. Sorry!

  9. Here's a new version that should (hopefully) fix the problem of platforms/emulators being deleted accidentally. I also added an override that adds Ratings and Release date from Launchbox Database, if present.

    Version: 0183_Beta3
    Date: 2/28/2017 1:25am

    https://drive.google.com/file/d/0B23vaxsfSk1ybDcwTng3d1BuZ1k/view?usp=sharing

    The other requests are still pending.
    Please backup your files, test it and report if you can. Thanks!

    -Kris

     

    • Like 1
  10. 4 hours ago, audunv said:

     


    Ok, thanks for clearing that up.

    But the command line parameter for software lists is only needed if you are using MAME as the emulator.

    If I want to use a different emulator for Gameboy, for example Retroarch, the command line parameter needs to be empty, or else it won't work.
    There is also no way to bulk edit this field in Launchbox, so you would have to remove it manually for every single game.

    Because Lightspeed supports to define an emulator other than MAME, I also think it should be possible to change what goes in the command line field for software lists games.

    Lightspeed is definitely a great tool.
    Thank you, Kris. :-)

    Yeah, my intention was always to support Mame only, so I never worried about people trying to use it to import for other emulators, but it's a great point and not hard to change. I can keep the way it is when the first radio is checked (main emulator Mame) and create a complete override when any other radio (emu2, 3 and 4) is checked. That's actually a good suggestion, thanks!

  11. 55 minutes ago, audunv said:

    I found some more issues.

    When I import software list roms, Lightspeed automatically adds command line like platform name, for the platform I'm trying to import. I want that field to be empty. 

    If you add a command line when selection output, that value is added to gameboy. 
    LS1.PNG.da18909ff90ecb6af7e9b8e3139badc5.PNGLS2.PNG.35877382f67bdfed129d210661e83f27.PNGLS3.PNG.108f79386bb9d5a50ac7b499bd6cdad1.PNGThis does not happen for the arcade roms.

     

    If I change for example rating or commandline and export again, no changes are made to the platform.xml when choosing "merge to library".

    If I choose overwrite library the platform xmls are updated, but platforms not in the export gets deleted.

     

    About the command line, this is the way it was supposed to work. Software lists need the slist name informed in the command line or else the game will not run, unlike arcade games, where no additional command (other than the name of the rom itself) is necessary. Because of that, when you add any info to the command line, that info is added to the mandatory command line already in there so the game will run. I wrote it to be game based instead of platform based, because some games will need a different command line for pal or ntsc games and a broad command line based on the platform will simply not cut it.

    About merging to library, if the game/platform is already in the library, nothing will be added and no info will be updated. If you are planning to change things later on, you will definitely need to use the overwrite option instead, which should affect all platform(s) being exported by Lightspeed. I know, it's not ideal yet, but that is what it does at this point. To change info in batch mode you will need to use Launchbox, but I am not sure if it supports changing command line in batch mode at this point.

    About the platforms being deleted, this is related to the issue I will be looking at tonight, together with the emulators.xml issue.

    All in all, Lightspeed was always intended to be the first pass when you are starting to populate a brand new library. All the requests to make it compatible with existent library/platforms is a thing that I am slowly migrating to, but Launchbox has a ton of files that I need to read/parse/collect info from and their layout is not always the easiest, like in the case of the emulators.xml file where you can find the very same "<emulator>" tag being used in two different places.

    So it takes time to make it completely compatible with Launchbox. Other than that, if you are looking for the quickest way to migrate a huge library of mame games into a brand new Launchbox installation, with all the info and artwork parsed for you automatically, LS is a great tool.

    -Kris

  12. 7 minutes ago, Johnnydement said:

    But should not be any problem importing first with lights peed and then any other no? Or files become botched? 

    If you run LS first to get everything there and then import more things with Launchbox next, you should have no problems. But if later on you use LS again to add another platform, for example, it will most likely remove the emulators assigned by Launchbox and will try to assign Mame and Mess again. This should be a fairly simple fix, but the type that needs my attention, so I will look at it tonight since I am at work now :)

    • Like 1
  13. I know what's going on with emulators.xml. It's a little over-complicated the way I wrote the parser for it. I will simplify things tonight and get this fixed. I don't have anything imported by Launchbox in my library, so all my tests were done taking in account the stuff imported by Lightspeed only, which explain the problems related to other platforms not supported by Lightspeed, so your tests are definitely very appreciated and they will help to get things ironed out for everyone. Thanks!

    • Like 1
  14. @audunv, do you mean it's deleting the xml files and not recreating them correctly? It should read them into memory, parse everything and re-create the files at the end of the process. Are they simply gone at the end of the process?
    About the emulators.xml, that's definitely concerning.

    @CriticalCid, did you run into the same problem reported above? Did your other platform xml files get deleted as well? Making sure that this is not a permission related issue.

     

×
×
  • Create New...