C-Beats

Yeah. I've encountered the issue where the scrollbar visibility can't make up it's mind and it causes that flicker. I'm not entirely sure the cause just yet, but once I find it and get it corrected I'll push out a new version.

His plugin kind of does that. It allows you to change your metadata to match metadata in some one else's XML file (or diff XML files between your own builds). This thread was just me sharing mine for use in his plugin for people that were interested in the all the manual changes I've made to my metadata. I was just stating it'd be best to ask Joe in his plugin thread how custom platform names are handled as I honestly don't remember. If the other user doesn't HAVE the platform they'd be able to just copy your XML directly to their data folder and have it all and the plugin wouldn't be required at that point.

Joe is making the plugin and could probably answer that more. I personally will probably not be adding any custom platforms to the metadata I share in this thread. If I did it'd be to blow out the individual tables in my vpin games like Pinball FX3 and Zaccaria Pinball

Glad you got it sorted.

As Retro stated you may need to change view. I was thinking of the original Unified, I thought all it's default views were full screen video but it's been a minute since I've looked. I'd bind a key to "Change View" and then try out what the theme has to offer. Fairly positive it has a full screen video view to match what you see on platforms/categories.

I'm not sure we are talking about the same theme as the older Unified themes display the video on the entire screen.

Most of the "Unified" themes display the video on the whole screen and may be better for you. CoverBox tends to use a large portion of the screen for videos/screenshots as well.

I'd assume the configurations should carry between versions just fine but I don't know that for 100% sure.

Should be able to open up Windows Event Viewer and see an application error log that will tell you what happened.

Would depend what version you need. Right now LaunchBox is on .NET6 but comes with the runtimes so you shouldn't have to grab anything. If you're on an older version I believe we were using 3.1 which can be grabbed here

360 is starting to get into fairly new emulation that doesn't really run well yet. PS2 and under is fairly simple to emulate, anything newer and you WILL need a dedicated GPU to run reliably.

Yeah, when this was made LaunchBox already installed it for you so I didn't even have to worry about that. The popup should take you to a download link for the runtime though. Just download the desktop runtime and then run it and it should work. I'll have to see if I can find the files I used to make this and verify what .NET version it was though. I haven't touched this since I made it.

Typically the options are: Run two builds, one for you to manage all the roms, and another for when people are over Hide all the games in LaunchBox and then in the View > Show / Hide menu of LaunchBox make it so that "hidden" games are still visible. Then in Big Box you'll only see what you haven't hid

Their website is back up but the public API is still down. Once that returns LB functionality will return with it. They haven't announced any ETA on when to expect the API back up.

There is no tool to import them but you can manually add them to LaunchBox. The application path would be RetroArch, then the command line parameters would be to open that libretro core (which is what those games are last I knew).

I believe you're running into the minimum width that the new theme has on it's sidebar. You may need to try another theme (or modify that one) to allow you to use the sidebar at the size you're wanting.

Here would be a good place to start https://forums.launchbox-app.com/files/category/22-playlists-playlist-media/

We have quite a few extensions it's based on. Most of the extensions are file extensions for image, document, web page, and digital comic file types.

As of right now we look at the file extension of the additional applications application path to determine if the app is a "document" or not. As eluded chm hasn't been added to the list of extensions for that to occur with.

Sounds like you may have have a backup data file in your data folder that is getting in the way of your change saving/loading correctly. What does the contents of your \\LaunchBox\Data\Platforms look like?

LaunchBox doesn't have command line functionality so unsure what you're trying to do. The images would leave me to believe you're attempting to do something with Playnite not LaunchBox. ImageDupeGrouper is a popular addon for that frontend.

I'm a bit confused on why a plugin is required for this purpose. Sounds like the functionality already built into LaunchBox. In the side bar select the "Games Missing Media" filter and then select the "Games Missing Video" option.

Not sure anything is really being announced regarding who got the licenses, but most talks about that stream have been happening here

I get at what you're trying to convey but I will say most of these points are things done intentionally and for good reason. 1) This I'd have to look into but I believe since playing changes the data model for the game (because Play Count, Last Played, and Play Time are updated) both the platform the game is apart of needs saved and that call may be saving the playlists associated with that game (that's the part I'd have to confirm). 2) This point was done not entirely for the technical aspect but to address the human element. The backup process as it stands is simple to understand and explain to basically anyone. If the feature is on it creates a backup at the time the app is launched, and one when it's closed. There are no boolean logic gates to try to explain (or to potentially break within the application). This also offers some data redundancy so that if one of the files goes bad for any reason the user doesn't lose all the data between that file and the last backup (which is a guaranteed data loss). Right now if one file goes bad there is a solid chance no data is lost, or that the data loss would be pretty insignificant compared to a solution where only a file was only created on data change. Regarding the time 8s of file operations really doesn't mean much on the tail end of the application. There are no windows displayed and to the average user the application has successfully closed. Most users wouldn't even realize that save event occurred and so are fine with the fact it takes additional time. 3) To address the first point the font load thing I'd assume is just WPF logic loading the font files required by the view. This isn't something we call ourselves and is handled by the runtimes. I'm a bit confused by the second point simply because you're effectively asking for the same thing you are criticizing in the 4th point. To delay or offload the data load event of a selected game or platforms so that another selection can be made before the UI locks loading the data. 4) As stated above this is to allow the quick navigation between items. Without this logic many times you are starting a load process of a title you aren't actually going to stop on. This delay ensures navigation is speedy in the UI and a load event doesn't occur needlessly causing the UI to lock as items are loaded to it. If you know your machine is beefy enough that this isn't a huge concern then you can use the different binding and deal with the negatives that entails since they are reduced for you. We have to support a wider audience though and so want to ensure the default option is the best option for the large majority of our userbase and so play it safer with the logic you see in the UI now. What most of the items come down to a min/max mindset trying to be applied to a commercial product. While in a perfect world you'd be able to deliver that, in reality it's frankly not feasible to pull off do to money or time constraints. I'm not saying there aren't plenty of opportunities to improve LaunchBox and Big Box, and there are quite a few things you could have pointed out that I'd agree need looked into and corrected but I'm not sure these points are one's that would be in our (or the communities) best interest to devote a lot of dedicated time to. If we can address them while working in parallel on another item we'd love to take a look, but I'm not sure we could block other items for these changes at the moment. Not because we don't care, but because we just don't have the resources to devote to something most people really aren't even aware is happening. That being said I do appreciate you taking the time to voice your concerns. It's nice to understand what's on the community's mind and where they think the product could be improved.

Are you running the HSM shader? I know when using that shader it creates a significant delay in the start of RetroArch.