Avenger

It’s not going to be resolved unless LaunchBox implements scoped storage. All the other up to date front ends have implemented it for a long time. I don’t see how it can be avoided. It has been the android standard for years now.

Yeah I went through the trouble to contact someone at Redream like was suggested in the pop up in Launchbox and got the some info from them. It may not be what we wanted to hear but some feedback here would be appreciated.

By the way, the developer of Redream wrote a small note agreeing with the above assessment. Is there a chance Launchbox will ever work with Redream or will this be a stalemate at this point?

Concerning,Redream access from Launchbox for Android, I wrote in the redream discord and I think a moderator (but note, NOT the actual developer) answered. He is stating that Launchbox doesn’t have scoped storage support which I don’t know is correct or not. This is what he had to say with the images he provided. I hope this helps. ——- Eh .. tbh I'd say this is a launchbox issue that they're doing things the Android 10 way. They've had 4 major revisions to implement scoped storage. (Note:see first image below) This is misinformation. LaunchBox does not implement scoped storage and expects all other emulators to request access to all files on the users device? Daijisho can launch games via redream just fine on my android 14 device. Why? Because it implements scoped storage framework. (Note: see second image below) From what I remember, inolen did request all files access but google denied the request; I don't know why they are allowing it for other emulators, but really LaunchBox should consider adding scoped storage support ———

I took a chance and deleted my arcade collection in LaunchBox and reimported it and then went through the check for missining media and it went through this time. Maybe something got corrupted because the data folder was originally on the microsd card?

I am on Android 13. I just purchased a launchbox and emumovies license today. I added missing media to a N64 set with no issues. But the code is throwing a sharing exception when trying to add media to a large FB Neo rom set. I had the data directory, unknown to me, on the sd card so I moved it to internal storage but the errors continue. Here are the logs. I just purchased everything so I hope I can get it to work. Thanks. Debug 2023-11-09 05-23-18 PM.log Debug 2023-11-09 05-22-40 PM.log

Hi. If I have a large or complete set ROM library like for the N64, is there any way to force it to load and display every file? Like there can be a game rom and a 1.1 version or different region of the game and and want to see all of them in the list. Right now it parses the name to make one neat game entry. Second question. Is there no way to launch Redream from LaunchBox under Android 13? There has never been a workaround? Thanks.

I had installed LaunchBox on a Steam Deck booting Windows 11 a while ago. Is there a straight forward manner to get the built in game controller working? I remember at the time I set it up, it was convoluted. What are the current steps to configure it? Thanks.

Yes they are snapshots and videos specifically for MAME. They are named the same as the corresponding MAME ROM. I think I used them with previous versions of LaunchBox by setting the snapshot and video snapshot paths. But I guess they should go on the ssd if I can use them because I would think they would be scanned a lot.

Thank you. If I have custom snapshots and video “snapshots”, should those go on the ssd as well? I guess LaunchBox would scan them frequently to show them on the UI. Anything else I am forgetting about? Thanks!

I found a pretty old post that stated that Launchpad (and I guess other programs) won’t run good on a microsd because of the many small random read and writes. Is this still the case with modern microsd cards?I have a Sandisk 1TB microsd with class 10, etc. Thanks.

Okay, Thanks. I’ll probably move the CHD subdirectories to the single ROM folder.

The way the MAME roms are distributed, the roms are in one directory and the CHDs in another, with CHD sub-directories for each game. Before I import using the “Import MAME full set” tool, should I move the CHD subdirectories under the overall Rom directory? Or can the tool import a whole path consisting of multiple directories? From watching the tutorial video, it doesn’t look like you can select multiple directories Thanks.

After a long time, I’m setting up a new install of LaunchBox. I am a premium user. All the ROMs and CHD files are going on a microsd card. I am assuming LaunchBox will run a bit slow if I put the actual installation on a sdcard as well so I think I am going to put it on an SSD. If my assumption is correct, what else should go on the SSD? I have a MAME Extras directory with some subdirectories like screen snapshots and a directory with video snapshots. Should these both go on the SSD or only the images? Anything else that I am missing that should go on the SSD? Of course I would rather install everything on the microsd and have a complete portable solution but I don’t want it to run slowly. Thanks.

I deleted the controls binary file but I could try a completely fresh install. But I think I essentially did that because I later tried out a separate UI for it which I think came with the binary executable. Can you calibrate in the test menu? I thought I saw you can see which control you just moved. Thanks.