faeran

Your video shows what the issue is. You have nothing listed in the Region field. Fill it in with the correct region, save the change, then go back in and run the media downloader again.

Not at all. Actually the opposite. The idea is that if you import a Japanese ROM, and it's clear that the game is indeed a game from Japan, and there's a Japanese image on the GamesDB that can be downloaded for it, we download that for you. If the game doesn't have any identifiable region, we use your Region Priority to determine which image to download. There's more steps than that, but hopefully that clears things up a bit.

Thanks for the report. We'll get this fixed up for the next beta.

a video could help out a lot in your situation, as there's a ton of variables and this seems not easily reproducible, so I'm guessing it's related to some very specific thing on your set up. Also, if you can zip up your data folder and send it to me in a PM that could help as well.

Thanks. I added a few more questions. If you can answer that could be helpful. At first glance, I am not able to reproduce what I think you are seeing.

What view(s) are you using? Also, Are you using the game menu or are you bypassing it? Are you referring to the Playlist section or a playlist within the Platform Category section?

LaunchBox doesn't quite do things this way. It's more open ended, allowing any file to potentially be imported in. Most of the importer methods are entirely file agnostic. Platforms are similar, you can type in whatever platform name you want, however, if you want it to be linked to a platform we support on our Games Database website for scraping purposes, then you can check out what the GamesDB supports over there: https://gamesdb.launchbox-app.com/

Beta 3 is out with the following changes: Improvement: Optimized the fetching of RetroAchievement hashes to reduce API calls and prevent user timeouts Improvement: Disable automatic ROM import for specific platforms in the Edit Platform window Improvement: Simplified plugin names for better clarity Fixed: Resolved some play time sync issues Fixed: Corrected region sorting errors when combining games Fixed: The RetroArch plugin no longer creates unnecessary save folders

This is pretty much right. It's more based on the ROM itself though. For example, if you have a game from North America, it looks for North American images for it. It's more complicated than that, but that's the reason you see less images than what's on the GamesDB.

There's no properties to manipulate videos in that way, and it's more than likely that wouldn't help. It's possible it's a video issue, but it's also possible it's something that's not as apparent. Simple tests: Change video playback engine and see if it's still happening Remove the video file you think may be causing the issue and see if it's still happening

That does sound frustrating. If you check the video files that you downloaded using the Update Metadata and Media wizard, do they seem like they downloaded okay and can be played outside of LaunchBox? I just ran a test on a whole bunch of PSP games, but they all downloaded fine and play properly in both WMP and VLC, so I'm not sure what to tell you. This also seems like a different issue as VLC and WMP should work just fine.

So I checked this file out, loaded it into Big Box, navigated around in and out of the view, used both video playback engines while doing so, but I never got the crash you are seeing. It doesn't look like it's this file that is causing the issue that you are seeing unfortunately. I checked the contents of the file and I'm not seeing anything that stands out, at least with the video element.

Also, if you can post the full crash here that would be super helpful.

What does your 3D Cart Priorities look like under Tools > Options?

I could be forgetting something, but I'm fairly sure LaunchBox doesn't track achievements from the Epic Games Store.

Thanks Dave. This should be fixed in 13.17 beta 2.

Yeah the code could help, or you can paste the view file, and I can take a look at it for you when I have some time.

Beta 2 is out with the following changes: Fixed: Microsoft Xbox ISO files could fail to properly be identified using some import methods like the ROM Import Wizard Fixed: Resolved an issue that prevented game changes made in the Game Details view from being persisted to the database Fixed: Multiple null reference exceptions that could occur under certain conditions Fixed: Switching between Text List view to another view in Big Box would sometimes fail to load the correct information in the new view This should fix issues like the import bug some users were having, along with about 3 or 4 other Null reference errors that users were experiencing throughout the app.

It could be dependent on a lot of variables. What does your code look like?

Sorry, I misspoke in those threads (for anyone coming from those threads). The import bug is fixed internally and will be out in beta 2.

This issue has been resolved internally and will be out when beta 2 drops. If you would like to help test the beta, here's the link:

This issue has been resolved internally and will be out when beta 2 drops. If you would like to help test the beta, here's the link:

Basically because of exactly what you said. It's the way this particular theme was created. The BannerBox platform view code was designed so that the entire full screen that you see is essentially one giant horizontal wheel, specifically designed for banners with the ratio of 386x1080. Without a banner, you end up seeing what you see. Themes have full control over what you end up seeing visually on the screen. If I were to code this theme today, I would have built it more robust with fallback code to provide a better experience for when a banner doesn't exist, although at the time the theme engine wasn't robust enough to accommodate that.