faeran

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.

You'll need to go into Windows Logs > Application and find the error log that is a .NET application error. You'll usually find a group of 3 reports that deal with the crash. Also post your full hardware here as well.

A beta is out that should fix crashing issues when entering Big Box for users that are using a 30-series graphics card (and other cards that have issues with certain types of unstable hardware decoding). For users that were experiencing this issue, if you can confirm that the beta has solved this for you that would be wonderful.

A beta is out that should fix crashing issues when entering Big Box for users that are using a 30-series graphics card (and other cards that have issues with certain types of unstable hardware decoding). For users that were experiencing this issue, if you can confirm that the beta has solved this for you that would be wonderful.

It should be as simple as Sorting by Release Date. I just gave it a try and does appear to be working fine. Can you give some examples of exactly what you are doing so we can test on our end. You may want to edit a few of your games and make sure that they have release dates to sort with, that could cause problems if they do not.

A beta is out that should fix crashing issues when entering Big Box for users that are using a 30-series graphics card (and other cards that have issues with certain types of unstable hardware decoding). It should also fix the issue some people were having with themes like CityHunter 2. Once we have confirmation from enough users experiencing the crash that it fixed it for them, we will be releasing a hotfix just for that. From there, we will continue down our next cycle, which will include smoothing out any rough edges.

Nada, at least not for a long while. Unfortunately VLC caused major freezing issues due to the .NET wrapper. We spent months looking into fixing it, to no avail. The wrapper itself hasn't been updated for many years and seems abandoned, which forced our hand and required us to find alternate solutions.

There's both WMP and FFME, if you try whatever one you are not using and it's still happening, it's possible it's something else. If you do crash, check Event Viewer for the Windows application .NET errors and send us a report here: https://feedback.launchbox.gg/?b=679a6c5745a6e9cef9dabfce That will help us track things down.

Thanks for letting us know about this. Looks like Windows Defender has started flagging one of the temporary files that our installer creates while it is running. It looks alarming when it pops up, but it is just a normal helper file and not anything harmful. These kinds of false alarms happen sometimes when Defender updates its definitions and gets a little too aggressive. We are already submitting it to Microsoft so they can correct it in an upcoming update. Really appreciate you pointing it out. The faster we hear about this kind of thing, the faster we can get it resolved. In the meantime everything is safe to use and the update should still fully complete even with that error. Once Microsoft pushes the fix the warnings should disappear.

Thanks guys for the reports. For people having the issue with Big Box not starting for them and is available throughout the day, send me a PM and we can send you unofficial test builds to try and expedite the fix. The issue is essentially due to a specific piece of hardware that you are running that appears to have a conflict when it tries to decode video/audio elements, however none of our many computers have that specific piece of hardware to test with. If nobody has time, we'll go the public beta test route and we'll be phasing out different fixes until it's not longer an issue. For anyone wanting to be helpful, when it does crash, right click your Windows start button and click on Event View. Go into Windows Logs > Application. Find the errors reports about the crash. You'll usually find 2 Error reports and 1 Information report about it. You might as well dump them all here.

Thanks very helpful. From the sounds of it, can you confirm if you guys both have startup videos? If so, do you still get a crash if you remove them? Based on the errors, it's saying that your computers are having a hard time with hardcore decoding the videos, and we are working on a fix.

Would be nice for anyone having this issue to open Event Viewer, go into Windows Logs > Application, find the 2-3 reports about the crash, usually a couple error reports and one info report, and post them here.

You didn't express improperly. Windows is only brought up because it has an "Export to Android" functionality. So you could in theory, set yourself all up with your images on LaunchBox, which does have the drag/drop functionality of images, then use the Export to Android functionality to bring those images over to Android. So there is a way to do what you want right now, but it involves our Windows app at the moment, which we recognize is not ideal. While we would love to create some way for you to bulk import images into Android, we just don't currently support that at this time. The issue is that images in the app need to be processed and optimized before they are shown in the app. We have internally talked many times of how we'd handle some kind of Android image bulk importer process, whether it's dropping them in a folder which somehow triggers the image optimization process, or create some kind of manual process a user would have to run in the app itself. Most users end up using one of the 4 current ways we have for getting images into Android: Automatic image downloading, Manual bulk image downloading, single game media downloading, or the Export to Android functionality. However, feel free to create a feature request so we can keep track of it: https://feedback.launchbox.gg/?b=679a6b991b2011c4928c2573

Unfortunately, there's no easy way to bring your own images into Android. The only real way would be to first load them into LaunchBox for Windows and then use the export process to bring them over to Android. Android itself is more self contained and will download artwork automatically for you, and while there are single game media edits you can do, there's no bulk image import feature.