faeran

January 16

17 minutes ago, TheNewClassics said:

Is there a way to update BB themes (via Theme Manager) without being in BB? Because I can't see the text lists at all in BB, and I'm getting an error each time a text list tries to load.

I updated the OP with known issues with beta 1, which this falls under. There's some missing .NET 9 theme migration things that should be fixed by tomorrow.

I'll try and work through potential workarounds, or as the section indicates users can downgrade or wait for tomorrow when beta 2 releases.

January 16

Hi Everyone,

13.19 Beta 1 is out with a bunch of improvements and fixes. The main goal of this release will be focused on performance and under-the-hood advancements to help us get into a better position for future updates.

To that affect, beta 1 includes two major changes, including a complete under-the-hood change to how the LaunchBox Game Details view loads in each time you select a new game. Instead of reloading the entire pane, we are now only updating the bindings in that view. We've also migrated the app to .NET 9 (previously were using .NET 6.0). From a user-standpoint there's nothing you'll need to do other than running the update, as .NET 9 is built directly into the app.

If you are using a custom theme, you'll want to make sure to use the Theme Manager to update them to the latest versions before commenting below.

Thanks to all who help test these beta versions. Don't forget to include the following information in your feedback to help us out with tracking down with any issues you may face with these betas:

Your Windows version
Description of the issue
Can it be reliably reproduced on your end?
Reproduction steps

You can opt into the beta within LaunchBox by going to Tools > Options > General > Updates and turning on Update to Beta Releases. If a beta release is available, you will get prompted each time the app opens up, or you can manually check using Menu > Help > Check for Updates.

Full Changelog: https://www.launchbox-app.com/about/changelog

Beta 1:

Improvement: Improved speed at which the Game Details View loads in LaunchBox
Improvement: LaunchBox has now been upgraded to .NET 9.0 (from .NET 6.0)
Improvement: The LaunchBox Game Details Default view now features Related Games in a dedicated, easily accessible section, for a more performant and user-friendly experience
Improvement: The ability to disable individual Related Games sections has been added in LaunchBox, accessible under Options > Visuals > Game Details
Fixed: Restored the expected behavior for the top background image in the Default theme's Game Details view. It will now prioritize images from your Background image group before using a Gameplay Screenshot as a fallback
Fixed: Resolved an issue where image loading could be disrupted by multi-threaded gremlins
Fixed: Corrected an error introduced in version 13.18 where dragging and dropping non-ROM game files would incorrectly assign an unassigned emulator value
Fixed: Eliminated the unnecessary prompt to select a RetroArch core for platforms that have already been imported
Fixed: Restoring saves on an Additional App could inadvertently overwrite the save data of the primary game

Known Issues with Beta 1 (which will be solved in beta 2):

Some views in Big Box, including the system menu, and Options menu show up black due to .NET 9 namespace migration issues

Beta 2:

The Black Screens Big Box have been fixed (introduced in beta 1)
Under certain conditions game media within the carousel could show images from a previous game if the new game had no media (introduced in beta 1)

Known issues with Beta 2 (which will be solved in beta 3):

Opening a second Game Details view using the Related Games feature is not always loading properly
Related Game tabs not always resetting back to the first tab in the list under certain conditions
Expanded achievements is sometimes left on after changing to a new game
Platform Icon within Game Details not always appearing

Beta 3:

Fixed: Opening a second Game Details view using the Related Games feature is not always loading properly
Fixed: Related Game tabs not always resetting back to the first tab in the list under certain conditions
Fixed: Expanded achievements is sometimes left on after changing to a new game
Fixed: Platform Icon within Game Details not always appearing
Fixed: Clean Up Media utility no longer freezes when initiating scan
Fixed: Margin issue with the default theme's Documents and Links sections
Fixed: Visibility issue with the default theme's Media Preview box

Beta 4:

Improvement: This update replaced LaunchBox's legacy XML-based local game database with a high-performance SQLite database. Expect a noticeably faster startup time, lower memory usage, and a solid foundation for even more performance gains in upcoming releases
Improvement: The included version of VLC has been updated to version 3.0.21, bringing performance improvements, bug fixes, and updated codec support
Improvement: Platform Clear Logo and Icon for Bandai Super Vision 8000 is now included when importing this platform
Fixed: The auto-import feature for Playstation Vita games using the Vita3k emulator is now working correctly
Fixed: Resolved an error that occurred under specific conditions when using UNC paths
Fixed: Badges and Star Rating graphics on the GameDetails view should now work as intended (introduced in beta 1)
Fixed: Media Carousel alignment under certain conditions in specific custom themes
Fixed: Included 3DO Interactive Multiplayer logo not showing up after platform import

Known issues with Beta 3 (which will be solved in beta 4):

Star rating graphic in Game Details view not showing accurate info all the time
Badges that appear in the Game Details view not currently appearing

January 15

23 hours ago, retroD999 said:

Thank you @faeran for the quick response!

So, is the .scummvm files not the correct way to import these games?

If you don't use these files, how does the import handle when you have multiple scumm games in one folder? (I noticed a few games I have come up in scummvm with multiple versions because of the language, or some variation to run on a lower mem system)
I don't mind rebuilding the scumm setup - how do I go about it so I can run it via retroarch?

I know I can set retroarch and the scuymmvm core as the emulator on import, but what are the correct steps?
Do I simply import the root game folder and it will set it up correctly?
Do I not need to import the games in the rertoarch core to populate its ini file?

Looked into it a bit more and yes, you are right. The reason you were seeing what you were seeing with Bargon Attach because our current system uses their auto-play feature which then simply choosing the first game version on the list and plays that. That particular game has some unplayable game in that slot.

We'll definitely be taking a crack at shoring that up for standalone ScummVM in a future update.

As far as RetroArch core is concerned, we'll also get in the ability to import the core specific scummvm files without the need to using a dummy platform first in the next update like you did in your workaround.

January 14

4 minutes ago, retroD999 said:

Hello!

I am in the process of updating my LB build and I have hit a snag with ScummVM games (using LB v13.18)

My old build was setup using the epicfail files and using Retroarch as the emulator.

These no longer work in my new setup, and I was not able to use the updated epicfail system with Retroarch (I did update it and looked at the info on the forum).
However I have learned that I can use .scummvm files instead. This works - I can launch a scummvm file in retroarch directly, or from Launchbox. using the scummvm file as the application path.

Now, the problem I am having is, when I import scummvm files in launchbox (via file drag and drop or the import roms menu command), it sets the file's folder path as the application path, instead of the actual file.
The folder path does not work and I need to manually edit the app path to point to the scummvm file instead.

Problem is, it is a large collection and I was hoping there was a more automated way of doing this.

I am unable to force LB to import scummvm files as file paths - it seems to uses the parent folder instead no matter what I do.
Is this the intended behaviour? Is there a workaround? I have been trying all sort of things but was not successful.

Using the retroarch core instead the scummvm.exe is important to me - I like its shaders and almost all my setup uses retroarch as the emulator, so I would like to keep using it if possible.

Anyone has had a similar issue or found a workaround?

Hey @retroD999

This is intended behavior, in that all you need to do is drag/drop your ScummVM folder that holds all of your games, then it uses your game folders as the file path to pass along to the emulator.

We also built in a ScummVM downloader, which solves any headache with setting it up.

I just tested adding the ScummVM core to RetroArch and it seems to play games perfectly fine through the core as well. I set the ScummVM platform in its associated platform section and set the core.

Let me know if this isn't working for you and I can help you through the process.

January 14

On 1/12/2025 at 7:01 PM, ChunkyLoverMark said:

Hi, just wondering if there's a workaround fit this? For instance I have added Super Nintendo roms but I've changed the roms, added some and removed some. Is there a way I can remove just this platform from Android LaunchBox and re add the roms for this platform? So remove all images, videos, memory of these roms and start a fresh but keep all the other platforms I've already added?

You can long press over your SNES platform and choose delete. You'll also be asked if you would like to delete your media, as well as your ROMs. Make sure you say you don't want to delete your ROMs

January 13

On 1/10/2025 at 4:09 PM, jacksonjack said:

It works on android phones, but fails on chromebooks, I just tested it, it is unable to see network drives on chromebooks

Based on this document, it looks like Android apps are run in a container, which means it doesn't have access to a user's local network. That would explain why you are seeing what you are seeing.

Here's the link: https://developer.android.com/topic/arc#:~:text=This means that Android doesn't have direct access to the system's LAN interface

Here's the quote from that document that explains it:

Chromebooks run the entire Android OS in a container, similar to Docker or LXC. This means that Android doesn't have direct access to the system's LAN interface. Instead, IPv4 traffic passes through an internal layer of network address translation (NAT), and IPv6 unicast traffic is routed through an extra hop.

21 hours ago, Sharakk said:

First, I want to say I love the Download and Play feature! It has been a game-changer for browsing my library on my Android tablet, and I truly appreciate the functionality it provides.

However, I’ve noticed that the download speeds seem unusually slow. For example, when I use Android Launchbox to download a file (about 1.4 GB), it takes nearly an hour to complete. By comparison, using my Android file manager to download the same file from the same shared folder on my network takes less than 5 minutes.

I’ve tested my network and ensured that both devices and my server are optimized for high-speed transfers. My connection is capable of 2.5 Gbps via Ethernet, and file transfers outside of Launchbox consistently achieve speeds much faster than what I’m seeing within the app.

Could you let me know if there’s a reason for this discrepancy? Does Launchbox throttle transfer speeds, or are there settings I can adjust to improve performance?

We have some changes coming that should increase speed of downloads which basically changes the buffer size of the download. It does improve speeds at least internally.

However, just as a general rule of thumb for people reading this, it's still limited to the entire trace between the device you are using and where your games are stored. Therefore, if your handheld has the capability of doing Wifi 5 speeds, and your router is Wifi 6e, then you'll get Wifi 5 speeds. Your speed is as fast as your slowest bottleneck. Then you factor in signal strength, and the remaining trace between your wifi router and your server/computer, and you get a better picture of what your actual speeds might be. Then it'll be more about the hardware itself, storage also have max speeds that sometime are slower than network speeds these days.

We can also understand that some native apps can achieve greater speeds than an app like LaunchBox which doesn't have the same toolset as something like a native app.

Look out for the next beta and see if it helps your situation.

January 13

24 minutes ago, Drybonz said:

As I was saying, it's the default theme, but at least one other person mentioned, above, having this problem. Maybe they can say what theme they are using as well.

I'm trying to figure out any reliable way to reproduce this, but up until this point nobody internally can, so not sure what internal or external factors could be causing this.

If you can zip up your data folder and send it to me in a PM, that could help narrow things down.

January 13

2 hours ago, Rlad said:

Are these good examples?

Poster

Square

Icon

They look good to me.

great game too.

January 13

On 1/10/2025 at 5:41 PM, Drybonz said:

Not sure if this is a beta only issue, but this is the first time I have seen it. It has actually happened several times recently...

Everything in the game details will disappear. It is just a blank panel. Seems to usually happen after LB has been open for a while. Have to restart to get it back to normal. This is with the default theme.

This is the first time I'm hearing mention of this. Which theme are you using? Could very much be theme dependent, or a specific option dependent that's only used in specific themes.

On 1/11/2025 at 5:43 PM, UnnUndrgrnd4114 said:

Hey everyone. Granted this video's a few years old, I got the Kinhank 12 TB Hard Drive and attempted to put Launchbox on it as it didn't come with it for whatever reason, and it gives an error message: "This app can't run on your PC" (I did download 13.18) whenever I try to run it from the hard drive. It launches fine from the computer itself. Any help would be appreciated. Thank you

I would open a separate post for this, or this kind of relates to your scenario, so you may find some answers here too:

January 13

On 1/12/2025 at 8:58 AM, Sagien said:

Regarding guidelines, should the game's logo on the Poster and on the Square have the same size or should the Square's logo be bigger than the Poster's to account for a bigger image?

Poster and Square images are part of the Box - Front image group. If a game has an official version of either size available, it can come into those image types. If not, it can be used as the best recreation of the original artwork in this form factor. The goal being that in the future, this could be an option inside of LaunchBox/Big Box to display box images that are uniform across platforms, if users prefer.

January 13

14 hours ago, marph said:

Thanks @faeran for considering a more streamlined integration of the (great!) Game Discovery Center (GDC).

Basically I want to present a logical, hierarchical, self explaining menu to the user, with a simple, uniform design. I figured out that I have to set the startup view within BigBox to “Platform categories” to start at the playlist root from LaunchBox (Why isn’t it called “Root view”?). Currently I have the following playlist hierarchy or menu structure respectively:

Arcade

Computers

Consoles

Handhelds

Playlists

2-Player-Games

4-Payer-Games

Genres

Horror

Platformer

Puzzle

Racing

Pinball

…

Favorites

Favorite Game Franchises

Pokemon

Resident Evil

Wipeout

...

Star Rating

Star Rating 4+

Star Rating 4.5+

…

To Play

…

I use the theme “Pulse” with the following View settings:

PlatformsListView: Platform Wheel 2

GamesListView: Horizontal Wheel 1

To get a nice looking main menu I added clear logos to the playlist categories which did not receive one by the theme (see screenshot).

As mentioned in my last post, I don’t like the main menu of BigBox, because it mixes the available views (or are they called “root filter lists”?) together with other unrelated stuff like «About», «Options», «Shut Down» and so on. It would make much more sense if these root filter lists were placed into a submenu or were a different menu altogether.

Anyways. That’s a different topic. The reason I mention this, is because I think that the user should not have to access this rather confusing menu nor should he have to use a special hotkey to get to the GDC.

Now what could be the solution? I see 2 options:

Option 1: As mentioned by @Frooglemcdoo I could set the GDC as my startup view, if my whole playlist structure was accessible from within the GDC.

Option 2: I could add another playlist category to the playlist root called “Game Discovery Center” if it was programmable to act as a link to the GDC.

Logically option 1 would be cleaner, because as @Frooglemcdoo mentioned, the main purpose of GDC seems to be as the entry point to BigBox. The problem here though is, that the design of the GDC is totally different to the theme which I am using right now. So this would be totally confusing to the user. Another downside of this option is, that there seem to be no options to customize which subsections should be displayed in the GDC.

For that reason I prefer option 2 at the moment as a temporary solution until the theme devs have incorporated the GDC in their themes and the GDC is more customizable to the user.

What do you think of my ideas?

Yeah, I can understand both options.

The only reason I bring up the way that Big Box's hierarchy is set up is because usually users misunderstand how it's technically laid out behind-the-scenes, so no matter what we choose to do, it's sort of like a re-invisioning of how Big Box technically operates, or something that adds some kind of redundancy option to it to appease the way users might be utilizing a specific section.

The main reason for the Game Discovery Center to exist was actually to add a new section, separate from a user's Platform, or Platform Categories section, and then add it as an option for users if they prefer to use it as their startup view. At the time it was hard to really know how people would react to it, since nothing like it existed before in the application, but since technically the system view is the link between all other sections, it made sense to add it there as a starting point. Since this view never existed before, no current theme would have a "theme specific" version of it, which is also something we had to consider during development.

I do also like the idea of re-organizing the system view as well. Making it more clear which options are "sections", which ones are more options/management areas, and the like. I could see that also helping out.

We will consider all of this as we move forward and see what we can come up with.

January 9

4 hours ago, St3althShock said:

Your device specs

Samsung A52s

6GB of Memory

Snapdragon 778g

Adreno 642L

The version of Android and API version

Android 15, not sure about API

Description of the issue

Images not always loading after highlighting new game

Can it be reliably reproduced on your end?

Yes, I've uploaded a video to show this

Reproduction steps

Selecting any new game has a chance to not correctly load the media for that game.

The crash when rotating my device seems to be fixed in the beta update. Thanks

Thanks for the report.

The video is a bit unclear, but is it that screenshots didn't load into the background of the list for the double dragons, or was it something else?

If it was, can you edit the game's media and make sure one has downloaded for it?

January 9

10 hours ago, JAKAMY said:

Thank for the swift reply, I recorded NeoGeo import from SD, mam2003plus from SD, mam2003plus import without Mame data from sd. I also tried moving the LaunchBox folder to internal storage but it crashes all the same.
I started using LB on android from 1.16, I also own the pc version, I'll try the export to Android if this is a pocket 5 only issue 👍
NB: I reencoded the screen recordings to AV1 to save space for the upload
Cheers

Debug 2025-01-08 08-28-44 PM.log 17.75 kB · 0 downloads Debug 2025-01-08 08-27-01 PM.log 15.29 kB · 0 downloads Debug 2025-01-08 08-24-08 PM.log 3.39 kB · 0 downloads Debug 2025-01-08 08-22-37 PM.log 104.58 kB · 0 downloads

Thanks for that. While it wasn't happening on our devices, we were able to use your logs to figure out why it was happening with your specific dataset and fix it. We'll push this in the next beta.

Not related to the crashing, but in the first MAME2003 video - You checked the option "This is a full MAME set". You shouldn't do this for a MAME 2003 set, or there will be games (and version of games) that get imported that don't actually exist in your set.

7 hours ago, JAKAMY said:

I tried the export from LB PC for mame 263 merged no CHD. Launching the games landed to a black screen after a side load window. I made sure that the romset works in retroarch by manually importing there with the dat file and setting the sample folder for mame in system. yet they run from retroach playlist but still not from LB. I found then 2000+/3000+ <ApplicationPath> roms in the data xml to use their pc location instead of the games arcade folder on the sd card. I replaced the paths with the local one and now they do run now great 👍
I will test again the import locally when the next beta is up.
For now as a summary of what doesn't work on my pocket device:

any arcade imports beside naomi

Video streaming

display of platform videos

SMB download speed inside LB is very slow. (same roms using a file explorer from the nas to sd card downloads at 80MB/s and finish fast while in LB (no extract) it takes 5-10 times longer if not more.

Cheers

The export to Android for MAME isn't the best thing to use for a number of reasons, but the main one being that unless you have a full non-merged set, you'd end up with paths to files that don't actually exist. On Windows this isn't a problem, MAME can fill in the gaps, but on Android, you'll end up trying to send a file to the emulator that doesn't exist, causing a black screen. Black screen can also indicate missing core, as in the core LaunchBox thinks RetroArch has isn't the one RetroArch actually has installed. I'm guessing you found yourself in the former.

Thanks for your list. Just to give context to it, the only one that's a global issue is the video streaming which was broken whem Google made some security changes. We've searched for solutions to their new security measures, but have yet to find a suitable one, so if we can't, we may disable it temporarily for this update until we find one.

We are also exploring possibilities of increasing speeds of the ROM downloads, but no promises there.

5 hours ago, Xyb0t said:

Yes, they are primarily sourced from EmuMovies, and a handful from ScreenScraper.

Also the videos work perfectly for me if i install version 1.15 - that is a bummer. This might be on my end then, but i tried everything, messed with every setting, but no cigar. The 1.15 version works with just the default settings. As soon as i upgrade to 1.16 (and also the new beta) the issue arises.

Could be device specific, but not really sure at this point. The only thing we know at the moment is that it's not happening globally, which makes it a tougher thing to track down. Pretty sure a few people on the team have the same device as you do, I'll get them to test on it and that will give us a few more answers anyway.

January 9

On 12/30/2024 at 12:43 PM, WeldXMachina said:

Finally setting up BigBox and absolutely loving the Retrotastic theme. Am I not seeing the option to load images in the background "screen" of the game select wheel (when there is no video in the appropriate folder) or is that something that will require some custom tinkering?

Essentially what I *want* is to have video snaps for arcade and modern consoles but my retro console platforms I just want the music and some art to be displayed on the "TV screen" behind the wheel.

Nice. Glad you are liking the RetroTastic theme. I made it such a long time ago, I forget how I did it.

Your assumption is right that it would probably require some theme tinkering.

Here's a slightly altered Vertical Wheel 1 view you can try out. It should basically fall back to a screenshot image if a video doesn't exist.

WheelGamesView.xaml

Replace the one in the following folder:

\\LaunchBox\Themes\Retrotastic\Views\

January 9

If you've checked your spam folders and you don't see it, use the Contact Us form at the bottom of this page to send support a message. They can toss you a link.

January 9

If you know where your LaunchBox folder is on your device, can you use a files app to rename it temporarily, then open LaunchBox.

If done right, it will act as a brand new install. Let us know if you are seeing the same thing or not.

January 8

On 12/24/2024 at 2:49 PM, brunosardine said:

Hi @faeran Not sure if this is a theme or launchbox question. I can toggle on/off the 3d box sliding in from the right side (see image). This particular 3d box is not the static image, but the feature where you can rotate and spin the box around. Is there a way to show either a gameplay screenshot or video instead of the 3d spinny box? I've been messing around with media priorities to no avail. Perhaps a change in GameDetailsView I could make?

thanks!

That's baked into the theme itself, so there's no user option that could change switching one element out with another there.

However, you could create a copy of the theme and change that part of the code to suit your particular needs.

January 8

11 hours ago, Xyb0t said:

Thanks for the update 👍 Unfortunately i still experience the issue with tiny videos, described in more detail (with screenshots) here https://forums.launchbox-app.com/topic/88851-tiny-videos-unified-lite/

Device specs:
* Odin 2 Pro
* CPU: Snapdragon 8 gen 2
* GPU: Adreno 740
* RAM: 12GB LPDDR5x

Android and API:
* Android 13

Description of the issue:
* https://forums.launchbox-app.com/topic/88851-tiny-videos-unified-lite/

Can it be reliably reproduced on your end?
* Yes it is quite persistent
* I downgraded to 1.15 and the issue disappeared. All videos are normal size
* I did a factory reset on my Odin 2 Pro and re-installed 1.16 again, and the issue reappeared. All videos are small most of the time

Reproduction steps:
1 - Export games from LaunchBox (with videos)
2 - Import games to LaunchBox Android
3 - Select the gamelist view "Wheel with two-column details"
4 - Now when you open the gamelist, the video is most often tiny, about half size. Rarely the videos will show in normal size, but if it does you can just go back to platform view and then enter a gamelist, and the videos are all small again
5 - Also confirm that videos do not loop any more

Thanks for the report. Did a few round of tests but was unable to reproduce the tiny video issue. Were the video files sourced from EmuMovies or somewhere else?

As far as looping videos, we were able to reproduce and it should be fixed in beta 2.

January 8

16 hours ago, JAKAMY said:

Thanks for the update 😃

One remaining bug from 1.16 is the crash when trying to import any arcade, cps123 and neogeo Roms. It starts and crash without notification each time.

Tried these 5 mixing in all import option with and without make data using mame 263(Merged), mame plus 2003 set with and without chd, noeogeon only set all from NAS(SMB2+MTU/SMB3) or local sd card 80MB/s, 1TB.

Cheers

Your device specs:

Retroid pocket 5

8GB LPDDR5

128UFS internal storage

CPU sm8250

GPU Adreno 650

The version of Android and API version:

Version 13, Api 33

Description of the issue:
Mid import crash for any Arcade set preset with any custom import setting.

Can it be reliably reproduced on your end?
Tried many times with 3 different rom set, all fail.

Reproduction steps:
Import arcade roms set from NAS or Local SD card.
Added crash log and import video for neoegeo roms

Debug 2025-01-07 11-27-32 PM.log 10.62 kB · 0 downloads

Thanks for the report. Arcade over NAS is actually not yet supported. We added a prompt to beta 1 to stop users from accidentally importing them.

Local MAME imports are supported, but we are unable to reproduce any crashes with those imports. If you have time, can you upload another video showing the process from the home screen and going through the process of trying to import a MAME set on your local SD card.

January 8

On 1/3/2025 at 3:28 PM, Retrogamer4423 said:

I tried it and it's really amazing man. When I updated the old version to 13.18, I saw that launchbox opens very fast. However, when I downloaded and installed 13.8, there is a delay of about 15 seconds with m2 ssd.

I tried it and it's really amazing man. When I updated the old version to 13.18, I saw that launchbox opens very fast. However, when I downloaded and installed 13.8, there is a delay of about 15 seconds with m2 ssd.

It's feature dependent.

Here's a good article to read if you haven't yet, which explain why you are seeing what you are seeing, and what you can do about it:

January 8

On 12/26/2024 at 9:08 AM, St3althShock said:

Back to 1.15 till the bugs are fixed, .15 seems a bit smoother for my ageing A52s

If you can, check out 1.17 beta 1 and see if you are seeing the same thing on your device.

You can post any feedback in its beta thread:

January 8

Has anyone with the error tried to do this yet?

January 7

The Beta Thread for LaunchBox for Android 1.17 has been opened and can be found here:

January 7

On 1/4/2025 at 2:55 PM, Xyb0t said:

Hi guys, I think i found a bug in the new version. I am sorry if this is not the right place to report this.

It concerns videos in version 1.16 which does not scale correctly. I messed with it most of today and gave up, so i downgraded to version 1.15 and the issue disappeared immediately.

Please see this thread for some more context and screenshot examples:

Thanks, we'll look into this and see if it's something we can recreate on our side and see what we can do about it.

January 7

Hi Everyone,

1.17 Beta 1 is out with a bunch of fixes that solve a number of issues that cropped up due to the big MAUI framework change. This will be a short development cycle to shore up as many bugs as we can. Once this update goes live we will be pivoting to new feature releases.

For users that were having issues on 1.16, it would be great to hear from you if this beta solves the problems you were facing.

Thanks to all who help test these beta versions. Don't forget to include the following information in your feedback to help us out with tracking down with any issues you may face with these betas:

Your device specs
The version of Android and API version
Description of the issue
Can it be reliably reproduced on your end?
Reproduction steps

You can opt into the beta within LaunchBox for Android by going into Option and turning on the Update to Beta Releases option. If a beta release is available, you will get prompted each time the app opens up.

Full Changelog: https://www.launchbox-app.com/android-about/change-log

Beta 1:

Filter Views that utilize background videos should better identify the correct video to play
Fixed an issue where LaunchBox would freeze when launching games if notifications were blocked
The app no longer crashes if the user exits the network share username/password input dialog
Manually changing media from the LaunchBox Games Database for a single game should better reflect the new image selected
Fixed a rare crash that could occur when attempting to play a game
Addressed a crash that could occur when attempting to import games from a network
Fixed an uncommon crash that may occur when users navigate between the hamburger menu items
Fixed a crash that could occur on devices whose API is 27 or lower
Fixed a rare crash that could stop users from proceeding with the import process
Fixed several minor crashes reported by our reporting system

Beta 2:

Downloading bin/cue games over a network share now includes both downloading and deleting all associated files
Introduced a new "Download Game" option for games imported from a network share, enabling users to download games independently of playing them
Added the ability to delete the local version of a game while maintaining its availability over the network
Increased network buffer size to potentially improve download speeds for game files from network shares
The download pop-up for network share files is now more informative
Default Nintendo 64 core for RetroArch has been updated due to the previous one being retired
Resolved an issue where downloading EmuMovies videos could cause the application to crash
Resolved an issue where importing files over a network share did not consistently handle bin/cue files as intended
Addressed a problem where the selected platform or game information did not always update accurately when using touch controls
Resolved a crash that could occur while navigating within a Boxes Grid view
Addressed a crash that might happen during the import of MAME files
Fixed a crash that could occur when changing screen orientation while on a Filters View
Resolved a rare crash that could occur when long-pressing on specific elements
Corrected an issue where the background video element behaved incorrectly when a custom view file lacked a foreground video element
Fixed an issue that prevented Platform and Game videos from looping correctly

Profiles

Forums

Articles

Downloads

Gallery

Blogs

Posts posted by faeran