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.

Note that I tried the Model 3 Supermodel emulator with the same controller and everything works correctly. Different program, but it shows the inputs work.

I’ve seen this problem posted in a few places sporadically but never found a solution. I have a negcon PS1 driving controller I have attached to a raphnet PS1 adapter to connect to the PC. It shows distinct axis’s in the USB Controllers screen in Windows. So like steering is the X analog axis, acceleration is the Z axis and brake is like X-Rotation. I set this up in the model 2 config with the accelerator and brakes set to inverted. On the Daytona main menu selection screen, the accelerator accepts the current input (like an ok button) which matches the arcade behavior. But in game the accelerator is behaving as the brake and the brake as the accelerator. They are distinct axises so this is weird. The adapter I used is a direct input device so on my second attempt I used X360ce and mapped the steering to the first joy x-axis, accelerator to y-axis and brake to the second joy Y axis. I turn Xinput on in the emulator ini file and run but the same thing occurs. The controls are opposite in the game but on the main screen they are correct. Any Model 2 experts out there? I know the executable is getting a little long in the tooth. Thanks! Edit: To make it even simpler, I assigned accel to the left trigger and brake to the right trigger in X360ce. Same issue.

When you rerun the importer, it will delete the old MAME information in LaunchBox?

I have an older MAME romset scanned into LaunchBox. I just got the latest one and want to redo the special MAME scan that LaunchBox provides. How do I delete the old data first so I get the new set into LaunchBox cleanly?

Oh my. After all that it seems to be my mistake. The two games I tried, and played in the arcade in my younger days, don’t have moves with the B button plus joystick direction. It’s just the B button alone. To make sure, I tried another game which I know does have B button plus joystick moves and it works. What a memory lapse! Thanks for the advice and sorry to waste your time.

I know this isn’t the optimal forum for this question but I find the questions and answers are handled briskly here so I thought to give it a try. I am a lifetime license Launchbox owner. I have a new build with the latest windows 10 version on a handheld PC device known as the GPD Win Max. It is a fairly powerful PC. I know how to set controls with MAME and the left analog joystick pressed with the A button works fine. However when I press the left analog with the B button, it’s as if only the B button is pressed, ignoring the joystick direction. When I tried to use the direction control pad instead of the analog joystick, if I press any other button but A, the direction pad is also ignored. I tried with .198 ROMs of wwfsstar and wwfwfest along with .198 MAME. I also tried .223 mame64ui and retroarch with the same results. Note I didn’t use the latest ROMs with .223 since for those 2 games, .198 roms still seem to be compatible. I thought the problem was with the built in xbox 360 compatible controller on the handheld PC but I tried with an XBox Elite controller over bluetooth to the same result. I tested some Steam Games and pcsx2 and those work fine. I never had this problem on previous iterations of the handheld PC which I have owned. Note the windows 10 version was older on those. Would upgrading to .223 ROMs do anything? Obviously there is an incompatibility somewhere. Or can soneone point me to a mame forum that might be more appropriate? I tried mame reddit but there weren’t many responses.

Thanks! Pressing the text button was sufficient. I thought I was mistaken when I saw the titles were missing after I upgraded.

I recently upgraded Launchbox and the view I usually used is by screenshots. It used to also have the game title in text under the image even if you don’t click on the image. Is there anyway to get this functionality back? So all the images should have the game title under them. Thanks!

How well does n64 run on the Win 1? I hadn’t thought about running it on my Win 2 since I was planning to get a N64 controller and adapter and using my main PC. I’ll try the desktop mode setup on the Win 2 as you directed.

A bit off topic but I saw the retro-link controller today in a store. It looked a bit flimsy to me. I think it was $15 if I saw the right brand. I think I’m going to go with an original controller and an adapter if I can get the correct parts. Edit: I think what I saw was the N64 version.