faeran

Sorry about this. This all sounds environment specific, unfortunately. Did you ever mention which device(s) you are using?

Can you update to 13.24 beta 1 and see if that helps your situation. Opt in under Tools > Options > General > Updates To check for updates it's under Menu > Help > Check for Updates

Are you on 13.23 or 13.24 beta 1? If you are on 13.23, could you update to 13.24 beta 1 and see if it helps at all? You can do this in LaunchBox, under Tools > Options > General > Updates and make sure that beta updates are turned on. Then back in LaunchBox under Menu > Help > Check for Updates

Are you using The Grid - version 1.5? I just tested, but the cloud icon updated accordingly. We've actually tracked down what the cause may be and it looks to be caused by an Android 15+ feature called Edge to Edge. Not really something you can do about it but once our app targets newer API versions, and the user is on Android 15+ this issue starts to appear and we have to find a solution. We are currently working on this right now.

Potentially a theme issue. I'll look into it. Thanks!

The problem should be fixed. Let us know if anyone is still experiencing this. We are investigating the possibility to see if we can push through some of the submissions that happened during this problematic period, but so far it looks like we may not have enough data to go by.

I just ran a test and the system does appear to be working good. Here's a direct link just in case you need it: https://gamesdb.launchbox-app.com/account/register

In LaunchBox, it's under Tools > Options > General > Updates , and make sure Update to Beta Releases is checked Then back in LaunchBox click on Menu > Help > Check for Updates, and follow the notification prompt.

Sounds like a different issue. One troubleshooting step you can take is use the 13.24 beta 1 installer, most likely found under your LaunchBox\Updates folder, and install a different copy of LaunchBox in some other temp location. Load it up with a few games and see if Big Box works for you. That will determine whether you have an application issue or a Data config issue.

Update to 13.24 beta 1 and let us know if the crash goes away for you.

Method 1: What happens if you just manually add a game, either through Tools > Import > Manually Add a game, or right click the main area and choose Add, or press CTRL+N Then fill in the information you want, in the Platform field, type in your platform name: PC Ports You'll want to go through each section of that window and fill in the necessary things you want associated with that game, including the application path. The platform will appear in your side menu under the Platform section. Right click the platform and edit it, and change the Scrap As value to Windows Method 2: You can take a game's exe that you want to import, drag and drop it over LaunchBox, which opens the drag/drop wizard. Choose None of the Above and then type in your platform name PC Ports, and scrape as value of Windows. Then go through the rest of the wizard. On the last page you can edit the game name, which will be used to determine a game match. Once you are done the wizard your PC Ports platform is created and the game will be inside of it. Curious, why create a separate platform for Windows games instead of creating a PC Ports playlist?

It's the same as the Games Database account, but that is not the same as the forums here. If you don't have a LaunchBox Games Database account, then yes, you'll need to sign up.

Use a files app of some kind and check if you have a LaunchBox folder in both your SD Card and your internal storage. Can you check the Options page, close to the top there's a Data Folder and see if that's pointing to your SD card or your internal Storage. The going theory is that if you have LaunchBox folders in both locations you essentially have 2 LaunchBox builds on your device and the app could point to either of them and you'll have different libraries in both. To your backup question, if you want EVERYTHING, you'd back up the entire LaunchBox folder. If you just want your configuration stuff, that tells LaunchBox which settings and games are in your app, then backup your Data folder that's inside LaunchBox. If you only back up the Data folder, you'll need to download images and themes again, but your data will stay intact.

Sounds like you have more issues than just the update, you may want to open separate troubleshooting posts for each of your issues, they will most likely have different answers.

Thanks guys for letting us know. I've sent this to the attention of the web dev and we will fix this up as soon as we can.

Can you give a specific example of what you've tried?

We have a beta out right now that fixes a number of crashes that we've been collecting since 1.19 has come out. It also fixes some user reported issues like @Vader. If you can, update to the beta and see if it fixes the issue you've had. Here's the full breakdown of what we've fixed: Fixed an issue where using the Jump To menu could cause the navigation wheel to get stuck on the chosen game Resolved a crash that could occur when entering a game view while the game list was still loading Addressed a startup error that could happen the first time the Alphanumeric Index was used Corrected a problem that sometimes caused a crash when changing a RetroArch core under Emulator Settings Fixed a startup crash that could happen if the LaunchBox theme folder was marked as read only We plan on this being a short hotfix release, so once we have some confirmation going, expect the release go out shortly after.

Thanks for the suggestions. There's already a sound option under the Sound section, called Idle Master Volume. The entire screensaver theme system is 100% themable, so a lot of what you want can be changed with a custom theme. Here's a guide about it: https://feedback.launchbox.gg/help/articles/4202599-creating-custom-screensavers-for-big-box-themes The rest you should add it into our feedback form found here: https://feedback.launchbox.gg/?b=679a6b59391ce13a8f100ae4 Don't forget to get more specific about each one (ie. Allow minimum wait time to be adjusted further... by which values?). The more clear you can make your ticket, with some reasoning in there, the better traction it will end up getting.

Sorry to hear. There's actually nothing in our code that would delete a setup, and the internal data files always stay intact, so I'm not entirely sure what is happening there. Do you have an SD card or use multiple different drives on your device?

In LaunchBox, Tools > Options > General > Updates, check the Beta update option. Then Menu > Help > Check for Updates, and you should get a notification about updating to the beta.

Thanks for the report. We have a fix build brewing, and we'll make sure this one is fixed. It'll be out early in the week.

Check under Sound options for something called: Idle Master Volume

Update to the beta and see if it helps. I hope you mean when you say you changed to WMP, you mean Windows Media Player. After the update, if you are still experiencing the issue, follow the steps to provide an Event Viewer .NET crash log. Can you update to the beta and see if that helps in your situation. If not, send us another Event Viewer log, however, the logs you sent is missing the actual .NET error log (looks like you sent the other 2 only), so don't forget to include the .NET error crash report which should be very near these other 2.

That indicates you are still on version 13.23. Can you update to the beta, which is 13.24 beta 1, and see if you are still experiencing the issue?

That's unfortunately not the .NET error report. You'll find another report near this one that will provide a better picture of what's going on. Also note setting LaunchBox to WMP is not setting Big Box to WMP, they are different settings. We will need the Event Viewer report. Open Big Box, let it crash, then open Event Viewer, go into Windows Logs > Application, and you'll find about 3 reports related to the crash that you can post here. If you don't find any reports in there then the app isn't crashing and you may be experiencing something completely different.