Jump to content
LaunchBox Community Forums

neil9000

Members
  • Posts

    12,647
  • Joined

  • Last visited

  • Days Won

    38

Everything posted by neil9000

  1. As i said, have a look in the zip, they may be right in there, if so just extract them and import the actual roms, not the zips. You are not saving any space keeping them zipped.
  2. You will need to change the name for all the roms in windows, then when they are fixed delete the platform and import it again with the correctly named games.
  3. Also they are zipped, really no need at all for that with files so small. You might find the roms in the zips are actually named correctly if you extract them.
  4. Yes, remove that from the files, Launchbox thinks that is in the game name, so cant match them to actual games as they dont exist.
  5. Yeah thats a naming issue, your roms have # NES after every game, thats your issue.
  6. Are your games badly named? If Launchbox cant identify them then it cant get images.
  7. This will depend on how the games are installed. If they are not registered to the start menu when installed then Launchbox wont be able to find them.
  8. There isnt a option for it, you would have to modify the code of the theme you are using.
  9. Im not sure i understand here, what you set in Bigbox has no relevance to what you use in MAME, what you setup in Bigbox is literally only relevant to Bigbox, unless its a exit emulator or open pause menu setting. Once you start a game its the emulator that has control of your keyboard and not Bigbox, so it makes no difference at all what you have Enter set to in Bigbox at that point, whatever you have it set to in MAME is what is being used.
  10. Oh, my mistake then, looking at the file size it seemed way to big to be in the installer.
  11. Its not included in the install file, and is actually updated daily on our servers as new info is added to our database. Launchbox will check when you import games how old the metadata file you have is, and if its over 24 hours old it will download the new package.
  12. The metadata file is in the Launchbox/Metadata folder and is just called Metadata.xml. Id close Launchbox and delete that file, then in Launchbox go to the hamburger menu, then help and force update database metadata.
  13. Says local database, could be a corrupted metadata file maybe, could delete that and force a redownload of the metadata file?
  14. No, you payed for Launchbox, you didnt pay for it to stagnate on old out of date software.
  15. Well thats the nature of progress. You want new features then spend the ten seconds downloading and installing whats needed.
  16. Same here. Im using the user profile though, not a txt file.
  17. What? You do now how programs and PC's work right? Programs very very often rely on other libraries for them to actually work, Visual Studio and .NET Framework being the big two, most of the apps on your PC will use one version of one or the other. Just look in your add/remove programs list to see how many different versions you already have installed. Every time you install a game from steam it also installs the version it needs to actually run, you never seen a PC game during its install process install "common ridistributables"? This is no different, its just that most other programs install these is "silent" mode, meaning they dont even tell you they are being installed, they just go ahead and do it with no permission from you. You do you, but if you want to use the program then you need to say yes on that screen, at least Launchbox tells you what it is doing, unlike most other programs that go ahead and install this stuff without asking for your permission. You have probably installed hundreds of programs/games that also did this, you going to go and complain to every single one of those that they are installing things that are actually needed in order for the program/game to work? No i didnt think so, so why are you making a exception for Launchbox? Also i will note that most emulators also use directx and .NET, but i guess you havent complained to those creators that they are adding software to your PC that makes the emulators, you know, actually work?
  18. In Launchbox go to tools/options/updates, turn betas on then either restart or go to hamburger menu/help/check for updates.
  19. 11.3 official was released and then pulled originally, so some people updated to it while it was briefly out. The revised 11.3 is either out now, or due out very soon, i cant really tell as i was one of the people who updated when it was originally pushed out, so there is nothing for me to update to.
  20. Im not sure exactly, but 11.3 has moved to .net core instead of Standard .NET, and that necessitated moving a lot of files as .net core requires the .dll's and .exe's to be in the same folder, so a few files and folders in the Launchbox folder are now just links to the same files in the Launchbox/core folder.
  21. The early 11.3 betas broke all plugins, that has been mostly fixed, but there are a few still having issues.
  22. If you want to use RocketLauncher for bezels then you cannot use our startup screens. If games are starting minimized then that sounds like a RocketLauncher issue, as that is launching the game. RocketLauncher may need updating to work with the latest 11.3 version of Launchbox.
  23. Try this tutorial, it was made specifically for moving the image cache, but would work for other folders. Essentially you would move the image and video folders and use the program in the post to create a junction, so Launchboix still thinks the folders are in the normal location, but they are actually elsewhere. The only other way in the UI is to change each image type for each platform one by one, which is obviously tedious. You could probably edit the files directly somewhere, but im not going to recommend you mess with important files. Edit: forgot to actually link the tutorial.
  24. No, this is because you are using the standard rom import, so Launchbox doesnt know its a mame rom. it will just import the file and believe it is just one file. If you want to pick out games then you really need a non-merged set, they are bigger in size but each game has its own self contained zip, split and merged are sharing zips and files which makes it tricky. Games may be using files in completely unrelated games, simply because they used the same Arcade hardware, theres little point in adding the same file to the romset hundreds of times, when it can be added to one game and all the games that need that specific file can pull it from that one location. This is why a non-merged set is about twice the size as the others, each game is its own self contained zip, so there are thousands of duplicated files, but this means you can just pull any game you want out and know it will work. To be honest with you if you have a split fullset what i would do is import it as a fullset using that specific importer, and then delete games you dont want from the Launchbox UI, that way they dont show and clutter up the interface with games you dont care about, but MAME still knows where the files are and can retrieve a file from another zip from a game you have removed from the Launchbox UI if needed, so they dont show in Launchbox but are still there if MAME needs them.
×
×
  • Create New...