LaunchBox 14.1.0 Beta Thread

[MysterNybble]

4 hours ago, JoeViking245 said:

(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.

I'll try to confirm myself, but if you did get a debug log on this, might be useful to compare against

[MysterNybble]

3 hours ago, Rlad said:

Startup/Shutdown: FAST!

Wheels: SMOOTH!

Not specific to this Beta but got me to notice it, i'd expect the platform view font to change when changing the game details title font.

 

Appreciate the confirmation that perf work is noticeable

I'll chase the font thing. What you say does instinctively makes sense, so I'll double check it isn't different for an actual reason.

[AzgoRAth]

I can confirm with the latest beta that the retroachievements window in BB doesnt crash BB anymore and the double control bug is fixed too. Awesome job.

[xmas]

8 hours ago, JoeViking245 said:

(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.

Thanks for the tip, Joe! I dug into it and I think I found what was actually going on.

Whenever I imported PS1 ROMs, import wizard window showed a page saying a few BIOS files were missing. Since everything ran fine anyway, I always just skipped it. This time I sorted out all the missing BIOS files. The popup stopped appearing, and suddenly the target platform is preserved correctly on every custom platform, including Game Boy Advance (JP).

That’s the only thing I changed. Looking back, the issue seems to have started around the time LaunchBox began asking about BIOS files, rather than with a specific version, so I suspect the two are related.

One more odd thing: as a test, I removed the PS BIOS from RetroArch’s system folder again. This time LaunchBox didn’t ask about the BIOS at all, even after restarting the app, and the target platform still works correctly everywhere. So I’m honestly a bit confused, but it definitely looks connected to the BIOS check somehow.

9 hours ago, JoeViking245 said:

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.  

Ha! I’ve had it take 2 minutes too, but sometimes it genuinely goes past 5 minutes! 😄

[xmas]

4 hours ago, MysterNybble said:

First off thanks for all the details :). That said, not sure what you mean by this? https://feedback.launchbox-app.com/ is the official bug reporting form for live builds.

Ah, sorry for the confusion! What I meant was Help > Report Issue inside LaunchBox. It asks me to sign in with my Unbroken account. I follow the popup and sign in through the browser, and the browser says it’s complete and I can close the tab. But back in LaunchBox, nothing changes. it’s still asking me to sign in. Clicking the Reload button at the bottom doesn’t do anything either.

Thanks for sharing the feedback site link though, I’ll use that from now on!

4 hours ago, MysterNybble said:

Can you confirm Joe's suggestion, I think he's right. If that doesn't pan out, do you recall when this last seemed to work ok so I can compare the code?

Joe’s suggestion pointed me in an interesting direction. Whenever I imported PS1 ROMs, LaunchBox warned that a few BIOS files were missing, and I always skipped it since games ran fine anyway. Once I resolved all the missing BIOS files, the popup stopped appearing, and for a while the target platform was preserved correctly on all my custom platforms.

Oddly, when I removed the PS BIOS from RetroArch’s /system folder again to test, LaunchBox didn’t ask about the BIOS anymore, even after restarting, and the import still behaved correctly.

However, I spoke too soon. Shortly after, my Famicom (KR) platform started defaulting to Nintendo Entertainment System again. So the BIOS fix may have been a coincidence, or it only affects some platforms. It seems intermittent rather than tied to one specific platform.

As for when it last worked reliably, I can’t pin it to a specific version, sorry. I’ve included a Famicom (KR) drag & drop import in the debug logs below, in case that helps.

4 hours ago, MysterNybble said:

I shall take a look; debug logs might be useful here if you can provide them. Might point me to where the time goes.

Debug logs most likely will help me here, if you can provide them that would help.

Here are the debug logs. In this session I reproduced the following:

1. The first-import “Saving Game” delay, which took 4 minutes 33 seconds this time (timed with a stopwatch). The media download finished around 2:06 PM, right after the delay ended.
2. A drag & drop import into Nintendo Famicom (KR), where the Import Wizard defaulted the target platform to Nintendo Entertainment System
3. The Alternate Names file access error 

Hopefully they cover all three issues.


@JoeViking245 Quick follow-up: I spoke too soon. My Nintendo Famicom (KR) now defaults to Nintendo Entertainment System again, so the BIOS thing may have been a coincidence. Thanks again for looking into it!

Debug 2026-10-09 01-59-57 PM.log

Edited 1 hour ago by xmas