C-Beats

That is required to make a playlist visible in "Platform Category" view inside of LaunchBox and Big Box. To place the playlist in the "Platforms" view you need to check the bottom most check box on the "Details" page "Include this Playlist with Platforms"

It doesn't. That feature only looks in the platform you are importing when comparing names. It will only look in your entire collection when seeing if the exact file has already been imported or not.

Typically if the roms are listed on the last page it's because they are already imported. If you check the "Force import duplicate roms" checkbox in the options page and they suddenly appear in the import list then the games have already been imported.

You can go to the alternate names tab of the edit game window and select which title you want to use from there but we don't have any en masse tool to do that for all titles.

Yeah, what you're wanting to utilize is called a "Resource". To define them add the following block where you typically put your root element(s). The Root elements then go under this block. <UserControl.Resources> </UserControl.Resources> Any item in that block needs a x:Key defined (string) and then when you make a binding you just bind to StaticResource of the same name you put in the key. Wall2GamesView.xaml uses this functionality if you want to look at an example.

We honor your Marquee Image Type settings in our default marquees. If you want to utilize a banner image AS a marquee simply add them to your image priorities (it is already added by default) and it should be utilized by the Default Marquee View

Can't even begin to guess the cause for what you're seeing without you posting the error message you are seeing.

This can be done via Platform Category. You'd need to delete the auto-generated "Consoles" and "Handheld" categories (which will move all those platforms to the root), but after you do that it should be pretty close to your requested set up already.

The data is located in the bottom of that platforms xml file. The easiest way to get rid of the field across your whole library is to select a sidebar filter that selects all the games in your library, then select all items in the content grid (Ctrl-A works) then right click and select Edit (can also press Ctrl-E) to open the Bulk Edit Wizard. When you get to the page that asks you to pick the field select your custom field then leave the "Value" box blank and apply the changes. This will remove the field from your library without the need to manually alter xml files.

What theme are you running?

Pretty much EVERY time I've seen it's because if you look in Task Manager you have a service called "nahimic" running which has know issues with WPF. Can you see if it's running and disable it if it is, should solve the issue.

The download IS an .apk but some browsers for some stupid reason change it to bin to match your operating system. Try a different browser and you should see it as APK.

Could use the star rating field to make a playlist of items with 4+ stars, should be a pretty good starting point for you.

If you open Task Manager do you have a service called "nahimic" running in your service tab? This is the typical cause for a lot of weird UI glitching we've seen in recent past.

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.