LaunchBox 14.0.1 Beta Thread

[MysterNybble]

7 minutes ago, PadeMoNiuM Prods said:

@MysterNybble

Hi,

Just to clarify one important point: this was really the whole advantage of using Box - Full images in the first place.

Up to version 13.26, you could take a single unfolded full cover containing the back, spine and front, place it in the appropriate Box - Full folder, and LaunchBox would automatically wrap that image around the 3D box model.

That saved a huge amount of time because there was no need to manually create and separate three different images for Front, Spine and Back.

In fact, I assume this was one of the main reasons the Box -😅Full image type was introduced in the first place.

Otherwise, there is very little practical benefit to having a complete unfolded cover if LaunchBox cannot use it directly to construct the 3D box.

Someone originally implemented this behaviour so that a Full Box image could be mapped automatically onto the 3D model, and it worked perfectly for years.Since 13.27, that behaviour appears to have been lost.

The same Full Box image is still recognised, but instead of being wrapped correctly around the model, it is rendered as a long rectangular block.

Using separate Front, Spine and Back images still works, but that defeats the entire purpose and convenience of the Box - Full workflow.

So this is not really a request for a new feature. It is a regression of an existing feature that worked correctly up to 13.26.

I’m also attaching a video of the 3D thumbnail directly from LaunchBox.

 

 

As you can see, it is rendered exactly the same way as it is in Big Box, with the same incorrect rectangular shape.

And this is not an isolated game: it happens across the entire set. My NES collection, for example, was built using Box - Full / Full DVD images, so every game that relies on this method now shows the same problem.

This also confirms that the issue is not specific to one Big Box theme or one particular view. The incorrect rendering is already present in LaunchBox’s own 3D preview.I was wondering why I hadn't received any feedback on my post,

but it turns out I might be one of the few people using that optio👀😮—which actually saves a huge amount of time, because otherwise you have to set up the front, speed, and back every single time.

It would be a real shame to miss out on a feature that saves you so much time.

I don't disagree :). Could you give me the screenshots, so I can help you out so we can make sure it works correctly?

[PadeMoNiuM Prods]

@MysterNybbleOf course ! Thx.

[MysterNybble]

Just now, PadeMoNiuM Prods said:

@MysterNybbleOf course ! Thx.

Not sure you got my whole message:

#1) your "Box - Front" image priorities

#2) Screenshot of the image itself *in* windows explorer so we can see the thumbnail and where it's at and what it's called

#3) Screenshot of that image in the media of the game, so we can see what image type it thinks it is?

 

[PadeMoNiuM Prods]

@MysterNybble

Front image priorities =

 

Image in win explorer =

image in the media of the game=

[PadeMoNiuM Prods]

Don't hesitate if needed.I can do  you a demo of the Launch Box /Big Box on the 13.26  compared to today to show you the difference.

[MysterNybble]

2 minutes ago, PadeMoNiuM Prods said:

Don't hesitate if needed.I can do  you a demo of the Launch Box /Big Box on the 13.26  compared to today to show you the difference.

Can you try two things for me.

1. Uncheck "Box - Full" from that box front priority list.
2. Clear your image cache, either through the menu or just delete both Cache-BB and Cache-LB folders and let it regenerate.

Let me know if these work for you!

 

[PadeMoNiuM Prods]

11 minutes ago, MysterNybble said:

Can you try two things for me.

1. Uncheck "Box - Full" from that box front priority list.
2. Clear your image cache, either through the menu or just delete both Cache-BB and Cache-LB folders and let it regenerate.

Let me know if these work for you!

 

Sorry, I’m going to get some sleep now. It’s late here in France and I’m exhausted after a long day.

If you want to test it on your side, the important thing is to temporarily remove the separate Box - Front, Box - Back and Box - Spine images for the test game, and leave only the Box - Full image.

If LaunchBox then builds a proper 3D box from that single Full image, then the feature is working correctly on your setup.

If you have access to a 13.26 installation, you can also run exactly the same test there. On 13.26, that single Box - Full image should wrap correctly around the 3D model.

 

**One important detail for the test: please temporarily remove the separate Box - Front, Box - Back and Box - Spine images for that game and leave only the Box - Full image.

In my setup I was using the image priority settings, so simply changing the priority can still leave some ambiguity about which artwork LaunchBox is actually using.

The cleanest test is therefore to give LaunchBox no alternative: one game, one Box - Full image, and no separate Front, Back or Spine.

If that single Full image produces a correctly wrapped 3D box, then it works on your setup. If you can repeat the exact same test on 13.26, it should also show the old working behaviour.

 

I’ll check back tomorrow. Thanks for testing it.

[AzgoRAth]

11 hours ago, PadeMoNiuM Prods said:

Just a quick heads-up regarding the current 3D view testing: the Box - Full rendering regression I reported back in July is still present. I’ve just reproduced it again and attached a new screenshot. The full jacket is rendered as a single rectangular block instead of a properly mapped 3D box.

Original report: [link]

Since 3D views are currently being worked on for 14.0.1, I thought this might be a good time to bring it back to your attention.

What theme is this?

[spycat]

I normally have Box - Front, Box - Back and Box - Spine images in my Images tab of a game's Edit Metadata/Media, which allows the 3D Model Settings to render a 3D box using these 3 images.
Adding the Box - Full image results in the 3D Model Settings continuing to use the Box - Front, Box - Back and Box - Spine to create the 3D image, even that now the Enable Full Scan Images checkbox has been enabled.
However, If I delete the Box - Spine image then the 3D Model Settings will now use the Box - Full image to create the 3D box correctly.

By the way, The new Cassette option does not have an Enable Full Scan Images checkbox, so the 3D image created from a Box - Full image is incorrectly rendered here.
 

[faeran]

15 minutes ago, spycat said:

I normally have Box - Front, Box - Back and Box - Spine images in my Images tab of a game's Edit Metadata/Media, which allows the 3D Model Settings to render a 3D box using these 3 images.
Adding the Box - Full image results in the 3D Model Settings continuing to use the Box - Front, Box - Back and Box - Spine to create the 3D image, even that now the Enable Full Scan Images checkbox has been enabled.
However, If I delete the Box - Spine image then the 3D Model Settings will now use the Box - Full image to create the 3D box correctly.

By the way, The new Cassette option does not have an Enable Full Scan Images checkbox, so the 3D image created from a Box - Full image is incorrectly rendered here.
 

I can try and clear up some confusion here

You are correct in some of what you are seeing. The Box - Full image type has always been used as a fallback option over 3 images, and it has only ever worked for the Box and DVD models. Using 3 images is much preferred over a box full image due to the calculations that need to take place to try and deduce where the front/spine/back parts of the one box full image are, which the system doesn't always get right. The logic to load the 3 images is much more basic since it's just based on the front and spine image sizes to dynamically size the model.

This means that Cassettes also do not support a box - full image type, so if you do see a box - full image on a cassettes it means you may have manually added the box full image type to your box front image group (this is not on by default).

[Deam]

I'm having an issue with the beta (and 14 regular) relating to Big Box, the new Launchbox Reader, and games not going back to the emulator (Retroarch) but being stuck on a black screen (the Game Start Screen) when closing the reader. 

• The program you are referring to that you have tested: LaunchBox or Big Box - Big Box (and Retroarch)
• Your hardware specs and OS - Win 11, 16GB Ram, GTX 1080
• What you were doing in the app and how you were doing it
  • In Big Box, if I open the pause menu, then open a manual - if I get the reader menu and press "X" to close it to get back to the pause menu, then resume the game, it is stuck on a black screen (the launchbox game startup screen that runs with Big Box). If I alt tab I can get back to the game (which is still running in Retroarch). If I press the pause menu key combo again to close the Reader while in the reader, it just goes back into the game properly (bypassing the pause menu). Something happens when you close the Reader by pressing x when using a pause screen to access the manual in-game.
• Which theme you used - Unified (main and startup/pause screeens)
• The input you were using during your testing: controller, keyboard, or mouse - xinput controller
• List all community plugins that you have installed - only Kodi pluggin.

 

Edited 55 minutes ago by Deam