fromlostdays

Follow up information: The first thing you should know is breathe easy, it'll work either way for PS2 (not PSP fair warning). Apparently the emulator can account for both compression types because PCSX2 is awesome and this is just another reason why. However, technically, you should use createdvd on DVD titles and createcd on CD titles like JoeViking said. Theres an easy way to tell which you should use, and its by the file extension of the uncompressed rom. If its .iso = use createdvd .bin = use createcd That said, if I had already compressed my games to chd, I wouldn't worry about it. Hope it helps!

Nerco! So my ps2 games are all currently in .gz. I want to convert them to .chd. However, having just gone through this process with PSP games and learning that there is a huge difference between "createcd" and "createdvd" when compressing psp games (createcd causes the emulator to error), I'm wondering which of these options I should use for my PS2 games?

Good day! So my main launchbox build is getting up there in years. 🤣It's a massive build in terms of games, media etc. In fact, I bought a 1 terabyte M.2 drive just for launchbox and it's only got a couple hundred gigs of space left (I store my games seperately). I know a good chunk of that space is actually taken up by emulators. Everything from storing bezels, DLC files, necessary (and unnecessary emulator files). Anyway I'm getting to the point where I'm wanting to go in and clean out as many unnecessary files as I can. So, just regarding launchbox's program files, are there any I can trim? Caches? Like I said, this install is old (from back when launchbox just did DOS and updated over the years) and it's been accumulating files the entire time. For instance, just my launchbox/backups folder is almost 8 gigs. So, thought it would be interesting to figure out how to bring youth back to older installs by trimming some (if any) bloat? Any suggestions? EDIT: I'm aware of the tools launchbox has to clean up media, I'm talking strictly program files. Thanks!

So when launchbox passes the rom to mame to launch, mame is looking at the roms folder as set in the mame config. In my case that folder is on an external drive, and the config reflects that, but it's getting confused cause in that folder is a bunch of individual folders, and the command line is addressing that across the board? Nice. Oh, you got jokes. I never use retroarch for arcade either, it's just going to bother me that it doesn't work, but now, I'm maining retroarch playa. I'll let you know how to get it working. 💪 EDIT: Switching from the mame core to the fbneo core in RA fixed it, no additional steps required. Can't say why, but the mame core just doesn't seem to like trying to run non merged roms at the moment.

I've been on this kick to set all mame roms in individual folders named after the game, don't ask why its an obsessive compulsive thing. I'll worry about the finer details of updating the set later since I only update mame every few years. Anyway... I'm using the most recent non merged set and ran into this same problem which is how I wound up here. This worked great by the way, and thank you, but I was wondering if you could explain WHY this works a little more conceptually to me? Is it that whatever launchbox is telling mame on launch has mame defaulting to looking for the files in other zips? What's going on here? Lastly, is there a way to make the games work in Retroarch the same way, as it is having the same problem and I want to keep as many emulators working as possible. Thanks!

Currently at 74,000, but still less than 8 TBs of space. Handpicked for bigger disk systems, lots of 1g1r sets, all hacks, translated, etc. versions imported as additional apps to the main game, but with a lot of the mame software list imported. Collection very much has duplicate games across systems. A few of the older PC systems imported I haven't been able to get working. So, I can't say the entire collection works, but just to give an idea. I see people talking about 16 plus terabytes and I'm assuming they are doing full lists for PS2 and up.

Another option is to get a wrapper program. Steam and last time I checked a while ago DS4Windows both basically turn a PS controller into an Xbox controller (native xinput), which is better supported in general than what I'm guessing is Dinput for Playstation controllers.

To simplify this, think of Launchbox as "path to emulator, path to rom". It's just the front end. The way I use Launchbox is to have it memorize the "path to rom" to my individual rom folders. Emulators typically (retroarch aside) don't try to act like a front end, and when launching a game from within the emulator you often have to manually put in the path with some exceptions. That said, the way I have everything setup requires 2 elements: The organization of roms etc. into folders (for which I used a small program called File2Folders and a program called Bulk Rename Utility to accomplish) The saving of screenshots/save files into content directory (which is emulator specific) I'm being careful with my words because I set all of this up a long time ago and things may have changed, and also because there's a thousand different emulators out there, but lets take Dolphin for example. Dolphin saves gamecube saves into a virtual "memory card". You can change the default location of that memory card, but as far as I know, there's no way to set it to save an individual per game memory card into content directory. In other words the second element of my setup doesn't work for all systems. It will, however, work for all systems for which you use Retroarch. Retroarch lets you control where saves / screenshots etc. are dumped, and you can tell it to dump them in the content directory. Some emulators naturally dump this stuff into content directory, and some don't. The content directory for me isn't "Nintendo Entertainment System" continuing the above example. The content directory is "Super Mario 2" folder in the Nintendo Entertainment System folder, so everything works. I'm not exactly sure I'm addressing your question, so let me know if I'm not understanding you, and if I have, hope this helps. I think what you're ultimately asking is do I set this up through launchbox, and the answer is no. Beyond importing the roms, the screenshot and save file paths have to be set in each emulator.

This is probably more complicated than what I'm about to say considering the color change on the controller, but sometimes when an emulator closes it looks like bigbox is in the foreground, but its not. In other words, try to replicate this issue, and instead of restarting your controller, just click bigbox once with your mouse (to bring it to the foreground), then try the controller. This isn't a solution, but it'll help determine what the actual problem is, and what it isn't.

I keep my roms in individual subfolders as well. I'm not sure about launching through Mesen directly, but this is one of the many places Launchbox shines. In the launchbox rom import, go to "Add Files" navigate to the folder that contains all the individual game folders, and just do a search up top for the file extension, in other words for nintendo search ".nes", this will find all of your games in their subfolders, then select all the games (control + A), and then import like normal. This will import every game in their individual folder into launchbox. So with the below example, on import navigate to "nintendo entertainment system" Then just search for ".nes", select all and import: /nintendo entertainment system/super mario 2/super mario 2 (USA).nes If that's what you're asking about. Then just set mesen as your emulator. You could potentially do this with nes game folders nested in multiple different locations, if you wanted, but I don't see the function. The reason I personally use individual game subfolders, in case anyone asks, is that I set all my emulators to save savefiles and states into content directory, as well as screenshots etc. I also keep multiple versions (regionals, hacks, translations) in the same folder with the game, and I take the tags off the folder name. So the folder Nintendo Entertainment System/Super Mario 2/ Might have inside it: Super Mario 2 (USA).nes Super Mario 2 (Japan).nes Super Mario 2 (USA).sfc Super Mario 2.state Super Mario 2 (Hack).nes etc. Just personal preference.

I'm glad it works. It's been a while and sometimes little things change.

Actually, it turns out I already have a script for Demul in launchbox (It's been a long time since I messed with it). Anyway, in case I wasn't clear, go to Emulators/Demul in launchbox settings, then in the box that pops up go to the Running Script tab and put this: ; This section makes the emulator go fullscreen and closes Demul when pressing Escape Sleep, 9500 Send {Alt Down}{Enter}{Enter Up}{Alt Up} $Esc:: { Send !{F4} }

Rather than a command line parameter, you can use launchbox to automatically launch an AHK script. The first one in this thread is what you're looking for, just change the keys to Alt and Enter:

I was getting the same behavior, and same numbered errors. Changing the LB default theme to the old theme seems to have fixed it. To be clear, it's not happening on my main launchbox build. Its only happening on a smaller build I have for hand picked games. The only differences between the two are: The smaller build obviously has less games imported I've imported games more recently to the smaller build The big build is on an M.2 drive (not C Drive); the smaller on a SSD (Also not C Drive) Lastly, the big build refers to games on a different hard drive (all my games stored seperate), for the smaller build I let launchbox import the the games and store them in LB/Games. Thats all I can think of. Other than that, same versions of LB, and both were using the newest LB theme until I changed it to the older one on the smaller build. Definitely a puzzle. The first time it happened to me was during an import. And after that, it would usually happen if I tried to scroll games in LB, but not all the time, and it would happen scrolling random systems.

I would say there is absolutely a purpose in maintaining a database for the Othello, that said, all of the information you just shared should be in it. If im understanding right, it literally played SG games? If it had no exclusives of its own then I don't think we need duplicate entries of the games, though. But if it ran its own disks or carts or whatever even if the data was duplicated, it's worth preserving them distinctly imo. But that would depend on them having seperate rips.

You seem to have accidentally made it even more complicated than it already is haha. So, this all depends on how you save the config. You CAN save it per game. You can also save it per core, or per content directory, or per Retroarch as a whole. No. If you save your changes per game, no other game will be affected. If you save it per core, every game that uses that core will be affected, and if you save it per Retroarch, everything (every core) will be affected. Get the words "platform/engine" out of your mind, and think of cores. A core in retroarch is basically just an emulator built in a form that retroarch can use. So if you save any kind of config, inputs or otherwise, per core, then anything that uses that core will be affected. You can't even use the word "system" because some cores emulate multiple systems, and if you save a core config for that core it will affect all the systems that core emulates. So for example the "genesis plus gx" core emulates Sega Genesis, Sega Game Gear, Sega CD etc. So if you save settings "per core" on a Sega Genesis game, those settings will transfer over to Sega Game Gear, Sega CD etc. if you use the same core for multiple systems. Yes, if you save the binding per game, only the game that's open when you do it will be affected. If you are wanting individual bindings for specific games, my advice is to just edit the bindings on each game and save per game. Until you know what you're doing, you should stay away from saving anything per core and certainly saving anything to the Retroarch.cfg.

Number 1: Always start the 8bitdo controller by holding X & Start on the controller. This will start it in xinput mode and should fix your problem unless you did something funny to the input binding settings in RA. Number 2: Launchbox does download Retroarch for you now automatically, but are they not fundamentally linked. There's nothing you can do in launchbox that will affect the settings in Retroarch. It does not preconfigure controls for you. However, Retroarch has a bunch of preconfigured controllers on its own, and honestly the controller should work even not in xinput mode. That said, you should try to use xinput mode always for other reasons too. So getting in the habit of starting the controller as stated above is a good thing, regardless. Try that and see if RA doesn't recognize the controller. If it doesn't, Retroarch is a monster of emulation but the consequence of it being able to do so much is that it has tons of different configs and different layers of configs, its all very complicated. When you say you setup systems in Retroarch, do you mean that you saved settings changes in Retroarch either per config, per core, per directory or per game? Or do you just mean that you set the system up in LB? If you don't have any specific settings saved in RA that you don't want to lose, I'd say go ahead and reinstall the emulator itself. Only because if you don't know what you're doing and you're messing with input settings its going to be even more difficult if not impossible to troubleshoot the issue. Controllers are supposed to work out of the box in RA. Retroarch only saves certain settings in the retroarch.cfg and then only if you have set the setting to tell it to do that. haha. The rest of it's configs are in the "config" folder but honestly like I said it's all very complicated to type out. Better to start fresh. If you take anything away from this it should be that the controller should work just fine, try starting it in xinput mode, and there's nothing you can do in Launchbox to fix it. Any fix to the settings would have to be done in Retroarch itself. You can reinstall the emulator and start fresh without touching launchbox at all, no need to delete or readd games, just make sure the new version of Retroarch is in the same directory as the old (not at the same time haha, delete or move the old one first)

@C-Beats I can't see this being intended behavior, but the current version of launchbox automatically opens steam, if steam is closed when opening launchbox. I can't say how long this has been going on because I usually leave steam open, or if it was the result of a launchbox update or a steam update. I was scrolling the forums earlier on my phone and I saw a post about Steam taking focus when launching a steam game through Bigbox, though, and I wonder if these issues are related. If this IS intended behavior my apologies, you can delete this.

You can use this batch script to create m3us for every game in a system: Couple things: do read the directions in there as you do need a specific folder structure. I recommend using file2foldergui to move each game (set of discs) into one folder if you haven't already. Also this batch file creates m3us for every subfolder in a single directory, meaning you'll get an m3u even for single disc games (this is by design, and single disc m3us work just fine, but they aren't necessary. I like just all my games to have the same extension in launchbox). Alternately, you can just create a single folder for all multidisc games manually and leave the single disc games out of that directory while running the batch. Let me know if you have any questions. Lastly, as is, this works with cue files only. However, under the Support section another user and myself figured out how to make it work for CHDs.

A few ways. 1: Right click the game in LB, click "Edit" and then go to the Additional Apps tab. There you can set which version launches when clicked. 2: set up m3u files and import those instead of the roms for multidisc games.

I don't know if Launchbox can sort through this but some sets, like a Tosec set, zip up multiple versions of the rom in each zip. I recommend unzipping SNES anyway as it takes up no space, but open one of the roms in 7z and see if there is just one file in there or many. If there's multiple files I don't think the launchbox unzip feature will work. Edit: If you can't manually open any of the files in 7zip that usually means you didn't download the full files and will need to replace the set.

Launchbox is designed to automatically resume the download task even after reopening, as you're finding out. I don't know of any setting to turn that off. Looks like you loaded up a big chunck of games (9000) so as far as I know your best bet is to hit cancel and try to wait until it can fully cancel.