C-Beats

I'd check your coverflow quality setting inside of Big Box. We use an image caching system and your settings may be causing that image to be saved too small for your use case. Increasing the quality increases the size of the cached image so it looks better, but there will be a performance hit since you're reading a bigger file.

1) I'd have to look into this. I haven't really touched Steamy since I made it and would have to remind myself how I did that. 2) This won't happen. I'd have to write a plugin to coincide with the theme to do something like that and that is a bit more of a chore than I have time to deal with. I could probably help track down the XAML that sets it's location though and help you adjust it to put the logo where ever you're wishing it'd be.

There is an option in Big Box controller options to help turn off some problematic control logic. You can try turning that on and seeing it it helps. I've never used a WiiMote for anything other than Dolphin so not entirely sure how Windows is translating it, especially since that controller doesn't have any official drivers for Windows.

Would be easier for people to help you if you could provide a screenshot of what you're seeing that isn't correct.

Because of how the models/images are created and used a spine image will always produce a better looking model and so we use the 3 images when we can. There is no way to change that logic.

Could be a few things. 1) Your image cache is corrupted. In Big Box go to Options > Image Cache and clear all images. Then go back and see if they return 2) You have a service called "nahimic" running on your machine. Can check by going into task manager and the services tab and see if it there 3) If you're running an Intel GPU you need to open up there management software and set a rule for Big Box to either leave Anti-Aliasing off or on (is defaulted to an auto-detect setting) These 3 things cause the most issues with reports of elements not showing correctly.

Yeah this is a known issue that has been corrected already internally but hasn't made it into a public release yet. Should be fixed in 13.2 beta 1. Not real sure at this point when that will drop though.

You can set default artwork on a per platform basis if you wanted.

Point of the feature is to cleanly boot into Big Box on startup, not make Big Box a security suite for your PC. If you don't want users installing software, don't put any uninstalled game in your visible collection in Big Box. Even better yet, don't allow people access to your computer you can't trust not to do something like that in the first place.

I use an Odin Pro and the only issue I have is that sometimes their emulated controls cause the LB button to stick and causes menu to open/shut rapidly. To fix all you have to do is physically press the button though and that behavior stops. Outside of that I've had 0 issues.

You can change the display used in Big Box options for Big Box. MAME has an INI file that can be altered as well. I would verify that the correct monitor is still marked as primary in Windows though. LaunchBox doesn't tell emulators/games what screen to run on and so they default open on the default monitor unless that emulator/game overwrites that setting (like MAME does)

We're aware of Avalonia but moving to it would mean not only a complete rewrite of the UI, but would break all themes as well. So even the best case scenario is that we'd be able to right some sort of translation layer for themes to the new syntax, but to do that on top of an complete rewrite AND still deliver on the current product suite is a bit unrealistic for a team as small as ours.

Big Box by default opens up to Platform View, what you want to do is change settings to use Platform Category view instead which allows for this type of heirarchy. The tree needs to be built in LaunchBox using it's Platform Category View though as you can't set that up in Big Box.

\\LaunchBox\Data (contains all information about what's in your collection) \\LaunchBox\Images (by default is where all images are stored) \\LaunchBox\Videos (by default is where all images are stored) \\LaunchBox\Games (if you use this folder to store your ROMs) \\LaunchBox\Manuals (if you downloaded, or manually added, manuals) \\LaunchBox\Music (if you downloaded, or manually added, music) \\LaunchBox\Sounds (if you manually added Big Box navigation sounds) \\LaunchBox\Emulators (if you use this folder to store your ROMS) \\LaunchBox\Themes (Big Box themes if you want to back them up for any reason) \\LaunchBox\LbThemes (LaunchBox themes if you want to back them up for any reason)

Yeah we should look into that. I don't have any ETA guarantee's but I have it jotted down and put it on our short list of things to tackle

I can assure you the issue is local to your environment. We have already had several thousand users update automatically without issue so there is something going on in your setup. If you can proceed without the excessive aggression I'd be happy to help you troubleshoot the issue to see if we can find the cause and get you squared away.

Do you know how many pixels there are between the bottom of the back glass and the top of the DMD?

Yeah. That would fairly simple to do. I got some dev I got to finish up but if no one reaches out to ya by time I'll done I can write ya up something quick and dirty for ya.

Think you may have misunderstood. You have 2 files that need created for your entire library. The marquee view for your platform list, and the marquee view for the games list. The XAML would be pretty simple/straight forward. If you let us know what you want displayed on both monitors some one could help you make the files. If you just want two images shown it's a 5m job to do.

You'd have to manually create a marquee view file to do this, but yes it's entirely possible to do. I enjoy your cab design quite a bit though the main monitor being 4:3 for pinball I'm not sure I'd enjoy, the overall concept is pretty cool.

The GUID you see on some video filenames is because you have multiple games with the same title in the same platform. We add the game ID to the filename so we know for sure which video goes with which game.