C-Beats

I restored the thread:

Just so we're clear. You still have a distinct folder PER platform right? You didn't make all platforms dump into the same folder did you?

Make sure you updated the games to the correct emulator.

Just create two emulator entries a "RetroArch" and a "RetroArch (Alternate Cores)" and then point each set to the other emulator. In your case first one would point to FBNeo and the second to Mame2003. When doing this both emulator records can point to the same application path as well. You don't need two separate RetroArch installs.

Sounds like you put the script in the Exit Script instead of the Running Script. Exit script is what is ran when you press Exit Game on the Pause screen. Running script is ran while the game/emulator is being played.

You closed your side bar. Go to View > Show/Hide and select Side Bar. Alternatively you can press Ctrl+S to make it appear again as well.

While I appreciate that. Really the error message I asked about will get us FAR closer to identifying the issue than the log file will. Do you get an error when you see it crash, or does it just close?

Does the error window pop up when it crashes? If so can you post what that error is?

Not sure I agree in regard to the memory use. The only time reading from a memory is slower than reading from disc is when the OS has to shunt your data from the page file to the RAM before giving it to you. Also in regards to the UI, typically (at least in WPF) the cause for delay is CPU related (waiting for main thread so you can render the menu, or the time it takes to process the data the menu is built around) or hard drive I/O related (simply takes a bit to load a resource from file). In regard to the "true database" the only database backend that would work for LaunchBox (free to end user, and completely portable) that I know is SQLite. SQLite is nice for what it does but it's severely limited in how it stores its data in regard to data types and most of the comparison is done via strings which in C# is VERY slow, then you ALSO have the overhead over casting/serializing/de-serializing all the data you get from SQLite BACK to a data model useable by WPF. This would cause not only an increase in CPU time, but also memory (since now your data must be duplicated) and cause quite a bit of delay due to garbage collection (since those data models then need disposed) so you typically are at a net loss, more so than a gain. We COULD add more indexes to our internal database but again, if you're already talking about a large memory footprint, adding indexes would only increase that footprint since again, you are duplicating data to make the key lookup faster. You also have to ask yourself, how OFTEN would the index be used? If not very then you've cached the data and increased your foot print for a pretty rare use case. So it definitely is a bit more of a balancing game then many would like to admit.

What operating system are you running?

Image cache is on by default and because of your limited RAM amount your cache image size is already reduced some to compensate. That being said by default images aren't cached until they need to be (meaning the first time you need to see them). This DOES cause some delay in the first load because we load the image, then save a cached image (reduced sized image that is faster to read) and then load the image. You can skip the extra steps by Force populating your cache but this DOES take some time so you'd want to do it overnight.

Sorry to hear that! You can do what Rincewind suggested or email support directly at support@unbrokensoftware.com

You just need the .NET Core 3.1 Desktop Runtime found here: https://dotnet.microsoft.com/en-us/download/dotnet/3.1 (right hand side, middle bit)

Hey ya Tex. I've not seen RAM usage hit that high before on LaunchBox, but typical reasons for the usage getting higher than normal is because you have ran several imports and media grabs (namely from EmuMovies) since the application has been open. We do keep a lot of information in memory from both the files in the data folder but after running the first import we keep most information from the metadata file in memory as well as some response from third party sources like EmuMovies. This is done to drastically improve the amount of time subsequent imports take to run and reduce the amount we are hitting third party APIs. There are some things we would like to look into moving forward to help with the disposal of those but typically they don't become prohibitive to the user and so they have had to take a backseat to more pressing matters. That being said we do realize that performance isn't as good as it can be in several area's of the platform and are always working to improve things. In fact the current beta that is out right now is almost exclusively performance related changes. That being said it's worth pointing out while we monitor the memory consumption typically isn't the first metric we optimize against. Load time and UI performance are the first two metrics we shoot for generally speaking. If memory usage has to suffer for those two items (within reason of course) we typically lean for better load time and responsiveness because this is what the user feels the most. At this point in time memory is the cheapest resource on the computer and so optimizing against that as a heavy first place metric seems a bit misguided to me.

Not real sure what you asking to be honest. I can't really help in the repair of your PC, but LaunchBox is portable and all data/media is in the folder structure. You can just run a fresh/clean installer from our website over the current folder and restore the build to a working condition. There is no need to move files, the installer won't overwrite them.

We don't actually communicate at all to the emulator which screen it should be ran from, we just call the emulator via command line. The emulator may do other things when the executable is ran standalone, vs when it ran via command line, but you'd have the reach out the emulator devs to figure out what is causing that behavior.

Video load is threaded so the menu speed may deteriorate SOME but overall should remain about the same, you may have some video "pop in" because it takes so much longer to load potentially from NAS than local though.

Yeah. Just confirming the concern since you said you aren't as experienced with that emulator compared to the others.

Most of the time choppy sound in RetroArch isn't actually a sound problem per se but a video one. It means you're running far lower FPS than the target and Libretro is slowing or stopping the audio to keep it in sync with the video.

Not sure that's a bet I'd take round these parts. I know we have quite a few seasoned vets that could you give you a run for your money on that claim ;D We have PSCX-Reloaded and DuckStation stand alone emulators pre-configured for you in app (or how the command line arguments need to be for LB to launch them, emulator config changes still need to be done by you), both should get you going with PS1 fairly easily. Fairly certain that system requires BIOS files that you need to make sure match what the emulator expects, but I don't remember either being overly difficult to set up.

Never heard of that tool before, looks pretty interesting though.

Yeah Amazon is confirmed broken on the version you're on unfortunately. I've not heard any one having issues with the other two so I'd be curious to know how many items aren't showing for you with those libraries.

Ok, so sounds like they aren't showing up via the import wizard. That data we get from the storefronts directly via their APIs. I know 12.6 we have an issue with Amazon games not reporting correctly, but that is corrected in the 12.7 - beta 1 release. What storefronts aren't you seeing your entire library in?

I don't believe the CTC has any way of modifying that view. You CAN theme it, just not with the CTC. The file you want to change is OptionsView.xaml and you want to change line 84 to whatever image you are hoping to change it to.

When we say games "aren't detected" what do we mean? They aren't showing up in the import wizards, or are their installation state not being detected correctly?