Jump to content
LaunchBox Community Forums

flores9

Members
  • Posts

    123
  • Joined

  • Last visited

Everything posted by flores9

  1. @Jason Carr could you help with this please?.
  2. Ok, I think that the resolution of the names could be looking into these files from the MAME installation. (I attached). But I´m not sure, and how it works.
  3. @DOS76 thanks for the response. But do know why LB solve only part of the romset?. I think LB look for this information somewhere, but it´s incomplete... It´s probably it looks for in the MAME.exe or a directory from the installation? I attached the result, and the names that LB resolve are the correct, because the names of the romfiles are in MAME format.
  4. Hi folks!, I tried to import two Amstrad CPC collection based on the last version of MAME Software List (0,182), cpc_cass and cpc_flop. Both are with 6.000 and 31.000 roms. I imported with the option of forcing MAME metadata, but the result of the importing proccess bring me "only" 202 games. I tried checking no dupes, dupes, priorizing regions, and the result is the same. Does someone know how LB solve the names when force MAME metadata?, is normal this result with Amstrad CPC?. Thanks!
  5. Thanks @Jason Carr. I´ll put a ticket to implement a log screen, with information of the result of an import or the result of a metadata download. It would be useful to see how many images of any type founds LB in both repositories for the roms, and which of them are downloaded correctly at the end. On the other hand, I don´t know why both options of download metadata works differently (the edit option of a game always find the media, and always download media, forcing to duplicate image files).
  6. I tried a new fully import, and the result its the same if I include this game.
  7. ok... I tested to update media in packets, and I localized the error. If I try to download metadata and media for the "V2000" game of PSX (alone or with other roms selected", the wizard doesn´t download any video. But if I use the "richt click" / edit option, it download the video from emumovies. I also tried to reimport this game, and the result is the same. Any explanation?.
  8. Hi @Jason Carr now works correctly. But I´m experiencing another possible issue. I´m reupdating all the metadata and media of various platforms. And I noticed in the Playstation platform that not download all the media available, for example the videos. No videos are downloaded, and it´s possible that other things. My proccess is, select all roms, tools / download metadata and images / search metadata on local DB / I checked all options in both next screens (LBDB and Emumovies) / Check to replace all existing metadata. But if I select only some games (1, 10, 100, ...) and repeat the proccess, it works correctly. There is a way to view a log file to know what it happens?. I´m not experience this with other platforms.
  9. Hi @Jason Carr another similar error with the new beta. In this case importing a new platform "Nintendo Famicom Disk System". Both check and uncheck the grouping option, show this error, and after continue the import but importing less roms.
  10. I though that the scan option had a different way of manage roms. If it´s the same it makes sense. Thanks.
  11. Thanks @Jason Carr. It´s possible to implement the "force duplicate check" in the "scan for new roms" window?.
  12. @neil9000 but I am not talking about the new feature of grouping games. I only need to know if this check test a duplicate game looking for in the "new roms to be imported" or in the existing roms in the platforms?, or both?... or nowhere... Thanks!
  13. Sorry, my question would be " With the option checked, does this process force duplicates from the actual import process? or from the existing roms for that platform that exist in LB? " For example, I´ve in my collection a rom called "batman (EUR).zip". What happens (with the "force duplicates" option checked) in a new import of a game called "batman (JAP).zip" (considering that the game / name in the BD is the same).
  14. @Jason Carr after the crash window, the process continues normally. I´ve dubts with the "force duplicates" check. Does this process avoid duplicates from the actual import process? or from the existing roms for that platform that exist in LB? I´m just trying to add roms from different regions (I deleted a few days before with the audit option), but the "scan for added roms" option doesn´t show the "force duplicates" check), so the only way to add the roms is with the import process, but I´n not sure how it works.
  15. Hi @Jason Carr I´m trying to import an already existing romset of my collection. (just for trying the new grouping option). In this case I´m importing the Neo geo Pocket Color (that I have complete in LB with the same romset and the same platform name. Then I uncheck all the options of the last window (import duplicates, group games, etc...), I click "next" and appears all the games to import (it´s strange, because I don´t check the "include duplicate option", would it show only new roms, isn´t it???). And finally click the last "next" button and crash.
  16. Hi @Jason Carr in Tools / download metadata and images option, in the third window (when you select the media to download from the game database), doesn´t appear the "Select None" button. I´m using LB in Spanish languaje, and this only happens when you try to download images from an existing roms. The same option in the import new roms works correctly.
  17. Thanks @SentaiBrad, It´s make sense.
  18. Hi!, I just update to the last beta and I notice this beavior. When I imported my Amstrad CPC collection, for example, the scrapper recognize this three differents roms as the same game (Adidas Championship Football) in the Games DB: - Foot.7z - Adidas Championship Football.7z - Pi (19xx).7z I think it´s the first time I see this error. If I launch the same query in the Games DB it works in a different way, only match filename with the Adidas Championship Football game.
  19. Hi @Jason Carr, there are many differences beetween both "languages", in many words, but specially in the expressions, that many don´t exists in the "official" Spanish language. For example "Checalo aqui" it´s not understood by a Spanish person. If could be possible the implementation, it would be really good for LB, I think that a Latino / Spanish is extrange for Spanish people, because it uses many words thar look like mistakes or spanglish. I´ve been waiting to do this if finally you can implement these as a new language.
  20. Hi @Jason Carr, I was talking with @CliveBarker about the spanish translation. Now the ES option is really a Spanish / Latino derivation, that it´s correctly translate by Clive. I want to contribute with the translation of Spanish / Spain. Probably you need to make some changes in LB to add this option, but If you explain me how to begin the translations could be perfect. I prefer to begin the changes with the actual files of clive.
  21. Hi @Jason Carr, I tried to clean my data folder and all it´s working correctly, with the beta 2. I´ll test the last beta tonight. Only I have a little problem in LB when I try to select an image for the background, it not change, and always I have the default LB background, but in the options menu is selected another.
  22. @viking incredible!!... I really like it!
  23. @Jason Carr I think I Know the problem. When I restore to a previous version, I deleted all the games and a platform called "Commodore Amiga ADF", it dissapear from LB and I restart. When I launch LB, it appears again, with all the games. But when I try to change the name, it appears duplicate in the Manage Platform Window. And then LB crash in the next boot. Where are the information about platforms?, only in the Launchbox.XML file?, Can I delete manually?
  24. @Jason Carr is really strange. I tried this: - Restore a full copy of the LB entire directory, that is on the 6.9 beta 20 version. And it doesn´t have last changes on platforms and roms that I did yesterday - Update LB to 6.9 official, and it works - Update LB to 6.10 beta 2, and it crashs So I think the problem not is in the XML file. It´s probably that the error is in another file or folder?, metadata folder? . Or can be a problem of the new beta version (1 and 2)?
×
×
  • Create New...