JoeViking245

Oh... for the game saves, I don't know where they're saved to. The respective /user/ subfolders look pretty similar. So if the game is launched via QT, does it create the save in its /user/ folder? vs. if it launched from the command line using the pre-release exe file, does that method save it to the pre-release /user/ folder?

How exactly are you launching a game from outside of LaunchBox? I'm guessing via the QT launcher. And I presume it's this method that will also load the save state when launching a game. LaunchBox only looks for the file you tell it to execute. And LB won't create any folders for an emulator (except when you ask it to install one for you). That said, there are a few layers to making ShadPS4 completely portable. For the QT launcher, it needs a user subfolder. For the command-line launcher exe, you put it under launcher/versions/ folder. This you've already done. Then to keep the command-line launcher exe portable, it needs its own user subfolder. Emulators\shadPS4\shadPS4QtLauncher.exe Emulators\shadPS4\user\ Emulators\shadPS4\launcher\versions\Pre-release\shadPS4.exe Emulators\shadPS4\launcher\versions\Pre-release\user Without the respective \user\ folders, those exe's when executed individually will create the folder under AppData.

Yeah, doing that will definitely make them unable to get updated. I suggest not doing that. What version of LaunchBox are you running?

What theme are you using. Subsequent to my reply above, I was playing around with the Omni theme and experienced the same thing. But could not reproduce it with the Default theme.

Pretty sure I never had combine enabled (but stranger things have happened). All tests were ROMs imported from an internal HDD. Fortunately/un-fortunately, my 4 tests this morning were all under 15 seconds. With each import of 10 [different] ROMs being faster than the previous one. e.g. 15 sec, 13 sec, 11 sec and the last, seemingly near instant. The only difference from previous test was, today, the local db didn't get updated alongside the import process. And to clarify, all Saving Games times mentioned (1 minute, 4 minutes...) by me were from the time Saving Games appeared, to the end. aka, They did not include the update local db time. I'll try again tomorrow and see if I can find something in my/the process that triggers the anomaly.

An <Image /> (the line below your highlighted section that binds to the x:Name in your highlighted section) cannot display (have its Source be) an mp4 video file. It doesn't know what to do with it.

I don't know about the other questions. 2 ways an AutoHotkey script will run when you select Exit Game from the Pause Menu: If you have something in the Exit Script section for the emulator Which only executes from the Pause Menu. Exiting from the emulator window will not run 'this' script If the game has an Additional Application that is set to Automatically Run After Main Application Which will (should) run no matter how you exit the game

Update to this: Yesterday, I disabled Storefront Auto-Imports and this morning the same thing happened. (updating local db progress bar got 'stuck') After seeing it was stuck, I went to Tools < Options < General < Automated Imports, un-checked and re-checked Enable then clicked OK to save and close. Shortly after, got a Notification that 1 game was successfully imported. Clicked Details and it was blank. At this point, the progress bar went away. Today's findings: I have a "Docs" platform that I set up for testing the 'launching' of various types of documents. I imported \LaunchBox\Themes\Documentation.pdf as my pdf test case. Looking at the platform's Game Folder Path, I see it had gotten set to Themes. Per the logs (after the above un-check/check/click OK), the Auto-Import feature was attempting to import \Themes\Default\.bb-bundled-assets-stamp. I have reset the "Docs" Game Folder Path to Games\Docs so that "should" resolve things on my end. Note: Documentation.pdf was added to my collection back in July which is when I presume the Folder Path was set. It wasn't 'till recently the progress bar was getting 'stuck'. Debug 2026-10-12 05-24-54 AM.log

A shot-in-the-dark, reaching-for-stars, grasping-at straws... guess: You might be able [re]set the Cart Front Priorities. In LaunchBox under Tools < Options < Media < Cart Front Priorities, check Cart-3D then Move Selected Up to the top of the list.

Can't find the emulator "VBColor". You might try opening the Windows Command Prompt and try vbcolor.exe -h vbcolor.exe -? vbcolor.exe -help vbcolor.exe --help to see if will show a list of available parameters. Replace vbcolor.exe with the actual emulator's executable filename.

Does it eventually go away? Is it faster sometimes than another? Does it take a long time? Or is it just a matter of, 'it does it, and it's annoying to see'. Since you're seeing the same behavior on both the Old Default and the Default themes, it's obviously not a theme thing. I don't think it's "refreshing" anything. But rather saving changes (e.g. saving playtime when exiting a game). I don't see it happening here. But I'm also on 14.1-beta-2. Though not sure what, if anything had changed. Glad the problem is solved.

That line looks like the refreshing image cache progress bar. In "All" it could take a minute (maybe not a literal 'minute'. But could take several 'moments'). Clicking on a platform (especially a large platform) could do that as well. This (assuming it is the 'refreshing image cache') will occur as well when you change the Image Group. Though that doesn't explain it happening when you click on a game. It also doesn't jive with it only occurring after going to Tools-Options and clicking on an 'action'. That sequence could be coincidence. Dunno. I don't suspect it Theme related, but what theme are you using? And are you using the same theme on all 4 PCs? A test to rule out the theme being an issue would be to [for testing purposes] switch to the Default theme. Then see if it still occurs. Is that by chance actually 14.0.1? Or 14.1-beta-1 (or better yet, 14.1-beta-2)? And are all 4 PCs on the same release?

On 1st startup of the day, LB will update the local database file and "get stuck" at Applying Metadata. This was happening with beta-1 of this release as well. This update was not prompted by a Force Update nor manually importing any new games. It Just Did It™ on its own. I do have Automatic Imports enabled in Tools-Options and in Manage Storefronts (Steam only, "All Games"). No 'new games' are ever added. And shouldn't, as no ROMs/games were added to any folders, nor purchased/added any new Steam games to my Steam account. I do have 2 Steam games in my ImportBlacklist.xml. And rightfully so, these 2 games are not present in my LB collection. (Relevant? Dunno) I have not tested systematic disabling of Auto Imports. After a same-day restart of LB, all is good in the hood. Windows 11 (26H2) Default theme Plugins abound. But none that look at or touch games, folders, ROMs, local db, platforms (anything really) at Startup. Debug 2026-10-11 05-08-53 AM.log

It may help the developers to know: - Your Windows version/release (e.g. Windows 11, 26H2) - Your monitor/TV specs (y'all running on a 4k TV? Laptop?) - Your display settings Scale (e.g. "100% Recommended)") If your scale is set to something other than 100%, if you change it to 100% (or "Recommended") does it make a difference for the cursor?

Today's import (6 games, no images/videos) only took just shy of one minute. Started import (clicked Finish) at x:53:30 (53 minutes and 30 seconds). "Saving Games" at 53:51 Done at 54:49 (times noted above are from the PC's clock [lower right] which I have set to show seconds) Debug 2026-10-10 04-52-21 AM.log This one was 2 minutes "Saving Games" (note the date puts it prior to this beta series) Debug 2026-09-24 07-34-33 AM.log

(this is more of a comment than anything) Bug aside, is it possible that you have previously had a platform named "Play Station (KR)"? As in you imported games into a platform using that name and subsequently deleted all games in that platform. vs. deleting the platform. If you drag & drop ROMs and by default, "Play Station (KR)" is the 'selected' platform, my guess is that if you cancel that import and go to Tools-Manage Platforms, you'll have a platform with that name showing 0 (zero) games. (note to the developers) I've experienced this as well and have heard at least one other report regarding this. I did not test the "restarting LaunchBox brings back the delay on the next first import." My test on this, "Saving Games" (drag & drop 4 ROMS) took a solid 2 minutes. Which I can see feels like 5 to 10 minutes. Edit: Windows 11 (26H2) Did not test on Win 10 cab.

That's why. LaunchBox only downloads the official releases.

What updates do you have them setup to check for? (I think they're both similar)

Might try reporting in the latest release thread. This way the developers will for sure see this. As an aside, v13.15 is quite a big jump backwards. That was even before .NET 9.0 was introduced into LaunchBox (v13.19).

The correct place would be in the beta thread(s) for that release. This way the developers will for sure see it and hopefully have some insight for you.

Just tested and it's working fine here. Can you share a screenshot of the actual error (as there can be several different types).

The full C and E drives is most like the cause of the issue you've been having this whole time in your Stuck On "Loading Interface" AGAIN. This Is Unacceptable thread. Hopefully when you get your enclosure for your other drives and get things moved around, that will take care of things.

Yeah, that would definitely prompt the message "There is not enough space on the disk."

Auto import is enabled for that platform. You can edit the platform and check the box Disable ROM Auto-Import. If you want to disable it for all non-storefront platforms, you can do so inside Tools - Options.

How much free space do you have on your E drive? If your E drive has plenty of free space, how full is your OS drive (typically the C drive)? If when you close LaunchBox and it's finished doing its saves and cleanup and the empty Temp folders are still there, yes, you can delete them. Though they should get removed when properly shutting down LaunchBox. However, deleting empty folders won't free up any notable space.