Jump to content
LaunchBox Community Forums

C-Beats

Administrators
  • Posts

    5,115
  • Joined

  • Last visited

  • Days Won

    18

Everything posted by C-Beats

  1. You can create the playlist if you don't select the Games tab afterward. Loading all the games into the form like that WILL cause the issue you're seeing. If you just set the auto-pop criteria and hit save without going into that tab the playlist should save normally just fine.
  2. This error is thrown when Big Box's render engine gives the instructions to your GPU and the GPU returns an error code. Typically this is caused by bad video drivers, though sometimes can be caused by fullscreen exclusive applications interacting badly with other applications. First I would just try to repair your system by running command prompt as administrator and typing "/sfc scannow" (without quotes) and letting that run, then restarting your computer. If that doesn't work, you could try checking Cemu to see if it's running as full screen window or fullscreen exclusive (not really sure what it's options are). If running in exclusive you could try to swap to fullscreen window and see if that resolves the issue.
  3. 13.0 Beta 1 is out and has had a lot of changes made to the control that renders the wheel, as well as how the wheel is animated. Could you please update to 13.0 beta 1 and let me know if you see any changes?
  4. We would like to get these into LaunchBox in some fashion. Exactly how we want that to happen though is still a bit up in the air and will probably be determined by what progress we make working on the beta 2 release.
  5. RetroArch's updater grabs the nightly versions of the cores. We grab the stable. Because of that RA cores will always be newer, but may or may not always work with your version of RetroArch due to versioning mismatch.
  6. NA SNES/N64 spines are intended to go on the top/bottom of the box, not the sides. Rotate the box the other direction and you should see them.
  7. We will be supporting the "full" scan image types and you should be able to use them in the next beta release. They require some more logic to procedurally render on boxes correctly, we will be focusing on getting that type of logic resolved before next beta release.
  8. I don't have any ETA but we do plan to get them added to the database as supported image types.
  9. Multiple comparisons of the same field are joined by an OR comparison. So you're saying Publisher is not Atari OR is not Capcom, which means you'll get all items. If you have a premium license you could just add a custom field to items in a playlist (or not in one) and then auto-pop a playlist based on that field.
  10. I've got this on my list of things to look into. See if I can get ya some answers.
  11. The user that had the plugin made for him (and subsequently added it to the forums) decided to part ways and took down the posts before doing so. We simply respected his wishes. I believe @Fry actually developed the plugin. He may be willing to reupload, but that's entirely up to him.
  12. Do you have games that are missing a box image? Or does everything in your collection have one? Just trying to rule out that those entries may be displaying correctly because they are hitting games that don't have an image and so show the fallback one.
  13. There is no current way to hide a game from a platform but not playlists. You can remove a platform from the platform category view though. To do so edit the platform, go to the Parent tab and uncheck all the boxes.
  14. With a drive that big I'd use NTFS anyway. But to answer your question to get themes to work yes you may need to do some additional work if using an exFAT formatted disk. exFAT doesn't support the symlinks we use to make themes happy and without them themes that use media files can't find them and start throwing errors. Some themes won't be affected, many will be.
  15. ah never mind, didn't even notice the text underneath, which is what I assume you're wanting added.
  16. Just is the normal logo isn't it?
  17. Yeah, not entirely sure I understand the logic behind us allow that bar to resized. Maybe it is a legacy setting from Old Default, but I'm not sure I see the value in it now. I jotted it down for things to look into moving forward.
  18. Apologies I had forgotten you could even resize that control. You can do the following: Make sure LaunchBox is closed Go to \\LaunchBox\Data\Settings.xml and open it in a text editor Look for the "ControlsBarHeight" tag, and set it to 56, then save and close the file Reopen LaunchBox This should being that bar down so you can resize it back to whatever your setting was.
  19. Not ever seen that before. Should be able to press Ctrl+Shift+B to hide that menu. If using a theme I'd suggest repairing the theme as well.
  20. You can email support@unbrokensoftware.com and ask them to look into it. No one on the forums will be able to help you with your license file.
  21. You can check the size of yours to compare. The two caches are in \\LaunchBox\Images\Cache-LB\ and \\LaunchBox\Images\Cache-BB\
  22. We are actively looking into the cause of this and it should be corrected in the next beta release. I'll do my best to remember to post here when the release those changes are in comes out so you can opt into the beta and see if it corrects the issues you're seeing.
  23. LaunchBox itself being on an SSD will help because the disk I/O is faster. Most images are loaded from cache when possible so the media doesn't NEED to be on the SSD. That being said though some image types typically AREN'T cached and so those will still be slower. Main one being screenshots. Videos will also take longer to load off of a HDD obviously. That being said I run most of my LaunchBox builds from a HDD not a SSD and in some circumstances you CAN tell the difference, but most of the time on my computer the difference is fairly negligible. It's never bothered me enough that I'd deal with moving the installs, especially give how large they can get with all the associated media.
  24. If the emulator you're pointing us to isn't MAME (and the correct version for your romset) I can see this being an issue. We ask the executable to produce a xml file we use to parse the data for the games you're importing. If not an official MAME release that command may not work, or may output data in a format that could cause issues.
  25. When the error pops up can you copy/paste it's contents to this post? There are a lot of potential causes for a null reference like that and the stack trace provided in that window will be crucial in determining the cause for the error.
×
×
  • Create New...