Jump to content
LaunchBox Community Forums

Recommended Posts

Posted

Beta 4 is out now with the following changes:

  • Scoped Storage framework support has been integrated into all custom emulators and several known emulators, including DraStic, Redream, DroidArcadia. This enables enhanced folder and file permission settings, addressing requirements for certain emulators
  • The following platforms have been added: BBC Microcomputer System, Emerson Arcadia 2001, Atari Jaguar CD, Epoch Super Vassette Vision, Fujitsu FM Towns Marty, Interton VC 4000, Mega Duck, Nokia N-Gage, Oric Atmos, Philips Videopac+, PICO-8, ScummVM, Sega Pico, Sony Playstation Vita, Nintendo 64DD, Sony Playstation 3, Microsoft Xbox
  • The following Emulators have been added: Azahar, Citron, DroidArcadia,Infinity P8 Player
  • The following Cores have been added to RetroArch: Dirk Simple
  • Fixed the following Emulators: DuckStation, DraStic
  • Touchscreen controls are now fully functional on the "Browse for New Games Database Image" page

 

There was some major rework done to facilitate the scoped storage change, but the benefits there will be felt in this update and future updates. Scoped storage support will help us launch into emulators that don't specifically have frontend support built into them, but are targeting Android 11+ OS. The way we've implemented this is that Scoped Storage is not required for any emulator that has frontend support (like DraStic and Redream). For the ones that don't, or for the ones that may benefit from it, you may get a one-time prompt during a game launch to provide access to your game folder. Once set, you shouldn't have to set it again. You can also optionally set it under Emulator Settings for all custom emulators, and for a select few emulators.

The main thing to test here is to make sure you can still launch your games for all your platforms. We want to make sure we didn't accidentally do something we shouldn't have.

Thanks for helping with these betas!

  • Like 1
  • Thanks 1
Posted
3 hours ago, mturner7415 said:

Strange issue with application not starting when touching screen or pressing launch button.  Started in B2 and persists in B3.  Reboots will sometimes, but not always, fix the problem.  Other applications functioning normally.  Anyone else having this problem?

Sometimes app will start properly after a system restart but not always.  Tried Force Quit a couple times as it appears to be running (but no window available when trying to switch to it) and then nothing.

  • System: Retroid Pocket Pro 4
  • OS: Android 13
  • LB: v.1.18 - B3

Hi, could you record a short video showing your problem? Also, can you make sure that you don't have a notification that some media is playing in the notification window?

Posted
13 minutes ago, ChunkyLoverMark said:

I'm not seeing Nintendo 64DD in the list of platforms in beta 4: 

 

Screenshot_20250409-185643.png

Yeah, sorry for that mistake...
We added it to the app but didn't include it in the Platforms list.
It will be fixed in the next beta (which I suppose will be this or the following week)

  • Like 2
Posted
21 hours ago, x4ml said:

Hi, could you record a short video showing your problem? Also, can you make sure that you don't have a notification that some media is playing in the notification window?

Tried it this morning and worked like a charm.  Just upgraded to B4, will let you know if it happens again.

  • Like 1
Posted

Is there any expected additional information coming on how to configure existing metadata for Scoped Storage support on emulators that need it?

Posted
On 4/13/2025 at 7:10 PM, cult said:

Is there any expected additional information coming on how to configure existing metadata for Scoped Storage support on emulators that need it?

Hello!

The app will request Scoped Storage access automatically if the emulator you selected requires Scoped Storage and the Android API version equals or exceeds 30 (Android 11).

Emulators that require Scoped Storage access:
DraStic
Redream
DroidArcadia

On the Game Metadata Page, you can clear the "Startup Uri File (Scoped Storage)" value, and it will be automatically filled in the next time you click the "Play" button. You can't set this value by yourself.

Let me know if you need any other information.

Posted
On 3/25/2025 at 4:11 AM, Eyebrows Cat said:

Lenovo Legion Tab Y700 Gen2 (2023)

ZUI 16.0.622

I checked further. No matter how many times I touch the image, there is no reaction. However, the "←" key to go back does react.
Thank you in advance.

The bug we reported previously has been properly fixed in the latest beta version.
Thanks for updating.

  • Like 2
Posted
31 minutes ago, AndrewSpec said:

I can confirm that Redream works fine. But Duckstation can't load any game with Failed to open CD image error.

Can you be more specific about a few things:

  • Version of Duckstation
  • Type of files you are trying to launch
  • The actual file under the game's metadata that is being used to launch the game
  • Version of Android you are on, and API level (if you can find it)
  • Device that you have

 

Posted
Just now, faeran said:

Can you be more specific about a few things:

  • Version of Duckstation
  • Type of files you are trying to launch
  • The actual file under the game's metadata that is being used to launch the game
  • Version of Android you are on, and API level (if you can find it)
  • Device that you have

 

  • version 0.1-8889 - latest beta from 09.04.2025 (downloaded from duskstation.org/android)
  • *.cue
  • /storage/emulated/0/LaunchBox/Games/psx/Carmageddon/Carmageddon.cue
  • Android 15, API level 35
  • Samsung Galaxy S24 Ultra

Duckstation has Scoped Storage Permission inside LauchBox but when I edit any game metadata the Startup Uri Flie (Scoped Storage) is set to none. As I understand it should be set automatically like for Redream. I've tried to do a clean import for PSX but still every game has that property set to None.

  • 2 weeks later...
Posted

Beta 5 is out with the following:

  • Introduced an option to clear Scoped Storage permissions on the GameEmulator and PlatformsEmulators settings pages
  • Added Scoped Storage blacklist for emulators incompatible with Scoped Storage access - Currently has Flycast on it
  • Implemented default platform configurations for various libretro cores:
    • mupen64plus_next_gles3_android for Nintendo 64DD
      picodrive_android for Sega Pico
      o2em_android for Philips Videopac Plus
      sameduck_android for Mega Duck
      b2_android for BBC Microcomputer System
      virtualjaguar_android for Atari Jaguar CD
      mamemess_android for Interton VC 4000
      scummvm_android for ScummVM

  • Resolved a crash when launching games in the AetherSX2 emulator
  • Addressed a rare crash during game imports
  • Fixed an occasional crash while displaying images
  • Corrected a rare crash when clearing the platform image view

Other than a few smaller things, we are at the stage where this represents the majority of version 1.18. Any testing that can be done on emulators and emulator launching would be much appreciated, as the entire system got touched in some way or another to accommodate for all the changes for this release.

  • Like 2
Posted
On 4/15/2025 at 8:06 PM, AndrewSpec said:
  • version 0.1-8889 - latest beta from 09.04.2025 (downloaded from duskstation.org/android)
  • *.cue
  • /storage/emulated/0/LaunchBox/Games/psx/Carmageddon/Carmageddon.cue
  • Android 15, API level 35
  • Samsung Galaxy S24 Ultra

Duckstation has Scoped Storage Permission inside LauchBox but when I edit any game metadata the Startup Uri Flie (Scoped Storage) is set to none. As I understand it should be set automatically like for Redream. I've tried to do a clean import for PSX but still every game has that property set to None.

If you have time, see if beta 5 helps with your situations of launching Duckstation. You should now have the option of setting or clearing Scoped Storage permissions in the emulator settings. You can check both scenarios and see if either work for you.

Our testing showed that for all of our devices Duckstation did not need scoped storage, but it might be different on your device.

Posted
On 4/24/2025 at 8:31 AM, faeran said:

If you have time, see if beta 5 helps with your situations of launching Duckstation. You should now have the option of setting or clearing Scoped Storage permissions in the emulator settings. You can check both scenarios and see if either work for you.

Our testing showed that for all of our devices Duckstation did not need scoped storage, but it might be different on your device.

People have been complaining for years that duckstation needed scoped storage support in Launchbox.  So there is something amiss if your setups don’t require it.  Maybe a newer version of duckstation is needed to be tried?  Somehow it works without it with an old version maybe.  I have like the other user, have cue files on a microsd card and get permission errors trying to load a game.  Same as it always was.

Posted
28 minutes ago, Avenger said:

People have been complaining for years that duckstation needed scoped storage support in Launchbox.  So there is something amiss if your setups don’t require it.  Maybe a newer version of duckstation is needed to be tried?  Somehow it works without it with an old version maybe.  I have like the other user, have cue files on a microsd card and get permission errors trying to load a game.  Same as it always was.

Seems to be the opposite to what you are saying in our findings. Newer versions no longer needed scoped storage due to a change in the app, but that change required different launching arguments. However, in saying all of that, it's a moot point. Beta 5 now allows you to choose to launch the app in either the frontend supported URIs or the scoped storage URIs for Duckstation, and based on what we've seen, the app accepts both for all of our hardware/software combos.

If you do wish to try, report back here with your findings, including all listed in the first post. 

Posted

For reference, I will write the settings that allowed me to launch Playstation games on Duchstation (0.1-8889) from Launchbox (1.18β5) in my environment. The ROMs are located on the SD card.

Device
Lenovo Legion Y700 2023

Emulator settings
Duckstation
Games Path Not Set
Unpack ROM archives OFF

When I set Scoped storage permission, all games did not launch.

The extensions specified in Launchbox are as follows.

Extensions that could be launched
.chd
.bin
.img

Extensions that could not be launched
.cue
.sub

  • Like 1
Posted
3 minutes ago, Eyebrows Cat said:

For reference, I will write the settings that allowed me to launch Playstation games on Duchstation (0.1-8889) from Launchbox (1.18β5) in my environment. The ROMs are located on the SD card.

Device
Lenovo Legion Y700 2023

Emulator settings
Duckstation
Games Path Not Set
Unpack ROM archives OFF

When I set Scoped storage permission, all games did not launch.

The extensions specified in Launchbox are as follows.

Extensions that could be launched
.chd
.bin
.img

Extensions that could not be launched
.cue
.sub

Hmm It may be that .cue files are not working when launched via launchbox.  Both myself and the other user with issues use cue files.

Posted (edited)

That seems to be the issue. When Launchbox scrapes the rom directory it picks up the .cue file name instead of the .bin one.  I changed .cue to .bin and it worked.

 

Edit: And it works without scoped storage like you stated.

Edited by Avenger
  • Like 1
Posted (edited)
On 4/24/2025 at 2:31 PM, faeran said:

If you have time, see if beta 5 helps with your situations of launching Duckstation. You should now have the option of setting or clearing Scoped Storage permissions in the emulator settings. You can check both scenarios and see if either work for you.

Our testing showed that for all of our devices Duckstation did not need scoped storage, but it might be different on your device.

I still have issues. It doesn't  matter if it's cue or bin. As you can see on my video Tekken 3 has the scoped storage path set but it's loading only to bios. If I manually run Duckstation and choose Tekken 3 it loads.

Also I checked if with the scoped storage path cleared it's working but no, it's not.

 

Edited by AndrewSpec
Posted
3 hours ago, AndrewSpec said:

I still have issues. It doesn't  matter if it's cue or bin. As you can see on my video Tekken 3 has the scoped storage path set but it's loading only to bios. If I manually run Duckstation and choose Tekken 3 it loads.

Also I checked if with the scoped storage path cleared it's working but no, it's not.

 

Will it still start if I clear the scope storage in the emulator settings like in this video? In this environment, .bin is starting up.

  • Like 1

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...