C-Beats

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?

All of your data is in the \\LaunchBox\Data\ folder and can be copied directly to a fresh install. If those files were some how corrupted you also have (by default) backups on that are saved in \\LaunchBox\Backups\ which is just you entire Data folder backed up. You may have to redownload images if you need to move to a fresh install, but at least you won't need to do the imports and re-setup emulators, etc

Yeah, I did see that the Drag/Drop import had an issue where one grid wouldn't let you delete, that should be fixed in next beta. The regular Import ROM wizard should let you though by pressing the delete key.

Can confirm the bug, will be fixed in next beta. Thanks for the report!

This window wasn't changed in this beta release, but deleting in this window SHOULD work. I'll take a look and see if I can replicate, if so I'll see about getting it fixed before next beta release.

In the Edit Game window there is a "Music Path" that you can set. Point that to the file you want to play for that game and it should play.

Glad to hear

Beta is now live: If you are experiencing slow menus could you please update to the beta version (done in LaunchBox options, update page) and let us know in this thread if it did or did not help your menu's open up faster?

We took a look at the menu code and found things we can do that should improve the menu responsiveness for everyone. The changes should be in the next beta. I'll do my best to remember to update this thread when the release is out and you all can help us test and make sure you are seeing the improvements on your machines like we hope you will.

I'd check Task Manager and see if anything of your computer resources are running low. If I had to guess it's because of your RAM amount. 8GB isn't a ton by todays standards and will fill up quickly depending on what all you are doing. If you find RAM may be the issue you could try to increase your page file size and see if that helps. It will let the OS dump some of your RAM from non-active process to your hard drive to help free up memory.

I personally don't have a shield to really help verify how well the app works on it. You CAN however use it for free and judge it yourself, the only limitation to the free version that I'm aware is the library item count. Free cannot have more than I believe 100 games in it. It's also important to point out that an Android Premium license is NOT the same as a PC Premium license, they are separate things entirely. A PC premium license doesn't work on Android and vice versa so no single license would get you Big Box AND an unlocked Android app.

Be careful setting the frame rate too low as it will usually cause audio stuttering issues since RetroArch does it's best to make sure the audio stays synced to the video. Because you're rendering so slow it has to stop the audio until the video catches up and the results are far from desirable.

They are in the files you said you looked in. They just aren't in the <Game> tags, scroll to the bottom and you'll see them.

Not sure I agree with the replacement, but both could/should able to be added independently. They are two completely different styles of boxes so there is no point in debating file size / dimension at that point. They are entirely different images.

Pretty sure we added a "Broken" column to list view as well