C-Beats

Yeah, not even sure at this point what the DAT is showing you that isn't already being displayed though. I still wouldn't get your hopes up as I just don't have time to invest into any huge undertaking but I'd be curious to understand what you DON'T have now that you want in those files.

Short answer is yes. Long Answer: You may run into issues with some features if the SD card drive isn't plugged in and you attempt to do certain things in app since it'll attempt to look for or create a folder on a drive that isn't present. You also could potentially just save LB TO the SD card and run it from there on the Windows devices. It WILL run a lot worse that way since SD card read/write speeds aren't typically as good as SDD/HDD but it's technically possible.

RAM usage (especially the usage displayed in Task Manager) isn't typically the greatest metric to use. Is there a reason you're caring about what that metric is? The OS will swap out what's in physical RAM as needed, even if we are sitting on that amount as displayed in Task Manager, some of that could be on disk (and will be should another process need it). If you're running out of physical memory you can look at increasing the page size on your boot drive. This is essentially part of your hard drive you're telling the OS it can use to shunt memory data into if it needs more space. Can help you in the interim. Typically Big Box uses less memory than LaunchBox since LaunchBox stores the local games DB definition in memory and I don't believe Big Box does. This is to make several actions in the app run quicker.

Think the thing we should be congratulating @Joe35car on is their awesome taste in LaunchBox themes!

In the wheel? That typically can't be changed, there ARE views that show the covers though instead of the logo's you just need to change to them. Something like Horizontal Boxes (I believe we call it)

Work around would be to turn off auto-import for GOG via Tools > Manage > Storefronts. If you can't get to it then with LaunchBox closed go to \\LaunchBox\Data\Settings.xml and change the value in the <GogAutoImport> brackets to "Off" (without quotes). Save the file and reopen LaunchBox

In Big Box options there is an option to set the default view. In the new install it's set to Discovery Center, you'll want to change that to either Platforms or Platform Category

You're half way to the solution in your description. You DO indeed want platform categories view, you just don't want your game platforms placed in a category like they are now. You can edit the platforms so that their parent is root and then delete the categories they were in. This would make it so the game platforms are at the root level and don't take 2-3 levels to get to the games list while having your comics still nested. The "base image" thing I'm not real sure what your hope is. Are you referring to the image in the wheel or somewhere else?

Translations are ready for 13.18! Thanks once again to everyone for all your hard work and help. @Opak @Kondorito @Cauptain @Nyny77 @dukeemu @cyanjiang @Just001Kim @MajKSA @gamehacker @alexposad @k_kutsugi @Bardock @Soomin papa @thewhite

I honestly can't remember the last time I opened Big Box for personal reasons. I live pretty exclusively in the LB app. I just don't utilize the datagrid view ever. If you just want a fixed column size it's pretty easy to alter that in the theme XAML. Something like that is so subjective to each individual user we'd never be able to make everyone happy. We have the theming engine to allow for really minute granular changes like that so at least users have a possible way of changing things that a global setting would be hard to enforce/implement.

There are plugins to rename all your images to be named by filename like most other frontends utilize to make this endeavor easier. We also offer a plugin system to help in the development of software or scripts to write should you need a more customized/personalized solution. Since we utilize non-propriety file system you can also massage and manipulate the files from one application to another fairly easily via any other tools like mass file renamers/converters or tools you want to write in a language you're more familiar in. Images are only grabbed for the region assigned to the game. Our download tools also allow you to limit the number of images per use case. To grab duplications you have to be intentionally doing so. We also have tools in the software to help reduce the number of un-needed image files should you decide you'd like to change primary regions or what you'd like that limit to be moving forward in your collection. In short if you're duplicating images, you're using the app incorrectly and have manually went out of the way to generate it. Again this is you coming to early conclusions about a product because you refuse to commit to a migration of workflows. In how many markets are two competing products ever designed to flow freely from one to the other? It's why a lot of middleware companies exist that create adaptors from one to the other. We already have quite a large number of tools available on our forums for download that do this migration adaptation for you to reduce the amount of friction your change from one product to the other will take, but that doesn't remove the fact that you ARE moving from one product to another. If you upload to our website (https://gamesdb.launchbox-app.com) and not a third party like Emu-Movies we do then ensure all files are parsed and downloaded correctly and would moving forward. Does us no good to us to have assets on our server that the clients can't reliable pull down and use. Again the choice to share artwork you create is your own (and we respect the decision regardless of which you make), but you've rushed into another "gotcha" that doesn't actually exist if you'd go through the workflows already designed to do the things you're attempting to do.

Yeah, I personally find the ever looming OSaaS model Windows is trying to migrate into to be awful and something I'd like to avoid for as long as possible.

Can you confirm what theme/view you are using? If it's what I suspect this likely isn't an issue related to the beta.

Was able to look in the code and verify why you're seeing this. I'll do my best to get it corrected before 13.18's final release. For now the work around would be to have a second emulator record created that only lists that platform once in it's associated platform and launch with that (or make the option the same on both cores).

I don't foresee us dropping Windows 10 anytime soon. The ONLY reason we dropped Win7 was because one of our dependencies did. I personally am on Windows 10 and have no desire to move to Windows 11 and so will be personally pushing to stay on that OS for as long as I can. That being said I don't make any final calls in regard to any of this so can't really make any guarantees on the matter.

Please post errors in beta version to the beta thread so we can keep track of them and ensure they aren't a new error caused by a change we made.

I believe this bug is address in the recent beta update. You can go to LaunchBox and opt-in to beta updates to grab it and see if that resolves your issue.

While we appreciate any constructive criticism's from users (new or long standing) I'd also ask you take the time and attempt to use the software as it's intended before making any final calls. If all you want to do is use another program as if it was Hyperspin than just continue to use Hyperspin. The way other software work will not be the same and it won't correlate 1:1 in almost any way. Things like the insistence of using RocketLauncher will only cause undue headaches for very little gain and will inevitably sour your experience with the application. LaunchBox is open ended enough that it'll let you do a lot of interesting things if you want, but the more you fight against the intended use of the application the more manual and grueling your migration process will be. As you've seen should you run into issues in your migration the forums are always willing to help out, you just got to be open to the fact that the most correct steps in how to achieve what you're trying to do WILL NOT be the same as they were in your previous set up.

13.17 IS the latest version. We dropped a beta update of version 13.18 Beta 1 yesterday. Beta updates require you to opt into them in the options menu (Tools > Options > Updates). Go to the page and check the box and then you will detect beta updates. Beta updates are more prone to errors/bugs since they've only been vetted internally and haven't been tested en masse by users though and so you need to be aware of the potential drawbacks. We do our best to ensure all beta releases are stable, but unfortunately that's not always the case.

I added the alias and then manually refreshed our metadata.xml files server side. Inside of LB go to Tools > Download > Force update local games data (bottom most item) and then try to scan again

There were a few bad records in the DB again, I cleaned them out and should eliminate the error.

Yeah, if the cause is something similar to before the less items in the queue the more often you're going to see it since the odds of tripping on the bad record are increased. I'll take a look and see what I can find out. Thanks for the heads up.

Locking thread as I can see this going no where positive for any party involved.

Can just look in the Alternate Name section of the game and select the English translated title (if the DB entry has one for that game). May need to update your metadata from the DB to get the newest strings first though.