fromlostdays

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.

Confirmed. That's wild.

Steam hasn't updated yet for me I guess, for whatever reason, and SteamLauncher is still working fine for me. But, there is an option in the SteamLauncher settings under the Misc tab to update the vtables. Not sure if it works or not as I can't test it, but its worth trying.

Why are you downloading zips of anything? Just grab the exe installer: https://github.com/thebezelproject/BezelProject-Windows/releases