C-Beats

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.

I'm fairly certain that was put in with the idea that most users would prefer the game itself to be as large as possible on the screen and to have the bezels be used only to fill dead space, instead of the shrinking the game to fit inside the bezel. I personally have to shut that setting off on my cab as well so I do understand it's not a setting EVERYONE will want to use, but it's fairly easy to remove should you want to.

I was referring to if you upload to the Games Database. Both could be uploaded as a pack to the forums without issue as well if that's what you were referring to. I'm sure many would appreciate it being in both.

@moudrost Can you see if these improvements help with your Big Box Attract mode stability as well and let us know if you see any positive or negative changes? @maabus Can you confirm the issue you saw related to this is corrected? @jagarbet I believe the music related issues you brought up are corrected in this update, could you confirm? @Zkyo This should resolve your report. Could you please confirm you see this corrected? @skizzosjt This should resolve your game count issue you reported. Please confirm you see it corrected in this update. @JoeViking245 Can you confirm you're seeing this update corrects the issues you brought up related to your plugin and data saving? @atbc @Thornback @skizzosjt Could you please confirm if this update corrects the behavior you reported in 12.15? If you do still have this issue please let me know what theme you are running so I can try and reproduce.

Yeah. Those are fine. I'd just put them in the image types I referred to. We really don't have a great place for the icons, but the backgrounds would be a nice add as we tend to have a lot of holes in that image category in the database.

You have an example of the icon/background? I can't immediately think of any reason not outside of the fact we really don't have an image type for icons so not entirely sure what would be best for that. Probably Fanart - Box Front

In the options there is a Security section where you can hide those when locked. Just hide them all when locked then lock Big Box and you can get rid of a low of menu actions throughout Big Box that way.

Yeah, you can either mix and match using your own theme, or set the theme to Colorful then go to every platform and use the "Change Theme" and "Change View" buttons (not set by default) to change that platform to the Theme/View you want to use for it. Your changes will save if you have the "Remember View per Platform" setting on

I'd try upgrading to 12.15 and see if you notice any improvements (you can downgrade back to 12.1 after if you don't without worrying about losing your data)

Probably an issue with the KeyboardView.xaml file in your theme. Navigate to \\LaunchBox\Themes\{Theme name you're using}\Views and delete the KeyboardView.xaml in there and restart Big Box and you should be able to use it properly

Are you using the 3D Box image group in LaunchBox? By Default it's Boxes which uses the Box Front image