C-Beats

Version - Doesn't contain any - Beta; Demo; Prototype Just tried it and works as expected.

That makes more sense. Thanks for updating everyone and letting us know, much appreciated.

Zip files are almost never required or of any real help. This is especially true for cart based systems where the ROM files are already extremely small. Zipping them just adds more process overhead before you can use the file. If the emulator has to unzip before reading the file it can also wear out SSDs because you have to write to the disk so much more often. CD based systems all have compressed file types that don't require the entire file be uncompressed to read and should be used to save space. Extensions like CHD, RVZ, CISO, etc.

Pretty sure since this post we've added several new auto-populate rules. May be able to help you find a solution if you post what you're actually trying to accomplish.

Appears to be the 3D model which can use Box - Front, Box - Back, Box - Spine or Box - Full Scan to render appropriately. You can override what model is used on a per platform or per game basis inside of LaunchBox as well

Our application isn't written in something similar to assembly so the likelihood that a change in motherboard is the cause for this is highly unlikely. On the extremely unlikely event the motherboard IS the cause of some compatibility it'd be with one of the runtimes in use by the application, not the application itself. The runtimes in questions would be things like Visual C++ runtimes, Direct X, .NET 3.1, and .NET 9 runtimes. That is the code that is hitting at that level more so than ours and would need corrected. None of which are controlled by us so not something we'd be able to "fix". As I understand support has reached out to you and is willing to work with you regarding the issue. If the meantime if there are any customers of yours with any of these systems I'd suggest doing some of the following to help correct any issues on the OS level that could cause issues that would be perceived as a cause for this. Ensure all drivers/BIOS are up to date for hardware (MOBO, CPU, GPU are the main ones, ensure Direct X is up to date can help as well) Open powershell as admin and run the following: Dism /Online /Cleanup-Image /ScanHealth (run this first. This checks that the comparison values of the next tool are correct and so ensures it works properly) If any corruption is found you can run the following in that same elevated powershell window to correct: Dism /Online /Cleanup-Image /RestoreHealth (if this step is needed a computer restart should be performed before the following) Open command prompt as admin and run the following: sfc /scannow (this command checks OS system files for corruption and attempts to clean up any issues found, if it finds and repairs anything please restart your computer before attempting to start LaunchBox again) Verify your OS settings and your MOBO settings are playing nice. Win11 adds a lot of hardware level security settings and there being a mismatch in there can cause operation issues, especially when hitting the filesystem like we do. If you do the above and it still doesn't work please perform the following: Navigate to \\LaunchBox\Core and run LaunchBox.exe, allow it to crash Open Task Manager and ensure it's no longer running in the background Open Windows Event Viewer Navigate to your application logs Look for two errors back to back pertaining to the failure of LaunchBox Send us BOTH error logs. One typically is far better use than the other and so having both just makes sure we get the one with more pertinent information. A report of your hardware could also help. If you could run msinfo32 (press Win+R and then type it in run and press enter) and get a screen grab of the first summary screen it opens to that could help us gather more hardware specific information.

How are you adding the game?

Thankfully LaunchBox has a pretty rigorous theming engine. You (or some other themer) could likely add something like this already with it if you didn't want to wait for us to drop anything official.

What you're asking for is the functionality offered by our "Platform Categories" view. It can be used both in LB and BB. It allows for the use of Categories which acts essentially like a folder that contains other categories, playlists, and platforms and allows for navigation like you're asking about.

I can count one one hand how many times we've put out a release that can't be easily rolled back by just running the installer for the previous version. If it takes you more than that to restore a built after an update feel free to make a post on the forums asking for help.

If you're referring to the LB context menu in a game any additional applications that are links are located in Media > Links. This was changed in 13.18

That prompt is just asking if you want to close BB and run the installer you already told us to download via the settings. If you don't want it doing that in Tools > Options > Updates within LaunchBox shut off the update auto-download.

For those having the issue could you post up the following information: 1) What theme are you using? 2) What platform view are you using? 3) What game view are you using? 4) Do you let attract mode change platforms or no?

Believe this to be related to a bug found and resolved internally. The code passed to custom badge plugins passed null game references to the badge code which caused exceptions downstream causing that issue. Should be resolved in next release. Currently isn't a work around other than disabling the badge throwing the error.

I went ahead and decompiled the library attached. It looks like they are using that DLL to render your marquee. They are basically creating a WinForm window that is displayed in your marquee. The library allows you to change the settings for it. You could potentially look into the Third Screen Plugin found on the forums or just use Big Box's marquee view for marquee functionality.

Just do as instructed and uncheck the Attempt to hide console window on startup/shutdown option in the Edit Emulator window and you can use the emulator as desired without any side effects (or least none that I've seen personally or had reported)

@Kevin_Flynn @AlabasterSlim only the local copy of the games database we use to scrape metadata/media was converted to Sqlite. Your local files are still the same XML files they've always been.

Yeah, I think this is the cause. I have a full path in mine that isn't in yours and it's causing issue in the code. A work around for now is to open the yml file and in the "pref-path" entry put the full path to the folder the emulator is located in. Save the file and then try to import again in LB. Alternatively you can rename/move that file out of that directory, run the import and put it back. I've noted the problem location in code and it should be corrected in the next beta release.

Could you check to see if there is a config.yml file in your emulators root directory and if so PM it to me so I can attempt to step through code on my end @cscottbrown @ry4man93

That would depend on your auto-import setting. Tools > Manage > Storefronts will show what you have set to auto-import.

Apologies, that menu has had it's strings/location changed a bit since first added and I always forget the new one. The second screenshot is showing me what I was hoping to see. I'm at a loss for the moment since I can't replicate on my end. As time permits I'll walk through the code and see if there anything else we can walk through in an attempt to figure out why it's not working correctly for you. Are you opening the app from a network location or as administrator?

Yeah, worst case scenario is that on starting the app back up you'll import a bunch of games you may not want

If you go to View > Show/Hide within that menu are some selections like "Hide Games Missing..." are any of those checked?

If you press "Force Import Duplicates" in the import options page do you see them then? Also if you go to Tools > Manage > Platforms do you see Vita listed? If so does it have a game count?

@cscottbrown Can you run a normal ROM import using any file/folder and import for Playstation Vita and in the emulator page select Vita3k. When you get to the last page regardless of what you selected to import from all games not yet imported that are installed to Vita3k should appear on the game select page. Select a row and press delete to remove it. Let the import run and then close LB. Open it again and see if the scan picks up the row you deleted on restart. We are seeing a bit of a delay in the auto-import process in 13.19 likely related to the Sqlite change so give it a while longer (no longer than 3-5m depending on your specs).