C-Beats

You may be able to ask around to see if some one can try to make a plugin that could do this. Plugin would have to make LaunchBox window "TopMost" until a game is launched, then make it TopMost again after it's closed. VERY janky and prone to failure so I really wouldn't suggest it, but could potentially work. That being said LB doesn't lock out any operations and so the kids could still potentially add/remove games, media, or metadata from your collection should they press the commands to do so.

I can't think of a single delete operation in LaunchBox that doesn't ask for you to confirm the deletion so I'm not entirely sure where this post is coming from. What are you doing that you are seeing files being deleted?

I'd check the emulators compatibility page, it sounds like that game may just not run on that emulator. Xbox emulation is still in VERY early stages and isn't near as stable as other platforms so issues SHOULD be expected.

What LaunchBox version are you trying to run currently? Also what operating system are you using? The newest version is built using .NET 6.0, while a version that old is still on .NET Framework. The fact that THAT old of a version works fine would leave me to believe that one of the following is happening: There is a conflict in your set up with the new .NET runtime There is a conflict in your set up with your machine and the Direct X version installed (For max WPF performance you should be running 9+) Newer versions offload much more to the GPU than older versions (this is ESPECIALLY true in Big Box) and so the move to your GPU could be causing more stress which could lead to throttling (check your temps while running) Several third party graphics apps like Nvidia GeForce and AMD control center have per app settings that can be set. We've seen some issues with any of those that try to force Anti-Aliasing. If you are using an app like that turn it to either on or off and not a setting that lets it automatically choose. This mostly affects Intel graphics but we've seen some issue with some AMD cards in the past

Talking about this

I'm not real sure what to call the buttons on the device but if you press the one this image points to in the tray that opens up the icon (that by default) is in the middle of the top most row it will change you control mode for ALL applications. Make sure this is set to "Gamepad" and not "Keyboard" or "Auto"

I fully admit I am no system admin and tend to run for the hills when it comes to any system maintenance or OS setting questions. I personally have never seen that on any PC I've ever own and would hate to even guess is causing that and whether that is intended behavior or not.

Just wanted to make everyone aware that the RetroAchievements API we use to gather a games achievement data as well as your achievement progress is down and under extended maintenance in an effort to fix some of the stability issues they've had lately. The following was posted by the RetroAchievements team via their Discord: We realize this is a major inconvenience but at the moment any solution or path forward is out of our hands. We ask that no one brigade or harass the team at RetroAchievements about when to expect the API to come up again. They are already under immense level of stress just trying to get this all corrected and interrupting them helps no one. We'll monitor the situation and do our best to keep you informed as best as we can.

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?