LaunchBox 14.1.0 Beta Thread

[kobaturtle]

On 10/18/2026 at 1:50 PM, MysterNybble said:

My assumption is it's related to the images you have for different games. Can you confirm a few things:

• Is it consistent (i.e. same game always works or doesn't) or more random?
• What are some games it doesn't work on?
• Can you compare the images you have for those that work versus not and see if anything is different?
• Where did you source your imagery from?

Thanks!

@MysterNybble sorry for the delay.

Issue still occuring on 14.1 release

• Is it consistent (i.e. same game always works or doesn't) or more random? Yes, same games. Some works, some doesn't, under the same system
• What are some games it doesn't work on? No apparent reason so far 
• Can you compare the images you have for those that work versus not and see if anything is different? Exact same pixel ratio size for each games under the same Box-front directory
• Where did you source your imagery from? some from packs, some from me, no consistency though  (exemple attached, Forza 5 not being rendered in 3D), both .png files. screenshot taken from a custom theme but same issue using the default theme.

Edited November 2 by kobaturtle

[Madhead]

On 10/29/2026 at 7:05 PM, JoeViking245 said:

If you haven't done so already, you may want to check the integrity of the drive the images are being stored on.

chkdsk something-something comes to mind.

Sorry for the late reply, but yeah I’ve done that. Right now I'm just treating my setup like a temporary thing, modifying, adding and fixing things. It's not for stable use. For every media addition I now log in a changelog then back it up.

[Mark Norville]

Hopefully someone else has reported this, this is not about the beta version

Updated to version 14:01 and if you select force login in attempt it asks you to fill in your Steam details, so when you try and do that it does not work.

So the only way of updating your Steam library is by not selecting force log in,

Regards

Mark

[stigzler]

Just showing some appreciation for the less visible improvements you guys are making to LB/BB. Just been doing some work on a plugin and both the LB/BB startup and shutdown are now super reliable and quick. Makes things sooooo much better (both for dev and production). Great work chaps. 👏

[xokia]

Doesnt look like launchbox can launch ps3 games that are eboot.bin anymore?

If you select play I get the question of what to use for the .bin file

[JoeViking245]

14 minutes ago, xokia said:

If you select play I get the question of what to use for the .bin file

Double check the emulator that's associated with the game you're trying to launch.  (edit game, Emulation section)

[xokia]

4 hours ago, JoeViking245 said:

Double check the emulator that's associated with the game you're trying to launch.  (edit game, Emulation section)

If I just choose play I get the .bin issue
If I choose play version and select the version that is the eboot.bin in launches fine

 

[JoeViking245]

7 hours ago, xokia said:

If I just choose play I get the .bin issue
If I choose play version and select the version that is the eboot.bin in launches fine

You didn't indicate whether you did what I asked you to do, or not. Looking at that right-click menu, it appears you do not have an emulator assigned to that game. So instead, let's try this so as to be able to better help you determine what the issue may be.

Edit the game and share a screenshot of:

• the game's Launching section
• the game's Emulation section
• the game's Additional Version section
• select the 1st additional version and click edit Additional Version
  • share a screenshot of the widow that pops up
• click Cancel and select the 2nd additional version and click edit Additional Version
  • share a screenshot of that widow that pops up

(5 screenshots)

[xokia]

5 hours ago, JoeViking245 said:

You didn't indicate whether you did what I asked you to do, or not. Looking at that right-click menu, it appears you do not have an emulator assigned to that game. So instead, let's try this so as to be able to better help you determine what the issue may be.

 

Clearly they are both RPSC3 the "name" was auto added by the importer

The purple icon next to the title name shows what emulator was selected.

Edited 10 hours ago by xokia

[JoeViking245]

13 minutes ago, xokia said:

Clearly they are both RPSC3 the "name" was auto added by the importer

Good.  So as an Additional Version, it is assigned to RPCS3. 

What about for the main game that is set in the Launching section?  You know.... The one that LaunchBox launches when you simply click Play.  Does it have an emulator assigned to it in the Emulation section?  (...for the 3rd time.)

[xokia]

3 hours ago, JoeViking245 said:

Good.  So as an Additional Version, it is assigned to RPCS3. 

What about for the main game that is set in the Launching section?  You know.... The one that LaunchBox launches when you simply click Play.  Does it have an emulator assigned to it in the Emulation section?  (...for the 3rd time.)

The eboot.bin is the default main game which the .bin is what its complaining about.

The secondary game is a .ISO

The eboot.bin was added after the .iso and make default was selected. That is why the .iso appears first.
Keep in mind I used the import file option for both. So anything "not" checked would be the import wizard not selecting the option. RPSC3 was selected at the emulator for both imports.
The purple rpsc3 icon next to the title name under play version is your clue what emulator was selected.

I'll check more when I get home later today.
 

Edited 10 hours ago by xokia

[JoeViking245]

With RPCS3, if you have auto-import enabled, LaunchBox will pick up all the file types (iso, bin, etc.) for the games [that have been added to the emulator] and add them to your collection.  (vs. a manual Import-File)  But again, they needed to be added to RPCS3 first for LB to 'see' them.

(maybe something to try in the future)

 

36 minutes ago, xokia said:

The eboot.bin is the default main game which the .bin is what its complaining about.

The secondary game is a .ISO

The 2 (and only) games I have for PS3 are both bin files and were auto-added to LB (but doesn't matter HOW they were added. As long as they point to the correct file).  They're both 'main' games with no additional apps.

Here's what one of them looks like.

Notice that in the Emulation section, the box is checked and RPCS3 is selected. This way when I click Play, LB sends the full path to that eboot.bin file, to the emulator RPCS3.

I have it on good authority that if you were to also check that box and set the emulator to RPCS3, clicking Play will start the game without needing to right-click and select the version.  Well maybe not "on good authority" as you refuse to provide the images (which are 'worth a thousand words') I asked for.  So call it "an educated guess".

[xokia]

1 hour ago, JoeViking245 said:

 

I have it on good authority that if you were to also check that box and set the emulator to RPCS3, clicking Play will start the game without needing to right-click and select the version.  Well maybe not "on good authority" as you refuse to provide the images (which are 'worth a thousand words') I asked for.  So call it "an educated guess".

I'm not home I cant provide the second photo. Clicking Play should start the "default" game correct? which is eboot.bin which is the picture I provided above.

The second game is a .iso and launchbox shouldnt be passing the .iso off as it is not the "default" and its not complaining about a .iso its complaining about a .bin

But i'll check the .iso when I get home which it should NOT be launching.

*UPDATE* Let me know what else you need.

 

This should be filled in by the importer. 


After Manually adding this it works. But the import tool "SHOULD" fill that out when you select RPSC3 as the emulator to go with the game.

Edited 8 hours ago by xokia

[JoeViking245]

26 minutes ago, xokia said:

Clicking Play should start the "default" game correct?

No.  Clicking Play only launches the ROM that's pointed to in the Launching section, with the emulator that's in the Emulation section.  Clicking Play has no reason to look at Additional Versions.  Can look at it this way, if it's just a single game with no other versions, would it be listed as an Additional Version? (rhetorical question)

If there isn't anything in the Emulation section (as with a game you start with a batch file or an exe), LaunchBox attempts to execute the file that's in the Launching section.  Which is why I suggested in the 1st place to "double check the emulator that's associated with the game you're trying to launch.  (edit game, Emulation section)".  

What appeared to be happening was, LB was attempting to execute full/path/to/eboot.bin (aka the file in your Launching section) because there was nothing in the Emulation section. Then Windows wanted to know how you want to open the file.

[xokia]

what's the point of the "use emulator" section (under edit additional versions)? should this all not be added as part of the import wizard?
Seems like an import file bug to me. There is now a dependency on filling things out manually after a file is imported.

I do not recall having to do that in prior versions. Once imported whichever file you selected as default would get launched.
This is the first time I have manually had to go to emulators and manually point it to a specific emulator after importation. 

 

[JoeViking245]

16 minutes ago, xokia said:

what's the point of the "use emulator" section (under edit additional versions)? 

Until recently, Additional Versions, Documents, Links were all Additional Apps. You wouldn't want your "GameMap.png" to open with the emulator.

Maybe you have a Model 2 game in your Arcade platform that works with MAME. But you have a variant of that game as an Additional Version and you want to use SM2-Emu for that specific version.  Having it there creates for near endless possibilites.

 

21 minutes ago, xokia said:

should this all not be added as part of the import wizard?

It is and it was. That's why your Additional Versions have an emulator assigned to them.

 

21 minutes ago, xokia said:

Seems like an import file bug to me. There is now a dependency on filling things out manually after a file is imported.

I do not recall having to do that in prior versions. Once imported whichever file you selected as default would get launched.
This is the first time I have manually had to go to emulators and manually point it to a specific emulator after importation. 

This is the 1st I've heard of someone importing games and having the selected emulator in the Wizard not get assigned to the main game.

I call it glitch in the matrix, and suspect you couldn't repeat it if your tried.

 

The good thing is that this was a super easy fix. 
If you experience this in other platforms, please let us know.