C-Beats

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.

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.

Is the monitor set to Landscape or Portrait in Windows display settings?

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.

Right now there is not way to do this currently. The reader will always open at the start of the document.

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.

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)

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.

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.

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.

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

What version of LaunchBox are you on? Default should already be acting correctly and I can't rep it NOT updating on my machine.

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

Working directory I believe should be \\LaunchBox\Core\. If that doesn't work just try setting it to the \\LaunchBox folder

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.

@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?

It should be working now. Had an issue with the web page we get the data from.

Event Viewer have anything more useful? Could you PM me your log file for that run?

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?

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?

@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.

Your post doesn't have enough detail to really give a definitive answer since you haven't said what systems you are trying to emulate. Do you know what the newest system is you are trying to emulate? That would determine how powerful a GPU you need. Most emulation is done single threaded and so when looking at CPU you'd want one with a decent single core performance. GPU really depends on the system you're trying to emulate as a lot of the retro stuff typically doesn't really hit the GPU much. If you have shaders enabled in RetroArch they tend to hit your GPU harder than the game you're trying to emulate (with exception for a few of the newer systems like PS3)

All the storefronts have logic built into the app to determine if they need installed or not. I'd have to review the code to see how we handle that logic for games that have Installed = false and ensure the string is correct for that as well.

What are your transitions set to? If you set them all to Quick Fade do you still see the issue?

A lot of visual things can be altered by what theme you're using so it may be possible your theme just doesn't utilize the feature. The icon next to the game option refers to Text Views. In that view you should see the icon to the left of the text if the theme hasn't overrode that logic.