faeran

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.

Welcome in. There are a lot of different ways you can import games into LaunchBox, and you'll find that most of them are open-ended. While the program tries to guide you through some known best practices, importers tend to be generalized. What would help in identifying what happened is if you could guide us through the exact way you imported, also the names of your game folders and the folder structure would help determine what's going on as well. If games have been imported properly but you are not seeing them, it would mean either you are hiding them with one of the options under View > Hide Games, they were imported into a section you are not looking, or it's possible that you've imported multiple games that have the same name as another game and LaunchBox has combined them into one game entry. As far as extension types go, LaunchBox is file type agnostic and will import the files you tell it to.

Not every emulator is the same. Most emulators do have some kind of method to make it portable, but each one would require some research as to how they do it. There's no one size fits all solution there. Any emulator that you download inside of LaunchBox, we tend to automatically apply the portable solution for each of the emulators that we support.

Beta 3 is out with the following changes: New Premium Feature: LaunchBox and Big Box now include a brand new FFMPEG-based video playback option, delivering more reliable performance, with the old VLC engine now phased out We are coming to the end of the cycle very soon if all goes well. The main change in this beta is obviously the FFMPEG-based video playback engine, which replaces the old VLC option. You will need to switch to this engine to try it out. In LaunchBox, go to Tools > Options > General > Video Playback In Big Box, go to Options > Videos > Video Playback Engine Please give it a try and let us know how it performs for you. Any feedback will be a huge help in making sure this new engine is ready for prime time. @Fursphere - we have put in a potential fix for the issue you were hitting with the MAME Arcade Full Set Importer. Previously, if LaunchBox timed out when trying to reach MAME's GitHub to fetch all available versions, it would block you from moving forward. Now, if that request fails, there is a fallback that should let you continue down the manual path and point directly to your own MAME emulator. Hopefully you have some time to confirm this works for you now.

That points to using an older version of a custom theme. The way you can confirm this is if text lists for the default views are also seeing this slowdown or not. Thanks. We are able to reproduce and should be fixed before release!

Moving LaunchBox to the internal hard drive is free for you to do and it would probably help with some of what you are seeing.

Have you updated the custom themes you've been using?

Just to rule out a few things. Are you mapping your network for a drive letter, or are you just using the shared drive path to the ROM folder? If it's easy enough, could you run a dir/b on your japanese n64 ROM folder and post it here, I can use that in my tests to rule out naming of the files. One thing that stands out is that you moved the LaunchBox folder from one drive to another, and sometimes when you do this, Windows has a hard time with file permissions, which is never an easy thing to solve. I'd make sure the entire LaunchBox folder has the correct owner. It might be worthwhile to force the owner to all folders and files, and to force it to take on full read/write permissions on all the files. You will obviously want to do this while LaunchBox and all LaunchBox processes are not running. You'll also want to make sure you aren't running any syncing software on the folder, whether it be Dropbox, Onedrive, etc... When your import doesn't work, edit the platform and see if it actually received a scrape as value or not.