Jump to content
LaunchBox Community Forums

C-Beats

Administrators
  • Posts

    4,693
  • Joined

  • Last visited

  • Days Won

    14

Everything posted by C-Beats

  1. It's because the first game had 3 playable goblins, the 2nd had two, and the third had one. All solid games I used to love playing growing up. Nice to see them getting some love. Never even realized there WAS a 4 or 5
  2. Caching is done off thread, UI operations have to be done on the primary. The two shouldn't really affect each other much. The only "bog down" you should notice is it takes longer to see grid images that don't have the cache already built.
  3. It'd be helpful if you could post the error you are seeing.
  4. It's likely caused by image caching. I took a quick look at Steamy and I didn't actually put the caching progress bar in that theme (like I admittedly should have). In that theme there is no way to see visually in the UI that LaunchBox is caching images.
  5. Tools > Manage > Platforms. Select the platform who's media you want to move and press Edit. In the folders tab point the images to the new location and then press OK to save. LaunchBox will ask if you want us to move the images you already have to the new location. Press yes.
  6. If you tell it to. If you want to just update that one field then use bulk edit to clear it on all the games and then select the "don't overwrite" option
  7. Not related to beta. Was an issue on the web database side of things that has been resolved. You will have to force update your games database to see the new data.
  8. C-Beats

    HELP

    Some emulators have files that are required to emulate your games properly. Most of the time these are what are known as BIOS files. BIOS files are like ROMs of the hardware that are used to emulate the system. That error is telling you that LaunchBox doesn't see the file it believes the emulator requires to emulate your game properly. You should be able to click on the indicator to get the MD5 hash of the file in question and Google it and come up with results as to what it is and why it's needed.
  9. Error is cut off but I assume this is the error you normally would get in Win7. CefSharp is the dependency we have that no longer works on Win7 because of a security patch that was required didn't work in that OS.
  10. I understood what you wanted. Remove the command line argument and reap the rewards. What that command is saying is "hey cut the artwork if you need to in order to make the gameplay area bigger". Without it MAME uses the lay file of the overlay which will show all the artwork but will also make your gameplay area smaller.
  11. Yeah, MAME ROMs need to be launched with the matching MAME version. There are sets out there to correspond to the version of MAME/RA MAME core you're trying to use but all of it is a bigger pain than simply having a set and emulator of the same version. Outside of that you'll be just chasing issues left and right.
  12. The answer to your issue depends on how the theme you're using was created, and how your marquee monitor is built. The first is easy, try moving to default theme and see if it appears better. Second will take a bit more to figure out. Some marquee monitors are just cut monitors that still act like the full size and so the marquee has to be treated slightly differently to make those work. We have compatibility settings in Big Box to assist with those if that's the case.
  13. Step AWAY from the LaunchBox this instant! lol Import your games to the PROPER platform. This will make managing your library a million times easier then trying to micro manage everything under a single platform. If you want that hierarchy just use platform category view and create an "All Games" (or "Kitchen Sink" playlist at the top). You can even just use Platform view and add that all games playlist to the platform list. There are FAR more sensible options available to you then trying to import all games to the same platform...
  14. ROMs would. Storefront games should not.
  15. Correct. With these new variables it's now possible to grab any individual part of the rom path and then add quotes manually where needed (or use the noromfile to stop the romfile from being added at all). The Edit Emulator window's sample command has been updated so that all of these variables are correctly reflected in it as well to help avoid confusion and allow you to play around with it and see what the outcome would look like.
  16. was referring to the mame.ini
  17. If you didn't let us install MAME for you and set the command line you'll need to add your ROM path to the INI file manually so MAME knows where your games are
  18. Leaving this here as it could be pertinent for others
  19. If you're referring to the welcome screen for new versions/installs there is a checkbox in the lower left to stop it from appearing, then press close button. We can try to help you through this but premium doesn't change this process at all and you'd have seen it before making your purchase. Again if you're more specific we can walk you through why you're not getting any, nothing has been changed in regard to the ability to grab them in a very long while. Currently there are I believe 5 emulators that we do this for you. In the latest version (in beta) we have made it possible for users to create plugins that do the same so the number of emulators this will be possible for will only continue to grow. Again though, NOT a premium feature. Not sure how you came to that conclusion as Android has FAR less themes than PC. If you don't see something you like in Themes Manager you can look on the forums for even more options.
  20. We don't plan to get rid of these options as they generally work for everything. The added arguments are for those who REALLY customize their command line to do more non-traditional things like load config files via CLI. It also helps with some emulators that have more problematic command line arguments that don't generally work with the standard LB process flow. I realize the term "parens" and "brackets" aren't always the same across regions. We are referring to '(' and ')' not '[' and ']'. That being said, yes this is used in the logic to match DB items. Namely we're looking for publisher. This is mostly for games that have two games with the same title but different publisher. In the DB the title should be "Title (Publisher)" which also corresponds to how the ROMs are typically named. This process should do a better job picking the DB item that matches the ROM in question.
  21. @dmjohn0x appreciate you trying to help the community but you can't link to sites that allow you to download copyright protected material. I removed the links for you.
  22. %romfilename% - Filename of the ROM WITHOUT extension %romextension% - Extension of the ROM file (ie, .rom) %romlocation_noquotes% - Path to the ROM without quotes %noromfile% - Replaced with empty string, suppresses rom file being added to end of the command line
  23. MAME games didn't come in a Box. They are arcade cabinets. Because of this most WON'T have Box images (nor should they). We recommend for Arcade games that you select "Advertisement Flyer - Front" and use that as a box image for that platform. Also the GamesDatabase is populated by our userbase, if you notice a game is missing something feel free to upload an image to fill in the gap.
  24. What's in the folder? Like I said we don't ever use it so I'm not sure how best to help ya.
  25. If the image folder is deleted the cached images would be removed as well so shouldn't be an issue. @Lahrs I'd suggest setting the media limit to 1 and only grab images you need for your desired experience. Typically a Box, Logo, Background, Screenshot is enough. If you want vids you can grab those but they do take up quite a bit of hard drive space.
×
×
  • Create New...