Jump to content
LaunchBox Community Forums

C-Beats

Administrators
  • Posts

    4,500
  • Joined

  • Last visited

  • Days Won

    14

Everything posted by C-Beats

  1. I can't remember which version introduced it (though I believe it was 12.14) but there was a bug where the correct theme video wasn't always being grabbed. This bug is corrected in 12.16 so if you haven't upgraded I would do that first and see if it solves the issue. Also if you haven't already try clearing your image cache via the options menu. May be that you just have an old cache image in there that needs cleaned out.
  2. You can hide a large percentage of options by locking Big Box. You could also potentially just skip the Game Details screen where that option is available. Doing this means that when selecting a game you immediately launch it without the need to hit Play on the Details view at all
  3. I've not done it but know it CAN be done but you can set up Big Box to run as a windows shell by altering some registry keys. What this does is skips the process of starting explorer.exe and runs Big Box immediately instead. Because you need to alter registry keys and aren't starting up Windows "normally" I do need to warn you that mileage may vary and you need to be careful and ensure you do it correctly or you could break something in your OS installation.
  4. If you're on an older version of LaunchBox there was a bug updating/repairing themes (via the Theme Manager) that you were actively using and it would not extract the new theme properly. If not on the current version (or applying the theme manually instead of using the Theme Manager) I would update and try again. If you cannot update because of an expiring premium license the work around would be to change to the Default theme, and then update/repair the theme you want to use, and then change to it. Doing things in that order should get you up and running correctly.
  5. Big Box defaults to using Platform view, you need to change to Platform Category view in the system menu to see those. You can change your settings in the Options menu to make it so Big Box in the future starts in that view as well.
  6. If you've changed the app path to point to the exe you are no longer using the automatic logic since you removed the Epic Games ID we use to do all of it. You should be able to manually set the install flag in Edit Game and it'll stay how ever you have it set.
  7. Is the monitor set to Landscape or Portrait in Windows display settings?
  8. You can manually add images you get from their website to LaunchBox but at this time we do not have the ability to scrape the website from them in-app. We've been asked not to pursue such a feature until they complete their upcoming API update and we are respecting their wishes.
  9. Right now there is not way to do this currently. The reader will always open at the start of the document.
  10. If you're getting that message after running the installer than something didn't install correctly. I'd try moving the installer to a different location and see if you can redownload the installer. Then if it works delete the one you had moved.
  11. Close LaunchBox, then go to \\LaunchBox\Updates and try to manually run the installer from there and see if it works. If the file is corrupted or doesn't work delete it and LaunchBox will download it again for you (assuming you have the updates turned on in Options)
  12. 1) No the clients we added it for have specific install command line switches that should start the install process in the clients for the game selected 2) The process we start for the clients still requires mouse input which isn't real conducive to the controller interface of Big Box and so for now wasn't put into it. You could always submit a feature request asking for it to be put in there as well.
  13. Thanks for this screenshot. It helped me realize you were talking about Theme specific settings and I was able to find the cause of what you're seeing. The issue has been resolved and shouldn't happen in the next version. Thanks for the additional information and the report.
  14. We did have memory issues related to VLC videos that were addressed in 12.16. If not on that version you definitely should be if your looking for the best attract mode stability.
  15. Sounds like you have an issue with that drive and a corrupt file. I'd try to manually remove the file and see if you can get rid of it that way. Then you can restart the install or press try again. Overall though you can run the app fine with the existing sound file (the file hasn't changed in the update either) so skipping for that file wouldn't be the end of the world
  16. What version of LaunchBox are you on? Default should already be acting correctly and I can't rep it NOT updating on my machine.
  17. This is potentially because FlowImage uses cached image when possible. You could copy Defaults GameMarqueeView.xaml to what ever theme you're using then in the FlowImage control named "MarqueeImage" add the following property to the control UseImageCache="False". This will make the control use the raw image in full size and not the smaller cache file
  18. Working directory I believe should be \\LaunchBox\Core\. If that doesn't work just try setting it to the \\LaunchBox folder
  19. Does the clock in Default theme work for you? If so I'd take a look at it and see what you're doing differently.
  20. @Rlad @skizzosjt Can you let me know if you're stilling seeing issues with videos not playing when backing into a Platform or Game view?
  21. It should be working now. Had an issue with the web page we get the data from.
  22. Event Viewer have anything more useful? Could you PM me your log file for that run?
  23. Going to assume this is you just confirming those transitions DO NOT work for you, but ARE NOT the transitions you were using when initially reporting this issue, is that correct?
  24. I don't remember seeing your initial report on this. Is EVERYTHING black, or just the part that should be displaying a video? Does the wheel render as it should still?
  25. @skizzosjt The updater requiring the stable release before the beta release is intentional. This is so that you have the stable release installer available to you in case the beta has a bug in it and there is a need to downgrade to the latest stable build.
×
×
  • Create New...