C-Beats

We don't personally use VSS at all. It's basically a Windows backup process that is failing. Do you have a backup application running, or the automated backup systems in Windows enabled?

Just so we're clear the profile switch CAN be configured per app, but is also a global setting. Basically the device tells Windows it's a KB+M and a controller, then switching between control modes changes what one Windows thinks you're using.

I'll have to take a look in the morning and see if I can find anything out about what could be causing that as I've never seen that before. Do the other logs have any useful information in them?

Just got an Ally today and it's shed some light on potential issues you may be running into. Ally has a "control mode" that can be assessed in Amory crate (or it's quick menu that is accessed by the bottom most function key located to the left of the screen). I JUST got through all the darn Windows/Asus updates so haven't tested Big Box with it, but I'd assume that because of how Big Box control logic works that you will need to force the Ally into "Gamepad" control mode for Big Box to see the inputs we use for controller mapping. If you NEED KB+M control mode you may need to set up a profile in Armory Crate to tie the navigation bindings to the correct ROG Ally buttons (similar to using something like Xpadder)

We moved to .NET 6.0 in 13.3 and the runtime comes packaged with the app so there is never a need to ask for you to download it moving forward.

Can't grab it from the website. You enable the beta updates in app. In Tools > Options there is an Update page where you can opt into beta releases.

The current beta release would give relief to the .deps.json file missing but that shouldn't affect stability in any way. Very least it may be best to migrate to it so you can remove that error just incase it's hiding the real cause of the issue.

I don't personally use a marquee in any of my builds but these are pretty interesting. If you don't mind the criticism I'd consider adding a white border around the logo's you use as they can be hard to see against the video. Also with that being said the Nintendo logo you're using has some holes not punched out in it (first e is still filled in) that give it a really unpolished feel. Overall the concept is sound and I'm glad your enjoying the process.

If you're on the latest version of LaunchBox you have no need to download the runtimes as they come with the application.

Not ENTIRELY sure I'm following you. Are you having issues with keybindings inside of Big Box, or inside of your game? If inside your game you're going to need to change your emulator settings.

Can you go down one record and look at that one? Typically those errors come in pairs. The first one is the error that caused the crash, and the second is something just saying, "Yep it crashed!" and is far less useful.

I'd take a look in Windows Event Viewer and see if there are application error logs that may be saying why the computer is shutting down then. Also what theme are you using? Does the experience change if using Default (if not already)?

You can run the app on exFAT but will require some manual effort to make themes play nice. This is because symlinks aren't supported on that format and so the automated process that takes cares of this doesn't work. Basically you need to copy some directories to the core folder, then mark them read-only. Namely the \\LaunchBox\Themes folder and copying it to \\LaunchBox\Core\Themes. Then if you ever install a new theme you'll need to drop it in BOTH folders moving forward. If the drive is still fairly empty you could also just reformat it to NTFS and then use it as normal.

Not sure what you mean, on my screen that's what's in my post

LaunchBox and Big Box both have controller support that can be changed in the options menu. Just tell it you want to use whatever controller device the Ally registers as (or can just check "Enable All Controllers") and then set the bindings to the buttons you want them to be on.

We may be doing a case sensitive search instead of case-insensitive like we probably should be. I'll have to take a look into the code and verify.

I can't help you with CTC settings as I've never used the app but I could potentially help with the XAML. What are you attempting to do?

If OneDrive has the files we need to read/write to locked because it's attempting to sync it'd cause LaunchBox to fail to open.

What drive format is your SSD using? Is it Fat32 or NFTS?

Issue with a lot of this stuff is being able to find models that work in the app well. Some models wouldn't be AS bad as they are unique and don't require us manually altering the required files to display the texture on. At the moment there are no solid plans on adding models outside of box models. Maybe one we have all THOSE models in we can look at adding others, but adding them before Box models are done doesn't seem like the best path forward. Realistically this feature would implemented in a way where in the game model overrides you can override with a specific model file you point us to and we load for you. This would give you the flexibility to find and utilize any model you wanted without us being tasked with the immense task of finding or creating procedural models that can be used to display models with artwork from your collection.

Do you have a key bind set to "Shut Down" that may be accidentally being hit? Are you actively interacting with your machine when it shuts down, or are you running attract mode and just notice it shuts down?

Big Box doesn't have a minimize option.

Since last time you reported this issue you found it to be a USB device being plugged in that caused your issue I'd first go into LaunchBox and Big Box and disable the "Enable All Controllers" option and just use a dedicated controller and try that first. LaunchBox may be polling and waking up a device that is otherwise off and causing issues. If you have any software monitors that apply different profiles to your peripherals based on what software is open (most mouse and keyboard support software does this). I'd shut them off and try as well to make sure opening LaunchBox isn't changing a profile that is causing issues. Typically when you see Windows lag like that it's either your CPU getting locked up or the boot disk having read/write issues. LB could be making these worse by writing to the cache and making your drive have to index things after the fact and negatively impacting performance. This gets even worse if using an SSD over 80% utilization. Also in the future when you close LaunchBox process, make sure to go to the "Details" tab in Task Manager and ensure that all LaunchBox processes HAVE indeed closed. If your machine is lagging AFTER LaunchBox processes are closed you have something NOT LaunchBox related going on with your system. A good place to start is to vet your system files by running Command Prompt AS ADMINISTRATOR and running the following command "/sfc scannow" (without quotes) and seeing if it detects anything. Restart your computer after running it. Also ensure your drivers are all up to date. If you have a Razer mouse ensure you have Synapse running as their mouses are known to cause issues similar to what you're describing if the mouse can't communicate with synapse.

I realize this may happen with some systems simply because the box - front images don't ENTIRELY match the UI you are creating (namely 3DS) but you have some platforms where the artwork is cut off quite a bit. I noticed it with 3DS, Sega 32X, and Nintendo Switch. May be possible to adjust those image types to sit in the UI a tad better without cutting off as much of the image. Not trying to discourage you or insult your work, I think what you've gotten done is pretty amazing and is no small feat (poor @faeran STILL has nightmares from his CoverBox days where he too made a unique view per platform lol). You seem eager to learn and take the constructive criticism and I just want to make sure you have the tools and input to make this theme as awesome as your vision is for it. As a work around for some systems where the media type used in the UI doesn't EXACTLY match the front image (like the Nintendo systems that use a square icon instead of the box) Big Box DOES support theme overrides and could be possible for the theme to either be packaged with or use images specific to this theme that would work a bit better for those platforms. I personally would love to get a square image set for my library as there are several solid use cases for them.

As stated in theme manager, that theme requires version 13.4 or newer to function correctly. You are on 13.3. If you do not wish to upgrade to 13.3 you can download an older version of Big Details from the forums